[01:18] <vorlon> why does kitty, in universe, trigger an apport autopkgtest. :|
[01:19] <vorlon> Provides: x-terminal-emulator
[01:19] <vorlon> siiiiiigh
[01:26] <Eickmeyer> vorlon: I was wondering the same thing. It's merely a terminal emulator.
[01:31] <vorlon> yeah this is the 'autopkgtest picks up all provides and non-default alternatives' thing
[01:31] <Eickmeyer> *facepalm*
[01:32] <vorlon> I don't think I can actually argue that it's incorrect.  It's just annoying when it's slowing things down
[01:32] <Eickmeyer> Yep. It's keeping python-defaults from migrating, which is keeping hugin from migrating, which is keeping ubuntustudio from building.
[01:33] <Eickmeyer> I've been keeping an eye on the excuses today.
[01:34] <vorlon> kitty already passed on a retry, and I've pushed a skiptest for omniorb-dfsg
[01:34] <Eickmeyer> Oh, perfect.
[01:35] <Eickmeyer> python-bumps is having... bumps.
[11:50] <LocutusOfBorg> sigh, gnat
[11:53] <ricotz> hello ubuntu-archive, please reject the libroffice package of 2023-01-19 from jammy/unapproved - https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=libreoffice
[11:55] -queuebot:#ubuntu-release- Unapproved: libreoffice (jammy-proposed/main) [1:7.4.4-0ubuntu0.22.10.2~bpo22.04.1 => 1:7.3.7-0ubuntu0.22.04.2] (ubuntu-desktop)
[11:56] -queuebot:#ubuntu-release- Unapproved: rejected libreoffice [source] (jammy-proposed) [1:7.3.7-0ubuntu0.22.04.2]
[12:02] <seb128> ricotz, ^
[12:02] <ricotz> seb128, ty
[12:24] <kanashiro[m]> ubuntu-archive: could you please remove ruby-defaults from sync-blacklist.txt? I need to sync it from Debian unstable now
[12:24] <kanashiro[m]> https://bazaar.launchpad.net/~ubuntu-archive/+junk/sync-blacklist/view/head:/sync-blacklist.txt#L653
[12:24] <kanashiro[m]> https://bazaar.launchpad.net/~ubuntu-archive/+junk/sync-blacklist/view/head:/sync-blacklist.txt#L737
[13:40] <vorlon> kanashiro[m]: done
[13:47] <kanashiro[m]> vorlon: ty!
[14:18] <kanashiro[m]> vorlon: there is still this occurrence of ruby-defaults in that file: https://bazaar.launchpad.net/~ubuntu-archive/+junk/sync-blacklist/view/head:/sync-blacklist.txt#L734
[14:21] <vorlon> we had it blacklisted twice? oh well then
[14:22] <vorlon> kanashiro[m]: fixed harder
[14:22] <kanashiro[m]> it seems so
[14:22] <kanashiro[m]> thanks!
[14:24] <tsimonq2> Not sure if autosync is still off, but sip6/pyqt5 should finally unstick things once synced
[14:25] -queuebot:#ubuntu-release- Unapproved: rejected docker.io [source] (bionic-proposed) [20.10.21-0ubuntu1~18.04.2]
[14:26] -queuebot:#ubuntu-release- Unapproved: docker.io (bionic-proposed/universe) [20.10.21-0ubuntu1~18.04.1 => 20.10.21-0ubuntu1~18.04.2] (no packageset)
[14:31] <vorlon> hopeful for a successful gprbuild/s390x autopkgtest run with --all-proposed
[14:32] <vorlon> LocutusOfBorg: fwiw 'retry-autopkgtest-regressions --all-proposed | grep gprbuild' gives you a single run which gathers up all relevant triggers into a single request, a bit more efficient...
[14:32] <vorlon> (since you're already doing --all-proposed, there's no reason to have separate runs)
[14:33] <vorlon> hmm some of these logs are still showing conflicts with gnat-11
[14:34] <vorlon> unreproducible in a lunar container :P
[14:35] <vorlon> gnat is already the newest version (11.2ubuntu1).
[14:35] <vorlon> what is this lie
[14:47] <vorlon> skiptesting everything related to gprbuild/s390x, I don't know why this failed only on s390x but it's testbed / apt config nonsense and not worth blocking on
[14:49] <bdmurray> I've seen an autopkgtest failure or with a kernel panic `Begin: Running /scripts/init-bottom ... [   42.658620] mv invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=0`
[14:49] <bdmurray> https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/i/initramfs-tools/20230202_100732_4ba12@/log.gz
[15:02] -queuebot:#ubuntu-release- Unapproved: accepted docker.io [source] (bionic-proposed) [20.10.21-0ubuntu1~18.04.2]
[15:26] <LocutusOfBorg> vorlon, this is true, but I sometime fail to get output from the retry-autopkgtest-regressions script
[15:26] <LocutusOfBorg> and yes, locally it doesn't have the conflict issue, on s390x environment
[15:27] <LocutusOfBorg> so we are waiting for pyqt5 now?
[15:31] <bdmurray> LocutusOfBorg: "fail to get output"?
[15:33] <vorlon> bdmurray: the filtering to avoid duplicate requests sometimes goes awry
[15:35] <LocutusOfBorg> sometimes the script returns "null"
[15:36] <LocutusOfBorg> maybe arraybolt3 or arraybolt3[m] can have a look at lubuntu-update-notifier sadness on amd64 autopkgtests?
[15:37] <LocutusOfBorg> https://autopkgtest.ubuntu.com/packages/l/lubuntu-update-notifier/lunar/arm64
[15:37] <LocutusOfBorg> I can't reproduce locally tbh
[15:39] <LocutusOfBorg> for pyqt5 regression of pyspread we probably need 5.15.8+dfsg-2
[15:42] <LocutusOfBorg> pyqt5/sip6 uploaded
[16:08] -queuebot:#ubuntu-release- New binary: uwsgi [amd64] (lunar-proposed/universe) [2.0.21-4] (no packageset)
[16:09] -queuebot:#ubuntu-release- New binary: uwsgi [armhf] (lunar-proposed/universe) [2.0.21-4] (no packageset)
[16:09] -queuebot:#ubuntu-release- New binary: uwsgi [s390x] (lunar-proposed/universe) [2.0.21-4] (no packageset)
[16:12] -queuebot:#ubuntu-release- New binary: uwsgi [ppc64el] (lunar-proposed/universe) [2.0.21-4] (no packageset)
[16:19] -queuebot:#ubuntu-release- New binary: uwsgi [arm64] (lunar-proposed/universe) [2.0.21-4] (no packageset)
[16:20] -queuebot:#ubuntu-release- New: accepted uwsgi [amd64] (lunar-proposed) [2.0.21-4]
[16:20] -queuebot:#ubuntu-release- New: accepted uwsgi [armhf] (lunar-proposed) [2.0.21-4]
[16:20] -queuebot:#ubuntu-release- New: accepted uwsgi [s390x] (lunar-proposed) [2.0.21-4]
[16:21] -queuebot:#ubuntu-release- New: accepted uwsgi [arm64] (lunar-proposed) [2.0.21-4]
[16:21] -queuebot:#ubuntu-release- New: accepted uwsgi [ppc64el] (lunar-proposed) [2.0.21-4]
[16:24] <arraybolt3> LocutusOfBorg: wrt lubuntu-update-notifier sadness on PyQt5, I also could not reproduce locally and asked vorlon to trigger an --all-proposed autopkgtest retry. All that seemed to do was cause another failure but this time because of a quirk in the infra (the failure was obviously not an actual failure, I think it was some "could not retrieve file" something or other).
[16:25] <arraybolt3> I don't even see how the failure in there has anything to do with PyQt5, but I was unable to make it fail no matter what I did.
[16:27] <arraybolt3> Hmm, though I thought I was looking at a Bash error or something, now that i look closer, it might be an actual failure...
[16:45] <arraybolt3> Since I can't reproduce the failure locally, I just did an upload that adds more info to the autopkgtest output so that hopefully the logs tell us what's happening when the test runs in production.
[16:46] <tsimonq2> arraybolt3: The arm64 failure?
[16:47] <tsimonq2> LocutusOfBorg: not probably, we definitely need the two aforementioned uploads ;)
[16:47] <arraybolt3> tsimonq2: NO, the apt-check failure.
[16:48] <tsimonq2> arraybolt3: I'll follow up in l-devel
[16:51] -queuebot:#ubuntu-release- Unapproved: rejected grub2 [source] (jammy-proposed) [2.06-2ubuntu7.2]
[16:52] -queuebot:#ubuntu-release- Unapproved: grub2 (jammy-proposed/main) [2.06-2ubuntu7.1 => 2.06-2ubuntu7.2] (core, i386-whitelist)
[17:00] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [source] (jammy-proposed) [2.06-2ubuntu7.2]
[17:03] -queuebot:#ubuntu-release- Unapproved: grub2 (focal-proposed/main) [2.04-1ubuntu26.16 => 2.04-1ubuntu26.17] (core)
[17:08] <LocutusOfBorg> tsimonq2, arraybolt3 yes, the apt-check is transient, the other one is a failure in sip
[17:08] <LocutusOfBorg> so, meh and upload and wait
[17:11] -queuebot:#ubuntu-release- Unapproved: accepted golang-github-openshift-imagebuilder [source] (focal-proposed) [1.1.0-2ubuntu0.20.04.2]
[17:21] <arraybolt3> LocutusOfBorg: Hmm, I didn't even see the other failure, so I thought the apt-check thing was the only thing going wrong.
[17:22] -queuebot:#ubuntu-release- Unapproved: rejected grub2 [source] (focal-proposed) [2.04-1ubuntu26.17]
[17:23] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [source] (focal-proposed) [2.04-1ubuntu26.17]
[17:24] <LocutusOfBorg> autopkgtest for pyspread/2.1.1-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Not a regression, ppc64el: Regression ♻ , s390x: Regression ♻
[17:24] -queuebot:#ubuntu-release- New binary: uwsgi-plugin-php [amd64] (lunar-proposed/universe) [0.0.15] (no packageset)
[17:24] <LocutusOfBorg> arraybolt3, ^^ :)
[17:24] <LocutusOfBorg> and its due to a problem in pyside2, introduced by a problem of sip6
[17:25] <LocutusOfBorg> so, upload and rebuild is needed
[17:25] -queuebot:#ubuntu-release- Unapproved: accepted golang-github-fsouza-go-dockerclient [source] (focal-proposed) [1.6.0-2ubuntu0.20.04.2]
[17:25] <LocutusOfBorg> (and probably stopping autosync until the migration happens is something to be done)
[17:25] <arraybolt3> Oh. I must be missing backlog, since that has nothing to do with what I thought we were talking about :P Sorry.
[17:26] -queuebot:#ubuntu-release- New binary: uwsgi-plugin-php [armhf] (lunar-proposed/universe) [0.0.15] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: uwsgi-plugin-php [s390x] (lunar-proposed/universe) [0.0.15] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: uwsgi-plugin-php [ppc64el] (lunar-proposed/universe) [0.0.15] (no packageset)
[17:26] <LocutusOfBorg> arraybolt3, pyside2 regressed two autopkgtests, one we spoke about apt-foo, the other was another regression in pyside2 itself
[17:26] <LocutusOfBorg> so, giving back your apt-check test is not useful since we rebuild pyside2 anyway
[17:26] <LocutusOfBorg> and with pyside2 I mean pyqt5
[17:27] -queuebot:#ubuntu-release- New binary: uwsgi-plugin-php [arm64] (lunar-proposed/universe) [0.0.15] (no packageset)
[17:28] <arraybolt3> K, I hope that works. I'm worried that maybe it's not PyQt5's fault at all, but the way the regressions are happening does seem to imply that it is.
[17:28] <arraybolt3> (Sorry if I sound inexperienced, I've not hardly worked with autopkgtests in the past, I'm just learning how to use them now.)
[17:28] <LocutusOfBorg> arraybolt3, I couldn't reproduce locally, so I agree
[18:15] <Eickmeyer> Looks like hypothesis is the major hurdle for python3-defaults.
[18:18] <tsimonq2> Eickmeyer: Uh, how?
[18:18] <tsimonq2> skiptest is put in place, aren't we waiting on pyqt5?
[18:19] <Eickmeyer> tsimonq2: If there's skiptest in place, then that's surprising as it's still showing regressions on all Britney outputs for over the past 24 hours.
[18:20] <tsimonq2> It's still going to show the regressions, it just doesn't care about them.
[18:20] <Eickmeyer> Ok. Well, I still doubt it'll migrate.
[18:20] <tsimonq2> skiptest likely means "skip the autopkgtest Britney policy when considering this"
[18:22] <Eickmeyer> Nvm, it's pyqt5 we're waiting on now.
[18:22] <tsimonq2> I just said that... ;)
[18:22] <Eickmeyer> I didn't investigate deep enough. *facepalm*
[18:22] -queuebot:#ubuntu-release- New: accepted uwsgi-plugin-php [amd64] (lunar-proposed) [0.0.15]
[18:22] -queuebot:#ubuntu-release- New: accepted uwsgi-plugin-php [armhf] (lunar-proposed) [0.0.15]
[18:22] -queuebot:#ubuntu-release- New: accepted uwsgi-plugin-php [s390x] (lunar-proposed) [0.0.15]
[18:22] -queuebot:#ubuntu-release- New: accepted uwsgi-plugin-php [arm64] (lunar-proposed) [0.0.15]
[18:22] -queuebot:#ubuntu-release- New: accepted uwsgi-plugin-php [ppc64el] (lunar-proposed) [0.0.15]
[18:31] <vorlon> LocutusOfBorg: autosync is already turned off ftr
[18:31] <LocutusOfBorg> oh nice!
[18:32] <LocutusOfBorg> vorlon, do you think we can remove uwsgi-plugin-luajit on ppc64el?
[18:32] <LocutusOfBorg> not yet done in Debian (I pinged maintainer on irc #-devel)
[18:33] <LocutusOfBorg> Missing build dependencies: libluajit-5.1-dev
[18:33] <LocutusOfBorg> this is not going to build ppc64el anytime soon
[18:33] <vorlon> looking
[18:33] <vorlon> LocutusOfBorg: I don't see anything to remove
[18:34] <Eickmeyer> I just got the build failure email. Removing hugin from Ubuntu Studio to get it to build.
[18:34] <LocutusOfBorg> vorlon, its in release?
[18:34] <vorlon> LocutusOfBorg: not according to rmadison
[18:34] <LocutusOfBorg> meh strange
[18:34] <LocutusOfBorg> https://launchpad.net/ubuntu/+source/uwsgi-plugin-luajit/0.0.7build1
[18:34] <vorlon> LocutusOfBorg: what are you seeing that tells you it's there?
[18:34] <LocutusOfBorg> I see it here
[18:34] <vorlon> you see that it was built
[18:34] <LocutusOfBorg> ohhhhhhhhhhhhhhh
[18:34] <LocutusOfBorg> :D
[18:34] <vorlon> but the binary was removed, probably from a previous request of yours :)
[18:35] <LocutusOfBorg> I though after removal somebody was doing no change rebuild to avoid confusion
[18:35] <LocutusOfBorg> thanks!
[18:36] <LocutusOfBorg> so, bpftrace now back in sync with Debian
[18:36] <LocutusOfBorg> sip6/pyqt5 building, but will take 18 hours to complete riscv
[18:36] <LocutusOfBorg> paraview might now build on riscv64
[18:36] -queuebot:#ubuntu-release- Unapproved: rejected bind9 [source] (focal-proposed) [1:9.16.1-0ubuntu2.12]
[18:36] <LocutusOfBorg> don't see any other blocker for big migration?
[18:37] <LocutusOfBorg> (uwsgi fixed)
[18:38] <LocutusOfBorg> if anybody can see if we have other blockers, please write them here
[19:09] -queuebot:#ubuntu-release- Unapproved: bind9 (focal-proposed/main) [1:9.16.1-0ubuntu2.12 => 1:9.16.1-0ubuntu2.13] (core, i386-whitelist)
[19:30] -queuebot:#ubuntu-release- Unapproved: neutron (focal-proposed/main) [2:16.4.2-0ubuntu5 => 2:16.4.2-0ubuntu6] (openstack, ubuntu-server)
[20:00] -queuebot:#ubuntu-release- Unapproved: accepted squid [source] (jammy-proposed) [5.2-1ubuntu4.3]
[20:10] <ricotz> LocutusOfBorg, I think you want to cancel that https://launchpad.net/ubuntu/+source/pyqt5/5.15.8+dfsg-2~build1/+build/25542934
[20:27] <LocutusOfBorg> ricotz, the builders are not busy, and that build is like one hour older of the newer sync one
[20:27] <LocutusOfBorg> so, its like watching the future :D
[20:39] <ricotz> LocutusOfBorg, seems like a waste if this is going to run 18 hours as you mentioned
[20:40] <LocutusOfBorg> feel free to cancel it :)
[20:41] <ricotz> I don't have the rights to do so
[20:55] <LocutusOfBorg> done
[21:39] -queuebot:#ubuntu-release- New binary: ruby-psych [amd64] (lunar-proposed/universe) [5.0.2-1build1] (no packageset)
[21:39] <bdmurray> ginggs: I see you requested finalcif be run - how did you end up there? I'm dealing with an issue where some tests are OOM'ing and the test environment is handling that differently.
[21:40] <bdmurray> ginggs: I've added finalcif to big_packages and was wondering if you might have found a list of packages that might need to be in big because reading journalctl is lame.
[22:11] -queuebot:#ubuntu-release- Unapproved: pivy (jammy-proposed/universe) [0.6.5-1build6 => 0.6.5-1ubuntu0.22.04.1] (no packageset)
[22:12] -queuebot:#ubuntu-release- Unapproved: pivy (kinetic-proposed/universe) [0.6.7-0.1 => 0.6.7-0.1ubuntu0.1] (no packageset)
[22:24] <vorlon> kanashiro[m]: reverting your protobuf upload, protobuf is part of the python3 transition
[22:41] <kanashiro[m]> vorlon: sorry, my script goes through all ruby rdeps and protobuf is one of them