[05:34] <LocutusOfBorg> libghc-gitit-dev/amd64 has unsatisfiable dependency
[05:34] <LocutusOfBorg> vorlon, ^^ rebuilt gitit
[05:35] <vorlon> because of the abi instability I suppose
[07:02] -queuebot:#ubuntu-release- Unapproved: loguru (jammy-proposed/universe) [0.6.0-1 => 0.6.0-1ubuntu1] (no packageset)
[07:05] -queuebot:#ubuntu-release- Unapproved: mypy (jammy-proposed/universe) [0.942-1 => 0.942-1ubuntu1] (no packageset)
[07:59] <RAOF> If anyone felt like a quick FFe review, the Mir one should be pretty simple: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1988702
[07:59] <ubottu> Launchpad bug 1988702 in mir (Ubuntu) "FFe: Upstream 2.9.0 release" [Undecided, New]
[08:01] <RAOF> :)
[08:05] <RAOF> This GNOME MRE script is coming along nicely.
[08:05] <RAOF> 😃
[08:08] <seb128> RAOF, great!
[09:29] -queuebot:#ubuntu-release- New binary: gtksourceview5 [amd64] (kinetic-proposed/main) [5.5.1-2~fakesync1] (ubuntu-desktop)
[09:30] -queuebot:#ubuntu-release- New binary: gtksourceview5 [s390x] (kinetic-proposed/main) [5.5.1-2~fakesync1] (ubuntu-desktop)
[09:30] -queuebot:#ubuntu-release- New binary: gtksourceview5 [ppc64el] (kinetic-proposed/main) [5.5.1-2~fakesync1] (ubuntu-desktop)
[09:33] -queuebot:#ubuntu-release- New binary: gtksourceview5 [armhf] (kinetic-proposed/main) [5.5.1-2~fakesync1] (ubuntu-desktop)
[09:36] -queuebot:#ubuntu-release- New binary: gtksourceview5 [arm64] (kinetic-proposed/main) [5.5.1-2~fakesync1] (ubuntu-desktop)
[09:46] -queuebot:#ubuntu-release- New source: fonts-yas (kinetic-proposed/primary) [4.0-0ubuntu1]
[10:01] -queuebot:#ubuntu-release- New binary: gtksourceview5 [riscv64] (kinetic-proposed/main) [5.5.1-2~fakesync1] (ubuntu-desktop)
[10:13] -queuebot:#ubuntu-release- New: accepted gtksourceview5 [amd64] (kinetic-proposed) [5.5.1-2~fakesync1]
[10:13] -queuebot:#ubuntu-release- New: accepted gtksourceview5 [armhf] (kinetic-proposed) [5.5.1-2~fakesync1]
[10:13] -queuebot:#ubuntu-release- New: accepted gtksourceview5 [riscv64] (kinetic-proposed) [5.5.1-2~fakesync1]
[10:13] -queuebot:#ubuntu-release- New: accepted gtksourceview5 [arm64] (kinetic-proposed) [5.5.1-2~fakesync1]
[10:13] -queuebot:#ubuntu-release- New: accepted gtksourceview5 [s390x] (kinetic-proposed) [5.5.1-2~fakesync1]
[10:13] -queuebot:#ubuntu-release- New: accepted gtksourceview5 [ppc64el] (kinetic-proposed) [5.5.1-2~fakesync1]
[10:37] <waveform> part of the reason u-boot is currently stuck in proposed is because the version (https://launchpad.net/ubuntu/+source/u-boot/2022.07+dfsg-1ubuntu3) introduces a new binary pkg, u-boot-microchip, to support a RISC-V board -- would I be right in assuming an AA needs to ack that new package?
[10:42] <ginggs> waveform: yes, it waits here https://launchpad.net/ubuntu/kinetic/+queue
[11:26] -queuebot:#ubuntu-release- Unapproved: virtualbox (focal-proposed/multiverse) [6.1.34-dfsg-3~ubuntu1.20.04.1 => 6.1.38-dfsg-3~ubuntu1.20.04.1] (kernel-dkms, ubuntu-cloud)
[11:27] -queuebot:#ubuntu-release- Unapproved: virtualbox-ext-pack (focal-proposed/multiverse) [6.1.34-1~ubuntu1.20.04.1 => 6.1.38-1~ubuntu1.20.04.1] (no packageset)
[11:27] -queuebot:#ubuntu-release- Unapproved: virtualbox (jammy-proposed/multiverse) [6.1.34-dfsg-3~ubuntu1.22.04.1 => 6.1.38-dfsg-3~ubuntu1.22.04.1] (kernel-dkms, ubuntu-cloud)
[11:27] -queuebot:#ubuntu-release- Unapproved: virtualbox-ext-pack (jammy-proposed/multiverse) [6.1.34-1~ubuntu1.22.04.1 => 6.1.38-1~ubuntu1.22.04.1] (no packageset)
[11:27] -queuebot:#ubuntu-release- Unapproved: virtualbox-guest-additions-iso (focal-proposed/multiverse) [6.1.34-1~ubuntu1.20.04.1 => 6.1.38-1~ubuntu1.20.04.1] (no packageset)
[11:29] -queuebot:#ubuntu-release- Unapproved: virtualbox-guest-additions-iso (jammy-proposed/multiverse) [6.1.34-1 => 6.1.38-1~ubuntu1.22.04.1] (no packageset)
[11:29] -queuebot:#ubuntu-release- Unapproved: virtualbox-hwe (focal-proposed/multiverse) [6.1.34-dfsg-3~ubuntu1.20.04.1 => 6.1.38-dfsg-3~ubuntu1.20.04.1] (kernel-dkms)
[11:32] -queuebot:#ubuntu-release- Unapproved: virtualbox-hwe (jammy-proposed/multiverse) [6.1.34-dfsg-3~ubuntu1.22.04.1 => 6.1.38-dfsg-3~ubuntu1.22.04.1] (kernel-dkms)
[12:45] <waveform> ginggs, thanks! If any AA wants to take a look at u-boot-microchip in the new queue, I'd be happy to answer any questions (should be a fairly simple one; it's "yet another" u-boot binary pkg in support of a new board -- LP: #1987505 is the related bug)
[12:45] <ubottu> Launchpad bug 1987505 in u-boot (Ubuntu) "Package U-Boot for PolarFire SoC Icicle Kit" [Undecided, New] https://launchpad.net/bugs/1987505
[13:42] -queuebot:#ubuntu-release- Unapproved: jansson (jammy-proposed/main) [2.13.1-1.1build3 => 2.14-2~22.04.1] (desktop-core, i386-whitelist, ubuntu-server)
[13:51] <LocutusOfBorg> vorlon, sil2100  I would *really* appreciate virtualbox SRU review/accept for jammy/focal
[13:51] <LocutusOfBorg> the current version is broken by kernel in security pocket
[13:52] -queuebot:#ubuntu-release- New: accepted u-boot [riscv64] (kinetic-proposed) [2022.07+dfsg-1ubuntu3]
[14:00] <LocutusOfBorg> is this the ghc migration run?
[14:01] -queuebot:#ubuntu-release- New binary: sptag [amd64] (kinetic-proposed/universe) [0.0~git20220729.a192a17+ds-2] (no packageset)
[14:06] <ginggs> waveform: somebody did it ^^^
[14:06] <waveform> ginggs, thanks -- I think that was sil_2100 :)
[14:11] <LocutusOfBorg> jbicha, seb128 LP: #1988230 is now holding the whole ghc migration
[14:11] <ubottu> Launchpad bug 1988230 in glib2.0 (Ubuntu) "glib 2.73 breaks modemmanager" [High, Triaged] https://launchpad.net/bugs/1988230
[14:11] <LocutusOfBorg> shouldn't we just remove the blocking tag since new modemmanager is available?
[14:11] <jbicha> LocutusOfBorg: the new modemmanager is in kinetic-proposed, not kinetic yet. We're working on it
[14:12] <LocutusOfBorg> otherwise we can revert to old glib2.0, let ghc migrate, and restore?
[14:13] <jbicha> LocutusOfBorg: could you wait maybe one more day? if people depend on modemmanager for internet, it's not nice to break it
[14:13] <LocutusOfBorg> removing/restoring shouldn't affect end users, or not?
[14:15] <jbicha> you would need to rebuild your ghc stuff against an old glib. Or you could just wait a day
[14:15] <LocutusOfBorg> oh... I wound't know that
[14:15] <LocutusOfBorg> but is the mir getting also sorted out?
[14:16] <jbicha> Seb is going to revert the universe dependency because the MIR got stuck
[14:16] -queuebot:#ubuntu-release- Unapproved: pulseaudio (jammy-proposed/main) [1:15.99.1+dfsg1-1ubuntu1 => 1:15.99.1+dfsg1-1ubuntu2] (core, i386-whitelist)
[14:22] <LocutusOfBorg> oh ok makes sense thanks
[14:25] <jbicha> sorry for the delay, glib ended up being more disruptive than we originally thought but the good news is that it's no longer using the old pcre3
=== popey6 is now known as popey
[14:27] <LocutusOfBorg> jbicha, this is why we have devel releases, to check/build/test :)
[14:28] <LocutusOfBorg> and that pcre2/pcre3 story is really a sad story, too difficult to do the porting
[14:28] <LocutusOfBorg> same for ffmpeg 5
[14:28] <LocutusOfBorg> for ettercap I did the pcre2 move recently, hopefully bugs are now fixed
[14:29] <LocutusOfBorg> while for ffmpeg 5 I still can't make hedgewars build with it
[14:29] <LocutusOfBorg> :/
[14:52] <seb128> LocutusOfBorg, jbicha, technically glib still has known regressions around regexp handling which Marco is working on fixing upstream so letting it that version migrate isn't going to be ideal
[14:52] <seb128> but maybe it's ok and better than holding the ghc transition...
[14:56] <LocutusOfBorg> I see Marco is working right now on upstream branch (and pushing)
[14:57] <LocutusOfBorg> so maybe if we fix modemmanager to avoid universe dependency and we upload patches... we can go?
[14:57] <seb128> LocutusOfBorg, could be, but it means another upload and queue of autopkgtests triggers
[14:57] <Trevinho> per se glib changes are good to go for MM, as for gtksourceview i think we uploaded another version not-using gregex, even if not ideal isn't the best
[15:01] <seb128> Trevinho, those components have been handled so it's not the issue, more than until your branch lands there are known regressions in glib which could impact on other components
[15:59] <vorlon> seb128: I do want to get the ghc transition done and cleared off my list; can you make a call right now to whether it's better to let glib2.0 in with the potential regressions, or to temporarily pull it out of -proposed and rebuild the haskell revdeps against old glib?
[16:00] <vorlon> i.e. if you can't give me a green light right now to unblock LP: #1988230 then it's better to temporarily pull it from -proposed so I can trigger rebuilds during my workday and get ghc through
[16:00] <ubottu> Launchpad bug 1988230 in glib2.0 (Ubuntu) "glib 2.73 breaks modemmanager" [High, Triaged] https://launchpad.net/bugs/1988230
[16:40] <rs2009> any progress on fixing systemd-resolved's postinst when installing in a chroot? (to fix the livecd builds)
[16:59] <bdmurray> rs2009: There is a new version of systemd in -proposed and it is currently waiting on some autopkgtests
[17:09] <LocutusOfBorg> bdmurray, sadly systemd autopkgtests shows broken machine
[17:10] <LocutusOfBorg> No UUID given. Instance won't be deleted!
[17:10] <LocutusOfBorg> Unexpected error:
[17:10] <LocutusOfBorg> meh
[17:12] <bdmurray> LocutusOfBorg: I'm talking to enr0n about that in #ubuntu-devel
[17:47] <jbicha> vorlon: we'll drop the blocker tag today as soon as modemmanager migrates; should be soonish now that it no longer needs the universe dep
[17:52] -queuebot:#ubuntu-release- New: accepted sptag [amd64] (kinetic-proposed) [0.0~git20220729.a192a17+ds-2]
[17:52] <cjwatson> Oh yeah, that systemd-resolved fix looks pretty plausible to me
[18:01] <seb128> vorlon, what Jeremy said, let's unblock glib, we covered the known issues and we can do a follow up bugfix upload tomorrow
[18:18] <vorlon> jbicha, seb128: cheers
[18:33] <sergiodj> hello, can someone take a look at this FFe for sssd, please?  https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1988615
[18:33] <ubottu> Launchpad bug 1988615 in sssd (Ubuntu) "[FFe] Merge sssd 2.7.3-2 from Debian unstable" [Undecided, New]
[18:46] -queuebot:#ubuntu-release- New: accepted fonts-sahel [source] (kinetic-proposed) [3.4.0-0ubuntu1]
[18:46] -queuebot:#ubuntu-release- New binary: fonts-sahel [amd64] (kinetic-proposed/none) [3.4.0-0ubuntu1] (no packageset)
[19:29] -queuebot:#ubuntu-release- New sync: llvm-toolchain-15 (kinetic-proposed/primary) [1:15.0.0-1~exp1]
[20:24] <vorlon> sergiodj: I see you've identified a change in sssd that's useful to have, but what about other changes that are less important to us and introduce risk?
[20:29] -queuebot:#ubuntu-release- Unapproved: cockpit-podman (jammy-backports/universe) [51-1~bpo22.04.1 => 53-1~bpo22.04.1] (no packageset)
[20:30] -queuebot:#ubuntu-release- Unapproved: accepted cockpit-podman [source] (jammy-backports) [53-1~bpo22.04.1]
[20:31] <sergiodj> vorlon: the other upstream changes are really minor and don't introduce any new features, as far as I have investigated.  I can update the FFe bug to detail them if that's preferred.  the debian changes are also minor and the most controversial one has been reverted
[20:59] <vorlon> sergiodj: yes, please detail on the bug (and note that you consider them minor)
[20:59] <vorlon> rs2009: oh hey look https://cdimage.ubuntu.com/ubuntu-unity/daily-live/current/
[20:59] <sergiodj> vorlon: will do, thanks.
[21:00] <vorlon> rs2009: note that this is "oversized" because we do not have a size limit declared for Ubuntu Unity images so it uses the default of "CD sized"; feel free to let me know what you think the limit should be (increments of 100MB only)
[21:12] <vorlon> jbicha: are there going to be breaks: declared from libglib2.0-0 to the old modemmanager?
[21:15] -queuebot:#ubuntu-release- New: accepted fonts-yas [source] (kinetic-proposed) [4.0-0ubuntu1]
[21:16] <sergiodj> vorlon: bug updated.
[21:16] -queuebot:#ubuntu-release- New binary: fonts-yas [amd64] (kinetic-proposed/none) [4.0-0ubuntu1] (no packageset)
[21:20] <jbicha> Trevinho: ^ breaks
[21:22] -queuebot:#ubuntu-release- New: accepted fonts-sahel [amd64] (kinetic-proposed) [3.4.0-0ubuntu1]
[21:22] -queuebot:#ubuntu-release- New: accepted fonts-yas [amd64] (kinetic-proposed) [4.0-0ubuntu1]
[21:23] -queuebot:#ubuntu-release- New: accepted roger-router [sync] (kinetic-proposed) [2.4.2-3]
[21:26] -queuebot:#ubuntu-release- New binary: roger-router [amd64] (kinetic-proposed/none) [2.4.2-3] (no packageset)
[21:26] -queuebot:#ubuntu-release- New binary: roger-router [ppc64el] (kinetic-proposed/none) [2.4.2-3] (no packageset)
[21:26] -queuebot:#ubuntu-release- New binary: roger-router [s390x] (kinetic-proposed/none) [2.4.2-3] (no packageset)
[21:27] -queuebot:#ubuntu-release- New binary: roger-router [arm64] (kinetic-proposed/none) [2.4.2-3] (no packageset)
[21:28] -queuebot:#ubuntu-release- New binary: roger-router [armhf] (kinetic-proposed/none) [2.4.2-3] (no packageset)
[21:30] -queuebot:#ubuntu-release- New: accepted roger-router [arm64] (kinetic-proposed) [2.4.2-3]
[21:30] -queuebot:#ubuntu-release- New: accepted roger-router [armhf] (kinetic-proposed) [2.4.2-3]
[21:30] -queuebot:#ubuntu-release- New: accepted roger-router [amd64] (kinetic-proposed) [2.4.2-3]
[21:30] -queuebot:#ubuntu-release- New: accepted roger-router [s390x] (kinetic-proposed) [2.4.2-3]
[21:30] -queuebot:#ubuntu-release- New: accepted roger-router [ppc64el] (kinetic-proposed) [2.4.2-3]
[21:52] -queuebot:#ubuntu-release- New binary: roger-router [riscv64] (kinetic-proposed/universe) [2.4.2-3] (no packageset)
[22:20] <bdmurray> vorlon: what is being held up in -proposed?
[22:20] <vorlon> bdmurray: modemmanager, e.g.
[22:22] <bdmurray> vorlon: it looks like it is running now
[22:22] <vorlon> bdmurray: thanks
[22:22] <bdmurray> oh, sorry its network-manager triggered by modemmanager
[22:23] <vorlon> yeah
[22:23] <vorlon> I've retriggered the fwupd test
[22:23] <bdmurray> hello passed for me
[22:24] <bdmurray> https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/h/hello/20220907_212119_895ea@/log.gz
[23:08] <vorlon> LocutusOfBorg: do you happen to have any idea why various haskell packages are still blocked in -proposed as 'has unsatisfiable dependency'? (Rather rude of britney to say this without saying what dependency it thinks is unsatisfialble, since apt seems perfectly happy)
[23:11] <vorlon> LocutusOfBorg: ah I think it's an issue of ghc having migrated but having missed a publication run, making everything momentarily unhappy
[23:53] <bdmurray> I'm gonna run `retry-autopkgtest-regressions --only-unknown`