[01:04] <Fujitsu> lamont: Looks like you could have hppa finished for Christmas.
[01:04] <lamont> Fujitsu: queue is empty, it wants a full give-back of the anything not buit
[01:05] <Fujitsu> That's what I was meaning.
[01:05] <Fujitsu> 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] <lamont> cool
[01:19] <Rinchen> hppa is always empty lamont  ;-)
[01:43] <gspr> 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] <Fujitsu> There are other ways to do it, but they are nasty, improper and confusing, so won't be mentioned here.
[01:44] <Fujitsu> And they might not even work.
[01:44] <gspr> heh, ok
[01:45] <gspr> I'm just looking to do things the right way
[01:45] <gspr> and I'm a bit confused: What decides which distribution version a package is built for?
[01:45] <gspr> I always thought it was the distribution field in the changelog
[01:45] <gspr> 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] <Fujitsu> It is the distribution field in the .changes, which is derived from that in the changelog.
[01:46] <Fujitsu> Right, the .changes are specially generated for syncs, or they're overridden internally.
[01:46] <gspr> yeah OK
[01:47] <Fujitsu> PPA has the suite override feature which allows you to do similar things.
[01:47] <Fujitsu> (add a /hardy or whatever to the upload URL, and the package will go to hardy)
[01:47] <gspr> 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] <gspr> oh, right
[01:47] <gspr> that's nice
[01:47] <Fujitsu> A changelog entry is better.
[01:48] <Rinchen> I'm off... have a happy next week folks
[01:48] <Fujitsu> You too, Rinchen.
[01:48] <gspr> 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] <gspr> if every import should be given a changelog entry
[01:49] <Fujitsu> We don't change the version, as ours are official packages.
[01:50] <gspr> ok
[01:50] <gspr> thanks for the help
[01:50] <Fujitsu> 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] <gspr> yeah
[12:11] <poeloq> re
[12:29] <Hobbsee> i think soyuz exploded.
[12:29] <Hobbsee> does someone have root access to the buildds?
[12:30] <Fujitsu> Hobbsee: Why?
[12:30] <Hobbsee> 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] <Hobbsee> i'm not sure if they attempted to build, but failed due to deps, every 40 seconds...
[12:31] <Fujitsu> Which 500 and when?
[12:31] <Hobbsee> well, there were a whole stack for hppa
[12:31] <Hobbsee> just a couple of days ago
[12:31] <Fujitsu> They're done.
[12:31] <Hobbsee> they are?
[12:31] <Hobbsee> Fujitsu: and http://launchpadlibrarian.net/11030532/buildlog_ubuntu-hardy-i386.rhythmbox_0.11.4-0ubuntu1_FAILEDTOBUILD.txt.gz ?
[12:31] <Fujitsu> I'm not sure how, but they're legitimately out of pending.
[12:32] <Fujitsu> Hobbsee: GNOME was broken for a while, perhaps.
[12:32] <Fujitsu> That's a fairly normal failure.
[12:32] <Hobbsee> Totals by arch:
[12:32] <Hobbsee>     * sparc:612
[12:32] <Hobbsee>     * i386:627
[12:32] <Hobbsee>     * amd64:623 
[12:32] <Hobbsee> ah, yup, you're right
[12:32] <Hobbsee> (main, failed to install packages)
[12:32] <Fujitsu> Failed to build?
[12:33] <Hobbsee> no, no, install
[12:33] <Fujitsu> Where?
[12:33] <Hobbsee> exploded the day after release, too.  heh
[12:33] <Hobbsee> http://people.ubuntu.com/~ubuntu-archive/testing/hardy_probs.html
[12:33] <Fujitsu> Ah.
[12:35] <Fujitsu> 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] <Hobbsee> ah, good
[12:38] <Fujitsu> So yes, Soyuz had its usual fatal bug just before release of a milestone, but it got fixed quickly :)
[12:38] <Hobbsee> no, i didn't think they could all build that quick.
[12:41] <Fujitsu> I think it's broken because esound-common has gone away.
[12:41] <Fujitsu> Yes, that's it.
[12:41] <Fujitsu> That will have broken... a lot.
[12:43] <Fujitsu> ... it got demoted, then repromoted 3 hours later.
[12:44] <Hobbsee> neat!
[12:45] <Fujitsu> The esound-common binary seems to not exist in the archive.
[12:48] <Hobbsee> Fujitsu: soyuz probably got hungry.
[13:20] <ubotu> New bug: #178102 in soyuz "(Quick) promotion and demotion can lose binaries" [Undecided,New] https://launchpad.net/bugs/178102
[13:50] <ubotu> New bug: #178107 in rosetta "Translation download requests not fulfilled" [Undecided,New] https://launchpad.net/bugs/178107
[13:50] <Fujitsu> Dupe.
[17:46] <kiko> shalom
[17:46] <kiko> how is everybody
[17:47] <kiko> kinda quiet I can see :)