[05:09] <Eickmeyer> vorlon, teward: notified upstream that dragonfly-reverb, when compiled, is basically done so illegally: https://github.com/michaelwillis/dragonfly-reverb/issues/66
[05:10] <Eickmeyer> Read the backscroll. Thanks for putting this to bed (finally!). :)
[08:31] -queuebot:#ubuntu-release- New binary: linux-signed [s390x] (groovy-proposed/main) [5.8.0-18.19] (core, kernel)
[08:33] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (groovy-proposed/main) [5.8.0-18.19] (core, kernel)
[08:33] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (groovy-proposed/main) [5.8.0-18.19] (core, kernel)
[08:35] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (groovy-proposed) [5.8.0-18.19]
[08:35] -queuebot:#ubuntu-release- New: accepted linux-signed [s390x] (groovy-proposed) [5.8.0-18.19]
[08:35] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (groovy-proposed) [5.8.0-18.19]
[09:10] <xnox> vorlon:  interesting that ruby2.7 just built for you. when i try to rebuild it locally all the rubygem specification timing/date comparison fails. I wonder if it is becuase my chroots locally use GMT instead of UTC or some such.
[09:11] <xnox> anyway glad that it built fine in launchpad.
[10:27] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-450 [amd64] (focal-proposed) [450.66-0ubuntu0.20.04.1]
[10:27] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (focal-proposed/main) [5.4.0-45.49] (core, kernel)
[10:28] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-450 [i386] (focal-proposed) [450.66-0ubuntu0.20.04.1]
[10:28] -queuebot:#ubuntu-release- New binary: linux-signed [s390x] (focal-proposed/main) [5.4.0-45.49] (core, kernel)
[10:28] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (focal-proposed/main) [5.4.0-45.49] (core, kernel)
[10:28] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (focal-proposed) [5.4.0-45.49]
[10:28] -queuebot:#ubuntu-release- New: accepted linux-signed [s390x] (focal-proposed) [5.4.0-45.49]
[10:29] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (focal-proposed) [5.4.0-45.49]
[10:29] -queuebot:#ubuntu-release- New binary: linux-signed [arm64] (focal-proposed/main) [5.4.0-45.49] (core, kernel)
[10:30] -queuebot:#ubuntu-release- New: accepted linux-signed [arm64] (focal-proposed) [5.4.0-45.49]
[10:47] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-5.4 [amd64] (bionic-proposed/main) [5.4.0-45.49~18.04.2] (no packageset)
[10:48] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-5.4 [s390x] (bionic-proposed/main) [5.4.0-45.49~18.04.2] (no packageset)
[10:49] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-450 [amd64] (bionic-proposed) [450.66-0ubuntu0.18.04.1]
[10:49] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (bionic-proposed/main) [4.15.0-115.116] (core, kernel)
[10:49] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-450 [i386] (bionic-proposed) [450.66-0ubuntu0.18.04.1]
[10:49] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (bionic-proposed/main) [4.15.0-115.116] (core, kernel)
[10:49] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (bionic-proposed) [4.15.0-115.116]
[10:49] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (bionic-proposed) [4.15.0-115.116]
[10:50] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-5.4 [arm64] (bionic-proposed/main) [5.4.0-45.49~18.04.2] (no packageset)
[10:53] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-5.4 [amd64] (bionic-proposed) [5.4.0-45.49~18.04.2]
[10:53] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-5.4 [s390x] (bionic-proposed) [5.4.0-45.49~18.04.2]
[10:53] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-5.4 [arm64] (bionic-proposed) [5.4.0-45.49~18.04.2]
[11:11] <RikMills> Laney: britney runs are crashing :/
[11:17] <apw> RikMills, got a reference to 'crashing' in the log
[11:17] <RikMills> apw: https://paste.ubuntu.com/p/9qXwTy9bs6/
[11:18] <RikMills> similar in all runs from 06:40 this morning
[11:22] <apw> RikMills, and yet different specifics, odd
[11:22]  * RikMills nods
[11:23] <apw> RikMills, and it actually failed the same way at 01:40:05 and then worked the one after
[11:23] <RikMills> o_O
[11:23] <apw> RikMills, and happened yesterday too like 4 from last
[11:24] <apw> 21:16:23.log
[11:24] <apw> so randomly happening recently i think
[11:24] <RikMills> not surprised that went under the radar if only occasional until, this morning then
[11:25] -queuebot:#ubuntu-release- New binary: jollyday [amd64] (groovy-proposed/universe) [0.5.10-1] (no packageset)
[11:27] <apw> RikMills, yeah it seems to mention one then move on, which is odd
[11:27] <apw> in the next run i mean
[11:29] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [ppc64el] (xenial-proposed/main) [4.15.0-115.116~16.04.1] (kernel)
[11:29] <LocutusOfBorg> hello apw can you please NBS-proposed cleanup this one?
[11:29] <LocutusOfBorg> old binaries left on riscv64: mariadb-plugin-rocksdb (from 1:10.3.22-1ubuntu2)
[11:29] <LocutusOfBorg> upstream seems like to have decided to not support rosksdb on riscv64
[11:30] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (xenial-proposed/main) [4.15.0-115.116~16.04.1] (kernel)
[11:31] <LocutusOfBorg> the build time goes from 4 hours to 6 on riscv64
[11:35] <LocutusOfBorg> I asked to maybe reintroduce it on https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1876814
[11:36] -queuebot:#ubuntu-release- Unapproved: shim-signed (bionic-proposed/main) [1.37~18.04.7 => 1.37~18.04.8] (core)
[11:37] <RikMills> apw: the packages britney is mentioning in the crash seem to be ones that are 'grouped' from a landing ppa?
[11:38] <RikMills> apw: ha! latest run seems ok. :rolleyes
[12:01] <apw> RikMills, if it hadn't worked i was going to consider removal; if it is working ok sometimes, then we can wait on laney
[12:02] <RikMills> yeah, I saw the 4/5 fails in a row and jumped to a conclusion. fingers crossed
[12:03] <apw> RikMills, oh it was good you brought it up, as we could have missed it
[12:03] <RikMills> indeed
[12:05] <apw> RikMills, i bet there is a bug in the group-by-ppa module from the rebase, and it only triggers on some of the packages in the group; and processing order is run dependant
[12:06] <RikMills> sounds likely
[12:11] <RikMills> apw: any change you could remove the ppc64el, s390x & riscv64 release binaries of libkf5mailimporter? the version in proposed gained a build dep the depends on qtwebengine, so is no longer buildable on those architectures
[12:11] <RikMills> *any chance
[12:33] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-release-upgrader [source] (focal-proposed) [1:20.04.25]
[12:35] <sil2100> RAOF: hmmm
[12:36] <sil2100> RAOF: so I see you have removed memtest86+ from focal-proposed as per SRU verification failed - I don't think that was necessary
[12:36] <LocutusOfBorg> ubuntu-archive please old binaries left on riscv64: mariadb-plugin-rocksdb (from 1:10.3.22-1ubuntu2)
[12:36] <sil2100> RAOF: the only bug that was verification-failed from what I see was LP: #1874125, which was a bug for a no-change-rebuild
[12:37] <sil2100> RAOF: the other bug was important for our enablement of the 20.04.1 upgrades
[12:37] <sil2100> RAOF: and it was *not* verification-failed, so we need to re-include it basically with the same changes
[12:38] <sil2100> RAOF: actually, that version was verification-done...
[12:39] <sil2100> RAOF: eh, now I need to think if I can to undelete it somehow
[12:41] <sil2100> apw: do you know if we can somehow re-publish deleted package versions in the archive?
[12:46] <sil2100> cjwatson: hey! Maybe you know ^ ? Can we re-publish deleted package versions somehow?
[12:57] -queuebot:#ubuntu-release- Unapproved: accepted grubzfs-testsuite [source] (focal-proposed) [0.4.10.1]
[13:03] <sil2100> I wonder what would happen if I copy-package this with binaries to a PPA and then bin-sync back to the archive?
[13:03] <cjwatson> sil2100: in a standup, give me 20 minutes
[13:04] <sil2100> cjwatson: thanks!
[13:04] <sil2100> Ah, I forgot about --force-same-destination
[13:04] <sil2100> Maybe that would work
[13:15] <ahasenack> hi ubuntu-archive, did someone move bin:nginx-full (from src:nginx) from universe to main in groovy?
[13:16] <ahasenack> it was in universe all is life, up until groovy
[13:16] <ahasenack> and that is generating component mismatches
[13:21] <ahasenack> https://launchpad.net/ubuntu/groovy/amd64/nginx-full/1.18.0-3ubuntu1 is the last one that was in universe
[13:21] <ahasenack> https://launchpad.net/ubuntu/groovy/amd64/nginx-full/1.18.0-3ubuntu2 was in main already
[13:36] <cjwatson> sil2100: right, --force-same-destination should work as long as you also use --include-binaries so that it doesn't try to rebuild
[13:39] <sil2100> Thanks, trying that!
[13:39] <sil2100> It's always a bit scary as the binaries aren't listed when running the command
[13:40] <sil2100> But I remember that's normal
[13:40] <cjwatson> indeed, the list of binaries is guesswork
[13:43] -queuebot:#ubuntu-release- Unapproved: memtest86+ (focal-proposed/main) [5.01-3.1ubuntu1 => 5.01-3.1ubuntu2.1] (desktop-core, ubuntu-server) (sync)
[13:45] -queuebot:#ubuntu-release- Unapproved: accepted memtest86+ [sync] (focal-proposed) [5.01-3.1ubuntu2.1]
[13:47] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.15.0-115.116~16.04.1]
[13:47] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [ppc64el] (xenial-proposed) [4.15.0-115.116~16.04.1]
[13:47] <rbasak> sil2100: could I have an additional SRU hat review on https://bugs.launchpad.net/ubuntu/+source/sup-mail/+bug/1888749 please? Also this will need an AA hat review/accept as it's in NEW.
[14:02] -queuebot:#ubuntu-release- Unapproved: neutron (focal-proposed/main) [2:16.0.0-0ubuntu0.20.04.2 => 2:16.1.0-0ubuntu1] (openstack, ubuntu-server)
[14:05] <ddstreet> Laney i updated autopkgtest-cloud worker-lxd.conf to put haveged in the long_tests (and was merged), but then i re-ran haveged for armhf and it still timed out after ~3h, does the autopkgtest-cloud lxd worker need to be restarted to pick up the change? or does a different worker conf need editing or something?
[14:06] -queuebot:#ubuntu-release- Unapproved: sosreport (focal-proposed/main) [3.9.1-1ubuntu0.20.04.2 => 4.0-1~ubuntu0.20.04.1] (ubuntu-desktop, ubuntu-server)
[14:09] -queuebot:#ubuntu-release- Unapproved: glance (focal-proposed/main) [2:20.0.0-0ubuntu0.20.04.1 => 2:20.0.1-0ubuntu1] (openstack, ubuntu-server)
[14:27] <ahasenack> hi ubuntu-archive, did someone move bin:nginx-full (from src:nginx) from universe to main in groovy?
[14:27] <ahasenack> https://launchpad.net/ubuntu/groovy/amd64/nginx-full/1.18.0-3ubuntu1 is the last one that was in universe
[14:27] <ahasenack> https://launchpad.net/ubuntu/groovy/amd64/nginx-full/1.18.0-3ubuntu2 was in main already
[14:28] <seb128> ahasenack, it was not me and I don't know if we have logs for binary promotions
[14:28] <ahasenack> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#nginx
[14:29] <ahasenack> it should be reverted
[14:29] -queuebot:#ubuntu-release- Unapproved: accepted sosreport [source] (focal-proposed) [4.0-1~ubuntu0.20.04.1]
[14:29] <ahasenack> unless we discover the reason why it was moved, and perhaps sometihng else needs to be done then
[14:40] <cjwatson> seb128: We do
[14:41] <cjwatson> https://launchpad.net/ubuntu/groovy/amd64/nginx-full
[14:41] <cjwatson> Says it was vorlon
[14:42] <seb128> cjwatson, ah, thanks, I don't know how to end up there from the UI but good to know about the URL at least
[14:54] <xnox> seb128:  from build, click on binary header to get to binary, then click to it, and then history. or yeah, just construct the url
[14:57] <ahasenack> vorlon: hi, when you get online, could you please move nginx-full back to universe? See chat above. Unless I'm missing something
[15:01] -queuebot:#ubuntu-release- Unapproved: accepted rpcbind [source] (xenial-proposed) [0.2.3-0.2ubuntu0.16.04.1]
[15:02] <vorlon> ahasenack: according to https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.html something wants it in main, that's why it's promoted; work out what that is and fix it so we can demote it cleanly?
[15:03] <ahasenack> vorlon: sorry, I don't see "nginx" (subscring search) in that page, what am I missing?
[15:05] <vorlon> ahasenack: that's the point - it's not in the page, so component-mismatches does not believe it's a candidate for demotion
[15:05] <ahasenack> but it's requiring packages in universe
[15:05] <vorlon> but it's also strange that it has binary deps that are in universe and *those* are not listed for promotion
[15:05] <ahasenack> yeah
[15:05] <ahasenack> nginx-full/amd64 in main cannot depend on libnginx-mod-http-geoip2 in universe
[15:05] <ahasenack> and so on
[15:06] <cpaelzer> hi, anyone of the release team around to oconsider https://code.launchpad.net/~paelzer/britney/hints-ubuntu-groovy-vagrant-libvirt/+merge/389888 ?
[15:07] <vorlon> ahasenack: fwiw nginx-full shows up in germinate-output via supported-misc-servers.depends
[15:07] <ahasenack> hmm
[15:07] <ahasenack> let's see when that was added/changed
[15:08] <ahasenack> cpaelzer: does that ring any bell?
[15:08] <cpaelzer> I haven't committed anything yet :-)
[15:08] <cpaelzer> but I can take a look as part of the seed cleanup I do
[15:08] <ahasenack> I'm checking too
[15:09] <cpaelzer> ahasenack: ok, if you don't conclude on it let me know what I should continue tomorrow ok?
[15:10] <vorlon> I'm going to try demoting it and see what changes
[15:11] <ahasenack> grep nginx-full -r shows nothing
[15:11] <ahasenack> $ grep nginx -r .
[15:11] <ahasenack> ./platform/supported-misc-servers: * nginx
[15:11] <ahasenack> ./platform/supported-maas: * nginx-core
[15:11] <ahasenack> maybe nginx
[15:11] <cpaelzer> ahasenack: seed -> nginx -> nginx-full
[15:12] <cpaelzer> as seen in https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.groovy/all+extra
[15:12] <ahasenack> nginx has this weird depends sequence: nginx-core (>= ${source:Version}) | nginx-full (>= ${source:Version})  | ..
[15:13] <ahasenack> it's a very long a | b | c | d | ... depends line, ugh
[15:13] <cpaelzer> if it should just be nginx-core we can exchange that in the seed
[15:13] <cpaelzer> do you happen to know what the (current) preferred root package to keep in is?
[15:14] <ahasenack> no
[15:14] <ahasenack> the amount of meta packages this one has is incredible
[15:16] <tseliot> sil2100, hey, I don't know if the question you asked me still needs an answer
[15:16] <cpaelzer> ahasenack: I think you need to look into and decide which of -core/-full/-light we actually want to support and then we set that in the seed
[15:16] <cpaelzer> or it is an actual issue with a new dependency from -full
[15:16] <ahasenack> I need to understand if this changed from the previous upload to now in the pkg, or in the seeds
[15:16] <ahasenack> working on it
[15:16] <tseliot> vorlon, hi, can you approve nvidia 450 and 450-server in bionic-proposed and focal-proposed (in NEW), please?
[15:17] <ahasenack> because 1.18.0-3ubuntu2 was already in main, and that was unexpected
[15:17] <ahasenack> as 1.18.0-3ubuntu1 was in universe, and we didn't ask for any universe->main movement as we didn't expect it
[15:18] <cpaelzer> the dependency of nginx -> nginx-full (as alternative) was there quite some time
[15:19] <cpaelzer> despite the dependnecy being there in focal https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.focal/all+extra does not list it
[15:21] <cpaelzer> maybe it would be in component mismatch focal as "need to be promoted"
[15:21] <cpaelzer> is that report somewhere?
[15:22] <ahasenack> don't know
[15:22] <ahasenack> checking the diff between the nginx uploads in d/control, it's not clear to me why anything in that would have triggered this
[15:23] <cpaelzer> I have not seen a difference on that end either
[15:23] <cpaelzer> but on the three B/F/G germinate output it is way different
[15:24] <cpaelzer> e.g. bionic germinate lists nginx-full but it is not in main there - /me is puzzled
[15:24] <ahasenack> didn't rbasak say a while ago that there was something odd with germinate recently in groovy?
[15:25] <cpaelzer> I asked, in focal&groovy he was puzzled by some things missing
[15:41] <rbasak> eg. https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.eoan/rdepends/memcached/ exists but https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.focal/rdepends/memcached/ does not
[15:41] <rbasak> seeded-in-ubuntu says that memcached is no longer seeded
[15:42] <rbasak> src:memcached is still in main in Focal and in Groovy
[15:42] <rbasak> I didn't understand why this is the case
[15:44] <rbasak> memcached is still in supported-misc-servers in platform: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/platform/tree/supported-misc-servers#n36
[15:53] <rbasak> nginx is also in there via the same seed.
[15:53] <rbasak> So it sounds like it might well be the same issue to me.
[15:54] <rbasak> Though, oddly
[15:54] <rbasak> https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.groovy/rdepends/nginx/nginx does exist and lists Supported-Misc-Servers
[16:03] <sil2100> tseliot: hey! Yeah, I guess it's still something I might like to investigate
[16:05] <tseliot> sil2100, ginggs replied, but perhaps you were offline: "<ginggs> I think removing pyhst2's binaries on amd64 will allow nvidia-cuda-toolkit to migrate, and pyhst2 can migrate when n-g-d-450 and l-r-m are sorted"
[16:06] <tseliot> and 450 and the lrm should be sorted in groovy now
[16:09] <ginggs> tseliot:  a p w performed a miracle and everything migrated without having to remove pyhst2 on amd64.   as noted, pyhst2 was removed on ppc64el previously
[16:10] <tseliot> great :)
[16:11] <ginggs> tseliot: btw, I think your drivers are missing a .shlibs file
[16:11] <ginggs> you used to have https://github.com/tseliot/nvidia-graphics-drivers/blob/304-xenial/debian/nvidia-304.shlibs
[16:12] -queuebot:#ubuntu-release- Unapproved: pluma (focal-proposed/universe) [1.24.0-1 => 1.24.1-0ubuntu1] (ubuntu-mate, ubuntukylin)
[16:12] <tseliot> ginggs, that was ages ago, and a leftover from the original debian packaging, I think
[16:13] <ginggs> tseliot: i think it's still needed
[16:13] -queuebot:#ubuntu-release- Unapproved: mate-system-monitor (focal-proposed/universe) [1.24.0-1 => 1.24.1-0ubuntu1] (ubuntu-mate, ubuntukylin)
[16:13] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-450-server [source] (focal-proposed) [450.51.06-0ubuntu0.20.04.1]
[16:14] <tseliot> ginggs, does anything other than nvidia rely on those libraries?
[16:14] -queuebot:#ubuntu-release- Unapproved: mate-screensaver (focal-proposed/universe) [1.24.0-1 => 1.24.1-0ubuntu1] (ubuntu-mate)
[16:15] <ginggs> tseliot: well the one issue I recall was if one built a GL package locally, with nvidia drivers installed, it would pick up a dependency on that version of the nvidia driver, instead of libgl1
[16:17] <ginggs> tseliot: the issue i saw most recently was pyhst2 picked up a dependency on nvidia-graphics-drivers-450 instead of any nvidia driver that provides libcuda
[16:18] <vorlon> tseliot: nvidia-graphics-drivers-450-server> done
[16:18] <tseliot> ginggs, patches are welcome. I have a lot on my plate
[16:18] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-450-server [amd64] (focal-proposed/none) [450.51.06-0ubuntu0.20.04.1] (i386-whitelist)
[16:18] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-450-server [i386] (focal-proposed/none) [450.51.06-0ubuntu0.20.04.1] (i386-whitelist)
[16:19] <tseliot> vorlon, thanks, now only 450 is missing
[16:19] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-450-server [source] (bionic-proposed) [450.51.06-0ubuntu0.18.04.1]
[16:19] <ginggs> tseliot: thanks, i'll have a look
[16:19] <tseliot> great
[16:21] <vorlon> tseliot: missing> I don't see it waiting in the new queue for me in those series?
[16:22] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-450-server [i386] (focal-proposed) [450.51.06-0ubuntu0.20.04.1]
[16:22] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-450-server [amd64] (focal-proposed) [450.51.06-0ubuntu0.20.04.1]
[16:23] <tseliot> vorlon, it seems that somebody accepted them: https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/450.66-0ubuntu0.18.04.1 https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/450.66-0ubuntu0.20.04.1
[16:23] <tseliot> vorlon, they should be move to restricted though
[16:23] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-450-server [i386] (bionic-proposed/multiverse) [450.51.06-0ubuntu0.18.04.1] (no packageset)
[16:24] -queuebot:#ubuntu-release- Unapproved: rpi-eeprom (focal-proposed/multiverse) [7.8-0ubuntu0.20.04.1 => 7.8-0ubuntu0.20.04.2] (no packageset)
[16:30] <vorlon> tseliot: component fixed
[16:30] <RikMills> vorlon: could you remove the release ppc64el, s390x, riscv64 release binaries for libkf5mailimporter? proposed version can no longer build on those, as now has a build dep that requires qtwebengine
[16:32] <tseliot> vorlon, thanks!
[16:34] -queuebot:#ubuntu-release- New source: raspberrypi-userland (focal-proposed/primary) [0~20200520+git2fe4ca3-0ubuntu2~20.04.1]
[16:36] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-450-server [amd64] (bionic-proposed/multiverse) [450.51.06-0ubuntu0.18.04.1] (no packageset)
[16:38] <vorlon> RikMills: done
[16:38] <RikMills> ty!
[16:41] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-450-server [amd64] (bionic-proposed) [450.51.06-0ubuntu0.18.04.1]
[16:41] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-450-server [i386] (bionic-proposed) [450.51.06-0ubuntu0.18.04.1]
[17:09] <ahasenack> vorlon: hi, did you try the demotion of nginx-full?
[17:27] -queuebot:#ubuntu-release- Unapproved: libreoffice (focal-proposed/main) [1:6.4.5-0ubuntu0.20.04.1 => 1:6.4.6-0ubuntu0.20.04.1] (ubuntu-desktop)
[17:36] <ahasenack> I see you did
[17:50] <ahasenack> vorlon: could there be something wrong with component-mismatches? https://pastebin.ubuntu.com/p/vTKF3NDGXv/
[17:51] <ahasenack> granted that Depends line boggles my mind
[18:22] <ahasenack> vorlon: it's in main again, is that happening automatically?
[18:23] <ahasenack> https://launchpad.net/ubuntu/groovy/amd64/nginx-full
[18:40] <vorlon> ahasenack: I only demoted it for -proposed so far; I guess I should do so for release pocket also, done
[18:41] <ahasenack> ah, thanks
[18:41] <ahasenack> let's see if it behaves :)
[18:41] <Eickmeyer> sil2100: Can I get a quick ACK on SRU bug 1892949?
[19:37] <enyc> Hrrm, not sure which channel to use  ....   packages.ubuntu.com  seems broken if i'm not mistaken
[19:37] <enyc> .... come back to life eventualyl!
[19:38] <sil2100> Eickmeyer: looking
[19:39] <sarnold> enyc: broken in what way? seems to be working for me
[19:39] <sarnold> eg this gave an expected result https://packages.ubuntu.com/search?searchon=contents&keywords=do-release-upgrade&mode=exactfilename&suite=eoan&arch=any
[19:40] <enyc> sarnold: it was giving cosnsntant  internal error contant rhonda@ubuntu.com   whenevre clicking on any package details....
[19:40] <enyc> sarnold: e.g.   https://packages.ubuntu.com/virtualbox-qt       would work ... but if you then clicked on focal-updates (or any other distro)  to see actual details,   was *consistently*  failing
[19:41] <enyc> working again now!
[19:42] <sarnold> enyc: aha, hooray it's working anyway :)
[19:49] <vorlon> ahasenack: hur hur; nginx-core is arch: any, nginx-full in arch: all, so since nginx is not built on i386, the arch: all nginx that's in main tries to pull in arch: all nginx-full for installability on i38
[19:49] <vorlon> 6
[19:50] <vorlon> ahasenack: I think this is best solved by making nginx-full arch: any
[19:50] <ahasenack> but it's just a metapackage
[19:50] <vorlon> and nginx, as well
[19:50] <vorlon> yes, but it's an "arch-dependent" metapackage by virtue of i386 being messy
[19:50] <ahasenack> so it's because we don't have it on i386
[19:50] <ahasenack> more delta with debian
[19:50] <ahasenack> can't this be sorted with something in multiarch?
[19:50]  * ahasenack thinks
[19:51] <vorlon> it can't because germinate doesn't support multiarch
[19:51] <vorlon> and component-mismatches relies on germinate output
[19:51] <ahasenack> ah, that
[19:51] <ahasenack> so it is because of seeds
[19:55] <ahasenack> I'll file a bug for this, as in 2 weeks for now we will be "why is this metapackage arch any?"
[19:57] <ahasenack> vorlon: so this: https://paste.ubuntu.com/p/bbJNQ2RFRt/
[19:59] <Eickmeyer> vorlon, teward: I've been hit with a huge surprise. The dragonfly-reverb developers are switching Noto Sans to Bitstream Vera as of right now. I took a cursory glance at the license, and it seems to be GPL-compatible. Thoughts?
[20:07] -queuebot:#ubuntu-release- Unapproved: accepted ubuntustudio-default-settings [source] (focal-proposed) [20.04.2.2]
[20:12] <teward> vorlon: ahasenack: Debian upstream's your next hop :p
[20:12] <teward> get them to make the change for nginx metapackage any
[20:12] <teward> then we'll trickle in the change
[20:12] <ahasenack> teward: they will never take this, i386 isn't a problem they have
[20:12] <teward> because I don't know if it causes problems in Debian
[20:12] <teward> ahasenack: the 'maintainership' has changed, they might
[20:12] <teward> also
[20:12] <teward> >teward: they will never take this, i386 isn't a problem they have
[20:12] <teward> you haven't asked
[20:12] <teward> them
[20:12] <teward> sooooooooooooo
[20:12] <teward> **try**?
[20:12] <ahasenack> I tried for othe rpackages
[20:13] <ahasenack> but sure, it varies
[20:13] <teward> we're trying to *reduce* the deltas not introducing *new* deltas
[20:13] <ahasenack> since maintainers are different
[20:13] <teward> ahasenack: TO BE FAIR
[20:13] <teward> a lot of our delta was absorbed upstream
[20:13] <teward> SO
[20:13] <teward> s/upstream/in Debian/
[20:13] <teward> if you haven't tried
[20:13] <teward> you're going to get the standard "Ask Debian" reply that is typical of upstreaming things :p
[20:14] <sarnold> o/~ to be faaaaair o/~
[20:14] <teward> *yeets sarnold into /dev/null* :P
[20:14] <teward> for reasons
[20:14] <teward> ahasenack: if the argument can be made in a way that makes sense i'm pretty sure they won't object
[20:15] <teward> ahasenack: i can reach out to them if you REALLY want me to
[20:15] <teward> but i'm currently on a conference call for security issues @ work
[20:16] <ahasenack> don't even know yet if this works
[20:21] <Eickmeyer> sil2100: Hey! Where did we land?
[20:22] <Eickmeyer> nm, just got the email. :D
[20:46] <ahasenack> teward: uploaded, let's see if the component mismatch is gone by tomorrow (https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.html)
[20:46] <ahasenack> then we can talk about debian :)
[20:47] <teward> ahasenack: um
[20:47] <teward> you broke it
[20:47] <teward> nginx-full has third party components not permitted to be in main
[20:47] <teward> nginx-core's the only Main-permitted flavor
[20:47] <teward> sarnold can attest to that 'cause sarnold handled the initial MIR in 14.04 cycle
[20:48] <teward> (nginx-full also is NOT a metapackage, because not all modules are 'dynamic' and are statically compiled in)
[20:48] <teward> so if you are treating nginx-full as a metapackage, you are doing it wrong.
[20:48] <teward> (`nginx-core | nginx-full | nginx-light | nginx-extras` is the dependencies for a reason for the `nginx` metapackage in that order)
[20:48] <ahasenack> teward: hold
[20:49] <ahasenack> I do NOT want nginx-full in main
[20:49] <teward> then i wonder why it's calling a misma... ohhhhhhhhhhhhhhhhhhhh sorry
[20:49] <teward> i derped (E:DeadBrain)
[20:49] <ahasenack> something was pulling it into main, and we didn't know why
[20:49] <ahasenack> see vorlon's diagnostic/troubleshooting above
[20:50] <ahasenack> see the dance between main and universe here: https://launchpad.net/ubuntu/groovy/amd64/nginx-full
[20:50] <teward> o.O
[20:50] <teward> yeah as i said, i derped and misread
[20:51] <ahasenack> cool :)
[21:13] -queuebot:#ubuntu-release- Unapproved: cloud-init (focal-proposed/main) [20.2-45-g5f7825e2-0ubuntu1~20.04.1 => 20.3-2-g371b392c-0ubuntu1~20.04.1] (core, edubuntu, ubuntu-cloud)
[21:16] <LocutusOfBorg> vorlon, pleeeeeeease old binaries left on riscv64: mariadb-plugin-rocksdb (from 1:10.3.22-1ubuntu2)
[21:39] <vorlon> LocutusOfBorg: oops, had tried to do this once already but fat-fingered the command and hadn't looked at error output. done now
[21:40] <LocutusOfBorg> lovely thanks
[21:42] <vorlon> Eickmeyer: yes, bitstream vera license is GPL-compatible, so that would be fine
[21:43] <Eickmeyer> vorlon: Ok, I'll respond accordingly.
[22:05] <Eickmeyer> vorlon: Is Debian Import Freeze in effect yet?
[22:05] <Eickmeyer> Really, anybody can answer this question ^
[22:05] <vorlon> Eickmeyer: no, but will take effect before end of the day
[22:06] <Eickmeyer> vorlon: Ok, lsp-plugins has an upgradabilty issue that has been solved by the latest upload of lsp-plugins to Sid.
[22:07] <vorlon> well, the Debian archive only gets refresh 4x daily, so if it hasn't already synced, you should assume the need to follow up with a manual sync
[22:07] <Eickmeyer> Ok, that makes sense. Thanks.
[22:09]  * enyc meows!
[22:44] -queuebot:#ubuntu-release- Unapproved: cloud-init (xenial-proposed/main) [20.2-45-g5f7825e2-0ubuntu1~16.04.1 => 20.3-2-g371b392c-0ubuntu1~16.04.1] (edubuntu, ubuntu-cloud, ubuntu-server)
[22:52] -queuebot:#ubuntu-release- Unapproved: cloud-init (bionic-proposed/main) [20.2-45-g5f7825e2-0ubuntu1~18.04.1 => 20.3-2-g371b392c-0ubuntu1~18.04.1] (edubuntu, ubuntu-cloud, ubuntu-server)
[22:52] <blackboxsw_> Hi vorlon or any other SRU vanguard around, if there is time today. We just queued uploads into -proposed for xenial bionic and focal for cloud-init 20.3 as part of https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1893064 if someone would be able to let this uploads in to start "-proposed" aging and SRU verification we'll  be able to start our verification sooner and potentially release next week.
[23:22] -queuebot:#ubuntu-release- New binary: mutter [s390x] (groovy-proposed/main) [3.37.91-1ubuntu1] (desktop-core, desktop-extra)
[23:25] -queuebot:#ubuntu-release- New binary: mutter [amd64] (groovy-proposed/main) [3.37.91-1ubuntu1] (desktop-core, desktop-extra)
[23:26] -queuebot:#ubuntu-release- New binary: mutter [ppc64el] (groovy-proposed/main) [3.37.91-1ubuntu1] (desktop-core, desktop-extra)
[23:39] -queuebot:#ubuntu-release- New binary: mutter [armhf] (groovy-proposed/main) [3.37.91-1ubuntu1] (desktop-core, desktop-extra)