[00:05] <vorlon> LocutusOfBorg: now it's showing mpd uninstallable on ppc64el instead of riscv64, so ummmm
[03:03] <vorlon> kanashiro: fyi, it appears libruby2.7 provided some virtual packages that are not provided by libruby3.0 (at least ruby-rexml), which is invisible to reverse-depends, so now there are a significant number of uninstallables in the release pocket https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy_uninst.txt
[04:19] <doko> autopkgtest [09:47:02]: test live:  - - - - - - - - - - results - - - - - - - - - -
[04:19] <doko> live                 FAIL stderr: W: http://ddebs.ubuntu.com/dists/jammy/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
[04:19] <doko> autopkgtest [09:47:02]: test live:  - - - - - - - - - - stderr - - - - - - - - - -
[04:19] <doko> W: http://ddebs.ubuntu.com/dists/jammy/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
[04:19] <doko> W: http://ddebs.ubuntu.com/dists/jammy/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
[04:19] <doko> W: http://ddebs.ubuntu.com/dists/jammy-updates/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
[04:19] <doko> W: http://ddebs.ubuntu.com/dists/jammy/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
[04:19] <doko> W: http://ddebs.ubuntu.com/dists/jammy-updates/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
[04:19] <doko> W: http://ddebs.ubuntu.com/dists/jammy-proposed/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
[04:19] <doko> W: http://ddebs.ubuntu.com/dists/jammy/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
[04:19] <doko> W: http://ddebs.ubuntu.com/dists/jammy-updates/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
[04:19] <doko> W: http://ddebs.ubuntu.com/dists/jammy-proposed/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
[04:19] <doko> autopkgtest [09:47:02]: @@@@@@@@@@@@@@@@@@@@ summary
[04:19] <doko> something in the live builds breaks random autopkg tests ...
[04:20] <doko> https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/c/crash/20220312_094712_338dd@/log.gz
[04:35] <doko> juliank: apt changes?
[05:05] <Eickmeyer[m]> doko: I was noticing that too and migrated stored keys out of trusted.gpg. Seems a bit premature since apt-key is still a thing for now.
[08:02] <LocutusOfBorg> vorlon, I'm rebuilding them all
[09:14] <LocutusOfBorg> btw vorlon #1964624 I'm removing the block proposed tag
[09:14] <LocutusOfBorg> the sync from Debian enables it again
[16:27] <vorlon> doko: did you sync python3.10 3.10.2-6 over 3.10.2-5ubuntu1? (for some reason launchpad isn't saying in the publishing history)  and if so, what's your plan here wrt PIE?
[16:33] <vorlon> LocutusOfBorg: did you happen to go any farther on the python3-igraph vs python3-leidenalg misbuild?
[18:35] <LocutusOfBorg> vorlon, can we force the libsndio transition please?
[18:36] <LocutusOfBorg> britney logs are a lie
[19:44] <vorlon> LocutusOfBorg: you mean, force the packages that are rebuilt for the new/old soname?
[19:44] <vorlon> LocutusOfBorg: and is that a no for whether you've looked at python3-leidenalg and its wrong dependencies?
[20:32] <vorlon> LocutusOfBorg:  libsndio7.0 : Breaks: libsndio7.1 (<= 1.8.1-1~exp2) but 1.8.1-1~exp2 is to be installed
[20:34] <vorlon> LocutusOfBorg: so openal and revdeps need to transition together
[20:34] <vorlon> trying a hint for that
[21:09] <mwhudson>  i wonder what happened here https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#xmltooling
[21:09] <mwhudson> the failure looks very much like what the commit message claims to fix
[21:10] <vorlon> mwhudson: haven't had a chance to look
[21:18] <mwhudson> although the .bak in the error message is strange
[22:34] <vorlon> LocutusOfBorg: that did the trick, removing libsndio7.1 now
[23:04] <LocutusOfBorg> thanks!
[23:07] <LocutusOfBorg> vorlon, IIRC leidenalg is RC buggy in Debian too
[23:07] <LocutusOfBorg> I'll check again tomorrow after some sleep
[23:07] <vorlon> LocutusOfBorg: well, I don't think we have a python build system delta that would make it buggy only in Ubuntu; no bugs open on https://bugs.debian.org/src:python-leidenalg though
[23:16] <mwhudson> vorlon: for xmltooling i think upstream screwed up and released an unclean tarball
[23:17] <mwhudson> but poking continues
[23:18] <mwhudson> oh wait no
[23:18] <mwhudson> this test is downloading a file from the internet and doing things with it
[23:26] <vorlon> oh then let's just mark that test bad :P
[23:31] <mwhudson> vorlon: i just removed those tests
[23:31] <mwhudson> vorlon: so do what you said or wait for my package to go through, either works i guess
[23:32] <mwhudson> (also: upstream *did* screw up and release an unclean tarball, but that's not important)
[23:41] <vorlon> mwhudson: we can just wait for that to go through then