[05:20] -queuebot:#ubuntu-release- New binary: foonathan-memory [amd64] (kinetic-proposed/universe) [0.7.2-2] (no packageset)
[05:20] -queuebot:#ubuntu-release- New binary: meshoptimizer [amd64] (kinetic-proposed/universe) [0.18+dfsg-2] (no packageset)
[05:23] -queuebot:#ubuntu-release- New binary: meshoptimizer [ppc64el] (kinetic-proposed/universe) [0.18+dfsg-2] (no packageset)
[05:23] -queuebot:#ubuntu-release- New binary: meshoptimizer [s390x] (kinetic-proposed/universe) [0.18+dfsg-2] (no packageset)
[05:25] -queuebot:#ubuntu-release- New binary: foonathan-memory [s390x] (kinetic-proposed/universe) [0.7.2-2] (no packageset)
[05:25] -queuebot:#ubuntu-release- New binary: foonathan-memory [armhf] (kinetic-proposed/universe) [0.7.2-2] (no packageset)
[05:25] -queuebot:#ubuntu-release- New binary: meshoptimizer [armhf] (kinetic-proposed/universe) [0.18+dfsg-2] (no packageset)
[05:26] -queuebot:#ubuntu-release- New binary: foonathan-memory [ppc64el] (kinetic-proposed/universe) [0.7.2-2] (no packageset)
[05:26] -queuebot:#ubuntu-release- New binary: meshoptimizer [arm64] (kinetic-proposed/universe) [0.18+dfsg-2] (no packageset)
[05:27] -queuebot:#ubuntu-release- New binary: foonathan-memory [arm64] (kinetic-proposed/universe) [0.7.2-2] (no packageset)
[05:40] -queuebot:#ubuntu-release- New binary: meshoptimizer [riscv64] (kinetic-proposed/universe) [0.18+dfsg-2] (no packageset)
[05:49] -queuebot:#ubuntu-release- New binary: foonathan-memory [riscv64] (kinetic-proposed/universe) [0.7.2-2] (no packageset)
[08:45] <sil2100> Hello everyone! In some moments I will be re-spinning 22.04.1 desktop image - but this will be a non-candidate test image for the snapd OEM-install fix
[08:51] -queuebot:#ubuntu-release- Unapproved: accepted apt [source] (bionic-proposed) [1.6.16]
[08:55] <RikMills> sil2100: ack
[08:56] <RikMills> and morning :)
[09:10] <sil2100> o/
[09:12] -queuebot:#ubuntu-release- New: accepted cryptsetup [amd64] (kinetic-proposed) [2:2.5.0-1ubuntu1]
[09:12] -queuebot:#ubuntu-release- New: accepted cryptsetup [armhf] (kinetic-proposed) [2:2.5.0-1ubuntu1]
[09:12] -queuebot:#ubuntu-release- New: accepted cryptsetup [ppc64el] (kinetic-proposed) [2:2.5.0-1ubuntu1]
[09:12] -queuebot:#ubuntu-release- New: accepted cryptsetup [s390x] (kinetic-proposed) [2:2.5.0-1ubuntu1]
[09:12] -queuebot:#ubuntu-release- New: accepted cryptsetup [arm64] (kinetic-proposed) [2:2.5.0-1ubuntu1]
[09:12] -queuebot:#ubuntu-release- New: accepted cryptsetup [riscv64] (kinetic-proposed) [2:2.5.0-1ubuntu1]
[09:12] -queuebot:#ubuntu-release- New: accepted cryptsetup [i386] (kinetic-proposed) [2:2.5.0-1ubuntu1]
[09:12] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-515 [amd64] (kinetic-proposed) [515.65.01-0ubuntu2]
[09:12] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-515 [arm64] (kinetic-proposed) [515.65.01-0ubuntu2]
[09:25] -queuebot:#ubuntu-release- Unapproved: accepted cryptsetup [source] (jammy-proposed) [2:2.4.3-1ubuntu1.1]
[09:28] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Jammy 22.04.1] has been updated (20220808)
[09:56] <sil2100> mardy: hey! The new image is ready ^ and via the manifest I see the right snapd snap being pulled in "snap:snapd edge 16727"
[10:00] <sil2100> mardy: can you give it a spin?
[10:04] -queuebot:#ubuntu-release- Unapproved: snapd (focal-proposed/main) [2.55.5+20.04 => 2.56.2+22.04ubuntu1] (core)
[10:08] <sil2100> Okay, so mvo uploaded the .deb version of snapd with the fix. I'll get it into Unapproved and will build another image with it for testing purposes
[10:09] <sil2100> (possibly -proposed enabled, or maybe pulled in via a PPA)
[10:18] -queuebot:#ubuntu-release- Unapproved: rejected snapd [source] (focal-proposed) [2.56.2+22.04ubuntu1]
[10:20] -queuebot:#ubuntu-release- Unapproved: snapd (jammy-proposed/main) [2.55.5+22.04 => 2.56.2+22.04ubuntu1] (desktop-core, ubuntu-server)
[11:54] -queuebot:#ubuntu-release- Unapproved: snapd (jammy-proposed/main) [2.55.5+22.04 => 2.56.2+22.04ubuntu1] (desktop-core, ubuntu-server)
[12:04] <ahasenack> hi all, I'm on +1 maintenance this week
[12:04] <ahasenack> #PSA
[12:10] -queuebot:#ubuntu-release- Unapproved: rejected snapd [source] (jammy-proposed) [2.56.2+22.04ubuntu1]
[12:13] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (jammy-proposed) [2.56.2+22.04ubuntu1]
[12:25] <jbicha> ubuntu-archive: I need help with bug 1983372
[12:29] -queuebot:#ubuntu-release- New: accepted dkim-rotate [amd64] (kinetic-proposed) [0.4]
[12:29] -queuebot:#ubuntu-release- New: accepted foonathan-memory [amd64] (kinetic-proposed) [0.7.2-2]
[12:29] -queuebot:#ubuntu-release- New: accepted foonathan-memory [armhf] (kinetic-proposed) [0.7.2-2]
[12:29] -queuebot:#ubuntu-release- New: accepted foonathan-memory [riscv64] (kinetic-proposed) [0.7.2-2]
[12:29] -queuebot:#ubuntu-release- New: accepted meshoptimizer [amd64] (kinetic-proposed) [0.18+dfsg-2]
[12:29] -queuebot:#ubuntu-release- New: accepted meshoptimizer [armhf] (kinetic-proposed) [0.18+dfsg-2]
[12:29] -queuebot:#ubuntu-release- New: accepted meshoptimizer [riscv64] (kinetic-proposed) [0.18+dfsg-2]
[12:29] -queuebot:#ubuntu-release- New: accepted elbe-keyring [amd64] (kinetic-proposed) [20220614]
[12:29] -queuebot:#ubuntu-release- New: accepted foonathan-memory [ppc64el] (kinetic-proposed) [0.7.2-2]
[12:29] -queuebot:#ubuntu-release- New: accepted meshoptimizer [arm64] (kinetic-proposed) [0.18+dfsg-2]
[12:29] -queuebot:#ubuntu-release- New: accepted meshoptimizer [s390x] (kinetic-proposed) [0.18+dfsg-2]
[12:29] -queuebot:#ubuntu-release- New: accepted foonathan-memory [arm64] (kinetic-proposed) [0.7.2-2]
[12:29] -queuebot:#ubuntu-release- New: accepted meshoptimizer [ppc64el] (kinetic-proposed) [0.18+dfsg-2]
[12:29] -queuebot:#ubuntu-release- New: accepted foonathan-memory [s390x] (kinetic-proposed) [0.7.2-2]
[12:39] <fnordahl> Hello, I have an upload to jammy-proprosed that appears stuck, does anyone have insigths?: https://launchpadlibrarian.net/614063377/ovn_22.03.1-0ubuntu1_source.changes
[12:43] <schopin> fnordahl: from https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ovn your package FTBFS on armhf
[12:44] <schopin> Oh right, jammy, sorry :/
[12:45] <tsimonq2> https://people.canonical.com/~ubuntu-archive/pending-sru
[12:47] <tsimonq2> https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=
[12:47] <schopin> I see ovn in the unapproved queue for Jammy
[12:47] <tsimonq2> fnordahl: My best guess is that you'll see it accepted on Friday or so once 22.04.1 is out. I think they're basically only accepting security updates right now
[12:49] <sil2100> Yeah, if it's an upload in the Unapproved queue then I can try reviewing it later today, but seeing that there's 22.04.1 + matthieu out this week, I'm a bit swamped to do regular SRU shifts
[12:51] <fnordahl> thanks for the inputs. I was unaware of the ftbfs, I'll chekck those!
[13:53] <ahasenack> ubuntu-archive: hi, audacity was removed from debian testing today (https://tracker.debian.org/news/1352473/audacity-removed-from-testing/), it fails to build with current ffmpeg and needs a major version bump (3.1.3) + big patch (https://github.com/audacity/audacity/pull/3121/files)  to do so. We might consider removing it from kinetic too
[13:53] <ahasenack> reverse-depends is ugly though :(
[13:54] <ahasenack> the other option is going ahead of debian on this one, and take ownership of its maintenance
[14:16] <Eickmeyer[m]> ahasenack: Ubuntu Studio lead here. We seed audacity. I'm going to give a strenuous "NOPE" on removing it. We need to do whatever we can to keep from removing it, it's a very widely used and high-profile application.
[14:18] <ogra> there is a well maintained snap of audacity though ... (3.1.3 as well)
[14:18] <Eickmeyer[m]> It was removed from testing, but not unstable.
[14:19] <Eickmeyer[m]> ogra: I'm not going to seed a snap if a .deb exists.
[14:19] <ogra> your choice ... just wanted to point out that there is a version that works, is well maintained and would be able to update independent of the OS
[14:21] <Eickmeyer[m]> ogra: Right, I mean, if it comes down to it as "I had no choice" I'll definitely do it. :)
[14:21] <ogra> 🙂
[14:29] <ahasenack> Eickmeyer[m]: yeah, I figured once I saw the rdeps
[14:30] <Eickmeyer[m]> ahasenack: Also commented on the bug. :)
[14:30] <ahasenack> Eickmeyer[m]: do you happen to know the debian maintainer?
[14:30] <Eickmeyer[m]> ahasenack: Pretty sure it falls under the entire multimedia team.
[14:32] <ahasenack> found an older update request bug, which first highlighted that the package is stale: https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1924841
[14:33] <Eickmeyer[m]> ahasenack: Dennis Braun was last to touch the packaging. I think part of the problem is that audacity has some undesirable characteristics that hit with 3.0 that they wanted to remove, so nobody has touched it. https://salsa.debian.org/multimedia-team/audacity
[14:33] <ahasenack> ah, you even commented on the bug I just linked
[14:33] <Eickmeyer[m]> Yep, just now.
[14:34] <ahasenack> I mean, the other one: https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1924841
[14:34] <Eickmeyer[m]> Oh yeah.
[14:34] <ahasenack> wgwidgets, hm
[14:35] <ahasenack> we don't have 3.1, nor does debian
[14:35] <Eickmeyer[m]> Yeah, that's a blocker.
[14:36] <Eickmeyer[m]> Probably what's been preventing this.
[14:37] <ahasenack> and now there is 3.2, supposedly ABI stable I guess?
[14:37] <Eickmeyer[m]> That's what I'm reading too.
[14:37] <ahasenack> released July 7th 2022
[14:39]  * Eickmeyer[m] scours salsa
[14:40] <ahasenack> audacity: PKG_CONFIG "wxwidgets >= 3.1.3"
[14:40] <ahasenack> (master branch)
[14:41] <Eickmeyer[m]> ahasenack: https://salsa.debian.org/freewx-team/wxwidgets3.2
[14:41] <ahasenack> it's in the NEW pocket still
[14:42] <Eickmeyer[m]> So, we're just waiting on the FTPMasters.
[14:42] <ahasenack> for this one step, yes
[14:43] <ahasenack> we "could" go through NEW in ubuntu first, with a lower version, and sync later when debian accepts it
[14:43] <ahasenack> let me update the bug first with this info
[14:43] <Eickmeyer[m]> Ok, so there's hope. I can ping Dennis when it hits unstable, or we can JFDI.
[14:44] <Eickmeyer[m]> Or there's that option.
[14:44] <Eickmeyer[m]> Ok
[14:49] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Jammy 22.04.1] has been updated (20220808.3)
[14:52] <ahasenack> I wonder how to get notified when 3.2 is accepted from NEW
[14:52] <ahasenack> it's not in the debian tracker yet, since it's a new package
[14:52] <ahasenack> I guess I'll watch salsa for now
[14:53] <Eickmeyer[m]> Yeah, unfortunately.
[14:53] <ahasenack> ah, subscribe to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919903
[14:54] <Eickmeyer[m]> Well, that would make sense. 😅
[15:04] <mardy> sil2100: I tried the image, but unfortunately it seems that the connections are still being deleted. It's a bit of a mystery to my why this happened, but I'm looking at the logs.
[15:07] <vorlon> ogra, Eickmeyer[m]: "there is a snap" does not mean it's maintained to the standards required for seeding in images
[15:08] <Eickmeyer[m]> vorlon: Agreed. Now that I think about it, it likely doesn't have the right track for a seed anyhow.
[15:08] <ogra> vorlon, this one surely is (diddledani is one of the most reliable snap maintainers we have) 🙂 but yeah, it isnt "canonical tagged" ... i wouldnt have mentioned it if i wouldnt blindly trust the packager though
[15:09] <mardy> xnox: hi! About your comment on the systemd "default" target not being the best option, do you have a link to where you read that? Because, indeed, it looks like our workaround did not work, but I struggle to understand why.
[15:09] <vorlon> ogra: is the snap built in launchpad? do we know where the source is? does the Ubuntu community have access to patch it?  Do we have a way to apply security updates? "reliable snap maintainer" is a very small part
[15:10] <vorlon> mardy: "did not work" - was this anything other than the bootstrap problem that the snapd snap's own mount unit needs to have the right WantedBy= and therefore we have to update both the deb and the snap?
[15:10] <vorlon> (per my comment on the bug)
[15:12] <ogra> vorlon, not sure if the snap is built in LP or via GH actions ... but given diddledani waits for her final "go" to finally start working in the desktop team i bet all non-matching bits around your questions could easily be arranged 🙂 a direct link to the source is in the package description
[15:13] <ogra> either way, U-Studio prefers the deb anyway ... so this is probably moot ...
[15:14] <mardy> vorlon: no, the WantedBy= line is there, and has the expected value
[15:17] <mardy> vorlon: there is no line in the logs saying "Reached target: OEM Configuration", like what I would expect from looking at https://git.launchpad.net/ubiquity/tree/data/oem-config.target
[15:19] <mardy> I'll collect the logs and paste them
[15:37] <sil2100> mardy, vorlon: can you try the latest desktop jammy image I built?
[15:38] <sil2100> mardy, vorlon: it has the new snapd deb *only*, it's built using a PPA that should have built with -updates + snapd 2.56.2+22.04ubuntu1
[15:39] <sil2100> I can also build one with both
[15:39] <sil2100> But mvo seemed to imply only the .deb one needing to be updated
[15:43] <sil2100> Anyway, this started getting me worried, since if this by some chance does not work, we might not be able to make it for Thursday!
[15:48] <sil2100> vorlon: also, I'm thinking of releasing ubuntu-release-upgrader to -updates later today, do you think there's any risk doing that before we respin .1 candidates?
[15:48] <sil2100> Guess it could wait but then again I think we have another u-r-u fix queued up
[15:48] <arraybolt3[m]> I can test.
[15:49] <mardy> sil2100: I'll try tomorrow morning unless vorlon beats me to it
[15:49] <mardy> arraybolt3[m]: oh, super!
[15:49] <arraybolt3[m]> Gimme a minute to get set up and sync the image and I'll try whatever you want.
[15:50] <mardy> sil2100: my feeling is that the fix is just not the right one. Not sure why, but that "OEM Configuration" target does not seem to be triggered...
[15:50]  * mardy is EOD
[15:50] <sil2100> arraybolt3[m]: thanks!
[15:50] <sil2100> arraybolt3[m]: http://cdimage.ubuntu.com/jammy/daily-live/20220808.3/jammy-desktop-amd64.iso <- I guess this is the image
[15:51] <arraybolt3[m]> Thanks, that will make things easy.
[15:54] -queuebot:#ubuntu-release- Unapproved: mysql-8.0 (focal-proposed/main) [8.0.30-0ubuntu0.20.04.2 => 8.0.30-0ubuntu0.20.04.3] (i386-whitelist, ubuntu-server)
[15:55] <Eickmeyer[m]> FYI everyone: arraybolt3 became a full-fledged Lubuntu (and therefore Ubuntu) Member this weekend. Yes, that's me 100% embarrassing him. :)
[15:56] <arraybolt3[m]> LOL I didn't feel embarrassed by it. Thank you guys for everything you've done to help me get here!
[15:57] <bdmurray> sil2100: the ubuntu-release-upgrader changes are only in DistUpgradeQuirks.py which is only used during release upgrades so there is very very very little risk in releasing it before .1
[15:57] <bdmurray> sil2100: Also on Friday I noticed that the mirrors list could use an update as there were quite a few changes to the mirrors list
[15:58] <sil2100> Let me check up on the validation of u-r-u and then release it
[15:59] <sil2100> arraybolt3[m]: congrats! \o/
[15:59] <jbicha> arraybolt3[m]: welcome!
[15:59] <sil2100> It is certainly deserved
[16:00] <arraybolt3[m]> sil2100, jbicha: Thank you, glad to be here!
[16:13] <arraybolt3[m]> sil2100: zsync complete, testing VM now. Any special steps other than a simple OEM installation and then test out snaps?
[16:14] <sil2100> arraybolt3[m]: I think just the usual OEM install as you did previously, as I remember you were able to reproduce the issues
[16:14] <arraybolt3[m]> 👍️ Will report back soon.
[16:41] <arraybolt3[m]> Thanks for your patience, my first install b0rked (I think it had something to do with how I handled the VM, not with the ISO itself) and I had to do a second one. I'm almost done with the second one now.
[16:47] <sil2100> Fingers crossed!
[16:48] <arraybolt3[m]> sil2100: Well, I'm not sure if anything was supposed to happen in a log or whatever, but Firefox is launching out of the box on a fresh OEM install with the image you gave me.
[16:48] <sil2100> yaaay!
[16:48] <sil2100> vorlon: ^
[16:48] <arraybolt3[m]> snap-store also is working.
[16:48]  * sil2100 dances
[16:49] <sil2100> arraybolt3[m]: thanks for testing this! It's good news, since I was worried that by some weird chance the fix is not sufficient
[16:49] <sil2100> vorlon: can you give it a spin as well? Just to get a bit more test coverage
[16:49] <arraybolt3[m]> Sure, happy to help! That was really fun!
[16:49] <arraybolt3[m]> I'll plop my testcase on the QA tracker.
[16:59] <bdmurray> sil2100: I could test it, which image should I use?
[17:00] <sil2100> bdmurray: latest amd64 desktop image, I pasted a direct link somewhere earlier in the backlog o/
[17:00] <arraybolt3[m]> This is the one I used: http://cdimage.ubuntu.com/jammy/daily-live/20220808.3/jammy-desktop-amd64.iso (sil2100 gave me the link)
[17:01] <bdmurray> thanks
[17:11] -queuebot:#ubuntu-release- New binary: openimageio [amd64] (kinetic-proposed/universe) [2.3.17.0+dfsg-1ubuntu2] (ubuntustudio)
[17:13] -queuebot:#ubuntu-release- New binary: openimageio [s390x] (kinetic-proposed/universe) [2.3.17.0+dfsg-1ubuntu2] (ubuntustudio)
[17:16] <xnox> mardy, one moment please.
[17:17] <xnox> am i connected
[17:17] <xnox> is mardy still here?
[17:19] -queuebot:#ubuntu-release- New binary: openimageio [ppc64el] (kinetic-proposed/universe) [2.3.17.0+dfsg-1ubuntu2] (ubuntustudio)
[17:45] <vorlon> xnox: you ar econnected and mardy is not
[17:46] <vorlon> xnox: but if you want to argue about default.target, I'm here :)
[17:46] <bdmurray> my testing of OEM install looks good
[17:48] <vorlon> sil2100: ^
[17:48] <sil2100> \o/
[17:49] <vorlon> I'm going to do a test as well but don't expect to find anything different
[17:49] -queuebot:#ubuntu-release- New binary: openimageio [armhf] (kinetic-proposed/universe) [2.3.17.0+dfsg-1ubuntu2] (ubuntustudio)
[17:50] <xnox> vorlon:  i wrote more about it on the closed github issue. Basically default.target is a on-disk symlink, which may or may not be the target one actually booted. As one can override which target one boots to, without it being default.target. meaning for many cases we still have the bug.
[17:50] -queuebot:#ubuntu-release- New binary: openimageio [arm64] (kinetic-proposed/universe) [2.3.17.0+dfsg-1ubuntu2] (ubuntustudio)
[17:51] <vorlon> xnox: ok; how would we solve the problem more generally then?
[17:56] <vorlon> (or feel free to link me to the github issue)
[17:56] -queuebot:#ubuntu-release- New: accepted nginx [amd64] (kinetic-proposed) [1.22.0-1ubuntu1]
[17:57] -queuebot:#ubuntu-release- New: accepted openimageio [amd64] (kinetic-proposed) [2.3.17.0+dfsg-1ubuntu2]
[17:57] -queuebot:#ubuntu-release- New: accepted openimageio [armhf] (kinetic-proposed) [2.3.17.0+dfsg-1ubuntu2]
[17:57] -queuebot:#ubuntu-release- New: accepted openimageio [s390x] (kinetic-proposed) [2.3.17.0+dfsg-1ubuntu2]
[17:57] -queuebot:#ubuntu-release- New: accepted openimageio [arm64] (kinetic-proposed) [2.3.17.0+dfsg-1ubuntu2]
[17:58] -queuebot:#ubuntu-release- New: accepted openimageio [ppc64el] (kinetic-proposed) [2.3.17.0+dfsg-1ubuntu2]
[18:02] <xnox> vorlon:  see all the comments on https://github.com/snapcore/snapd/pull/12011#issuecomment-1208396784
[18:07] <jbicha> sil2100: Firefox ran fine after OEM install. I tested both with and without Internet access during install.
[18:11] <sil2100> Great news, thanks everyone!
[18:11] <sil2100> I asked Sergio from the snapd team to run their snapd SRU validation tests on it
[18:12] <sil2100> Hopefully we'll be releasable tomorrow and can spin candidate images ASAP
[18:17] <bdmurray> It'd be good to update the SRU bug - bug 1983528 w/ testing results too
[18:41] <sil2100> jbicha, arraybolt3[m]: ^
[18:41] <arraybolt3[m]> sil2100: On it.
[18:47] <sil2100> Thank you!
[19:14] -queuebot:#ubuntu-release- Unapproved: golang-1.16 (bionic-proposed/universe) [1.16.2-0ubuntu1~18.04.1 => 1.16.2-0ubuntu1~18.04.2] (no packageset)
[20:34] <vorlon> xnox: thanks, fair enough. fwiw I did find other units with WantedBy=default.target on my system so it seems we have other bugs
[20:34] <vorlon> (nvme-cli, e2fsprogs, zsys)