[12:48] <doko> Laney, are you able to setup a transition tracker?
[12:56] <Laney> doko: Yes, ~ubuntu-transition-trackers is the relevant team.
[12:57] <doko> Laney, for libstdc++6 (not yet starting, but I would like to get an idea ...) I assume the goal would be dependencies on libstdc++6 (>= 5)
[12:59] <Laney> doko: Could you supply a .ben file please? lp:~ubuntu-transition-trackers/ubuntu-transition-tracker/configs has examples
[13:01] <doko> Laney, how can I test ben files?
[13:02] <Laney> you can set ben up locally (it's in the archive), or we can iterate on the running installation
[13:02] <doko> hmm, can't find an example which uses versions ...
[13:04] <Laney> http://people.canonical.com/~ubuntu-archive/transitions/html/r-base.html ?
[13:07] <doko> how do I write libstdc++6 without version information, just add a $?
[13:09] <doko> Laney: http://paste.ubuntu.com/11804485/
[13:11] <cjwatson> ($|,) IIRC
[13:11] <cjwatson> You need to escape the literal () there
[13:11] <doko> yep, http://paste.ubuntu.com/11804499/
[13:12] <cjwatson> And the .*) or .*\) is kinda pointless, that just asserts lack of syntax error :)
[13:13] <doko> http://paste.ubuntu.com/11804509/
[13:17] <Laney> doko: cjwatson: lunch calls, feel free to push it
[13:19] <doko> not a member
[13:21] <cjwatson> doko,Laney: committed
[13:21] <doko> thanks. when will it show up?
[13:21] <cjwatson> next run
[13:21] <cjwatson> should be under half an hour or so
[13:22] <cjwatson> probably less, it's already 10min since the last run
[13:48] <rbasak> How do I go about getting an answer from the release team about nginx? And is this something that is within the mandate of the relese team or does it need to go to the TB?
[13:53] <doko> cjwatson, Laney: can I add exclusions for packages where I know they are not needed?
[14:05] <cjwatson> doko: You can add .package conditions to is_good, I suppose, or just ignore them
[14:05] <cjwatson> doko: http://ben.debian.net/#_query_language
[14:18] <Laney> That r-base one has exclusions
[14:21] <cjwatson> oh yeah, is_affected is a better place to put them
[15:20] <doko> please could somebody accept the cross toolchain updates for trusty? just building from the sources of the accepted binutils and gcc-4.8 packages
[15:20] <doko> please could somebody look at python3 for trusty?
[15:52] <sil2100> Hello release team! I'm looking for an archive admin to ACK the renamed binary packages due to the API/ABI bump
[15:53] <sil2100> https://ci-train.ubuntu.com/job/ubuntu-landing-013-2-publish/62/artifact/platform-api_packaging_changes.diff
[16:15] <sil2100> slangasek, infinity: ^ (sorry for the direct ping)
[16:16] <slangasek> sil2100: would prefer a pointer to the silo, not the raw diff
[16:16] <slangasek> s/silo/dashboard entry/
[16:17] <sil2100> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-013 <- here's the silo PPA for instance
[16:17] <sil2100> http://people.canonical.com/~platform/citrain_dashboard/#?q=ubuntu%2Flanding-013
[16:17] <sil2100> Dashboard entry
[16:19] <slangasek> sil2100: jenkins shows packaging_changes diffs for 5 packages in that silo, have the others already been signed off?
[16:20] <sil2100> slangasek: yes, I checked those, they're sane and for packages in the universe, mostly those changes are for the bump
[16:20] <slangasek> ok
[16:21] <slangasek> heh, somebody should clean up the dummy transitional packages in there
[16:27] <slangasek> sil2100: acked, publishing
[16:28] <sil2100> Thanks! :)
[20:20] <slangasek> RAOF: it looks like you accepted shim-signed into precise-proposed yesterday?  there's a shim sync that needs to go with that (and shim and shim-signed syncs for all the other releases)
[23:23] <RAOF> slangasek: Ok. I accepted shim-signed into precise-proposed because it wasn't documented as requiring shim, and it had an obvious bug and way of tracking it. How are we tracking the shim sync (and the shim-signed syncs for other releases)?