[00:43] jethrogb: #ubuntu-packaging is more appropriate [00:58] dobey: thanks, ill try it there [00:58] although i think ive mostly figured it out [07:48] What's up with the PPA buildds? I have uploaded a package yesterday and it still needs ~8 hourse before it gets build? [07:48] the build farm was moved, so it has been offline for a few days [07:48] We still don't have all the builders back after the DC move last weekend [07:48] so it's still catching up on the build log [07:48] The queue's about half the length it was yesterday [07:49] If you have some builds you particularly care about, they can probably jump the queue a bit :) [07:50] btw is seems the i386 queue is much more congested, I guess this is because all arch builds are done on i386? [07:50] pmjdebruijn: Right [07:50] wgrant: I am waiting for build 3734327 and 3734333. Thanks. [07:51] btw [07:51] * pmjdebruijn loves the PPAs [07:51] wgrant: thanks for your great work [07:52] (well and the rest of the launchpad team) [07:52] blueyed: Should start in a couple of minutes [07:52] pmjdebruijn: Thanks :) [07:53] Hopefully the queues will clear in the next day or two === mthaddon` is now known as mthaddon [07:54] wgrant: I used to host my own repo, without superclean builds and signed packages [07:55] the PPAs were quite the leap forward :) [07:59] Yeah, they make that all a tonne easier. === czajkowski changed the topic of #launchpad to: Build delays due to hardware move | Help contact: czajkowski | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad [08:03] blueyed: Those are built [08:40] Hi. I'm following instructions at https://help.launchpad.net/Packaging/UploadErrors for the 'File already exists in ' error. It mentions: 'note that there is no need to include the original tarball in the upload, a reference to the right file will suffice' <- how do I do that? To begin with, I only did debuild and dput. [08:59] Anyone got an idea on this: [08:59] bzr: ERROR: http://bazaar.launchpad.net/~percona-core/percona-server/5.6/.bzr/repository/packs/a1849bf089d97de2c75cd97f17f4998e.pack is redirected to https://launchpad.net [08:59] $ bzr branch lp:percona-server/5.6 /home/jenkins/workspace/percona-server-5.6-trunk [08:59] You have not informed bzr of your Launchpad ID, and you must do this to [08:59] write to Launchpad or access private data. See "bzr help launchpad-login". [08:59] bzr: ERROR: http://bazaar.launchpad.net/~percona-core/percona-server/5.6/.bzr/repository/packs/a1849bf089d97de2c75cd97f17f4998e.pack is redirected to https://launchpad.net [08:59] czajkowski, ^ ? [08:59] czajkowski, this seems pretty consistent. [09:01] basically... are now *two* of our bzr repos in some way corrupt [09:02] if I curl that url, it's not a redirect [09:02] huh. [09:02] what happens if you log in and use bzr+ssh rather than http? [09:03] mgz, this is on jenkins slaves, which will never do bzr+ssh [09:03] ...but does it work? [09:03] trying locally... [09:03] bzr+ssh would work, yes [09:03] That HTTP thing was transient [09:03] okay... so if i try again it should work? [09:03] you could get your bot to do bzr+ssh by the way, some of ours do [09:04] stewart: Yeah, it should work [09:04] mgz, even without launchpad login? [09:04] generally you create an account and generate an ssh key for it, then put that on the machine with the conf [09:05] we'd end up having a garbage account though... which wouldn't be ideal. just another place for compromise to occur :/ [09:09] stewart: sorry wasnt looking at irc, I see mgz is helping and will know more anyways [09:13] hoping it works. kinda takes a while when you have a several hundred MB repo [09:31] stewart: If you're using http access currently, the machine pseudo-account doesn't need any specific privileges at all - so there's no compromise risk [09:33] What does this exactly mean: Rejected: mudlet_2.0-rc13.dsc: Version older than that in the archive. 2.0-rc13 <= 2.0-rc12-2.1ubuntu2 <- no, it's not older, it's *newer* [09:33] vadi2: ah, I see what's happening [09:33] vadi2: Nope, it's older [09:33] vadi2: The upstream version is everything before the final - [09:34] So I should try 2.0-rc12-3 ? [09:34] So it's (2.0, rc13) vs (2.0-rc12, 2.1ubuntu2) [09:34] Right, you'll need another hyphen [09:34] With anything at all after it [09:34] Or nothing, if you want to be strange [09:35] Alright, thanks! [09:35] vadi2: See http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version for details of how versions are interpreted [09:35] And considuer using dpkg --compare-versions to check [09:42] What affects the naming of the resulting dsc file? [09:42] It unfortunately got re-made as "mudlet_2.0-rc13" again. [09:43] Ah, probably the changelog file [10:36] Hi, is launchpad slower than usual? I created https://code.launchpad.net/~aacid/unity-greeter/no_servers_configured/+merge/120736 30 min ago and the diff is still not updated while usually takes no more than 5 mins [10:38] tsdgeos_: there seems to be some delays [10:38] ok, no problem, just reporting in case something was broken [10:39] if it's just "slower" no biggie [10:39] they are looking into it [10:42] my diff just appeared :-) === yofel_ is now known as yofel === Quintasan_ is now known as Quintasan [11:32] Hi, When I execute `bzr branch lp:ubuntu/precise/totem`, it returns "bzr: ERROR: Revision {package-import@ubuntu.com-20120109161939-wfwd46cy3ytl1qq3} not present in "Graph(StackedParentsProvider(bzrlib.repository._LazyListJoin(([CachingParentsProvider(None)], []))))".". [11:34] let's stick to #bzr for that [12:10] Hello. I have a package with version 1.0ubuntu1-0~22~oneiric1. I tried to upload a new package with version 1.0~5~22~201208221205~oneiric1m but launchpad says the latter version is "older"! How can I fix this? [12:14] that's a lot of tildes. [12:14] KNRO_: see the log from earlier today which covered just this question: [12:15] [12:18] so if I add a hyped 1.0-5 it will be newer than 1.0ubuntu1 ? [12:18] the 1.0ubuntu1 was a mistake at any rate, I forgot the hyper between the 1.0 and ubuntu1, and it seems I'm stuck now with this [12:18] hyphen lol [12:24] so it seems that debupstream 1.0ubuntu1 > 1.0 and this is where it fails [12:28] This is the changelog for the package: http://bazaar.launchpad.net/~mutlaqja/libindi/packaging/view/head:/indi-gphoto/changelog [12:29] isn't the debupstream supposed to be 1.0-ubuntu2? [12:31] The upstream version is the version with the last hyphen-separated segment removed [12:31] So, no [12:32] so just 1.0 in this case? [12:32] yes [12:33] so how do I make this newer than the one in archive 1.0ubuntu1 ? [12:33] other than making it 1.1 ! [12:33] 1.0.0 would work [12:34] Because . is newer than u [12:34] hmm okay thanks I'll give that a try [12:35] That or 1.0z or 1.0+ or something like that [12:56] well, I tried using deb-version {debupstream}~{revno}~{time} [12:56] is there something wrong with using that deb-version? [12:58] I'm getting this log: bzr: ERROR: bzrlib.errors.BzrCommandError: Invalid deb-version: {debupstream}~22~201208221247~oneiric1: Could not parse version: {debupstream}~22~201208221247~oneiric1 [13:01] {debupstream}+r{revno}-{revno:packaging} is what i use for my "daily" builds recipes [13:01] KNRO_: what bzr-builder format version are you using? [13:03] 0.4 [13:03] I'll use your suggestion! [13:03] hrmm [13:10] http access to bazaar.launchpad.net are very slow, what's happening? [13:27] mgedmin: hey they are looking into that at present [13:29] czajkowski, awesome! [13:35] KNRO_, if thats a raw error from the logs, doesn't that imply debupstream was not subbed in [14:03] bzr branches access over http seems to be back [14:05] mgedmin: Yeah, should be back to normal now. Our apache rewritemap script ran into some trouble, and apache likes to wait around even for requests that don't actually need it. === jibel__ is now known as jibel === cody-somerville_ is now known as cody-somerville === cody-somerville_ is now known as cody-somerville [15:49] You do still need to increment version numbers on deleted published packages from a PPA, right? [15:49] wgrant: ^? [15:49] Daviey: Yes [15:49] wgrant: thought so, thanks. [16:27] is there any reason why launchpad would say a branch is empty yet I can perfectly branch it? [16:28] mandel: if the branch scanner missed it in the datacentre futzing [16:29] generally pushing a new rev to the branch makes the scanner wake up and realise the branch is populated [16:29] mgz, ok, I'll do that to see what happens, thx === czajkowski changed the topic of #launchpad to: Build delays due to hardware move | Help contact:-| Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad === svuorela_ is now known as svuorela [17:44] hi. our repository on launchpad is apparently corrupted. what could we do? [17:44] $ bzr branch lp:maria/5.1 foo [17:44] bzr: ERROR: No such file: '/srv/bazaar.launchpad.net/mirrors/00/05/62/51/.bzr/repository/indices/b658cec5bdb393a80d29dc93e9c94ea3.rix' [17:54] i take it PPAs cannot hold Maverick or EOL-release packages? [17:54] (anymore) [17:55] TheLordOfTime: can't build new packages for them at least [17:55] PPAs with old maverick packages will still publish them right? [17:55] but no new ones can be built [17:55] ? [17:56] i think previously built/published packages hang around, but you can't build new [17:57] at least, i have a ppa that seems to still have jaunty/intrepid/karmic/maverick packages in it [17:57] lol [17:57] i probably have a PPA with packages in it like that :P [17:57] (in which case those PPAs must die) [17:58] ...launchpad likes scaring me with timeouts on the bounceback to mp page after I've done a really long comment [18:00] bounceback loses the page you were just editing, but does appear to mean the comment did get registered [18:05] LP times out pretty often [18:05] randomly too [18:06] I have problems with all the branches I push, I just pushed 3of them and lp states that the 3 of them are empty.. which is blocking some code from landing to trunk [18:08] mandel: pushes fresh from today? [18:08] mgz, yes, a few mins ago, max an hour ago [18:10] okay, that needs some action then [18:10] mgz, one of the branches is for example: lp:~mandel/ubuntuone-control-panel/fix-1019224 pushed 2 hours ago [18:11] mgz, and lp:~mandel/ubuntuone-control-panel/left-tabs has the same code pushed a few mins ago [18:11] the one from three hours ago seems to have worked though [18:11] so it may just be horrid lag, fallout from the datacentre move [18:14] mandel: so, apparently it's just being slow due to a backlog [18:15] mgz, ok, if you need more info let me know in the internal channel or here :) === zyga is now known as zyga-afk [18:19] Is anyone else having a problem looking at bzr branches in LP? [18:20] yes, depending on what exactly you mean. [18:20] It's very slow and/or timing out for me. Other parts of LP I am seeing fine === jussio1 is now known as jussi [18:23] codehosting is little more unhappy than normal right now. === czajkowski changed the topic of #launchpad to: Delays due to codehosting, it's being looked into| Help contact:-| Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad === czajkowski changed the topic of #launchpad to: Delays due to codehosting, due to backlog| Help contact:-| Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad [18:29] Thanks mgz, czajkowski [18:31] <--- vanishing [18:41] if i uploaded a native source packages with an omission in the control file that makes the build fail, how do i upload a new version of that package? [18:42] I get "Rejected: File hybrid-screenclone_20120821.0.tar.gz already exists in Jethro's packages, but uploaded version has different contents." === thomi_ is now known as thomi === zyga-afk is now known as zyga === Logan_ is now known as Chamserw === Chamserw is now known as Logan_ === Logan_ is now known as Logan === Logan is now known as Fluffernutter === Fluffernutter is now known as l === \u03b5 is now known as Guest73127 === dan64 is now known as Guest14436 === jelmer is now known as Guest73241 === dpb_ is now known as Guest92976 === jpds is now known as Guest81255 === jussi is now known as Guest83481 === jibel_ is now known as jibel [21:29] Hi, I am trying to do a bzr push, and I am wondering if I am not getting bzr to recognize my ssh keys. I have bzr launchpad-login marco-parillo, which is my launchpad id. [21:30] And I do have a ssh key set in launchapd. === Guest73241 is now known as jelmer === wgrant changed the topic of #launchpad to: Help contact: - | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad [23:59] Hi all, I have some automated jobs that run some 'bzr export' commands after a fresh install [23:59] twice just now I've received and error, both to do with the http access method