[01:04] lamont: Looks like you could have hppa finished for Christmas. [01:04] Fujitsu: queue is empty, it wants a full give-back of the anything not buit [01:05] That's what I was meaning. [01:05] That's a few hundred, IIRC. [01:05] * Fujitsu has confirmed that LP isn't being stupid about the empty queue - all the stuff that is marked as superseded is, in fact, superseded. [01:07] cool [01:19] hppa is always empty lamont ;-) [01:43] If I build a package for my PPA, I, like most people, find it convenient to add a ~ppaX to the package version. Can I do this without changing the changelog? It happens that I just grab a debian or hardy package and don't make any changes. Not that changing the changelog is a problem, but it sounds like the wrong way to do it [01:43] There are other ways to do it, but they are nasty, improper and confusing, so won't be mentioned here. [01:44] And they might not even work. [01:44] heh, ok [01:45] I'm just looking to do things the right way [01:45] and I'm a bit confused: What decides which distribution version a package is built for? [01:45] I always thought it was the distribution field in the changelog [01:45] but that would mean the changelog had to be changed for every package simply imported from debian, and that doesn't seem to be the case [01:45] It is the distribution field in the .changes, which is derived from that in the changelog. [01:46] Right, the .changes are specially generated for syncs, or they're overridden internally. [01:46] yeah OK [01:47] PPA has the suite override feature which allows you to do similar things. [01:47] (add a /hardy or whatever to the upload URL, and the package will go to hardy) [01:47] so, not that it matters, but let's say I pull a package directly from debian and put it in my PPA. Should I make a changelog entry to change the version number to ~ppa1, or should I change the .changes? [01:47] oh, right [01:47] that's nice [01:47] A changelog entry is better. [01:48] I'm off... have a happy next week folks [01:48] You too, Rinchen. [01:48] Fujitsu: That's what I thought at first. Again, not that it matters, but wouldn't this mean that every single package in ubuntu would have an -ubuntuX version attached to it? [01:48] if every import should be given a changelog entry [01:49] We don't change the version, as ours are official packages. [01:50] ok [01:50] thanks for the help [01:50] You probably want to let your packages be upgraded to the official ones if they appear, so you need to make your version sort lower, by appending ~ppa1 or similar. [01:51] yeah === stu1 is now known as stub === elkbuntu_ is now known as elkbuntu === bigon is now known as bigon` === \sh_away is now known as \sh === \sh is now known as \sh_away === bluekuja_ is now known as bluekuja === \sh_away is now known as \sh === \sh is now known as \sh_away === bigon` is now known as bigon === \sh_away is now known as \sh === \sh is now known as \sh_away === Hobbsee_ is now known as Hobbsee === \sh_away is now known as \sh === \sh is now known as \sh_away === \sh_away is now known as \sh [12:11] re [12:29] i think soyuz exploded. [12:29] does someone have root access to the buildds? [12:30] Hobbsee: Why? [12:30] Fujitsu: because it appears that lots of stuff is failing, where it should be there, and we've suddenly lost about 500 needs-build [12:30] i'm not sure if they attempted to build, but failed due to deps, every 40 seconds... [12:31] Which 500 and when? [12:31] well, there were a whole stack for hppa [12:31] just a couple of days ago [12:31] They're done. [12:31] they are? [12:31] Fujitsu: and http://launchpadlibrarian.net/11030532/buildlog_ubuntu-hardy-i386.rhythmbox_0.11.4-0ubuntu1_FAILEDTOBUILD.txt.gz ? [12:31] I'm not sure how, but they're legitimately out of pending. [12:32] Hobbsee: GNOME was broken for a while, perhaps. [12:32] That's a fairly normal failure. [12:32] Totals by arch: [12:32] * sparc:612 [12:32] * i386:627 [12:32] * amd64:623 [12:32] ah, yup, you're right [12:32] (main, failed to install packages) [12:32] Failed to build? [12:33] no, no, install [12:33] Where? [12:33] exploded the day after release, too. heh [12:33] http://people.ubuntu.com/~ubuntu-archive/testing/hardy_probs.html [12:33] Ah. [12:35] hppa's queue was empty just after rollout due to a bug I filed, but that got fixed a few hours later, and they came back. They dissipated again after a couple of days, but a number of checks that I've performed say that they're now in other sane statuses. [12:35] ah, good [12:38] So yes, Soyuz had its usual fatal bug just before release of a milestone, but it got fixed quickly :) [12:38] no, i didn't think they could all build that quick. [12:41] I think it's broken because esound-common has gone away. [12:41] Yes, that's it. [12:41] That will have broken... a lot. [12:43] ... it got demoted, then repromoted 3 hours later. [12:44] neat! [12:45] The esound-common binary seems to not exist in the archive. [12:48] Fujitsu: soyuz probably got hungry. [13:20] New bug: #178102 in soyuz "(Quick) promotion and demotion can lose binaries" [Undecided,New] https://launchpad.net/bugs/178102 === \sh is now known as \sh_away [13:50] New bug: #178107 in rosetta "Translation download requests not fulfilled" [Undecided,New] https://launchpad.net/bugs/178107 [13:50] Dupe. === \sh_away is now known as \sh === bigon is now known as bigon` === bigon` is now known as bigon [17:46] shalom [17:46] how is everybody [17:47] kinda quiet I can see :) === \sh is now known as \sh_away