[06:03] <cpaelzer> vorlon: thanks for letting me know, I'll reprep something that fits our needs then
[07:50] <ginggs> would someone please remove src:mathicgb from disco ?  it's not compatible with recent googletest LP: #1811562
[08:18] -queuebot:#ubuntu-release- New: accepted netkit-ftp-ssl [sync] (disco-proposed) [0.17.34+0.2-4.1]
[08:18] -queuebot:#ubuntu-release- New: accepted piuparts [amd64] (disco-proposed) [0.98]
[08:20] -queuebot:#ubuntu-release- New binary: netkit-ftp-ssl [s390x] (disco-proposed/universe) [0.17.34+0.2-4.1] (no packageset)
[08:20] -queuebot:#ubuntu-release- New binary: netkit-ftp-ssl [amd64] (disco-proposed/universe) [0.17.34+0.2-4.1] (no packageset)
[08:21] -queuebot:#ubuntu-release- New binary: netkit-ftp-ssl [armhf] (disco-proposed/universe) [0.17.34+0.2-4.1] (no packageset)
[08:21] -queuebot:#ubuntu-release- New binary: netkit-ftp-ssl [ppc64el] (disco-proposed/universe) [0.17.34+0.2-4.1] (no packageset)
[08:21] -queuebot:#ubuntu-release- New binary: netkit-ftp-ssl [i386] (disco-proposed/universe) [0.17.34+0.2-4.1] (no packageset)
[08:21] -queuebot:#ubuntu-release- New binary: netkit-ftp-ssl [arm64] (disco-proposed/universe) [0.17.34+0.2-4.1] (no packageset)
[08:23] -queuebot:#ubuntu-release- New: accepted netkit-ftp-ssl [amd64] (disco-proposed) [0.17.34+0.2-4.1]
[08:23] -queuebot:#ubuntu-release- New: accepted netkit-ftp-ssl [armhf] (disco-proposed) [0.17.34+0.2-4.1]
[08:23] -queuebot:#ubuntu-release- New: accepted netkit-ftp-ssl [ppc64el] (disco-proposed) [0.17.34+0.2-4.1]
[08:23] -queuebot:#ubuntu-release- New: accepted netkit-ftp-ssl [arm64] (disco-proposed) [0.17.34+0.2-4.1]
[08:23] -queuebot:#ubuntu-release- New: accepted netkit-ftp-ssl [s390x] (disco-proposed) [0.17.34+0.2-4.1]
[08:23] -queuebot:#ubuntu-release- New: accepted netkit-ftp-ssl [i386] (disco-proposed) [0.17.34+0.2-4.1]
[09:52] -queuebot:#ubuntu-release- Builds: Ubuntu Server amd64+mac [Trusty 14.04.6] (20190304) has been added
[09:52] -queuebot:#ubuntu-release- Builds: Ubuntu Server amd64 [Trusty 14.04.6] (20190304) has been added
[09:52] -queuebot:#ubuntu-release- Builds: Ubuntu Server i386 [Trusty 14.04.6] (20190304) has been added
[09:52] -queuebot:#ubuntu-release- Builds: Ubuntu Server powerpc [Trusty 14.04.6] (20190304) has been added
[09:53] -queuebot:#ubuntu-release- Builds: Ubuntu Server ppc64el [Trusty 14.04.6] (20190304) has been added
[11:01]  * apw reviews snapd across the
[11:01] <apw> board
[11:22] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (cosmic-proposed) [2.37.4+18.10]
[12:00] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-384 (xenial-proposed/universe) [384.130-0ubuntu0.16.04.1 => 384.130-0ubuntu0.16.04.2] (no packageset)
[12:01] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-384 (trusty-proposed/universe) [384.130-0ubuntu0.14.04.1 => 384.130-0ubuntu0.14.04.2] (no packageset)
[12:01] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-340 (xenial-proposed/restricted) [340.104-0ubuntu0.16.04.1 => 340.107-0ubuntu0.16.04.1] (ubuntu-desktop)
[12:02] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-340 (trusty-proposed/restricted) [340.102-0ubuntu0.14.04.1 => 340.107-0ubuntu0.14.04.1] (no packageset)
[12:03] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-304 (xenial-proposed/restricted) [304.135-0ubuntu0.16.04.2 => 304.135-0ubuntu0.16.04.3] (ubuntu-desktop)
[12:04] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-304 (trusty-proposed/restricted) [304.135-0ubuntu0.14.04.1 => 304.135-0ubuntu0.14.04.2] (ubuntu-desktop)
[12:20] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (bionic-proposed) [2.37.4+18.04]
[12:22] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (xenial-proposed) [2.37.4]
[12:23] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (trusty-proposed) [2.37.4~14.04]
[12:31] <ddstreet> seb128 for lp #1812760 why did you mark it verification-failed-bionic?
[12:35] -queuebot:#ubuntu-release- Unapproved: live-build (trusty-proposed/main) [3.0~a57-1ubuntu11.4 => 3.0~a57-1ubuntu11.5] (desktop-core)
[12:43] <cjwatson> sil2100: Could you do me a favour and run 'mark-suite-dirty -A ppa:snappy-dev/ubuntu/tools-proposed -s bionic' (from lp:ubuntu-archive-tools)?  That'll cause bionic to exist (after a publisher run) in http://ppa.launchpad.net/snappy-dev/tools-proposed/ubuntu/dists/, which would be helpful for some testing I'm doing
[12:44] <sil2100> cjwatson: sure
[12:45] <sil2100> cjwatson: should be done o/
[12:48] <cjwatson> sil2100: cheers
[12:49] <sil2100> Would be nice if someone could have a look at the trusty live-build changes for the initrd handling ^
[12:52] <acheronuk> mwhudson vorlon: FYI, I reported the biopython test issue upstream earlier: https://github.com/biopython/biopython/issues/1945
[12:52] <gitbot> biopython issue 1945 in biopython "Test precision failure on Ubuntu autopkgtests with glibc 2.29" [Open]
[13:10] -queuebot:#ubuntu-release- Unapproved: accepted fonts-liberation2 [sync] (bionic-proposed) [2.00.1-7~18.04.2]
[13:10] -queuebot:#ubuntu-release- Unapproved: accepted libreoffice-l10n [sync] (bionic-proposed) [1:6.0.7-0ubuntu0.18.04.4]
[13:11] -queuebot:#ubuntu-release- Unapproved: accepted libreoffice [sync] (bionic-proposed) [1:6.0.7-0ubuntu0.18.04.4]
[13:17] <cpaelzer> I'm wondering about the whereabout of libsodium in trusty
[13:17] <cpaelzer> I uploaded it as part of bug 1817665 on 26th of February
[13:17] <cpaelzer> and I have got the arrival in NEW queue from LP on all three
[13:18] <cpaelzer> but it seems vorlon could only see two in -NEW and accepted them
[13:18] <cpaelzer> I fail to find where the remaining one (src:libsodium) went
[13:18] <cpaelzer> From my POV it should still be in NEW of trust
[13:18] <cpaelzer> y
[13:18] <cpaelzer> but it isn't
[13:19] <cpaelzer> anyone able to help me finding it or should I just re-upload
[13:19] <cpaelzer> rbasak: you looked at the case in the past - have you had any issues seeing the uploads?
[13:20] <cpaelzer> ha - I found it
[13:20] <cpaelzer> it was accepted but missed an update to the bug
[13:20] <cpaelzer> interesting
[13:21] <cpaelzer> also it FTBFS which it didn't in the PPA that I had attached as proof
[13:21] <cpaelzer> ok - I can go from here - sorry for the noise
[13:23] <cpaelzer> umm the build started and stopped after 8 minutes - but for whatever reason LP doesn't show me logs oO?
[13:23] <cpaelzer> rbasak: do you see build logs on https://launchpad.net/ubuntu/+source/libsodium/1.0.8-5~ubuntu14.04.1/+build/16438047 ?
[13:24] <cpaelzer> I can hit retry but I want to understand as much as possible of this before I might trample on some evidence
[13:33] <apw> cpaelzer, no build log normally indicates an initialisation failure, i've seen those with timouts pushing the .dsc, though those are normally near exact multiples of 5m
[13:33] <apw> cpaelzer, and i don't see a log either
[13:33] <rbasak> Yeah that ^
[13:34] <juliank> Laney, sil2100 the order of rows changing all the time on autopkgtest request.cgi has been bugging me a bit, so I fixed it: https://code.launchpad.net/~juliank/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/363916
[13:34] <juliank> :)
[13:35] <juliank> Now I can switch between request tabs and easily compare them
[13:35] <cpaelzer> apw: rbasak: so it seems safe that I hit retry then - thanks
[13:36] <seb128> ddstreet, hey, arg sorry, I forgot to comment on it, it's because of bug #1818340 which is reported as a regression, to make sure we don't validate the SRU by error before that one is sorted out
[13:37] <seb128> xnox-, ^ would be nice to have your input on that one
[13:37] <seb128> ddstreet, I subscribed you to the new one though, before adding a comment saying why I was failing the SRU bug
[13:38] <ddstreet> ok thnx, i'll look at the new one
[13:39] <seb128> thx
[13:45] <cpaelzer> rbasak: apw: FYI as expected the rebuild worked fine
[13:45] <cpaelzer> odd case, but relieving that the resut was as expected
[13:50] <cjwatson> apw: not necessarily initialisation; any kind of catastrophic builder crash will do it too
[13:50] <cjwatson> or network failures during the build
[13:51] -queuebot:#ubuntu-release- New binary: python-libnacl [i386] (trusty-proposed/universe) [1.4.5-0ubuntu1~ubuntu14.04.1] (no packageset)
[13:58] -queuebot:#ubuntu-release- Unapproved: virtualbox (xenial-proposed/multiverse) [5.1.38-dfsg-0ubuntu1.16.04.2 => 5.1.38-dfsg-0ubuntu1.16.04.3] (ubuntu-cloud)
[13:59] -queuebot:#ubuntu-release- Unapproved: virtualbox-lts-xenial (trusty-proposed/multiverse) [4.3.36-dfsg-1+deb8u1ubuntu1.14.04.1~14.04.4 => 4.3.36-dfsg-1+deb8u1ubuntu1.14.04.1~14.04.5] (no packageset)
[13:59] -queuebot:#ubuntu-release- Unapproved: virtualbox-hwe (xenial-proposed/multiverse) [5.1.38-dfsg-0ubuntu1.16.04.1 => 5.1.38-dfsg-0ubuntu1.16.04.2] (no packageset)
[14:07] <cpaelzer> apw: thanks for helping before - you seem to be the AA being aroudn right now. bug 1817665 which my wondering about failed builds was before is about three packages with build dep each other
[14:07] <cpaelzer> apw: but also each of them will hit new queue, so while steve did that for the first already I'm now at https://launchpad.net/ubuntu/+source/python-libnacl/1.4.5-0ubuntu1~ubuntu14.04.1 in trusty-new and somewhen after acceptign that will see the same for pymacaroons
[14:08] <cpaelzer> apw: might I ask you to accept https://launchpad.net/ubuntu/+source/python-libnacl/1.4.5-0ubuntu1~ubuntu14.04.1 in NEW?
[14:08] <cpaelzer> or am I misreading the NEW that launchpad shows me
[14:08] <cpaelzer> as it is not in the classic "new queue" anymore
[14:08] <cpaelzer> there are too many things called NEW, time they get OLD
[14:09] <cpaelzer> hmm I can build pymacaroons now it seems, so it is - as I assumed - a different NEW
[14:10] <cpaelzer> apw: TL;DR no action needed right now
[14:10]  * cpaelzer goes mad for too many things at once and searches a cup of tea
[14:12] <cpaelzer> hmm, I spoke too soon - I again got "Missing build dependencies: python3-libnacl"
[14:13] <cpaelzer> so it might mean that the NEW being listed means some NEW queue - well for the Binaries maybe?
[14:13] <cpaelzer> yeah https://launchpad.net/ubuntu/+source/python-libnacl/1.4.5-0ubuntu1~ubuntu14.04.1/+build/16438055 is very literal about it "Binary packages awaiting approval in NEW queue"
[14:13] <cpaelzer> apw: so I was right with my initial request, might I ask you to accept those?
[14:14] <cpaelzer> rbasak: for our discussions if SRU-NEW queues go right to -proposed - It is true for the src-pacakge but Binaries seem to pop into needing NEW approval again (see above)
[14:15] <cpaelzer> I must admit I don't see why https://launchpad.net/ubuntu/+source/libsodium/1.0.8-5~ubuntu14.04.1 didn't trigger the same
[14:15] <cpaelzer> but I hope apw might explain me later when he gets to that
[14:27] <apw> cpaelzer, i would say it never built on i386 before
[14:32] <apw> cpaelzer, in fact it never existed before ... and i386 is arch:all
[14:40] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (trusty-proposed/main) [2.208.15 => 2.208.16] (desktop-core)
[14:44] <cpaelzer> apw: yep - as I said it was going to the new queue where vorlon accepted the source
[14:45] <cpaelzer> apw: just now after the build of libsodium all seems fine, but on python-libnacl the binaries are listed to be in NEW
[14:45] <cpaelzer> apw: and the whole point of the bug those are associated to is to bring all three packages formerly not in trusty at all to trusty
[14:45] <cpaelzer> that is bug 1817665
[14:46] -queuebot:#ubuntu-release- Unapproved: python-eventlet (bionic-proposed/main) [0.20.0-4 => 0.20.0-4ubuntu0.18.04.1] (openstack, ubuntu-server)
[14:46] -queuebot:#ubuntu-release- Unapproved: python-eventlet (cosmic-proposed/main) [0.20.0-5 => 0.20.0-5ubuntu0.18.10.1] (openstack, ubuntu-server)
[14:46] <cpaelzer> libsodium was not arch_all that was "normal" binaries per arch
[14:47] <cpaelzer> might that have been the reason it was not triggering NEW "again" ?
[14:48] <cpaelzer> while src:python-libnacl  with binaries python-libnacl and python3-libnacl are held again in NEW for the Binaries
[15:01] -queuebot:#ubuntu-release- Unapproved: accepted live-build [source] (trusty-proposed) [3.0~a57-1ubuntu11.5]
[15:03] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (trusty-proposed) [2.208.16]
[15:03] <apw> cpaelzer, and accepted
[15:04] <cpaelzer> thank you
[15:04] -queuebot:#ubuntu-release- New: accepted python-libnacl [i386] (trusty-proposed) [1.4.5-0ubuntu1~ubuntu14.04.1]
[15:04] <cpaelzer> if pymacaroons behaves the same I might ping again once built
[15:05] <sil2100> plz no releases into trusty-updates kthx
[15:16] <vorlon> sil2100: I guess maybe we shouldn't be trying to build panda images for 14.04.6
[15:20] <sil2100> vorlon: ah, I thought I saw them in .5, but I now see we actually didn't
[15:21] <sil2100> Ok, so my livecd-rootfs change is not needed then
[15:22] <sil2100> I mean, I'll release it into -updates later anyway so that the version number doesn't get burned down, the change is harmless in overall
[15:22] <vorlon> sil2100: even if we had released them, we certainly shouldn't be doing testing on panda now
[15:27] -queuebot:#ubuntu-release- New binary: pymacaroons [i386] (trusty-proposed/universe) [0.9.2-0ubuntu1~ubuntu14.04.1] (no packageset)
[15:29] <rbasak> sil2100: please could you delete python-certbot-nginx from xenial-proposed? This isn't part of the current SRU and is no longer planned to be landed.
[15:30] <rbasak> It'd be good to delete it in advance just in case (unlikely) people verifying the new SRU are relying on that somehow.
[15:30] <cpaelzer> apw: now the same again for https://launchpad.net/ubuntu/+source/pymacaroons/0.9.2-0ubuntu1~ubuntu14.04.1/+build/16438056
[15:30] <cpaelzer> apw: this is the last of that stack of packages
[15:30] <teward> rbasak: anyone relying on it is going to get smacked by me, because it breaks things.
[15:31] <rbasak> teward: in Xenial, or in general?
[15:31] <rbasak> But anyway, we're agreed then ?:)
[15:31] <teward> rbasak: in general, it does SSL configuration which has some headaches with multisite
[15:31] <teward> but I'm for dropping it in the existing SRU(s)
[15:31] <teward> rbasak: but i'm talking from an NGINX Generic Support perspective
[15:31] <cpaelzer> rbasak: I read teward as that being just one more reason to remove it from proposed
[15:31] <teward> it *works* with single sites.
[15:32] <Odd_Bloke> vorlon: vagrant is still stuck in disco-proposed, and I'm not sure why; updates_excuses.html looks clear, so I assume it's some dark magic^W^Winstallability issue?
[15:32] <teward> cpaelzer: please remove it from proposed, I'd sooner torch it in all releases but that's not my call.
[15:32] <rbasak> teward: does upstream have bug reports on your concern
[15:32] <rbasak> ?
[15:32] <rbasak> They are quite responsive
[15:33] <teward> rbasak: i've talked privately with them, it's more how it does its autoconfigs that results in a HUGE number of SSL config headaches that we see complained about in #nginx
[15:33] <teward> but they don't have a 'fix' because it's more for 'simple' deployments, rather than more complex deployments - certbot provides a certonly mode which is what I"ve pushed my recommendations with
[15:34] <teward> which *doesn't* break the configs already in place, and just gens the cert and you point your nginx configs there.
[15:34] <teward> but that's more me being overly picky about
[15:34] <rbasak> Should it maybe detect 'complex' and fail more gracefully, recommending certonly itself?
[15:34] <teward> rbasak: probably, but because of the *really* varying definitions of 'complex' it'd be difficult to ID probably
[15:35] <teward> cerbot's been on my radar as a headache that i try to avoid with its nginx plugins
[15:35] <teward> but *that* complaint is not enough on its own to purge it globally
[15:35] <teward> but for Xenial if it was never in there, drop it from -proposed
[15:35] <sil2100> rbasak: will do
[15:36] <vorlon> Odd_Bloke: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt shows sonic-pi becomes uninstallable
[15:36] <vorlon> (because ruby-i18n has to be updated at the same time as vagrant, and something in ruby-i18n makes sonic-pi uninstallable)
[15:36] <teward> rbasak: i'll gen an example and share it separately, but i've got a thousand things at work that need my attention first
[15:36] <Odd_Bloke> vorlon: Exciting stuff; thanks!
[15:37] <teward> rbasak: *currently* it doesn't 'break' unless you're trying to use the nginx plugin to configure multiple configs at once - *that* is where it can explodify.
[15:42] -queuebot:#ubuntu-release- Unapproved: packagekit (cosmic-proposed/main) [1.1.10-1ubuntu7 => 1.1.10-1ubuntu7.1] (desktop-core)
[15:45] -queuebot:#ubuntu-release- Unapproved: packagekit (bionic-proposed/main) [1.1.9-1ubuntu2.18.04.4 => 1.1.9-1ubuntu2.18.04.5] (desktop-core)
[15:47] -queuebot:#ubuntu-release- New: accepted pymacaroons [i386] (trusty-proposed) [0.9.2-0ubuntu1~ubuntu14.04.1]
[15:58] <cpaelzer> vorlon: I see you are around already - maybe you could do the accept of the binary packages in https://launchpad.net/ubuntu/+source/pymacaroons/0.9.2-0ubuntu1~ubuntu14.04.1/+build/16438056
[15:58] <cpaelzer> apw: helped me to get the other one processed, but that is still missing
[15:59] <cpaelzer> I see somebody said yes to those packages since the last reload that I did - thanks to vorlon/apw or whoever did it
[15:59] <vorlon> cpaelzer: I don't see any binaries waiting in the trusty new queue
[15:59] <vorlon> ok
[15:59] <apw> cpaelzer, pretty sure that 2 lines above says it is already done
[15:59] <cpaelzer> it does
[16:00] <Odd_Bloke> vorlon: So I've just spun up an i386 lxd container and installing vagrant/ruby-i18n and sonic-pi simultaneously didn't raise any issues; do you have any hints as to how I can go about reproducing the problem?
[16:04] <sil2100> infinity: hey! Any reason we still have bionic daily builds disabled?
[16:09] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop i386 [Trusty 14.04.6] (20190304.2) has been added
[16:11] <sil2100> hmm
[16:13] <sil2100> jibel: ^ ok, so i386 seems to have succeeded, but the amd64 livefs failed to build with -proposed enabled, looks like some strange kernel conflict
[16:13] <jibel> sil2100, can you build without proposed?
[16:13] <sil2100> Wonder if that's not caused by the trusty kernels that are in -proposed right now
[16:13] <jibel> and if it passes we're happy
[16:14] <sil2100> Yeah, I'm thinking even of just kicking a livefs build without cdimage
[16:15] <jibel> most of the build time is spent in livecd-rootfs so just trigger a build and if there are images then we're good
[16:33] <jibel> given the error, I am not sure a build without proposed will fix it
[16:34] <sil2100> jibel: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/trusty/ubuntu/+build/158473 <- it looks like it did
[16:35] <jibel> cool
[16:38] <sil2100> jibel: you want me to do a livefs build with -proposed disabled but with the live-build change included?
[16:39] <sil2100> Anyway, I'll look at the logs in a moment once again, but I'd just push it out to -updates and see how it goes
[16:42] <jibel> sil2100, yeah, sorry I thought you already pushed the fix
[16:58] <abeato> vorlon, hey, any chances initramfs-tools-devices can move forward from https://launchpad.net/ubuntu/disco/+queue ?
[16:59] <vorlon> abeato: I'll queue that up for review today
[17:00] <abeato> vorlon, sounds good, thanks
[17:01] -queuebot:#ubuntu-release- Unapproved: unity (bionic-proposed/universe) [7.5.0+18.04.20180413-0ubuntu1 => 7.5.0+18.04.20190304-0ubuntu1] (no packageset) (sync)
[17:01] -queuebot:#ubuntu-release- Unapproved: unity (cosmic-proposed/universe) [7.5.0+18.10.20180926.2-0ubuntu1 => 7.5.0+18.10.20190304-0ubuntu1] (no packageset) (sync)
[17:52] <vorlon> infinity: what's your plan for the remaining glibc autopkgtest regressions?
[18:00] <infinity> sil2100: bionic dailies were still disabled to avoid stepping on your toes with xenial and trusty.
[18:03] <infinity> vorlon: Is it just down to two now, or am I scrolling too fast?
[18:03] <vorlon> infinity: python-biopython + postgresql-hll are the two I know about and don't have an answer for
[18:03] <infinity> postgresql-hll/all and python-biopython/ppc64el is what I see.
[18:03] <vorlon> yes
[18:04] <infinity> Kay, I shall investigate and blame today, and if blame's not mine, hint.
[18:09] <vorlon> Odd_Bloke: ruby-activesupport (et al.) in disco release pocket have a versioned depend on older ruby-i18n, so if you're enabling -proposed for all and using that, it'll look fine since it's fixed there (but stuck)
[18:10] <vorlon> Odd_Bloke: found via lp:~vorlon/ubuntu-archive-tools/update-output-helper , ./update-output-helper -u, ./update-output-helper ruby-i18n/1.5.3-1 vagrant/2.2.3+dfsg-1ubuntu1
[18:11] <vorlon> Laney: ^^ fwiw I seem to have warmed to this tool since you first submitted it for review, and now use it exclusively for debugging update_output, maybe we should revisit merging it :)
[18:11] <Odd_Bloke> vorlon: Ack, thank you!
[18:12] <vorlon> Odd_Bloke: also, since ruby-activesupport == rails, and there was discussion w/ server team that we should remove rails rather than maintaining it as debs, perhaps someone wants to socialize that further...
[18:32] <infinity> vorlon: Oh, and nag re: tidying ubuntu-core history on nusakan.
[18:33] <vorlon> infinity: I'm not going to do it by hand, I'm going to land sil2100's branch (if it's ready)
[18:33] <vorlon> sil2100: ^^ is it ready?
[18:33] <vorlon> (afaics it's not so urgent that I should do it by hand)
[18:34] <infinity> I mean, we ran out of disk doing the last point release, so... Not urgent when I clean up after, but urgent if we like having breathing room.
[18:34] <infinity> The trusty one will be a lot smaller though (only Ubuntu), so *shrug*.
[18:37] -queuebot:#ubuntu-release- Builds: Ubuntu Server amd64+mac [Trusty 14.04.6] has been updated (20190304.1)
[18:37] -queuebot:#ubuntu-release- Builds: Ubuntu Server amd64 [Trusty 14.04.6] has been updated (20190304.1)
[18:37] -queuebot:#ubuntu-release- Builds: Ubuntu Server i386 [Trusty 14.04.6] has been updated (20190304.1)
[18:37] -queuebot:#ubuntu-release- Builds: Ubuntu Server powerpc [Trusty 14.04.6] has been updated (20190304.1)
[18:37] -queuebot:#ubuntu-release- Builds: Ubuntu Server ppc64el [Trusty 14.04.6] has been updated (20190304.1)
[18:41] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64+mac [Trusty 14.04.6] (20190304.4) has been added
[18:41] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Trusty 14.04.6] (20190304.4) has been added
[18:42] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop i386 [Trusty 14.04.6] has been updated (20190304.4)
[18:42] <infinity> sil2100: Why the changes for omap?  I'm about 103% sure there were not trusty omap images...
[18:42] <infinity> s/not/no/
[18:44] <infinity> sil2100: The part where I can find no omap images in www/ at all probably backs up that assertion.
[18:45] <sil2100> infinity: that's invalid, I thought I saw those in .5 but I saw wrong, I didn't build them now for instance
[18:46] <sil2100> I mean, my change was not needed
[18:46] <infinity> Indeed.
[18:46] <sil2100> But oh well, since I pushed it to -proposed I just let it out not to have a missing version number
[18:46] <infinity> Also mostly harmless if you're not building images, so carry on.
[18:46] <sil2100> And vcs
[18:51] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Trusty 14.04.6] (20190304.1) has been added
[18:51] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop i386 [Trusty 14.04.6] (20190304.1) has been added
[19:01] <acheronuk> infinity: upstream biopython don't seem bothered by that ppc64el fail: https://github.com/biopython/biopython/issues/1945
[19:01] <gitbot> biopython issue 1945 in biopython "Test precision failure on Ubuntu autopkgtests with glibc 2.29" [Open]
[19:08] <infinity> acheronuk: Yeah, I found my way there literally just now. :P
[19:08] <infinity> By way of debian/changelog -> old ticket -> new ticket.
[19:08] <infinity> *sigh*
[19:08] <infinity> acheronuk: So, yes, will upload a quick fix for that.
[19:09] <infinity> acheronuk: Unless you want to do the honors.
[19:12] <infinity> acheronuk: And since there seems to be parallel effort here, did you have any insight on postgresql-hll before I go stare at that one?
[19:12] <acheronuk> infinity: sadly, no upload permissions for that. also not really at the right machine to put something to sponsor together, so I would suggest you just do it :)
[19:12] <acheronuk> no clue on that one. sorry
[19:12] <infinity> acheronuk: Sure, I'll JFDI, you can feel free to do the upstream PR though.
[19:13] <infinity> (I mean, it's a 1-char change, not sure why they're asking for a PR, but I guess they want to give you credit, which is nice)
[19:14] <acheronuk> yeah. I'm really waiting on upstream to comment back if they want to change more than just that one line and reduce the required precision for the rest of that group of tests
[19:14] <acheronuk> as the last comment implied they might
[19:14] <infinity> That feels safest, probably, but one could also make a slippery slope argument that once you reduce by a place on all tests, you might fail to catch an actual rounding regression, or think next month it's okay to go from 4 to 3 or...
[19:15] <infinity> But meh.
[19:15] <infinity> Asking for 5 places from fastish math is asking a lot.
[19:16] <acheronuk> I know, but as 1st time I ever looked at these tests is today, I figured their call is best
[19:16] <acheronuk> fi they go silent on it, I'll just PR that one
[19:16] <acheronuk> *if
[19:19] <infinity> *nod*
[19:58] <doko> vorlon: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output_notest.txt shows much more migration issues. see my question here from Friday
[20:00] <vorlon> doko: were you testing with update-output-helper?
[20:04] <doko> vorlon: yes, and it doesn't work. L aney posted an update here: https://gist.github.com/iainlane/6360602ebd945f0f6c7a126091f02b79
[20:04] <doko> looks like an unfinished mutter transition
[20:05] <ginggs> would someone please remove src:mathicgb from disco ?  it's not compatible with recent googletest LP: #1811562
[20:16] <jibel> Are Ubuntu Desktop amd64+mac really something we want to release (and test) for 14.04.6?
[20:20] <infinity> jibel: We did for every previous point release, so meh.
[20:28] <jibel> not sure I'll be able to find the hardware somewhere.
[20:41] <infinity> Well, that could be problematic indeed if we have nowhere to test.
[20:42] <infinity> And if not, we can just not release that one.
[21:03] -queuebot:#ubuntu-release- Unapproved: golang-1.8 (bionic-proposed/universe) [1.8.3-2ubuntu1 => 1.8.3-2ubuntu1.18.04.1] (no packageset)
[21:04] -queuebot:#ubuntu-release- Unapproved: golang-1.8 (cosmic-proposed/universe) [1.8.3-2ubuntu1 => 1.8.3-2ubuntu1.18.10.1] (lubuntu, ubuntu-mate)
[21:05] -queuebot:#ubuntu-release- Unapproved: rejected golang-1.8 [source] (bionic-proposed) [1.8.3-2ubuntu1.1]
[21:18] <vorlon> abeato: fwiw 'lintian -I' shows some minor issues in the initramfs-tools-devices source package
[21:22] -queuebot:#ubuntu-release- New: accepted initramfs-tools-devices [source] (disco-proposed) [0.3]
[21:24] -queuebot:#ubuntu-release- New binary: initramfs-tools-devices [amd64] (disco-proposed/universe) [0.3] (no packageset)
[22:14] <vorlon> acheronuk, tsimonq2: Debian removed soprano from unstable in January; but it still has revdeps in Ubuntu.  Should we be nuking the rest of that kde4 stack?
[22:15] <tsimonq2> vorlon: ack on nuking as much of KDE 4 as possible. :P
[22:15] <tsimonq2> (Go ahead.)
[22:16] <vorlon> tsimonq2: that includes amarok which is currently seeded
[22:17] <vorlon> tsimonq2: do you care to update the seed?
[22:17] <tsimonq2> vorlon: I'll do that within the hour.
[22:19] <vorlon> tsimonq2: kde-runtime still has a ton of revdeps
[22:20] <tsimonq2> vorlon: Are any of those seeded? (I'm not at a computer.)
[22:20] <vorlon> don't know yet
[22:21] <tsimonq2> ack
[22:21] <tsimonq2> kde-runtime and rdeps should be removed as well.
[22:21] <vorlon> tsimonq2: but e.g. basket is not removed from Debian testing yet and doesn't have any bug reports above wishlist about this (Debian bug #874829)
[22:23] <tsimonq2> I believe the KDE 4 removal bugs were filed as wishlist, I don't quote recall.
[22:23] <tsimonq2> I also don't know if it's changed from being a Buster goal.
[22:23] <tsimonq2> Regardless, I support removal of KDE 4 completely.
[22:25] <vorlon> tsimonq2: and then for an unrelated stack, Debian also removed lxqt-l10n as 'obsolete source package' but it's not an obsolete source package in Ubuntu...
[22:26] <tsimonq2> Upstream couldn't makw up their mind. :P
[22:27] <tsimonq2> 0.12 was l10n in individual packages, 0.13 was all into lxqt-l10n, 0.14 is back  to 0m12 behavior
[22:27] <tsimonq2> *0.12
[22:27]  * tsimonq2 finds a computer so I can type properly.
[22:44] <tsimonq2> vorlon: amarok removed from the Kubuntu seed.
[22:47] -queuebot:#ubuntu-release- Unapproved: systemd (cosmic-proposed/main) [239-7ubuntu10.9 => 239-7ubuntu10.10] (core)
[22:48] -queuebot:#ubuntu-release- Unapproved: systemd (bionic-proposed/main) [237-3ubuntu10.14 => 237-3ubuntu10.15] (core)
[22:50] <ddstreet> vorlon hey, im back with systemd again :)  for lp #1818340: it appears the backport for lp #1812760 was incomplete/incorrect so reverted those patches and re-uploaded to -proposed.  should be a relatively easy review, as it's only removing patches you already looked at.  for the original bug, i'll take it over since dja did the original work, but has left
[23:12] -queuebot:#ubuntu-release- Unapproved: gdm3 (bionic-proposed/main) [3.28.3-0ubuntu18.04.4 => 3.28.3-0ubuntu18.04.5] (ubuntu-desktop)
[23:31] <vorlon> ddstreet: instead of including both the changelog entry for the previous upload and a new changelog entry marking this as a revert, could you please consolidate into a single changelog entry that only describes the differences vs current -updates?
[23:54] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64+mac [Trusty 14.04.6] has been updated (20190304.5)
[23:54] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Trusty 14.04.6] has been updated (20190304.5)
[23:54] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop i386 [Trusty 14.04.6] has been updated (20190304.5)
[23:56] -queuebot:#ubuntu-release- Builds: Ubuntu Server amd64 [Trusty 14.04.6] has been updated (20190304.2)
[23:57] -queuebot:#ubuntu-release- Builds: Ubuntu Server amd64+mac [Trusty 14.04.6] has been updated (20190304.2)
[23:57] -queuebot:#ubuntu-release- Builds: Ubuntu Server i386 [Trusty 14.04.6] has been updated (20190304.2)
[23:57] -queuebot:#ubuntu-release- Builds: Ubuntu Server powerpc [Trusty 14.04.6] has been updated (20190304.2)
[23:57] -queuebot:#ubuntu-release- Builds: Ubuntu Server ppc64el [Trusty 14.04.6] has been updated (20190304.2)