[00:38] <Eickmeyer> vorlon: Is there something we can do about the oversize warnings? I mean, with iso-level-3 they're moot and obsolete anyhow, I'm OK with setting them to 4TB or something rediculous.
[00:38] <Eickmeyer> *ridiculous
[00:39] <Eickmeyer> Pretty sure I asked in here a while ago.
[00:41]  * arraybolt3 pictures trying to install from a 4 TB ISO
[00:55] <vorlon> Eickmeyer: it's not moot.  you may not have a technical software limitation on the size of the image, but we still expect flavors to be accountable for the size, both in terms of what is reasonable as a download size for users and for what media they expect the images to be installable to
[00:56] <vorlon> there's also the fact that the data set size is large enough now that IS gets regular alerts about the disk usage on cdimage-master.
[00:56] <vorlon> you can ask to set a new limit for the size of your flavor images so that you don't get the oversize messages, but I'm not going to take away the fact that there *are* limits
[00:57] <vorlon> also, bear in mind that the size of the install image impacts what kind of hardware someone will be able to do a netinstall on, since the full ISO has to fit in memory along with the live session
[01:10] <Eickmeyer> vorlon: Ubuntu Studio is at 5.3 GB for Lunar. It climbed for Jammy simply due to the kernel and no additions there, so that's not on us. Edubuntu is at 5.1 GB. All of those are going to require a USB stick and clearly need at least an 8GB machine for netinstall.
[01:10] <Eickmeyer> That's just rough math.
[01:13] <Eickmeyer> This is coming up because I'm getting complaints about the alerts. Not the alerts themselves, but that the alerts are even a thing on the ML.
[01:13] <vorlon> the alerts are meant to be *addressed*, so
[01:14] <Eickmeyer> Right, but last time I tried to get them addressed I was ignored.
[01:14] <vorlon> did you try to address them by setting a new limit?
[01:14] <vorlon> I'm NOT going to remove the oversize check
[01:14] <vorlon> for any flavor
[01:14] <Eickmeyer> I don't have direct access to set the limit?
[01:14] <vorlon> MPs are possible
[01:14] <vorlon> or you can tell me what an appropriate limit is and I can set it
[01:15] <Eickmeyer> Well, that's the problem. This comes up every cycle. I estimate something that's somewhat future-proof and end up being wrong, which is why I want this to go away.
[01:15] <vorlon> yeah no
[01:15] <vorlon> flavor images don't get to grow without bound
[01:16] <Eickmeyer> Not trying to grow without bound, but growth is inevitable.
[01:16] <vorlon> agree a limit with the release team, set it, and if there's a reason the image exceeds it again in the future that's another conversation
[01:16] <vorlon> it might mean that you have to have that conversation each cycle
[01:18] <Eickmeyer> What's the point of the conversation if I simply set current+200MB, which gets agreed, and next cycle it goes over, so I set that+200MB? See where this is going? Endless cycle.
[01:18] <Eickmeyer> I'm not trying to be hostile here, just trying to make it make sense.
[01:18] <vorlon> the point is that if there's not an agreed limit there's no accountability for the image growth
[01:19] <Eickmeyer> That's not true. I'm constantly trying to keep the image down, but when the kernel itself or some other package makes the image go higher, that's beyond my control.
[01:19] <vorlon> you don't have to go in 200MB increments
[01:19] <Eickmeyer> That was an example.
[01:20] <vorlon> it's fine that you are within the flavor accounting for this.  But project-wide there needs to be accountability as well
[01:20] <vorlon> and this is how we ensure that
[01:20] <Eickmeyer> Ok, but that's a very heavy-handed approach, don't you think?
[01:20] <vorlon> we also have a problem with the Ubuntu Desktop images, because they keep growing rapidly due to proliferation of nvidia driver versions
[01:20] <vorlon> email is heavy-handed?
[01:20] <vorlon> all it takes is for you to tell me what you think the limit should be for lunar, we agree it, and I commit it
[01:21] <Eickmeyer> Well, a daily email, sure, especially when I'm the one that gets the complaint.
[01:21] <Eickmeyer> I just had someone on my team threaten to mute the ML.
[01:21] <vorlon> I get nag emails daily about *all* the images, so I'm not particularly sympathetic that you're complaining about email when it's entirely in your power to make it go away by telling me what you want the new limit to be
[01:21] <arraybolt3> Eickmeyer: From an outside standpoint, I'm unsure why it wouldn't be possible to ask for the limit to increase after the first, say, three times a notification about size shows up?
[01:22] <vorlon> the contact for it doesn't have to be a mailing list
[01:22] <arraybolt3> (Also what ML are you guys on that you're getting size notifications? Lubuntu is apparently oversized and I've not seen any email about it.)
[01:22] <Eickmeyer> arraybolt3: ubuntu-studio-devel@
[01:23] <arraybolt3> Huh. I guess lubuntu-devel must not be sending those for us then. Anyway, sorry to hijack the topic.
[01:23] <vorlon> the only flavors using mailing lists as the contact are ubuntustudio, xubuntu, and edubuntu
[01:23] <Eickmeyer> Ok, so I see where the idea originated.
[01:24] <Eickmeyer> Let's fix the contact then.
[01:24] <Eickmeyer> What are the other flavors using?
[01:24] <vorlon> individual email addresses for the flavor contacts
[01:25] <vorlon> you can send the email anywhere you want
[01:25] <Eickmeyer> I see. Let me get some new contacts for you, they'll likely be Launchpad email list contacts.
[01:25] <vorlon> ok
[01:26] <vorlon> in the meantime, while you haven't stated a specific limit, I'm taking the above conversation to mean that the ubuntustudio image is at the size you expect it to be for lunar and that you don't consider it oversized, so I'm going to raise the limit to something sensible
[01:27] <Eickmeyer> vorlon: That sounds great. Can we do the same for Edubuntu?
[01:27] <Eickmeyer> vorlon: ubuntustudio jammy is also getting warnings, despite no changes other than kernel.
[01:28] <Eickmeyer> s/no changes/no meaningful changes
[01:28] <vorlon> ftr the current limit for ubuntustudio is 5.5GB.  The image is at 5.7GB (GB, not GiB; this is 5.4GiB).
[01:28] <Eickmeyer> vorlon: New contact for image oversize for Ubuntu Studio: ubuntustudio-release@lists.launchpad.net
[01:29] <Eickmeyer> ack
[01:29] <jbicha> Eickmeyer: btw, I found that the new Ubuntu Desktop installer doesn't work in a VM with only 2 gigs of RAM but the "legacy" one worked
[01:30] <Eickmeyer> jbicha: Perhaps due to the snap technology used or...? (speculating)
[01:30] <jbicha> well it's Flutter too
[01:30] <Eickmeyer> Ah. Fair point.
[01:30] <jbicha> I should try that new mini ISO to see what it does
[01:31] <Eickmeyer> vorlon: New contact for image oversize for Edubuntu: edubuntu-release@lists.launchpad.net
[01:31] <Eickmeyer> I just want some form of future redundancy for bus factor.
[01:32] <Eickmeyer> Hence, ML.
[01:32] <Eickmeyer> But that way those that don't want the alerts don't get them.
=== chris14_ is now known as chris14
=== kgiii_ is now known as KGIII
=== KGIII is now known as Guest692
[05:25] -queuebot:#ubuntu-release- Unapproved: pasystray (lunar-proposed/universe) [0.8.1-1 => 0.8.2-1] (no packageset) (sync)
[05:25] -queuebot:#ubuntu-release- Unapproved: accepted pasystray [sync] (lunar-proposed) [0.8.2-1]
[06:18] <LocutusOfBorg> vorlon, we have now proper fixes for autopkgtests (currently failing) and for the linux-header installation failures
[06:18] <LocutusOfBorg> I think this is a good version to go in lunar...
[08:17] <LocutusOfBorg> cjwatson, hello, good morning, if possible, can we have a tail of https://launchpad.net/ubuntu/+source/llvm-toolchain-16/1:16.0.0-1~exp5ubuntu1/+build/25952684 ?
[08:18] <LocutusOfBorg> I reduced the parallel building even more
[08:18] <LocutusOfBorg> but I suspect its failing in some parallel linking instead, not sure if I have to also use -g1 or something similar
[08:21] <LocutusOfBorg> in previous log: https://paste.ubuntu.com/p/rjxvWJPZ2P/plain/
[08:21] <LocutusOfBorg> it was failing during build
[08:21] <LocutusOfBorg> and we already have -g1
=== guiverc2 is now known as guiverc
[08:55] <LocutusOfBorg> are dgit autopkgtests having sad day?
[08:57] <cjwatson> LocutusOfBorg: tail running.  (This is a very cumbersome thing though, would appreciate it not becoming too frequent a request)
[08:58] <LocutusOfBorg> cjwatson, thanks, unfortunately without bileto, and without failures in debian, I don't know how to debug it
[08:58] <LocutusOfBorg> but if you have any idea, please tell me, I'm really open to hints :D
[08:59] <cjwatson> How would bileto help?
[09:00] <cjwatson> I mean, compared to any random PPA
[09:00] <LocutusOfBorg> cjwatson, e.g. by doing a test with parallel=1
[09:00] <cjwatson> Sure - you could do that in a PPA though
[09:00] <LocutusOfBorg> what, riscv64 available for ppa?
[09:01] <cjwatson> You're a core-dev, you can have that on request
[09:01] <LocutusOfBorg> WOW!
[09:01] <LocutusOfBorg> that would indeed help!
[09:01] <cjwatson> It's not generally available, but core-devs have enough access to change Ubuntu that there's no real point in restricting it from them
[09:01] <LocutusOfBorg> let me ask
[10:38] -queuebot:#ubuntu-release- Unapproved: rejected tzdata [source] (kinetic-proposed) [2023c-0ubuntu0.22.10.0]
[10:42] <rbasak> bdrung: thanks - that looks good. Accepting. As you're moving the other fixes into a different SRU, please could you remove that from the SRU documentation in bug 2012599 to avoid confusion?
[10:42] -ubottu:#ubuntu-release- Bug 2012599 in tzdata (Ubuntu Kinetic) "tzdata 2023a/2023b/2023c release - Egypt restoring DST" [Critical, Triaged] https://launchpad.net/bugs/2012599
[10:43] -queuebot:#ubuntu-release- Unapproved: accepted tzdata [source] (kinetic-proposed) [2023c-0ubuntu0.22.10.0]
[10:44] <rbasak> bdrung: and presumably I should reject the remaining uploads for J,F,B then, right?
[10:45] <bdrung> rbasak, yes. I am preparing the new SRUs for <= jammy now.
[10:47] <bdrung> ticket description is now updated
[11:03] -queuebot:#ubuntu-release- Unapproved: tzdata (lunar-proposed/main) [2023c-1exp1ubuntu1 => 2023c-2exp1ubuntu1] (core)
[11:19] -queuebot:#ubuntu-release- Unapproved: tzdata (jammy-proposed/main) [2023b-0ubuntu0.22.04.0 => 2023c-0ubuntu0.22.04.0] (core)
[11:34] -queuebot:#ubuntu-release- Unapproved: tzdata (focal-proposed/main) [2023b-0ubuntu0.20.04.0 => 2023c-0ubuntu0.20.04.0] (core)
[11:56] -queuebot:#ubuntu-release- Unapproved: tzdata (bionic-proposed/main) [2023b-0ubuntu0.18.04.0 => 2023c-0ubuntu0.18.04] (core)
[11:59] <bdrung> rbasak, ^ all SRUs are ready
[12:10] <ahasenack> hi release team, I have this samba FFe, requested by the security team: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/2014052
[12:11] -ubottu:#ubuntu-release- Launchpad bug 2014052 in samba (Ubuntu Lunar) "[Lunar FFE]: Samba 4.18.1, 4.17.7 and 4.16.10 Security Releases" [High, In Progress]
[12:20] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (focal-proposed) [2:16.4.2-0ubuntu6.1]
[13:04] -queuebot:#ubuntu-release- Unapproved: accepted zfs-linux [source] (focal-proposed) [0.8.3-1ubuntu12.15]
[13:16] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (lunar-proposed/main) [27.14.2~23.04.1 => 27.14.3] (core)
[13:16] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (bionic-proposed/main) [27.13.6~18.04.1 => 27.14.3~18.04.1] (core)
[13:16] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (xenial-proposed/main) [27.13.6~16.04.1 => 27.14.3~16.04.1] (no packageset)
[13:16] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (focal-proposed/main) [27.13.6~20.04.1 => 27.14.3~20.04.1] (core)
[13:17] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (jammy-proposed/main) [27.13.6~22.04.1 => 27.14.3~22.04.1] (core)
[13:17] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (kinetic-proposed/main) [27.13.6~22.10.1 => 27.14.3~22.10.1] (core)
[13:18] <ginggs> ahasenack: samba FFe granted
[13:18] <ahasenack> ginggs: thank you
[13:19] <ahasenack> mdeslaur: ^
[13:19] <mdeslaur> cool, thanks
=== kgiii is now known as KGIII
[14:19] -queuebot:#ubuntu-release- New: accepted corectrl [sync] (lunar-proposed) [1.3.3+ds-1]
[14:28] -queuebot:#ubuntu-release- New binary: corectrl [ppc64el] (lunar-proposed/none) [1.3.3+ds-1] (no packageset)
[14:28] -queuebot:#ubuntu-release- New binary: corectrl [s390x] (lunar-proposed/none) [1.3.3+ds-1] (no packageset)
[14:30] -queuebot:#ubuntu-release- New binary: corectrl [arm64] (lunar-proposed/none) [1.3.3+ds-1] (no packageset)
[14:39] -queuebot:#ubuntu-release- Unapproved: netplan.io (lunar-proposed/main) [0.106-0ubuntu2 => 0.106-0ubuntu3] (core)
[14:43] -queuebot:#ubuntu-release- New binary: corectrl [armhf] (lunar-proposed/none) [1.3.3+ds-1] (no packageset)
[15:01] -queuebot:#ubuntu-release- New binary: corectrl [amd64] (lunar-proposed/universe) [1.3.3+ds-1] (no packageset)
[15:15] <ricotz> vorlon, hello :), could you check if this change got processed? https://git.launchpad.net/ubuntu-archive-tools/commit/?id=4b542fdbcf154ae71c4fa94b21ea6a6ece1300db
[15:15] -ubottu:#ubuntu-release- Commit 4b542fd in ubuntu-archive-tools "update-i386-whitelist: intuit more upcoming nvidia-graphics-drivers-* versions"
[15:16] <ricotz> so far I can't get the PPA to build i386 binaries for nvidia-graphics-drivers-530
[15:19] <vorlon> ricotz: I can rerun the command now
[15:19] <vorlon> wow, quite the list of removals actually
[15:19] <vorlon> Additions:
[15:19] <vorlon>  * libjxl-testdata
[15:19] <vorlon>  * nvidia-graphics-drivers-530
[15:20] <vorlon> ricotz: ^^ is that what you're wanting/expecting?
[15:20] <ricotz> vorlon, yes, that would be it
[15:20] <vorlon> ok; verifying this list of removals briefly before committing
[15:20] <ricotz> vorlon, I assumed this is running regularly?
[15:20] <vorlon> oh sweet this is because devscripts went arch: all
[15:20] <vorlon> ricotz: no it's a manual thing
[15:21] <ricotz> I see, should have asked earlier than waiting so long :\
[15:23] <vorlon> committed the changes now
[15:24] <ricotz> vorlon, regarding i386, what bugs me for some time is that aptitude has no i386 support
[15:24] <vorlon> i386 is not a host architecture
[15:24] <vorlon> oh, you mean aptitude not supporting installation of i386 packages, vs aptitude not being built on i386?
[15:25] <ricotz> meaning no i386 build anymore
[15:25] -queuebot:#ubuntu-release- New binary: corectrl [riscv64] (lunar-proposed/universe) [1.3.3+ds-1] (no packageset)
[15:25] <vorlon> oh
[15:25] <vorlon> yeah, not going to fix that
[15:25] <vorlon> i386 exists *only* to provide libraries for compatibility
[15:25] <ricotz> would be a better pbuilder-dist support ootb
[15:38] -queuebot:#ubuntu-release- Packageset: 33 entries have been added or removed
[15:39] -queuebot:#ubuntu-release- New: accepted corectrl [amd64] (lunar-proposed) [1.3.3+ds-1]
[15:39] -queuebot:#ubuntu-release- New: accepted corectrl [armhf] (lunar-proposed) [1.3.3+ds-1]
[15:39] -queuebot:#ubuntu-release- New: accepted corectrl [riscv64] (lunar-proposed) [1.3.3+ds-1]
[15:39] -queuebot:#ubuntu-release- New: accepted unhide [amd64] (lunar-proposed) [20220611-1]
[15:39] -queuebot:#ubuntu-release- New: accepted unhide [armhf] (lunar-proposed) [20220611-1]
[15:39] -queuebot:#ubuntu-release- New: accepted unhide [riscv64] (lunar-proposed) [20220611-1]
[15:39] -queuebot:#ubuntu-release- New: accepted corectrl [arm64] (lunar-proposed) [1.3.3+ds-1]
[15:39] -queuebot:#ubuntu-release- New: accepted corectrl [s390x] (lunar-proposed) [1.3.3+ds-1]
[15:39] -queuebot:#ubuntu-release- New: accepted unhide [ppc64el] (lunar-proposed) [20220611-1]
[15:39] -queuebot:#ubuntu-release- New: accepted corectrl [ppc64el] (lunar-proposed) [1.3.3+ds-1]
[15:39] -queuebot:#ubuntu-release- New: accepted unhide [s390x] (lunar-proposed) [20220611-1]
[15:39] -queuebot:#ubuntu-release- New: accepted unhide [arm64] (lunar-proposed) [20220611-1]
[15:47] -queuebot:#ubuntu-release- Unapproved: cd-boot-images-ppc64el (lunar-proposed/main) [14 => 15] (desktop-core)
[15:48] -queuebot:#ubuntu-release- Unapproved: cd-boot-images-riscv64 (lunar-proposed/main) [7 => 8] (no packageset)
[15:49] -queuebot:#ubuntu-release- Unapproved: accepted cd-boot-images-riscv64 [source] (lunar-proposed) [8]
[15:59] -queuebot:#ubuntu-release- Unapproved: accepted cd-boot-images-ppc64el [source] (lunar-proposed) [15]
[16:10] -queuebot:#ubuntu-release- Unapproved: accepted dkms [sync] (lunar-proposed) [3.0.10-8]
[16:18] -queuebot:#ubuntu-release- Unapproved: accepted gcc-11 [sync] (jammy-proposed) [11.3.0-1ubuntu1~22.04.1]
[16:21] -queuebot:#ubuntu-release- Unapproved: accepted gcc-11-cross [sync] (jammy-proposed) [11ubuntu1.2]
[16:25] -queuebot:#ubuntu-release- Unapproved: accepted gcc-11-cross-ports [sync] (jammy-proposed) [8ubuntu1.2]
[16:46] <rs20090> hi everyone, it looks like Ubuntu Unity's default background, set through a gschema override, is somehow overriden by Ubuntu's default wallpaper; one thing to note would be that Unity uses the same key for the background as GNOME (org.gnome.desktop.background - picture-uri); also, I don't see any errors when running 'glib-compile-schemas' and the
[16:46] <rs20090> wallpapers are visible in unity-control-center
[16:46] <rs20090> I'm unable to figure this out, so was wondering if anyone had any idea (this wasn't an issue in previous releases, either)
=== rs20090 is now known as rs2009
[16:47] <vorlon> rs2009: I'd suggest asking in #ubuntu-devel or #ubuntu-desktop
[16:48] <rs2009> vorlon: oh, sure +1
[16:49] -queuebot:#ubuntu-release- Unapproved: ubiquity (lunar-proposed/main) [23.04.4 => 23.04.5] (ubuntu-desktop)
[17:44] <renanrodrigo> hello all; could someone please take a look into ubuntu-advantage-tools getting into lunar? we had to upload a bugfix
[17:46] <renanrodrigo> (LP 2013409)
[17:46] -ubottu:#ubuntu-release- Launchpad bug 2013409 in ubuntu-advantage-tools (Ubuntu) "pro attach fails on interim releases when enabling livepatch" [High, In Progress] https://launchpad.net/bugs/2013409
[18:20] -queuebot:#ubuntu-release- Unapproved: breezy (lunar-proposed/universe) [3.3.2-2build1 => 3.3.2-2ubuntu1] (no packageset)
[18:21] -queuebot:#ubuntu-release- Unapproved: accepted breezy [source] (lunar-proposed) [3.3.2-2ubuntu1]
[18:34] <vorlon> mitya57: can you clarify why you're syncing a new upstream version of python-markdown, from experimental, post FF?  There's an open question about whether we actually want to have the archive frozen right now, but in the meantime this looks questionable for a package that's seeded in edubuntu and kylin images
[18:39] <Eickmeyer> looking
[18:42] <locutusofborg_> vorlon, if you want an easy accept, please look at qtcreator
[18:42] <locutusofborg_> the -2 upload is *just* fixing the arch:all build
[18:43] <locutusofborg_> qtcreator is stuck since 39 days
[18:43] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (lunar-proposed) [2.59.1+23.04]
[18:46] -queuebot:#ubuntu-release- Unapproved: accepted qtcreator [sync] (lunar-proposed) [9.0.2-2]
[18:47] <Eickmeyer> vorlon: RE: python-markdown: I can see why. Looks like a minor upstream bugfix release. Can't see any new features. No issues with it from an Edubuntu standpoint.
[18:47] <Eickmeyer> Literally a single commit diff in the upstream.
[18:48] <Eickmeyer> vorlon: Sorry, misspoke. It has official python 3.11 support too.
[18:49] <Eickmeyer> Still would rather have that.
[18:49] -queuebot:#ubuntu-release- Unapproved: accepted ibus [sync] (lunar-proposed) [1.5.28-3]
[18:49] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (lunar-proposed) [23.04.5]
[18:52] -queuebot:#ubuntu-release- Unapproved: rejected sox [sync] (lunar-proposed) [14.4.2+git20190427-3.5]
[19:01] -queuebot:#ubuntu-release- Unapproved: accepted librest [sync] (lunar-proposed) [0.9.1-6]
[19:04] -queuebot:#ubuntu-release- Unapproved: accepted gcompris-qt [sync] (lunar-proposed) [3.1-3]
[19:09] -queuebot:#ubuntu-release- Unapproved: accepted debian-archive-keyring [source] (lunar-proposed) [2023.3ubuntu1]
[19:11] -queuebot:#ubuntu-release- Unapproved: accepted mpv [source] (lunar-proposed) [0.35.1-2ubuntu1]
[19:18] -queuebot:#ubuntu-release- Unapproved: accepted libdatetime-timezone-perl [sync] (lunar-proposed) [1:2.60-1+2023c]
[19:25] <mitya57> vorlon, Eickmeyer: Yes, it's upstream patch release with no new features. Upstream has a very good test coverage and the new fixes are covered by tests too.
[19:28] -queuebot:#ubuntu-release- Unapproved: accepted python-markdown [sync] (lunar-proposed) [3.4.3-1]
[19:31] <mitya57> Thanks.
[19:41] -queuebot:#ubuntu-release- Unapproved: accepted gegl [sync] (lunar-proposed) [1:0.4.44-1]
[19:43] -queuebot:#ubuntu-release- Unapproved: accepted tzdata [source] (lunar-proposed) [2023c-2exp1ubuntu1]
[19:45] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-advantage-tools [source] (lunar-proposed) [27.14.3]
[19:46] -queuebot:#ubuntu-release- Unapproved: accepted netplan.io [source] (lunar-proposed) [0.106-0ubuntu3]
[22:10] <jbicha> vorlon: https://ubuntu-archive-team.ubuntu.com/proposed-migration/log/lunar/2023-04-03/21:58:12.log
[22:15] <vorlon> hmmMmm
[22:15] <vorlon> looking
[22:16] <vorlon> looks like some of the britney1 scripts invoke python instead of python3, how rude
[22:16] <vorlon> (I just removed the cowboyed python->python3 symlink today)
[22:19] <vorlon> jbicha: thanks for flagging, should be fixed now (we'll see in 2 minutes)
[22:23] <vorlon> hmm hmm apparently not
[22:24] <vorlon> aha got it
[22:26] <vorlon> jbicha: running
=== chris15 is now known as chris14
[22:37] <Ukikie> FWIW, I did that late sync of pasystray because it has "fixes broken output switching with wireplumber", since pipewire is now default it seems like that'd be important, but it's entirely unseeded so low risk. :3
=== chris14_ is now known as chris14
[23:40] <jbicha> vorlon: looks like britney is still broken?
[23:42] -queuebot:#ubuntu-release- Unapproved: epiphany-browser (lunar-proposed/universe) [44.0-1 => 44.1-1] (desktop-extra) (sync)
[23:43] <vorlon> jbicha: link?
[23:43] <vorlon> it was running
[23:43] <jbicha> vorlon: https://ubuntu-archive-team.ubuntu.com/proposed-migration/log/lunar/2023-04-03/23:26:17.log
[23:43] <vorlon> fun!
[23:47] <vorlon> jbicha: 2to3'ed the script, and updated the working directory, so the current run might get farther
[23:52] <vorlon> mmk failed again, digging
[23:53] -queuebot:#ubuntu-release- Unapproved: unknown-horizons (lunar-proposed/universe) [2019.1-5 => 2019.1-6] (no packageset) (sync)
[23:54] -queuebot:#ubuntu-release- Unapproved: accepted unknown-horizons [sync] (lunar-proposed) [2019.1-6]
[23:58] <vorlon> jbicha: got past fauxpkg.py thi stime