[01:45] um i'm confused [01:45] i uploaded golang-1.6_1.6-0ubuntu3_source.changes a while ago but it seems to have disappeared [01:45] about 25 mins ago i think [02:01] mwhudson: I see one in the unapproved queue that arrived 9 minutes after your last comment [02:01] slangasek: yes, that's the one that arrived when i just gave up waiting and tried again :/ [02:03] ok [02:06] slangasek: should the bot that auto accepts non-seeded uploads still be running? [02:06] mwhudson: yes, it should [02:18] ah there it is [02:21] golang doesn't get auto-accepted as it's in the supported seed [02:21] I manually reviewed it [02:22] slangasek: if you have a minute, can you review that lxc upload? [02:23] stgraber: yeah... and I guess you just accepted squid3, which is buggy [02:23] queue needs proper locking. :P [02:25] there a bunch of things the LP queue implementation needs before locking :) [02:26] *are [02:26] stgraber: oh ok [02:26] stgraber: thanks [02:30] slangasek: I'm taking a look at maas [02:31] stgraber: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/comments/26 [02:31] Launchpad bug 1473691 in squid3 (Ubuntu) "[FFe] squid: Update to latest upstream release (3.5)" [Critical,Fix committed] [02:35] slangasek: shouldn't the new squid package preinst also nuke the old /etc/init.d/squid3 as it does the upstart job? [02:42] stgraber: yes, it probably should [02:42] but it doesn't, so that upload is buggy [02:44] stgraber: alright, this lxc upload doesn't look like something that wants me to do a line-by-line review on it. Is this bugfix only? what upstream testing has been done? [02:47] slangasek: bugfix only ran through all of adt upstream as we do for every commit, has been in our ppa (as a git snapshot) for a few days [02:47] and yeah, those rcs are bugfix only [02:47] stgraber: ok, approved on the grounds that there are no /obvious/ bugs [02:48] yeah, that's been the case for the past 13 rcs, hopefully we'll soon be done catching the non-obvious ones :) [02:51] slangasek: ^ revert of previous upload + added conffile removal for /etc/init.d/squid3 [02:57] stgraber: dpkg-maintscript-helper has bits that are supposed to be called from other scripts besides the preinst; see the postinst and postrm [02:57] ...which is a lot easier to keep track of if the maintainer were using .maintscript instead of trying to do this by hand [03:01] wow, wtf, that's not going to be fragile at all [03:04] grep tells me I've got the same number of those as there was for squid3.conf, that's about as much testing as this got [03:04] heh [08:06] hi release team - for some reason I thought I had already raised a FFe for the next Ceph stable release runup for 16.04 [08:06] https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1563714 [08:06] Launchpad bug 1563714 in ceph (Ubuntu) "[FFe] Ceph Jewel stable release" [Undecided,New] [08:06] apparently not so here it is.... === s8321414_ is now known as s8321414 === s8321414_ is now known as s8321414 [12:02] infinity, pitti approved the FFE in bug #1558535. Could you also accept linux-snapdragon (and -meta) in the NEW queue ? [12:02] bug 1558535 in Ubuntu "FFE: linux-snapdragon" [Undecided,Triaged] https://launchpad.net/bugs/1558535 [12:08] rtg, done [12:08] doko, thanks [12:18] cjwatson, infinity: what can we do about the migration of gcc-5-cross-ports / gcc-defaults-ports. gcc-5-cross-ports isn't mentioned in update_excuses at all [12:19] will have to leave that question to somebody else, sorry === arges_ is now known as arges [12:59] doko: mind rejecting conjure, i need to update it from the results around the juju discussions [13:00] stokachu, done [13:00] doko: thanks man [16:33] doko: Did you review that new kernel you accepted at all? [16:57] infinity, only from a packaging point of view [16:59] doko: A license review tends to be a good thing on BSP kernels like that. [16:59] (it's not all upstream code from Linus's tree) [16:59] * infinity grabs it to do a quick once-over. [17:12] rtg: Alright, did a post-accept license review of linux-snapdragon, all looks sane. [17:38] infinity: mind if I poke/bother you about nginx for a bit, off-channel in PM, surrounding FinalFreeze? [17:39] s/surrounding/regarding/ [18:12] i wonder how bad is it that germinate says [18:12] ? Missing source package: golang (for golang-github-gosexy-gettext-dev) [18:12] ? Missing source package: golang (for golang-dbus-dev) [18:12] ? Missing source package: golang (for golang-github-coreos-go-systemd-dev) [18:12] ? Missing source package: golang (for golang-github-pborman-uuid-dev) [18:12] ? Missing source package: golang (for golang-gopkg-tomb.v2-dev) [18:12] ? Missing source package: golang (for golang-github-gorilla-mux-dev) [18:13] xnox: Those should all be rebuilt against golang-1.6 [18:13] If we're about to start enforcing Built-Using. [18:14] ah [18:14] so this is legit =) [18:14] Oh. This is also broken. :( [18:14] * xnox is like surely golang is not gone [18:14] mwhudson: I found some lolz. [18:15] (base)adconrad@nosferatu:/var/lib/apt/lists$ grep '^Built-Using: golang ' *Packages | wc -l [18:15] 357 [18:15] (base)adconrad@nosferatu:/var/lib/apt/lists$ grep '^Built-Using: golang-1.6 ' *Packages | wc -l [18:15] 0 [18:15] (base)adconrad@nosferatu:/var/lib/apt/lists$ grep '^Built-Using: golang-defaults ' *Packages | wc -l [18:15] 12 [18:16] mwhudson: Note that last one. I'm guessing there's something that does a Package->Source resolution for "golang-go" and fills in the wrong bits, when it should actually be hunting down the compiler used (golang-1.6 or gccgo-6) [18:18] xnox: Anyhow, rebuilding all of those would probably turn "golang" into "golang-defaults" which, for the purpose of component-mismatches, will DTRT. It's less ideal for actually tracking static compiling, though, and should be as above. :P [18:35] xnox,infinity: incidentally, per our conversation the other day, I realised that we also need to check for cases where sources in main b-d on virtual packages without a preferred real alternative, since those could end up being resolved differently [19:55] does openstack still has a freeze exception? [19:56] yes. [19:56] doko: ^ [19:56] ta [19:58] infinity: any chance you can review nginx (bug #1563393) for a freeze exception? We're in the home stretch - keeping us as close to what upstream has for 1.10.x is still the goal. which also reminds me, do you have any issues with me bouncing a couple of questions off you regarding nginx as we approach the final stretches of development? (I'm keeping an eye on that FinalFreeze date, hence the need for a discussion) [19:58] bug 1563393 in nginx (Ubuntu) "[FreezeException Needed] Update nginx to 1.9.13." [Wishlist,New] https://launchpad.net/bugs/1563393 [19:58] the discussion is more important than ^ that getting a review today, though [19:59] teward: Discuss away. I'm only doing IRC in small batches while I try to ignore blinky things to get other work done, but I'll get to you. [19:59] infinity: OK, the discussion has to occur off-channel, though, mind a PM for that? [19:59] given the info being shared [19:59] (E:NotForChannel) [20:05] infinity: ah haha [20:05] infinity: file a bug? [20:05] mwhudson: Is that not what I did, via the IRC interface? :P [20:05] heh [20:06] mwhudson/api/v1/filebug [20:06] (Internet RESTful Chat) [20:07] heh [20:07] i wonder what package the bug should be against... [20:07] mwhudson: Guessing dh-golang is where the magic happens. [20:08] mwhudson: And it probably just needs to dereference paths before doing the file->package->source resolution. [20:08] (Assuming it's checking the owner of /usr/bin/go and such) [20:08] wondering if mozc should be accepted ... we still have a very old version ... [20:08] https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1547816 [20:08] Launchpad bug 1547816 in mozc (Debian) "Merge mozc (2.17.2116.102+gitfd0f5b34+dfsg-1) from Debian unstable (main)" [Unknown,New] [21:40] infinity: got an example of a package that has broken built-using? [21:41] uh i guess lxd probably [21:44] yeah [21:48] infinity, thanks, re: linux-snapdragon === s8321414_ is now known as s8321414