[01:27] <amurray_> WantedBy=default.target is used by a lot of other packages already https://codesearch.debian.net/search?q=WantedBy%3Ddefault.target&literal=1
[07:05] -queuebot:#ubuntu-release- Unapproved: carla (jammy-proposed/universe) [2.4.2-0ubuntu2 => 2.4.4-0ubuntu0.22.04.1] (i386-whitelist, ubuntustudio)
[07:52] -queuebot:#ubuntu-release- Unapproved: rejected evolution-data-server [source] (jammy-proposed) [3.44.3-0ubuntu1]
[07:52] -queuebot:#ubuntu-release- Unapproved: rejected evolution [source] (jammy-proposed) [3.44.3-0ubuntu1]
[07:52] -queuebot:#ubuntu-release- Unapproved: rejected gjs [source] (jammy-proposed) [1.72.1-0~ubuntu22.04.1]
[07:52] -queuebot:#ubuntu-release- Unapproved: rejected gnome-shell-extensions [source] (jammy-proposed) [42.3-0ubuntu1]
[07:52] -queuebot:#ubuntu-release- Unapproved: rejected gnome-desktop [source] (jammy-proposed) [42.3-0ubuntu1]
[07:52] -queuebot:#ubuntu-release- Unapproved: rejected gnome-shell [source] (jammy-proposed) [42.3.1-0ubuntu2]
[07:53] -queuebot:#ubuntu-release- Unapproved: rejected mutter [source] (jammy-proposed) [42.3-0ubuntu1]
[09:41] <sil2100> Hey everyone!
[09:42] <sil2100> I was poking around various people for the snapd update verification. I think we have the overall validation done + the OEM install bug fix verified
[09:42] <sil2100> If there are no objections, I'll mark both as verified, get it landed in -updates and then, after it publishes fully, respin the world™
[09:55] <sil2100> ...no objections, so proceeding
[09:56] <sil2100> If anyone notices *any* new snap-related strangeness in the next days, please give me a sign
[09:56] <sil2100> We can always revert snapd
[11:31] <sil2100> Okay, looks like snapd is available
[11:31] <sil2100> Everyone! Spinning candidates!
[11:40] <luis220413> Ubuntu 22.10 Feature Freeze is approaching and I would like to get bug 1979893 fixed before that (because Varnish 7.x is a major release with many new features).
[11:41] <luis220413> Ubuntu Kinetic Feature Freeze is approaching and I would like to get bug 1979893 fixed before that (because Varnish 7.1.0 is a major release with many new features when compared with 6.6.1-1).
[11:41] <luis220413> The linked Debian bugs have not been responded to since June 26. I believe the libvmod-re2 source package should be removed from the Ubuntu archive and varnish-modules should not be built on armhf, or the test failures addressed or ignored on that architecture.
[11:41] <luis220413> See the bug for the rational
[11:41] <luis220413> *rationale
[11:46] <jbicha> luis220413: if you need a package removed, please also click the "Subscribe someone else" button on the bug report and add ubuntu-archive
[11:47] <luis220413> jbicha: Do you believe this removal should be done now? (Feature Freeze is on August 25.)
[11:48] <luis220413> s/done/requested/
[11:49] <jbicha> yes, it's good to get things done early :)
[11:52] <luis220413> jbicha: Subscribed. And I believe the build failure should be addressed by not building the package on armhf, because it is very bad to distribute a package where 80% of tests fail.
[12:00] <luis220413> And I believe this package has very little or no use on armhf, because this is a 32-bit architecture and Varnish, as a web cache, benefits from a large amount of memory (> 4 GB) that is only possible on 64-bit architectures.
[12:02] <luis220413> jbicha: Who can block a package from building in an architecture?
[12:03] <jbicha> someone needs to update the package's debian/control to specify what architectures it should build
[12:04] <luis220413> jbicha: This is a one-line change to debian/control. I will submit a debdiff in 2 minutes.
[12:05] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Jammy 22.04.1] has been updated (20220809)
[12:05] <jbicha> luis220413: have you ever filed a Debian bug? It might be good to ask the Debian maintainer if they want to make that change too?
[12:06] <luis220413> I have filed more than 5 bugs, and 4 are linked to in the Ubuntu bug I mentioned
[12:06] <luis220413> *Debian bugs
[12:08] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Jammy 22.04.1] has been updated (20220809)
[12:09] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Jammy 22.04.1] has been updated (20220809)
[12:12] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Jammy 22.04.1] has been updated (20220809)
[12:15] <luis220413> jbicha: OK, I will ask in the linked Debian bug for varnish-modules.
[12:16] <luis220413> On Thursday
[12:18] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Jammy 22.04.1] has been updated (20220809)
[12:19] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Jammy 22.04.1] has been updated (20220809)
[12:20] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Jammy 22.04.1] has been updated (20220809)
[12:20] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Jammy 22.04.1] has been updated (20220809)
[12:21] <rbasak> luis220413: I suggest you state your actual request in the bug. Right now if someone reads the bug they won't understand what you're requesting.
[12:25] <luis220413> jbicha: I will submit the debdiff now.
[12:29] <luis220413> jbicha, rbasak: Done
[12:50] <luis220413> RAOF, bdmurray: I will like one of you to sponsor the SRU in bug 1969734 to jammy-proposed. I know the SRU queue is soft-frozen for 22.04.1, but this is a priority SRU for a fatal bug in a package seeded in Kubuntu and Ubuntu Studio (and that I will get preinstalled in all Ubuntu flavors through a main inclusion report and metapackage changes).
[12:51] <luis220413> s/metapackage/package/
[12:56] <jbicha> luis220413: usually, main inclusion only affects future Ubuntu releases
[13:09] <luis220413> I will also get it preinstalled in Ubuntu Desktop and maybe Ubuntu Server
[13:10] <jbicha> Ubuntu Server doesn't use NM by default
[13:10] <luis220413> jbicha: But I will also file a SRU to get another preinstalled packages in Desktop (and maybe Server) to depend on the network-manager-openconnect and openconnect packages.
[13:10] <luis220413> jbicha: So what does it use to establish VPN connections?
[13:12] <luis220413> jbicha: But main inclusion can affect current and previous Ubuntu releases, as in bug 1956617
[13:13] <jbicha> there are exceptions. Include your reasoning for why there should be an exception to include it by default in 22.04 LTS in your main inclusion bug report
[13:17] <jbicha> Ubuntu Server recommends netplan which uses netword on servers by default. Maybe #ubuntu-server could help if you need more info than that
[13:17] <jbicha> *networkd
[13:17] <luis220413> jbicha: This is covered by point 3 in https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases: "For Long Term Support releases we sometimes want to introduce new features."
[13:18] <jbicha> yes, there can be exceptions to add new dependencies to LTS releases. It's not the default so you'll have to specifically argue for it
[13:21] <luis220413> jbicha: OK
[13:25] <luis220413> jbicha: The default Ubuntu Server 22.04 image does not provide VPN support.
[13:26] <luis220413> jbicha: Ubuntu Server 22.04 does not provide VPN support by default.
[13:28] <luis220413> RAOF, bdmurray: (repeating my previous comment) I will like one of you to sponsor the SRU in bug 1969734 to jammy-proposed. I know the SRU queue is soft-frozen for 22.04.1, but this is a priority SRU for a fatal bug in a package seeded in Kubuntu and Ubuntu Studio (and that I will get preinstalled in all Ubuntu flavors through a main inclusion report and metapackage changes).
[13:34] <luis220413> I will be back in 1 hour but remain online.
[13:59] <luis220413> I am back.
[14:07] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Jammy 22.04.1] has been updated (20220809)
[14:07] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Jammy 22.04.1] has been updated (20220809)
[14:07] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Jammy 22.04.1] has been updated (20220809)
[14:07] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Jammy 22.04.1] has been updated (20220809)
[14:07] -queuebot:#ubuntu-release- Builds: Ubuntu Base riscv64 [Jammy 22.04.1] has been updated (20220809)
[14:07] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Jammy 22.04.1] has been updated (20220809)
[14:17] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop arm64+raspi [Jammy 22.04.1] has been updated (20220809)
[14:19] <lucasmoura> Hi sil2100, we are currently on the process of releasing version 27.10 of the ubuntu-advantage-tools package. However, can we release it normally to Jammy, due to the 22.04.1 freeze ?
[14:29] <utkarsh2102> bdmurray: hellu, could you please move google-guest-agent from -proposed to -updates, please? cf: LP: #1959392
[14:51] <luis220413> bdmurray: (repeating my previous comment) I will like one of you to sponsor the SRU in bug 1969734 to jammy-proposed. I know the SRU queue is soft-frozen for 22.04.1, but this is a priority SRU for a fatal bug in a package seeded in Kubuntu and Ubuntu Studio (and that I will get preinstalled in all Ubuntu flavors through a main inclusion report and metapackage changes).
[14:52] <Eickmeyer[m]> luis220413: We've had a talk about this, but you've got to stop being so insistent. They will get to it when/if they have time.
[14:53] <luis220413> Eickmeyer[m]: But I believe this is a priority SRU and that is what vanguards are for.
[14:53] <luis220413> I just want this in -proposed. This is just a matter of reviewing the differences and accepting the package.
[14:54] <Eickmeyer[m]> luis220413: But pinging someone over and over again is not the way. Once is good enough, they get to it when they have time, and it's up to them to evaluate whether or not it's priority.
[14:55] <Eickmeyer[m]> Also, just because it's seeded does not mean it's priority. It's up to those flavor leads to evaluate whether or not it's priority and to approve it.
[14:55] <luis220413> Eickmeyer[m]: What is a priority SRU?
[14:56] <luis220413> bdmurray is the only SRU vanguard that is likely awake (and possibly working) now, according to the timezones in Launchpad profile pages.
[14:56] <Eickmeyer[m]> luis220413: I'm not on the SRU team, so it's not my place to say, but if I were to speculate it's usually something that fixes core functionality of the operating system.
[14:56] <Eickmeyer[m]> Yes, Brian and I are in the same timezone.
[14:57] <Eickmeyer[m]> But Brian is very busy and has other responsibilities as well.
[14:58] <bdmurray> The SRU vanguard is for reviewing packages to accept into -proposed from the unapproved queue (after they've been sponsored) and for accepting packages into -updates from -proposed. I thought we had discussed this on Friday luis220413
[14:58] <luis220413> bdmurray: This is the first case. The package has already been sponsored into the -unapproved queue.
[14:59] <luis220413> https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=openconnect
[14:59] <bdmurray> luis220413: okay, I saw you say 'sponsor' which means upload a debdiff to Ubuntu to me
[15:01] <luis220413> bdmurray: The debdiff is in the bug
[15:07] <tsimonq2> luis220413: Did you know that we have a sponsorship queue that's totally separate in both membership and duties to the SRU team? Ask in -devel for sponsors, don't ask here. It's not the best place for it.
[15:07] <tsimonq2> luis220413: Maybe after it's sponsored if all your ducks are in a row, yeah, perhaps ping the vanguard. once maybe in a day unless it's urgent.
[15:08] <luis220413> tsimonq2: Thanks! But I believe the package was already sponsored into the Unapproved queue.
[15:08] <luis220413> See https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=openconnect
[15:08] <tsimonq2> luis220413: Pinging people over and over for something that's unrelated to what they're currently working on is counterproductive and annoying. You have a lot of energy, I see you're excited, and I've been there. I'm excited to see what you can do. Please, just take it slower.
[15:09] <tsimonq2> (As in, pinging an SRU vanguard for sponsorship when they're in the middle of their SRU groove)
[15:09] <luis220413> tsimonq2: OK, but bdmurray was likely sleeping or not working when I pinged him except for the last ping.
[15:09] <luis220413> According to the timezone in his Launchpad profile
[15:10] <tsimonq2> If it needs to be reviewed and it's in the correct spot, they will get to it. Pinging in IRC is only needed if the fix is particularly urgent or if it's been a while with no activity. In this case, it's still really fresh
[15:10] <luis220413> tsimonq2: It is in the queue since August 2
[15:10] <tsimonq2> While Brian may be happy to help if you asked him to at some point, I'm unsure he'll be as willing to help if you continue sending him a million notifications :)
[15:11] <tsimonq2> And it's August 9th. 22.04.1 was supposed to be released last week but it got delayed
[15:11] <tsimonq2> Again... patience and understanding where we're at in the cycle is everything here
[15:11] <Eickmeyer[m]> To dovetail on that, SRU acceptance can usually take more than a week.
[15:12] <luis220413> tsimonq2: I believe this fix is particularly urgent because it renders Ubuntu (with network-manager-openconnect installed) unable to connect to GlobalProtect VPNs with a common server-side configuration.
[15:13] <luis220413> tsimonq2: I believe reviewing this SRU and accepting it into jammy-proposed should take only a few minutes. This is the last notification for Brian Murray I will send.
[15:13] <luis220413> For this SRU
[15:14] <tsimonq2> Well, you certainly have the visibility now :)
[15:14]  * ogra LOLs about "a few minutes" 🙂
[15:14] <Eickmeyer[m]> luis220413: "only a few minutes" is not for you to decide.
[15:14] <luis220413> tsimonq2: Other than to get it into jammy-updates after it is in jammy-proposed and verified. The reporter has verified their PPA version with the same debdiff.
[15:14] <ogra> noe that two weeks is extremely fast for any SRU usually .... typically assume "several weeks"
[15:14] <ogra> *note
[15:15] <luis220413> Eickmeyer[m]: It is not a decision, but a personal estimate.
[15:15] <tsimonq2> luis220413: Don't worry too hard about this interaction - let's just be better about this in the future please. I want to see your contributions and I'm excited for them but this could be more productive for us all, that's all I'm saying :)
[15:15] <tsimonq2> Again, patience
[15:16] <tsimonq2> You have the visibility. There isn't much more you can say at this point to get it bumped up without Desktop Team backing. I'm sorry
[15:16] <ogra> luis220413, but who are yu to estimate other peoples time (other people that are i.e. currently extremely busy fixing the regression screwup for 22.04.1 ... you are distracting them constantly from their work since a few days)
[15:18] <luis220413> I will leave now but I will see your replies in the logs.
[15:19] <ogra> please d not take it personal ... but tere are processes involved etc and a good estimate for any SRU is weeks, not minutes or day...
[15:19] <ogra> *days
[15:19] <luis220413> ogra: Why does it take so long to review the patch in a priority SRU?
[15:20] <tsimonq2> Agreed, definitely not personal from me either. I've been in your shoes and I get it. I'll say it again, patience is key here
[15:20] <tsimonq2> Because your definition of priority is different...
[15:21] <ogra> because people need to have spare time to do it, it is voluntary work for most of them ... and then there ar processes, different teams involved (as you just learned above, i.e. sponsors are different from SRU vanguards or archive admins etc)
[15:21] <luis220413> tsimonq2: Yes. For me, a priority SRU is a SRU that fixes one or more bugs with very high severity.
[15:21] <bdmurray> The SRU team is somewhat understaffed given that sil_2100 and aI have taken on additional responsibilities. The SRU team is working on the staffing issue though.
[15:21] <arraybolt3[m]> Just from my personal experience as a relatively new contributer, an SRU is "high-priority" when there's a deadline to meet and we're racing against the clock. For instance, I've seen at least two SRUs happen in the blink on an eye because they had to get in before the point release.
[15:21] <luis220413> luis220413: I am not taking this personally.
[15:22] <ogra> 🙂
[15:22] <ogra> good
[15:22] <luis220413> tsimonq2*: I am not taking this personally.
[15:22] <luis220413> I must really leave now but I will see your replies in the logs.
[15:22] <tsimonq2> All good :) just work on it okay? They'll get to it as soon as they can
[16:27] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi [Jammy 22.04.1] has been updated (20220809)
[16:27] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi [Jammy 22.04.1] has been updated (20220809)
[16:27] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+nezha [Jammy 22.04.1] has been updated (20220809)
[16:27] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unmatched [Jammy 22.04.1] has been updated (20220809)
[16:27] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+visionfive [Jammy 22.04.1] has been updated (20220809)
[16:57] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Jammy 22.04.1] has been updated (20220809)
[16:57] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Jammy 22.04.1] has been updated (20220809)
[16:57] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Jammy 22.04.1] has been updated (20220809)
[16:57] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity riscv64 [Jammy 22.04.1] has been updated (20220809)
[16:57] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Jammy 22.04.1] has been updated (20220809)
[18:17] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (focal-proposed/main) [27.9~20.04.1 => 27.10.1~20.04.1] (core)
[18:22] <arraybolt3[m]> The Ubuntu Studio 22.04.1 ISO doesn't seem to have built.
[18:22] <arraybolt3[m]> Oh wait nevermind, found it, the link is just wrong.
[18:22] <Eickmeyer[m]> They don't get built until right about now.
[18:23] <arraybolt3[m]> The link to the ISO on the QA tracker is pointing to a nonexistent folder where Kinetic images should have gone, but asking for a Jammy image.
[18:23] <arraybolt3[m]> So... no wonder it didn't work.
[18:24] <arraybolt3[m]> The real link is http://cdimage.ubuntu.com/ubuntustudio/jammy/dvd/20220809/
[18:24] <Eickmeyer[m]> Oh, that's bad.
[18:24] <Eickmeyer[m]> sil2100: The links on the iso tracker are messed-up.
[18:25] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (bionic-proposed/main) [27.9~18.04.1 => 27.10.1~18.04.1] (core)
[18:30] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (xenial-proposed/main) [27.9~16.04.1 => 27.10.1~16.04.1] (no packageset)
[18:37] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (jammy-proposed/main) [27.9~22.04.1 => 27.10.1~22.04.1] (core)
[18:52] -queuebot:#ubuntu-release- New binary: openfst [s390x] (kinetic-proposed/universe) [1.7.9-4] (no packageset)
[19:32] -queuebot:#ubuntu-release- New binary: openfst [armhf] (kinetic-proposed/universe) [1.7.9-4] (no packageset)
[19:39] <arraybolt3[m]> I don't think this is a regression, but autologin isn't working on Ubuntu Studio (despite having checked the box, the system still requires a password at bootup). I've noticed this same problem on Studio Kinetic. Mentioning it here since it might be an easy fix that we can get in before the .1 release.
[19:40] <arraybolt3[m]> (For just in case, I'm doing a test to see if it's a regression now.)
[19:42] <Eickmeyer[m]> arraybolt3: #ubuntu-studio-devel:matrix.org please...
[19:47] <bdmurray> Eickmeyer[m], arraybolt3[m]: Fixed the Ubuntu Studio download links
[19:48] <Eickmeyer[m]> bdmurray: Awesome, thanks!
[19:48] <arraybolt3[m]> \o/ Thank you!
[20:49] -queuebot:#ubuntu-release- Unapproved: dotnet6 (jammy-proposed/universe) [6.0.107-0ubuntu2~22.04.1 => 6.0.108-0ubuntu1~22.04.1] (no packageset) (sync)
[20:49] <sil2100> arraybolt3[m], Eickmeyer[m]: sadly, no more fixes other than critical-release-blockers from now on!
[20:50] <Eickmeyer[m]> sil2100: Yeah, no worries, it's not a regression anyhow.
[20:51] <sil2100> I mean, any respins starting tomorrow might be problematic, as there are new kernels in the pipeline
[20:51] <sil2100> I can't keep the flood gates closed for too long ;p
[20:52] <Eickmeyer[m]> Yeah, I've got an SRU or two I'm waiting on, but nothing critical.
[20:59] -queuebot:#ubuntu-release- Unapproved: rejected dotnet6 [sync] (jammy-proposed) [6.0.108-0ubuntu1~22.04.1]
[21:16] -queuebot:#ubuntu-release- Unapproved: dotnet6 (jammy-proposed/universe) [6.0.107-0ubuntu2~22.04.1 => 6.0.108-0ubuntu1~22.04.1] (no packageset)
[21:25] -queuebot:#ubuntu-release- Unapproved: accepted dotnet6 [source] (jammy-proposed) [6.0.108-0ubuntu1~22.04.1]
[21:35] -queuebot:#ubuntu-release- New binary: openfst [riscv64] (kinetic-proposed/universe) [1.7.9-4] (no packageset)
[22:03] -queuebot:#ubuntu-release- Unapproved: yt-dlp (focal-backports/universe) [2022.03.08.1-1~bpo20.04.1 => 2022.08.08-1~bpo20.04.1] (no packageset)
[22:05] -queuebot:#ubuntu-release- Unapproved: yt-dlp (jammy-backports/universe) [2022.07.18-1~bpo22.04.1 => 2022.08.08-1~bpo22.04.1] (no packageset)
[23:16] -queuebot:#ubuntu-release- New binary: anonip [amd64] (kinetic-proposed/none) [1.1.0-1] (no packageset)
[23:16] -queuebot:#ubuntu-release- New binary: secrets [amd64] (kinetic-proposed/none) [6.5-2] (no packageset)
[23:16] -queuebot:#ubuntu-release- New binary: gnome-epub-thumbnailer [amd64] (kinetic-proposed/none) [1.6-2] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: python-ldap [amd64] (kinetic-proposed/main) [3.4.2-2] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: gnome-epub-thumbnailer [ppc64el] (kinetic-proposed/none) [1.6-2] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: libcommuni [amd64] (kinetic-proposed/none) [3.7.0-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: gnome-epub-thumbnailer [s390x] (kinetic-proposed/none) [1.6-2] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: haskell-language-c99-simple [ppc64el] (kinetic-proposed/none) [0.1.2-2] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: libcommuni [ppc64el] (kinetic-proposed/none) [3.7.0-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: haskell-language-c99-simple [s390x] (kinetic-proposed/none) [0.1.2-2] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: renpy [amd64] (kinetic-proposed/universe) [8.0.1+dfsg-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: libcommuni [s390x] (kinetic-proposed/none) [3.7.0-1] (no packageset)
[23:25] -queuebot:#ubuntu-release- New binary: renpy [s390x] (kinetic-proposed/universe) [8.0.1+dfsg-1] (no packageset)
[23:27] -queuebot:#ubuntu-release- New binary: renpy [ppc64el] (kinetic-proposed/universe) [8.0.1+dfsg-1] (no packageset)
[23:32] -queuebot:#ubuntu-release- New binary: gnome-epub-thumbnailer [arm64] (kinetic-proposed/universe) [1.6-2] (no packageset)
[23:33] -queuebot:#ubuntu-release- New binary: gnome-epub-thumbnailer [armhf] (kinetic-proposed/universe) [1.6-2] (no packageset)
[23:37] -queuebot:#ubuntu-release- New binary: gnome-epub-thumbnailer [riscv64] (kinetic-proposed/universe) [1.6-2] (no packageset)
[23:40] -queuebot:#ubuntu-release- New binary: haskell-language-c99-simple [arm64] (kinetic-proposed/universe) [0.1.2-2] (no packageset)
[23:42] -queuebot:#ubuntu-release- New binary: libcommuni [armhf] (kinetic-proposed/universe) [3.7.0-1] (no packageset)
[23:43] -queuebot:#ubuntu-release- New binary: renpy [armhf] (kinetic-proposed/universe) [8.0.1+dfsg-1] (no packageset)
[23:46] -queuebot:#ubuntu-release- New binary: libcommuni [arm64] (kinetic-proposed/universe) [3.7.0-1] (no packageset)
[23:46] -queuebot:#ubuntu-release- New binary: renpy [arm64] (kinetic-proposed/universe) [8.0.1+dfsg-1] (no packageset)
[23:54] -queuebot:#ubuntu-release- New binary: libcommuni [riscv64] (kinetic-proposed/universe) [3.7.0-1] (no packageset)