[07:46] <cjwatson> jtaylor: It's not the arm64 compiler, it's the machines it's running on
[07:46] <cjwatson> jtaylor: birch usually does better
[07:46] <cjwatson> jtaylor: And indeed, you don't need to massively care yet ...
[07:47] <cjwatson> jtaylor: Until we have more reliable machines across the board, we're just bulk-retrying that kind of thing
[15:46] <xevwork> ScottK, Laney, tumbleweed: I'm looking at a discussion you had in April 2012 regarding pbuilder and "Distribution data outdated." Here's the transcript: http://irclogs.ubuntu.com/2012/04/26/%23ubuntu-motu.txt
[15:47] <xevwork> ScottK, Laney, tumbleweed: I use cowbuilder-dist on precise and it just recently stopped working.
[15:47] <tumbleweed> xevwork: bug 1241673
[15:48] <ScottK> xevwork: I stand by my comment that the distro-info design is broken.
[15:49] <xevwork> Well, I certainly wasn't expecting new releases to break pbuilder.
[15:49] <tumbleweed> yeah, you have to use it very carefully, to not crash when we don't have a current name
[15:49] <tumbleweed> ScottK: minor improvements in design would help a lot
[15:50] <xevwork> Is there a workaround I can put in place to get my package builds working again?
[15:50] <tumbleweed> xevwork: what release are you on?
[15:51] <xevwork> This is on precise.
[15:51] <tumbleweed> xevwork: there should be a new version of distro-info-data published in precise-proposed, in a few minutes
[15:51] <tumbleweed> I just uploaded it, waiting for it to be approved
[15:51]  * ScottK is processing the SRUs now.
[15:51] <tumbleweed> thanks ScottK
[15:51] <xevwork> Excellent. Thanks!
[15:53] <ScottK> tumbleweed: You forgot the maintainer change in precise.
[15:53] <tumbleweed> ScottK: it was already done
[15:53] <ScottK> Oh.
[15:54] <ScottK> That's what I get for looking at diffs.  Thanks.
[15:54] <tumbleweed> :)
[15:55] <tumbleweed> xevwork: you should see a deb here soon https://launchpad.net/ubuntu/+source/distro-info-data/0.8ubuntu0.5/+build/5114419
[15:58] <tumbleweed> there, built
[15:58] <tumbleweed> ScottK: I'll verify those when they're published
[16:16] <xevwork> tumbleweed: Thanks a lot! I'll test it after I have some lunch.
[18:15] <xevwork> tumbleweed: I just verified that it fixed the issue for me and commented on the ticket.
[18:15] <tumbleweed> thanks
[18:16] <xevwork> Thank you guys. That was a swift resolution.
[18:19] <xevwork> Judging by what I read, it seems like this has been a recurring issue.
[18:19] <xevwork> I'll poke through the code and see if I can come up with ideas for how to improve the system.
[18:19] <tumbleweed> yes. distro-info assumed that we'd know release names in advance
[18:20] <tumbleweed> that was true once upon a time, but sabdfl seems a bit busy, these days
[18:21] <xevwork> What was true once upon a time?
[18:22] <xevwork> Is there any high level documentation of the whole system and any interactions that may not be obvious?
[18:23] <tumbleweed> I think the things required are:
[18:25] <tumbleweed> add an optional parameter like outofdate='stale' (defaulting to 'error')
[18:25] <tumbleweed> teach distro-info about the new 'devel' symlink
[18:27] <xevwork> I'll see if I have some time to check it out this weekend. Probably won't be until next weekend, though.
[18:27] <tumbleweed> add a function that'll tell you if a release is stable / devel, so that one doesn't need things like https://bazaar.launchpad.net/~ubuntu-dev/ubuntu-dev-tools/trunk/view/head:/pbuilder-dist#L292
[18:28] <tumbleweed> for your case of pbuilder, it's already fixed by adding that try...except, but that's a bit ick
[20:42] <ScottK> tumbleweed: It's broken that building for an existing release that distro-info knows all about is at all affected by the lack of a devel release.
[20:45] <xnox> Laney: the transition tracker's go and the mirror bits need to learn about trusty.
[20:45] <xnox> =)
[20:46] <xnox> i'd commit to update it, but those scripts are not part of the branch it seems.
[20:53] <tumbleweed> ScottK: we fixed that post precise
[20:54] <ScottK> tumbleweed: Then let's fix it for precise too.  Once the current SRU is in, I'd accept such a change for a subsequent SRU.
[20:55] <ScottK> It still raises a warning, which is nonesense, but it less harmful than it was before.
[21:07] <tumbleweed> yeah, that's due to a poor API
[21:28] <stgraber> I: 01launchpad-chroot: [saucy-armhf-sbuild] Processing config
[21:29] <stgraber> I: 01launchpad-chroot: [saucy-armhf-sbuild] Downloading new Launchpad chroot.
[21:29] <stgraber> ^ love that hook! Looking forward to pushing a package version of it to trusty
[21:30] <stgraber> (sbuild hook that makes it use Launchpad chroots instead of a locally debootstrapped chroot, the package also contains apw's hook to support the various combinations of pockets and components)
[21:30] <stgraber> pretty much as close to a LP build as you can get locally
[21:32] <tumbleweed> stgraber: hrm, that sounds useful
[21:32] <tumbleweed> except for downloading massive chroots, that sonuds painful
[21:33] <stgraber> tumbleweed: well, it only re-downloads if it changed which doesn't happen terribly often