[00:47] <handsome_feng> Hi, Could someone in release team help to look into the ukwm in bionic new queue? It has been there for a long time. :( LP: #1740252
[00:47] <ubot5`> Launchpad bug 1740252 in Ubuntu Kylin "[FFe] ukwm" [Critical,In progress] https://launchpad.net/bugs/1740252
[01:26] <tsimonq2> slangasek: Could you look at ukwm when you have the chance? ^^^^^^
[03:40] <slangasek> tsimonq2, handsome_feng: yes, I'll make some time for ukwm tonight or tomorrow if no one beats me to it; sorry it's been stalled so long
[03:40] <tsimonq2> slangasek: Many thanks.
[03:41] <handsome_feng> tsimonq2, slangesek: Thanks very much!
[03:49] -queuebot:#ubuntu-release- Unapproved: akregator (artful-proposed/universe) [4:17.04.3-0ubuntu1 => 4:17.04.3-0ubuntu1.1] (kubuntu)
[03:56] <tsimonq2> Laney: Question regarding bug 1654761. I have the implementation for seeing if manually submitted URLs match running tests done, but my next step is doing the same with queued tests. I'm a bit unclear on how I can call get_queue_info() in webcontrol/request/submit.py ... should I import the function directly in webcontrol/request.cgi? I'm a bit lost on where the import goes.
[03:56] <ubot5`> bug 1654761 in Auto Package Testing "Make sure duplicate tests cannot be queued" [Undecided,In progress] https://launchpad.net/bugs/1654761
[03:56] <tsimonq2> BTW, my WIP code lives here: https://git.launchpad.net/~tsimonq2/autopkgtest-cloud/+git/bug-1654761
[05:32] <tsimonq2> But it says "should" so I have the ability to bump it without breaking policy.
[05:36] <krytarik> tsimonq2: Might want to repeat that in the channel it was intended for. :P
[05:39] <tsimonq2> krytarik: Er, yeah.
[05:39] <tsimonq2> krytarik: Thanks.
[05:40] <krytarik> No problem!
[05:40] <tsimonq2> (For the curious, I'm referring to the comment I'm about to make in bug 1752733.)
[05:40] <ubot5`> bug 1752733 in lxterminal (Ubuntu) "xiterm+thai is installed and set to x-terminal-emulator" [High,Triaged] https://launchpad.net/bugs/1752733
[07:36] -queuebot:#ubuntu-release- New binary: ruby-flipper [amd64] (bionic-proposed/none) [0.13.0-2] (no packageset)
[07:44] -queuebot:#ubuntu-release- New: accepted ruby-flipper [amd64] (bionic-proposed) [0.13.0-2]
[07:53] <estan> infinity: hey, c-blosc 1.14.2+ds1-1 now ready to be synced from unstable if you're up for it. it includes the fix for the ARM alignment debacle.
[07:56] <estan> (the important thing it brings is still of course the format compat bug fix: https://bugs.launchpad.net/ubuntu/+source/c-blosc/+bug/1755380)
[07:56] <ubot5`> Ubuntu bug 1755380 in c-blosc (Ubuntu) "[FFe] Please sync c-blosc 1.14.0+ds1-1 from debian unstable to bionic (1.11.1 has format incompat bug!)" [Undecided,Fix released]
[07:57] <tsimonq2> slangasek: Can you please process this? https://launchpad.net/bugs/173297n
[07:57] <ubot5`> Ubuntu bug 173297 in totem (Ubuntu) "after update XVID won" [Undecided,Fix released]
[07:57] <tsimonq2> er
[07:57] <tsimonq2> what
[07:57] <tsimonq2> https://launchpad.net/bugs/1732970
[07:57] <ubot5`> Ubuntu bug 1732970 in qtsystems-opensource-src (Ubuntu) "Remove cordova-ubuntu-3.4, qtfeedback-opensource-src, qtsystems-opensource-src from archive" [Undecided,New]
[07:57] <tsimonq2> That. :)
[08:16] <smb> slangasek, I am trying to fix some up (but since I cannot upload myself that always takes additional time). That other package we talked about here (tunneldigger). Question there is whether its worth fixing up
[08:43] <apw> smb, tunneldigger has already been removed
[08:43] <apw> smb, i think all of those are gone actually
[08:44] <smb> apw, ah ok, I probably should look at current britney
[08:51] <doko> apw: please ignore the linux autopkg tests on s390x. blocks binutils and gcc-*
[08:51] <doko> well, if appropriate
[08:51] <apw> doko, will look shortly
[09:23] <xnox> apw, it would be nice if the linux-azure kernel migrated from bionic-proposed -> bionic https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1749771 currently blocking foundations from building a full set of cloud images
[09:23] <ubot5`> Ubuntu bug 1749771 in Kernel Development Workflow "linux-azure: 4.15.0-1002.2 -proposed tracker" [Medium,In progress]
[09:23] <apw> xnox, indeed
[09:25] <doko> gcc-defaults-ports (1.173ubuntu1 to 1.174ubuntu3)
[09:25] <doko> Maintainer: Debian GCC Maintainers
[09:25] <doko> 0 days old
[09:25] <doko> missing build on ppc64el: cpp-powerpc-linux-gnu, g++-multilib-powerpc-linux-gnu, g++-powerpc-linux-gnu, gcc-multilib-powerpc-linux-gnu, gcc-powerpc-linux-gnu, gccgo-multilib-powerpc-linux-gnu, gccgo-powerpc-linux-gnu, gcj-powerpc-linux-gnu, gdc-multilib-powerpc-linux-gnu, gdc-powerpc-linux-gnu, gfortran-multilib-powerpc-linux-gnu, gfortran-powerpc-linux-gnu, gobjc++-multilib-powerpc-linux-gnu, gobjc++-powerpc-linux-gnu, gobjc-multilib-powerpc-
[09:25] <doko> linux-gnu, gobjc-powerpc-linux-gnu, pkg-config-powerpc-linux-gnu (from 1.173ubuntu1)
[09:25] <doko> Not considered
[09:25] <doko> because the powerpc packages are now built from the gcc-defaults source
[09:25] <doko> I mean, I could remove them in the release pocket, but that would temporarily break some build dependencies
[09:27] <apw> if gcc-defaults migrates first it will take over those binaries won't it ?
[09:27] <apw> then that one ought to be migratable safely
[09:30] <xnox> doko, that smells like it needs a britney hint, for the two to go together.
[09:30] <xnox> and to be considered together
[09:31] <apw> though it is considering there is no build so it won't consider it in that phase
[09:35] <LocutusOfBorg> hello folks, I have an issue, I introduced vbox-hwe packages to comply with new hwe stacks, now people are reporting that the hwe packages are not upgraded to bionic
[09:35] <LocutusOfBorg> how to solve? I mean, virtualbox-guest-x11-hwe should be changed to virtualbox-guest-x11 in the xenial/bionic move
[09:35] <LocutusOfBorg> but in the future, a new virtualbox-hwe package will exist for bionic too
[09:35] <LocutusOfBorg> what is the suggestion? make a fake virtualbox-hwe that is the same as virtualbox to make people upgrade smoothly?
[09:36] <Laney> tsimonq2: if you can import it, that should be OK I think, or else maybe factoring out the amqp bits from browse.cgi would be nice
[09:37] <xnox> LocutusOfBorg, hwe packages must exists in bionic release pocket
[09:37] <xnox> LocutusOfBorg, even if they are simply meta-packages pointing at the non-hwe one for now.
[09:37] <xnox> LocutusOfBorg, we are awaiting linux-meta-hwe for the same reasons.
[09:38] <tsimonq2> Laney: Oh, meaning, just take the AMQP bits from browse.cgi that I need and then just use that data? That works.
[09:42] <Laney> tsimonq2: Meaning put them in a common file and include it into browse and the other one
[09:42] <Laney> Not copy and paste.
[09:43] <LocutusOfBorg> xnox, makes sense, thanks
[09:43] <tsimonq2> Laney: Oh, gotcha.
[09:44] <tsimonq2> Laney: And I guess my original question relates to how to *actually* import it. Where might be the best spot if I wanted to just use the function from browse?
[09:46] <ginggs> estan: c-blosc sync'd
[09:54] <Laney> tsimonq2: Actually I don't know since it's a .cgi extension
[09:55] <Laney> You have to do some weird thing with imp or something I think - probably splitting out is cleanest and then you can put the import at the top
[10:03] <estan> ginggs: excellent, thanks. i will try it out from -proposed shortly, and report to https://bugs.launchpad.net/ubuntu/+source/c-blosc/+bug/1755380 (which was the original report in which i requested an FFE for 1.14.0).
[10:03] <ubot5`> Ubuntu bug 1755380 in c-blosc (Ubuntu) "[FFe] Please sync c-blosc 1.14.0+ds1-1 from debian unstable to bionic (1.11.1 has format incompat bug!)" [Undecided,Fix released]
[10:13] -queuebot:#ubuntu-release- New binary: ruby-flipper-active-record [amd64] (bionic-proposed/universe) [0.10.2-2] (no packageset)
[10:15] -queuebot:#ubuntu-release- New: accepted ruby-flipper-active-record [amd64] (bionic-proposed) [0.10.2-2]
[10:16] -queuebot:#ubuntu-release- New: accepted fluidr3mono-gm-soundfont [sync] (bionic-proposed) [2.315-2]
[10:23] <LocutusOfBorg> hello is it normal that we don't have a "request import" on launchpad anymore?
[10:23] <LocutusOfBorg> I'm talking about https://code.launchpad.net/~videolan/vlc/+git/vlc
[10:25] <apw> isn't that saying it is already in the queue ?
[10:34] <xnox> apw, re: doko bug, one can force-migrate things via hints too, i guess.... to avoid removals / temporary breakage in archive.
[10:34] <xnox> cause we do not want to raise uninstallable count in release pocket, as otherwise britney can go crazy and trade-migrate borken things
[10:35] <apw> indeed
[10:36] <apw> xnox, though this might simply be nbs in -proposed too
[10:42] <xnox> looking at nbs, btw
[10:42] <xnox> http://people.canonical.com/~ubuntu-archive/nbs.html -> iproute can be removed, as everything has alternative depends "iproute2|iproute"
[10:43] <xnox> (otherwise iproute2 would not have migrated....)
[10:54] <apw> doko, this gcc-defaults-ports -> gcc-defaults move, some of these binaries really are not being made by either any more, on ppc64el
[10:57] <apw> doko, that s390x looks to be the same thing, hinted
[10:59] <estan> ginggs: i've tested the c-blosc package in -proposed, it's looking good: https://bugs.launchpad.net/ubuntu/+source/c-blosc/+bug/1755380/comments/4
[10:59] <ubot5`> Ubuntu bug 1755380 in c-blosc (Ubuntu) "[FFe] Please sync c-blosc 1.14.0+ds1-1 from debian unstable to bionic (1.11.1 has format incompat bug!)" [Undecided,Fix released]
[11:02] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (artful-proposed) [2.31.2+17.10]
[11:03] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (xenial-proposed) [2.31.2]
[11:04] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (trusty-proposed) [2.31.2~14.04]
[12:09] <chrisccoulson> hi, can someone please approve my adobe-flashplugin partner uploads from last week?
[12:13] <cjwatson> LocutusOfBorg: that just means an import is already queued
[12:13] <cjwatson> as apw says
[12:14] <cjwatson> LocutusOfBorg: we had a hardware failure on the machine that was doing most of the code import work, which produced a backlog; a replacement is now in service, and looking at our graphs it's almost finished demolishing the backlog
[12:15] <cjwatson> was at around 4000 and now at 600
[12:30] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-edge [amd64] (xenial-proposed/main) [4.15.0-13.14~16.04.1] (kernel)
[12:44] <LocutusOfBorg> thanks, nice!
[12:45] <LocutusOfBorg> btw, I was aware of the backlog, I was just wondering why the "button" disappeared. if being queued means that the button is not clickable, even more efficient :)
[12:46] <LocutusOfBorg> yeah, "import now" is shown again in the web page, thanks!
[12:49] -queuebot:#ubuntu-release- New sync: musescore-sftools (bionic-proposed/primary) [20180222-2]
[12:54] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-edge [amd64] (xenial-proposed) [4.15.0-13.14~16.04.1]
[12:55] <tsimonq2> Laney: So then what would I do after splitting out? ;)
[12:56] <Laney> tsimonq2: Include the new file in both places and then use the functions
[12:58] <tsimonq2> Laney: I guess my Python is bad enough that I'm wondering how I'd import it from submit.py if the new file would be in its parent directory, if that makes sense...
[12:59] <tsimonq2> Laney: Meaning, do I put the new file in w/request or just in w/?
[13:00] <tsimonq2> (I can figure out everything but this. ;) )
[13:02] <Laney> tsimonq2: I think the sys.path will be okay since it's run from request.cgi in the top level, but if it's not you should be able to set it yourself
[13:02] <Laney> That part should be testable locally
[13:06] <tsimonq2> Laney: ok
[13:07] <tsimonq2> Laney: That's why I want to be careful, because while I'm checking the majority of my code in the interactive console, I don't have a full setup here...
[13:09] <Laney> tsimonq2: You should be able to set up a rabbitmq locally to connect to, and then use run-autopkgtest from lp:ubuntu-archive-tools to poke jobs into it
[13:09] <Laney> If you set up a worker you can even run those jobs :-)
[13:10] <tsimonq2> Laney: I'll give it a try. :)
[13:11] <tsimonq2> Laney: Otherwise, how are my two commits looking so far? https://git.launchpad.net/~tsimonq2/autopkgtest-cloud/+git/bug-1654761/?h=remove-ability-to-duplicate-tests-in-queue
[13:11] <ginggs> estan: bcolz autopkgtests failed (also in Debian) https://ci.debian.net/packages/b/bcolz/unstable/amd64/ does it need an update for the new c-blosc?
[13:12] <Laney> tsimonq2: I'm busy at the minute, will review properly later on but the shape of them looks nice, good work
[13:12] <tsimonq2> Laney: Sure, thanks.
[13:14] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (bionic-proposed) [4.15.0-13.14]
[13:54] <doko> apw: which ones?
[14:00] <apw> doko, i have not checked all of the ones in that list britney is whining about, but cirtainly the first one has only amd64/i386 binaries in proposed, which if it was coming out of gcc-default it would be there from that
[14:02] -queuebot:#ubuntu-release- New: accepted musescore-sftools [sync] (bionic-proposed) [20180222-2]
[14:04] -queuebot:#ubuntu-release- New binary: musescore-sftools [ppc64el] (bionic-proposed/none) [20180222-2] (no packageset)
[14:04] -queuebot:#ubuntu-release- New binary: musescore-sftools [s390x] (bionic-proposed/none) [20180222-2] (no packageset)
[14:05] -queuebot:#ubuntu-release- New binary: musescore-sftools [amd64] (bionic-proposed/none) [20180222-2] (no packageset)
[14:05] -queuebot:#ubuntu-release- New binary: musescore-sftools [i386] (bionic-proposed/none) [20180222-2] (no packageset)
[14:06] -queuebot:#ubuntu-release- New binary: musescore-sftools [armhf] (bionic-proposed/none) [20180222-2] (no packageset)
[14:06] -queuebot:#ubuntu-release- New binary: musescore-sftools [arm64] (bionic-proposed/none) [20180222-2] (no packageset)
[14:49] <Saviq> hey, what's the best way to get the Ubuntu release code in debian/rules? lsb_release isn't installed on the builders
[14:50]  * Saviq → #ubuntu-devel, sorry for the noise
[15:34] -queuebot:#ubuntu-release- New: accepted musescore-sftools [amd64] (bionic-proposed) [20180222-2]
[15:34] -queuebot:#ubuntu-release- New: accepted musescore-sftools [armhf] (bionic-proposed) [20180222-2]
[15:34] -queuebot:#ubuntu-release- New: accepted musescore-sftools [ppc64el] (bionic-proposed) [20180222-2]
[15:34] -queuebot:#ubuntu-release- New: accepted musescore-sftools [arm64] (bionic-proposed) [20180222-2]
[15:34] -queuebot:#ubuntu-release- New: accepted musescore-sftools [s390x] (bionic-proposed) [20180222-2]
[15:34] -queuebot:#ubuntu-release- New: accepted musescore-sftools [i386] (bionic-proposed) [20180222-2]
[16:36] -queuebot:#ubuntu-release- Unapproved: accepted flatpak [source] (artful-proposed) [0.8.9-0ubuntu0.1]
[16:36] <infinity> estan: Second hurdle, the new c-blosc regresses bcolz: https://ci.debian.net/packages/b/bcolz/unstable/amd64/
[16:37] <ginggs> infinity: he is aware, i updated the sync bug
[16:40] <infinity> ginggs: Ahh, missed that in backscroll.
[16:45] <xnox> infinity, please clean-up NBS libstd-rust-1.23, and then rustc 1.24.1 should migrate; on all arches btw ;-)
[16:45] <xnox> NBS in bionic-proposed that is
[16:46] <infinity> xnox: Thwacking.
[17:01] <infinity> doko: Are you doing a gcc-defaults upload to match http://launchpadlibrarian.net/361173244/gcc-defaults-ports_1.174ubuntu1_1.174ubuntu2.diff.gz ?
[17:01] <infinity> doko: (or reverting that change entirely, which I think would also be fine)
[17:41] <bashfulrobot> How's everyones beta testing/feedback going?
[18:16] <estan> infinity: yea, ginggs alerted me to it :( i could reproduce it with bcolz master and made an upstream report: https://github.com/Blosc/bcolz/issues/374
[18:18] <estan> (same upstream author, so hopefully it's just something wrong with the tests. would think it careless if he's breaking his own downstream in a minor version :))
[18:42] <slangasek> doko: are these various old gcc-N-cross packages really useful to carry?  Why do we need more than just the current default version?
[18:44] <slangasek> doko: btw, are we ready to drop gcc-4.8 now?  annoyingly, debian/control for old gcc series is never cleaned up wrt binaries that it no longer ships, so 'reverse-depends src:gcc-4.8' is useless for figuring this out; but I think we may have finally dropped the remaining bits of the Ubuntu Touch stack that needed it
[18:57] <slangasek> doko: https://paste.ubuntu.com/p/TS7FphQCK3/ and all the rest are alternatives.  So I think we can drop gcc-4.8 now
[18:58] <slangasek> xnox: why does boost prefer libstdc++-4.8-dev over libstdc++-dev?
[19:00] <slangasek> doko: LP: #1756972, I can pull the trigger or let you do it
[19:00] <ubot5`> Launchpad bug 1756972 in gcc-4.8 (Ubuntu) "RM: gcc-4.8: no longer used" [Undecided,New] https://launchpad.net/bugs/1756972
[19:03] <slangasek> doko: gcc-5 seems to have exactly two packages still using libgo7; maybe we should fix those and drop gcc-5 as well? (minica/s390x; pluginhook)
[19:05] <jbicha> slangasek: LP: #1756871 should be an easy one to remove :)
[19:05] <ubot5`> Launchpad bug 1756871 in libxfont1 (Ubuntu) "Please remove libxfont1 from Ubuntu" [Undecided,New] https://launchpad.net/bugs/1756871
[19:06] <slangasek> jbicha: why are we removing it from Ubuntu if it hasn't been removed yet from Debian?
[19:07] <jbicha> well we could wait a week or two for Debian if you want…
[19:07] <jbicha> its last rdepends was fixed this weekend
[19:08] <slangasek> jbicha: it's much more efficient to run process-removals against Debian removals rather than handle via individual launchpad bugs
[19:08] <jbicha> the fact that it has Ubuntu revisions doesn't matter much for that?
[19:10] <slangasek> jbicha: I always review the Ubuntu delta while running process-removals, and it's usually clear whether the delta represents a real committment to maintenance
[19:10] <slangasek> in this case it's security updates, so clearly not
[19:13] <slangasek> doko: minica, pluginhook uploaded (no-change rebuilds); gcc-5 is now free to go
[19:19] <slangasek> doko: LP: #1756979 - though maybe this one should be handled via Debian removal?
[19:19] <ubot5`> Launchpad bug 1756979 in gcc-5-cross (Ubuntu) "RM: gcc-5: no longer used" [Undecided,New] https://launchpad.net/bugs/1756979
[20:51] -queuebot:#ubuntu-release- New source: virtualbox-hwe (bionic-proposed/primary) [5.2.8-dfsg-5ubuntu18.04.1]
[20:54] <LocutusOfBorg> please accept virtualbox-hwe :) this is the upgrade path from xenial package
[20:57] <slangasek> chrisccoulson: I'm looking around for the adobe-flashplugin uploads you mentioned and I'm not finding them in queues.  Can you point me to where they are, specifically?
[21:00] <chrisccoulson> slangasek, oh, I just checked and someone approved them on thursday. Sorry about that :(
[21:00] <chrisccoulson> they do need copying to the release pocket though (if you give me half an hour or so)
[21:00] <slangasek> chrisccoulson: ack
[21:22] <chrisccoulson> slangasek, ok, those are good to go
[21:26] <slangasek> chrisccoulson: done
[21:37] <chrisccoulson> slangasek, excellent, thanks!
[21:41] -queuebot:#ubuntu-release- New source: virtualbox-hwe (bionic-proposed/primary) [5.2.8-dfsg-5ubuntu18.04.1]
[22:22] <sil2100> C/quit
[22:22] <sil2100> eh
[22:22] <sil2100> ;)
[22:22] <sil2100> o/
[22:22] <tsimonq2> irssi!
[22:22] <tsimonq2> :D
[22:23] <tsimonq2> (maybe?)
[22:23] <wxl>  /ctcp nick version
[22:23] <wxl> :)
[22:23] <wxl> but /quit's pretty universal across clients
[22:23] <tsimonq2> wxl: He doesn't have a bouncer (*ahem*) so I dunno if that's info I can see. :)
[23:10] -queuebot:#ubuntu-release- Unapproved: grub2 (xenial-proposed/main) [2.02~beta2-36ubuntu3.17 => 2.02~beta2-36ubuntu3.18] (core)