[00:10] -queuebot:#ubuntu-release- New binary: rocalution [riscv64] (noble-proposed/universe) [5.7.1-2] (no packageset)
[00:11] -queuebot:#ubuntu-release- New: accepted rocalution [amd64] (noble-proposed) [5.7.1-2]
[00:11] -queuebot:#ubuntu-release- New: accepted rocalution [ppc64el] (noble-proposed) [5.7.1-2]
[00:11] -queuebot:#ubuntu-release- New: accepted rocalution [arm64] (noble-proposed) [5.7.1-2]
[00:11] -queuebot:#ubuntu-release- New: accepted rocalution [riscv64] (noble-proposed) [5.7.1-2]
[01:23] <doko> kanashiro: what's the rationale for every no-change rebuild for dropping the old ruby version  picking up a dependency on the ruby-defaults in -proposed? that makes an awful amount of packages uninstallable and autopkg tests not being able to install packages, and failing with "unknown" versions.  this is no fun to work with
[01:48] <doko> vorlon, mwhudson: https://salsa.debian.org/toolchain-team/gcc/-/commit/d82fb8a8ab7b84f61fb8290a2c3aa2e3f54e7b8a
[01:48] <doko> that means that we are enforcing _FILE_OFFSET_BITS=64 on armhf, but not on any other architecture. Still thinking about enforcing that for our 64bit archs as well. And unsure about i386
[01:48] -ubottu:#ubuntu-release- Commit d82fb8a in toolchain-team/gcc "* Pass -D_TIME_BITS=64 together with -D_FILE_OFFSET_BITS=64 by default"
[01:55] <mwhudson> doko: does  _FILE_OFFSET_BITS=64 make any difference on our 64 bit arches?
[02:00] <doko> hmm, dpkg-buildflags doesn't pass this at all ...
[02:00] <doko> even not on i386
[02:05] <mwhudson> doko: as in its tests fail or it doesn't work?
[02:06] <doko> no, I just looked, if the flag is passed by dpkg-buildflags
[02:06] <doko> because on armhf, I have to define both flags, or else glibc raises an #error
[02:09] <mwhudson> oh i think i misparsed
[02:24] <mwhudson> i don't think we want to force the large file transition on i386 at this point do we?
[02:24] <mwhudson> afk for a bit, a bit more reachable on mm
[02:47] -queuebot:#ubuntu-release- New binary: python-maturin [amd64] (noble-proposed/universe) [1.3.2-1] (no packageset)
[02:48] -queuebot:#ubuntu-release- New binary: python-maturin [armhf] (noble-proposed/universe) [1.3.2-1] (no packageset)
[02:49] -queuebot:#ubuntu-release- New binary: python-maturin [ppc64el] (noble-proposed/universe) [1.3.2-1] (no packageset)
[02:52] -queuebot:#ubuntu-release- New binary: python-maturin [s390x] (noble-proposed/universe) [1.3.2-1] (no packageset)
[02:59] -queuebot:#ubuntu-release- New: accepted python-maturin [amd64] (noble-proposed) [1.3.2-1]
[02:59] -queuebot:#ubuntu-release- New: accepted python-maturin [ppc64el] (noble-proposed) [1.3.2-1]
[02:59] -queuebot:#ubuntu-release- New: accepted python-maturin [armhf] (noble-proposed) [1.3.2-1]
[02:59] -queuebot:#ubuntu-release- New: accepted python-maturin [s390x] (noble-proposed) [1.3.2-1]
[03:02] -queuebot:#ubuntu-release- New binary: python-maturin [arm64] (noble-proposed/universe) [1.3.2-1] (no packageset)
[03:47] -queuebot:#ubuntu-release- New: accepted python-maturin [arm64] (noble-proposed) [1.3.2-1]
[03:59] -queuebot:#ubuntu-release- New binary: haskell-reform-hsp [armhf] (noble-proposed/universe) [0.2.7.2-2build2] (no packageset)
[04:16] <doko> the ppc64el autopkg testers are unhappy: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/ppc64el/a/ansible/20240221_035828_1f136@/log.gz
[04:19] -queuebot:#ubuntu-release- New binary: python-watchfiles [amd64] (noble-proposed/universe) [0.21.0-2] (no packageset)
[04:26] -queuebot:#ubuntu-release- New: accepted haskell-reform-hsp [armhf] (noble-proposed) [0.2.7.2-2build2]
[04:26] -queuebot:#ubuntu-release- New: accepted python-watchfiles [amd64] (noble-proposed) [0.21.0-2]
[04:29] -queuebot:#ubuntu-release- New binary: python-watchfiles [arm64] (noble-proposed/universe) [0.21.0-2] (no packageset)
[04:31] -queuebot:#ubuntu-release- New: accepted python-watchfiles [arm64] (noble-proposed) [0.21.0-2]
[05:26] -queuebot:#ubuntu-release- New binary: libjwt [amd64] (noble-proposed/universe) [1.17.0-2] (kubuntu)
[05:28] -queuebot:#ubuntu-release- New binary: laniakea-spark [amd64] (noble-proposed/none) [0.1.1-1] (no packageset)
[05:29] -queuebot:#ubuntu-release- New binary: libjwt [arm64] (noble-proposed/universe) [1.17.0-2] (kubuntu)
[05:29] -queuebot:#ubuntu-release- New binary: libjwt [ppc64el] (noble-proposed/universe) [1.17.0-2] (kubuntu)
[05:29] -queuebot:#ubuntu-release- New binary: libjwt [armhf] (noble-proposed/universe) [1.17.0-2] (kubuntu)
[05:30] -queuebot:#ubuntu-release- New binary: ikos [amd64] (noble-proposed/multiverse) [3.2-3] (no packageset)
[05:31] -queuebot:#ubuntu-release- New binary: libjwt [s390x] (noble-proposed/universe) [1.17.0-2] (kubuntu)
[05:37] -queuebot:#ubuntu-release- New binary: ikos [armhf] (noble-proposed/multiverse) [3.2-3] (no packageset)
[05:37] -queuebot:#ubuntu-release- New binary: ikos [ppc64el] (noble-proposed/multiverse) [3.2-3] (no packageset)
[05:44] -queuebot:#ubuntu-release- New binary: ikos [s390x] (noble-proposed/multiverse) [3.2-3] (no packageset)
[05:45] -queuebot:#ubuntu-release- New binary: gcl27 [amd64] (noble-proposed/universe) [2.7.0-12] (no packageset)
[05:45] -queuebot:#ubuntu-release- New binary: ikos [arm64] (noble-proposed/multiverse) [3.2-3] (no packageset)
[05:50] -queuebot:#ubuntu-release- New binary: libjwt [riscv64] (noble-proposed/universe) [1.17.0-2] (kubuntu)
[06:22] -queuebot:#ubuntu-release- New binary: gcl27 [s390x] (noble-proposed/universe) [2.7.0-12] (no packageset)
[06:43] -queuebot:#ubuntu-release- New: accepted gcl27 [amd64] (noble-proposed) [2.7.0-12]
[06:43] -queuebot:#ubuntu-release- New: accepted ikos [amd64] (noble-proposed) [3.2-3]
[06:44] -queuebot:#ubuntu-release- New: accepted ikos [armhf] (noble-proposed) [3.2-3]
[06:44] -queuebot:#ubuntu-release- New: accepted ikos [s390x] (noble-proposed) [3.2-3]
[06:44] -queuebot:#ubuntu-release- New: accepted libjwt [amd64] (noble-proposed) [1.17.0-2]
[06:44] -queuebot:#ubuntu-release- New: accepted libjwt [armhf] (noble-proposed) [1.17.0-2]
[06:44] -queuebot:#ubuntu-release- New: accepted libjwt [riscv64] (noble-proposed) [1.17.0-2]
[06:44] -queuebot:#ubuntu-release- New binary: gcl27 [ppc64el] (noble-proposed/universe) [2.7.0-12] (no packageset)
[06:44] -queuebot:#ubuntu-release- New: accepted gcl27 [s390x] (noble-proposed) [2.7.0-12]
[06:44] -queuebot:#ubuntu-release- New: accepted ikos [ppc64el] (noble-proposed) [3.2-3]
[06:44] -queuebot:#ubuntu-release- New: accepted libjwt [arm64] (noble-proposed) [1.17.0-2]
[06:44] -queuebot:#ubuntu-release- New: accepted libjwt [s390x] (noble-proposed) [1.17.0-2]
[06:44] -queuebot:#ubuntu-release- New: accepted ikos [arm64] (noble-proposed) [3.2-3]
[06:44] -queuebot:#ubuntu-release- New: accepted libjwt [ppc64el] (noble-proposed) [1.17.0-2]
[06:44] -queuebot:#ubuntu-release- New: accepted laniakea-spark [amd64] (noble-proposed) [0.1.1-1]
[06:44] -queuebot:#ubuntu-release- New: accepted gcl27 [ppc64el] (noble-proposed) [2.7.0-12]
[07:53] -queuebot:#ubuntu-release- New binary: rpds-py [amd64] (noble-proposed/universe) [0.12.0-3] (no packageset)
[07:54] -queuebot:#ubuntu-release- New binary: rpds-py [arm64] (noble-proposed/universe) [0.12.0-3] (no packageset)
[07:54] -queuebot:#ubuntu-release- New binary: rpds-py [ppc64el] (noble-proposed/universe) [0.12.0-3] (no packageset)
[07:54] -queuebot:#ubuntu-release- New binary: rpds-py [s390x] (noble-proposed/universe) [0.12.0-3] (no packageset)
[08:00] -queuebot:#ubuntu-release- New binary: rpds-py [armhf] (noble-proposed/universe) [0.12.0-3] (no packageset)
[08:11] -queuebot:#ubuntu-release- New: accepted rpds-py [amd64] (noble-proposed) [0.12.0-3]
[08:11] -queuebot:#ubuntu-release- New: accepted rpds-py [armhf] (noble-proposed) [0.12.0-3]
[08:11] -queuebot:#ubuntu-release- New: accepted rpds-py [s390x] (noble-proposed) [0.12.0-3]
[08:11] -queuebot:#ubuntu-release- New: accepted rpds-py [arm64] (noble-proposed) [0.12.0-3]
[08:11] -queuebot:#ubuntu-release- New: accepted rpds-py [ppc64el] (noble-proposed) [0.12.0-3]
[08:23] <LocutusOfBorg> ubuntu-archive: please kick searx out from noble (Debian bug: #1051510). This will make flask migrate, with Python3.12 compatibility code
[08:23] -ubottu:#ubuntu-release- Debian bug 1051510 in src:searx "searx: SearX upstream is no longer maintained" [Serious, Open] https://bugs.debian.org/1051510
[09:33] <LocutusOfBorg> xnox, hello, can we please unblock boinc?
[09:33] <LocutusOfBorg> Not touching package as requested in bug 2051409 on Sat Jan 27 01:49:33 2024
[09:33] -ubottu:#ubuntu-release- Bug 2051409 in boinc (Ubuntu) "test file migrations" [Undecided, New] https://launchpad.net/bugs/2051409
[09:41] -queuebot:#ubuntu-release- Unapproved: linux-firmware (jammy-proposed/main) [20220329.git681281e4-0ubuntu3.28 => 20220329.git681281e4-0ubuntu3.29] (core, kernel)
[09:51] -queuebot:#ubuntu-release- Unapproved: linux-firmware (mantic-proposed/main) [20230919.git3672ccab-0ubuntu2.8 => 20230919.git3672ccab-0ubuntu2.9] (core, kernel)
[10:16] <adrien> what happened to lamassemble? I see "New: accepted lamassemble [amd64] (noble-proposed) [1.7.0-2]" 12 days ago, and it was in the way of python migrating which is why I was tasked with fixing the issue but now it's not in excuses anymore and the only version I see on LP is the previous one
[10:17] <adrien> not that I complain it disappeared! the issue was more likely with the new lamassemble version that the new python version, but I'd like to understand
[10:46] -queuebot:#ubuntu-release- New binary: ruff [riscv64] (noble-proposed/universe) [0.0.291+dfsg1-3] (no packageset)
[10:54] <ginggs> adrien: https://launchpad.net/ubuntu/+source/lamassemble/+publishinghistory
[10:55] <ginggs> expand the entry for 1.7.0-2
[10:55] <ginggs>  Removed from disk on 2024-02-19.
[10:55] <ginggs> Removal requested on 2024-02-19.
[10:57] -queuebot:#ubuntu-release- New: accepted ruff [riscv64] (noble-proposed) [0.0.291+dfsg1-3]
[11:06] <adrien> ginggs: thanks! I feel stupid, I remember publishinghistory was mentioned just a few days ago but my brain didn't link everything together /o\
[11:07] <adrien> doko: thanks for removing lamassemble :)
[12:22] <ahasenack> ubuntu-archive: hi, when someone as a moment, could you please complete the glusterfs demotion to universe? It's showing up in component mismatches already, as a "source and binary movements to universe"
[12:22] <ahasenack> https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/2045063 is the demotion bug
[12:23] -ubottu:#ubuntu-release- Launchpad bug 2045063 in glusterfs (Ubuntu) "Demote glusterfs for noble" [High, In Progress]
[12:23] <ahasenack> I thought it would happen automatically, maybe I'm wrong, or maybe there is something else keeping it in main that I haven't spotted
[12:24] <ahasenack> it will also move bin:qemu-block-supplemental and bin:samba-vfs-modules-extra to universe, that's expected
[12:24] <ahasenack> they are also showing up in the report as binary-only moves to universe
[12:48] -queuebot:#ubuntu-release- Unapproved: tzdata (mantic-proposed/main) [2023d-0ubuntu0.23.10 => 2024a-0ubuntu0.23.10] (core, i386-whitelist)
[12:56] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-advantage-tools [source] (mantic-proposed) [31.1~23.10]
[12:57] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-advantage-tools [source] (jammy-proposed) [31.1~22.04]
[12:57] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-advantage-tools [source] (focal-proposed) [31.1~20.04]
[12:58] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-advantage-tools [source] (bionic-proposed) [31.1~18.04]
[12:59] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-advantage-tools [source] (xenial-proposed) [31.1~16.04]
[13:01] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [amd64] (mantic-proposed/main) [31.1~23.10] (core)
[13:01] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [armhf] (mantic-proposed/main) [31.1~23.10] (core)
[13:02] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [amd64] (jammy-proposed/main) [31.1~22.04] (core)
[13:02] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [arm64] (mantic-proposed/main) [31.1~23.10] (core)
[13:02] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [s390x] (mantic-proposed/main) [31.1~23.10] (core)
[13:02] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [s390x] (jammy-proposed/main) [31.1~22.04] (core)
[13:02] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [ppc64el] (mantic-proposed/main) [31.1~23.10] (core)
[13:03] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [amd64] (bionic-proposed/main) [31.1~18.04] (core)
[13:03] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [i386] (bionic-proposed/main) [31.1~18.04] (core)
[13:03] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [amd64] (focal-proposed/main) [31.1~20.04] (core)
[13:03] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [armhf] (focal-proposed/main) [31.1~20.04] (core)
[13:03] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [s390x] (focal-proposed/main) [31.1~20.04] (core)
[13:03] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [armhf] (jammy-proposed/main) [31.1~22.04] (core)
[13:03] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [amd64] (xenial-proposed/main) [31.1~16.04] (no packageset)
[13:03] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [armhf] (bionic-proposed/main) [31.1~18.04] (core)
[13:03] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [arm64] (focal-proposed/main) [31.1~20.04] (core)
[13:03] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [arm64] (jammy-proposed/main) [31.1~22.04] (core)
[13:03] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [s390x] (bionic-proposed/main) [31.1~18.04] (core)
[13:03] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [ppc64el] (jammy-proposed/main) [31.1~22.04] (core)
[13:03] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [ppc64el] (focal-proposed/main) [31.1~20.04] (core)
[13:05] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [ppc64el] (bionic-proposed/main) [31.1~18.04] (core)
[13:05] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [s390x] (xenial-proposed/main) [31.1~16.04] (no packageset)
[13:05] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [i386] (xenial-proposed/main) [31.1~16.04] (no packageset)
[13:07] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [arm64] (xenial-proposed/main) [31.1~16.04] (no packageset)
[13:07] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [ppc64el] (xenial-proposed/main) [31.1~16.04] (no packageset)
[13:10] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [arm64] (bionic-proposed/main) [31.1~18.04] (core)
[13:11] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [armhf] (xenial-proposed/main) [31.1~16.04] (no packageset)
[13:13] -queuebot:#ubuntu-release- Unapproved: tzdata (jammy-proposed/main) [2023d-0ubuntu0.22.04 => 2024a-0ubuntu0.22.04] (core)
[13:13] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [riscv64] (mantic-proposed/main) [31.1~23.10] (core)
[13:24] <LocutusOfBorg> ubuntu-archive: please kick searx out from noble (Debian bug: #1051510). This will make flask migrate, with Python3.12 compatibility code
[13:24] -ubottu:#ubuntu-release- Debian bug 1051510 in src:searx "searx: SearX upstream is no longer maintained" [Serious, Open] https://bugs.debian.org/1051510
[13:24] <LocutusOfBorg> also fava bug: #1031724
[13:30] <athos> Oh... thx LocutusOfBorg. I did not know about that - I do use fava :(
[13:31] <LocutusOfBorg> athos, there is however an upstream new release
[13:32] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [riscv64] (jammy-proposed/main) [31.1~22.04] (core)
[13:34] <LocutusOfBorg> if you want to create an NMU... I'm happy to sponsor
[13:43] -queuebot:#ubuntu-release- Unapproved: tzdata (focal-proposed/main) [2023d-0ubuntu0.20.04 => 2024a-0ubuntu0.20.04] (core)
[13:44] <bdrung> rbasak, can you accept the tzdata SRUs please?
[14:01] -queuebot:#ubuntu-release- New binary: ubuntu-advantage-tools [riscv64] (focal-proposed/main) [31.1~20.04] (core)
[14:13] <arraybolt3> Any news on the casper front today? If not, I'm going to assume the SRU isn't happening in time for the release and will start doing testing accordingly.
[14:27] <athos> LocutusOfBorg: thanks! I will have a look on the weekend. It seems there is a lot of JS components which need to be packaged though :(
[14:28] <athos> I will assess it and reach out for sponsorship as needed :)
[15:23] <tsimonq2> ubuntu-sru, dviererbe: Hello! Was someone at Canonical working on testing this? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990621
[15:23] -ubottu:#ubuntu-release- Launchpad bug 1990621 in casper (Ubuntu Jammy) "[SRU] PXE Boot contains wrong suggested link to ISO for live file system" [Low, Fix Committed]
[15:24] <tsimonq2> To my understanding, this was planned for .4. Could someone please clarify?
[15:25] <tsimonq2> (arraybolt3 was asking above, just some proactivity for any potential respins. Thanks for your persistence!)
[15:28] <dviererbe> tsimonq2: I have this in my backlog. I tested the code outside of casper, but to be honest I still have to figure out how to trigger the code path within casper as I am not familiar with casper.
[15:30] <tsimonq2> dviererbe: Is there Interest in getting this to .4, to your understanding?
[15:30] <arraybolt3> I think we're close enough to release it may be best to just let this slide - we're going to go from having 8 testcases left in Lubuntu to having 18 testcases left if a respin is done (not to mention the effects on all the other flavors), and while that would have been easy if this had happened yesterday, it'll be hard if done today and very hard/impossible if done tomorrow.
[15:31] <arraybolt3> Maybe we can just skip it this cycle and try again next year or so?
[15:32] <dviererbe> Fine with me. It's a low importance bug.
[15:38] <tsimonq2> Sounds good. Thanks for the input!
[15:49] <sgmoore> Hello. I am told to ping ubuntu-release in regards to my 22.04.4 ISO being to big. Please forgive my newbness as I am the new Lead dev/ Release manager for Kubuntu and I fear hacking bits and pieces out of the image the day before release is a bad idea especially since I wasn't about when it released. Can we get an increase for this one and I promise to remove the bloat this upcoming LTS? Thanks for any assistance.
[15:52] <Eickmeyer> sgmoore: Not release team, but fellow flavor lead. Honestly, you shouldn't be afraid to ask for a size increase because applications and the kernel itself simply increase in size. In 22.04.4's case, it's likely just the kernel as I doubt the Kubuntu seed has changed since 22.04.3, so don't worry too much about asking for a size increase. :)
[15:53] <sgmoore> :)
[16:17] <bdrung> ahasenack, can you accept the tzdata SRUs please (on your shift tomorrow)?
[16:27] <tsimonq2> ah yes Qt looks blocked on a single autopkgtest at the back of the s390x queue now...
[16:39] <tsimonq2> hello nodejs
[16:54]  * LocutusOfBorg nodejs helloes back tsimonq2 
[17:04] <tsimonq2> :D
[17:29] <tsimonq2> maliit-framework makes glib2.0 and Qt be entangled :/
[17:34] <ahasenack> bdrung: I will look for sure
[17:35] <bdrung> thanks
[17:47] <tsimonq2> hi new Lintian :)
[18:11] <sgmoore> Hi all, I am having quite a few autopackage ( excuses ) tests falling over due to container failures ( https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/ppc64el/libq/libqapt/20240221_125240_f73a8@/log.gz ) is there someone I can poke to fix or point me to what to do?
[18:12] <tsimonq2> qa-help: ^^^
[18:17] <ginggs> tsimonq2: i think qa-help is over in # ubuntu-quality
[18:19] <tsimonq2> ginggs: ohh? TIL, thanks :)
[18:20] <UnivrslSuprBox> tsimonq2: if you ever need someone to shout at a maliit developer, I can help
[18:20] <tsimonq2> UnivrslSuprBox: Sounds good! although there's not much they could do, it's a Britney thing :)
[18:24] <Skia> sgmoore: I've ping bdmurray, since I'm off
[18:45] <bdmurray> sgmoore: I heard somebody else complaing about ppc64el their tests were on a different host though...
[18:49] <bdmurray> I've pinged IS
[18:50] <bdmurray> sgmoore: wrt to size bumps we'd prefer the flavour lead suggest a number rather than just ask for an increase that we have to guess at
[18:51] <ricotz> ahasenack, hello :), I am hoping you can take a look libreoffice/mantic tomorrow
[18:52] <ahasenack> ricotz: me too :)
[18:52] <ricotz> :)
[19:23] <bdmurray> sgmoore: you can see the current size limit here https://git.launchpad.net/ubuntu-cdimage/tree/lib/cdimage/tree.py?id=e0361427a783d6d025fc0390b3ff187766edd204#n1941
[19:33] <ahasenack> bdrung: bdmurray fixed autopkgtests, and now the jupyter ones are using the right version
[19:33] <ahasenack> we are just missing the unixsocket trigger I think. I triggered some, but there are many in the queue and I'm a bit lost, I think I will let it settle first, before restarting rerun attempts
[19:58] <ahasenack> ok, getting some greens finally on jupyter-notebook...
[20:00] <ahasenack> ohh, we are close
[21:15] <kanashiro> ubuntu-archive: I'd like some opinion about this issue with vagrant and some license change, it is currently blocking the ruby transition: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/2054608
[21:15] -ubottu:#ubuntu-release- Launchpad bug 2054608 in vagrant (Ubuntu) "License change and unmaintanability" [Undecided, New]
[23:53] <doko> kanashiro: please could you file a removal bug for redmine (removed in testing), including analysis of the rdeps?