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