[00:04] -queuebot:#ubuntu-release- New binary: onedriver [arm64] (noble-proposed/universe) [0.14.1-1] (no packageset) [00:07] ( we [Lubuntu] wanted to include arraybolt3 who isn't on Lubuntu Council; Aaron is going to act as release manager for 22.04.4 ) [00:09] wanting to include arraybolt3 can be done by adding him as a direct member of the team; the current situation as mentioned is that any core dev can now request iso rebuilds for lubuntu... [00:10] somehow Ubuntu Core Development Team is a subteam of Lubuntu Developers, which is in turn a subteam of lubuntu-iso-managers [00:15] I am a strong proponent that any team in Ubuntu which owns packages in the archive and maintains those packages in a launchpad team VCS should have core-dev as a member of that team so that there's not a disconnect between upload rights and commit rights [00:15] what I think is wrong here is that "ISO managers" is a superset of "Lubuntu Developers" [00:21] I mean, to me that seems backwards - core devs can and should be able to override things in the archive, but messing with the "upstream" (ish) sources should reasonably be limited to the people who have deep internal knowledge of those sources. On the other hand anyone who has deep internal knowledge of those sources also is a deep part of the corresponding team and should be able to do [00:21] ISO-related things like requesting respins. That's my first thought on it, though obviously I've not been around as long as others here so perhaps there are serious problems my way of doing things can result in (other than those caused by poor coordination, though that's a concern too). [00:26] vorlon, ~ubuntucinnamon-dev [00:29] ItzSwirlz: so as per the above discussion regarding lubuntu, setting this gives 128+ people access to request cinnamon respins https://launchpad.net/~ubuntucinnamon-dev [00:30] -queuebot:#ubuntu-release- Unapproved: gjs (jammy-proposed/main) [1.72.2-0ubuntu2 => 1.72.4-0ubuntu0.22.04.1~really.is.1.72.3.0ubuntu0.22.04.1] (desktop-core, desktop-extra, i386-whitelist, mozilla) [00:33] probably eventually have a group of people in a separate ~ubuntucinnamon-release team [00:34] perhaps better to wait until that exists, before changing the current working thing? [00:35] -queuebot:#ubuntu-release- Unapproved: gjs (jammy-proposed/main) [1.72.2-0ubuntu2 => 1.72.4-0ubuntu0.22.04.2~really.is.1.72.3.0ubuntu0.22.04.1] (desktop-core, desktop-extra, i386-whitelist, mozilla) [00:40] -queuebot:#ubuntu-release- Unapproved: gjs (jammy-proposed/main) [1.72.2-0ubuntu2 => 1.72.4-0ubuntu0.22.04.2~really.is.1.72.2.0ubuntu2] (desktop-core, desktop-extra, i386-whitelist, mozilla) [00:48] ItzSwirlz: You know, you can always just... you know, create ~ubuntucinnamon-release yourself. [00:58] -queuebot:#ubuntu-release- Unapproved: gjs (jammy-proposed/main) [1.72.2-0ubuntu2 => 1.72.4-0ubuntu0.22.04.2~really.is.1.72.2.0ubuntu2] (desktop-core, desktop-extra, i386-whitelist, mozilla) [01:26] vorlon: cd-boot-images* packages are phasing for jammy which seems unnecessary [01:30] bdmurray: bumped [01:33] -queuebot:#ubuntu-release- New binary: pytorch-scatter [amd64] (noble-proposed/universe) [2.1.2-1build1] (no packageset) [01:36] -queuebot:#ubuntu-release- New binary: pytorch-cluster [amd64] (noble-proposed/universe) [1.6.3-1build1] (no packageset) [01:40] -queuebot:#ubuntu-release- New binary: pytorch-scatter [arm64] (noble-proposed/universe) [2.1.2-1build1] (no packageset) [01:45] -queuebot:#ubuntu-release- Unapproved: gjs (jammy-proposed/main) [1.72.2-0ubuntu2 => 1.72.4-0ubuntu0.22.04.2] (desktop-core, desktop-extra, i386-whitelist, mozilla) [01:45] tjaalton: How would you like to proceed with https://bugs.launchpad.net/ubuntu/+source/samba/+bug/2046994? I just cleaned up the autopkgtest regressions (flaky tests). Jammy is verified by the user, but Focal is not verified due to hardware constraints. We could either leave Focal in -proposed until someone can verify it, or push both. [01:46] -ubottu:#ubuntu-release- Launchpad bug 2046994 in samba (Ubuntu Jammy) "Spotlight search function broken with macOS Ventura and later client" [High, Fix Committed] [01:53] -queuebot:#ubuntu-release- New binary: open3d [amd64] (noble-proposed/universe) [0.18.0+ds-3] (no packageset) [02:09] -queuebot:#ubuntu-release- New binary: pytorch-cluster [arm64] (noble-proposed/universe) [1.6.3-1build1] (no packageset) [03:13] -queuebot:#ubuntu-release- New binary: onedriver [riscv64] (noble-proposed/universe) [0.14.1-1] (no packageset) [05:15] -queuebot:#ubuntu-release- New binary: mininet [amd64] (noble-proposed/none) [2.3.0-1.1] (no packageset) [05:15] -queuebot:#ubuntu-release- New binary: mininet [ppc64el] (noble-proposed/none) [2.3.0-1.1] (no packageset) [05:16] -queuebot:#ubuntu-release- New binary: mininet [arm64] (noble-proposed/none) [2.3.0-1.1] (no packageset) [05:17] -queuebot:#ubuntu-release- New binary: mininet [armhf] (noble-proposed/none) [2.3.0-1.1] (no packageset) [05:17] -queuebot:#ubuntu-release- New binary: mininet [s390x] (noble-proposed/none) [2.3.0-1.1] (no packageset) [05:33] -queuebot:#ubuntu-release- New: accepted mininet [amd64] (noble-proposed) [2.3.0-1.1] [05:33] -queuebot:#ubuntu-release- New: accepted mininet [armhf] (noble-proposed) [2.3.0-1.1] [05:33] -queuebot:#ubuntu-release- New: accepted mininet [s390x] (noble-proposed) [2.3.0-1.1] [05:33] -queuebot:#ubuntu-release- New: accepted mininet [arm64] (noble-proposed) [2.3.0-1.1] [05:33] -queuebot:#ubuntu-release- New: accepted mininet [ppc64el] (noble-proposed) [2.3.0-1.1] [05:34] -queuebot:#ubuntu-release- New: accepted onedriver [amd64] (noble-proposed) [0.14.1-1] [05:34] -queuebot:#ubuntu-release- New: accepted onedriver [ppc64el] (noble-proposed) [0.14.1-1] [05:34] -queuebot:#ubuntu-release- New: accepted onedriver [s390x] (noble-proposed) [0.14.1-1] [05:34] -queuebot:#ubuntu-release- New: accepted rust-axum [amd64] (noble-proposed) [0.6.20-14] [05:34] -queuebot:#ubuntu-release- New: accepted onedriver [arm64] (noble-proposed) [0.14.1-1] [05:34] -queuebot:#ubuntu-release- New: accepted open3d [amd64] (noble-proposed) [0.18.0+ds-3] [05:34] -queuebot:#ubuntu-release- New: accepted onedriver [riscv64] (noble-proposed) [0.14.1-1] [05:38] -queuebot:#ubuntu-release- New binary: mininet [riscv64] (noble-proposed/none) [2.3.0-1.1] (no packageset) [05:47] -queuebot:#ubuntu-release- New: accepted mininet [riscv64] (noble-proposed) [2.3.0-1.1] [06:27] mitchdz: if you mean releasing it, then come back after the weekend [08:00] vorlon, I built llvm-18 with time64, but the "Provides" on armhf are still nill https://launchpadlibrarian.net/714611775/buildlog_ubuntu-noble-armhf.llvm-toolchain-18_1%3A18.1.0~rc2-3ubuntu4_BUILDING.txt.gz [08:00] what is going on? [08:01] what are you expecting to populate Provides: on armhf in this context? [08:02] if you mean Provides: ${t64:Provides} on libclang evaluating to empty on armhf this is expected [08:03] because armhf is the architecture where we're specifically NOT declaring ABI compatibility with pre-renamed packages [08:22] ok [08:22] INFO Processing upload gobject-introspection_1.78.1-15_amd64.changes [08:22] INFO Upload was rejected: [08:22] INFO gir1.2-glib-2.0-dev_1.78.1-15_amd64.deb: Version older than that in the archive. 1.78.1-15 <= 2.79.1-1 [08:22] INFO gir1.2-glib-2.0_1.78.1-15_amd64.deb: Version older than that in the archive. 1.78.1-15 <= 2.79.1-1 [08:22] wow another good way to delay the glib2 transition [08:24] jbicha, what is this takeover from glib2.0? [08:26] -queuebot:#ubuntu-release- New binary: cdogs-sdl [ppc64el] (noble-proposed/universe) [1.5.0+dfsg-1] (no packageset) [08:26] so maybe we shoudl sync glib again or drop the binaries ? [08:26] vorlon, this looks so sad [08:26] mm [08:27] I'm personally more concerned about it delaying python3-defaults, but, well [08:30] kick it out? but in any case, glib2.0 having higher version is sad [08:30] if we sync glib2.0 from debian experimental again such binaries will be dropped, but somebody needs to remove manually to let britney be happy? [09:45] -queuebot:#ubuntu-release- New binary: halide [amd64] (noble-proposed/universe) [17.0.0-1] (no packageset) [11:22] can someone please look at ubuntu-boot-test in NEW? [11:22] (and i also have a couple GRUB SRUs for jammy in mantic that have been sitting around since late last year) [11:41] LocutusOfBorg: I'm going to do another gobject-introspection upload https://salsa.debian.org/gnome-team/gobject-introspection/-/merge_requests/14 [11:41] -ubottu:#ubuntu-release- Merge 14 in gnome-team/gobject-introspection "Package gobject-introspection 1.79.1" [Opened] [11:41] thanks for caring [11:42] LocutusOfBorg: if we want a newer glib from Experimental we need to revert the renamed time library 🫤 [11:43] but new glib wouldn't fix the gobject-introspection issue [11:43] jbicha, why it won't [11:43] if we kick out the wrong binaries [11:43] sync newer glibc without time renaming foobar [11:43] drop wrong binaries [11:43] build gobject-introspection [11:43] you need archive admin for sure :D [11:44] glib2.0 doesn't have wrong binaries. Upstream is moving files from gobject-introspection to glib2.0 [11:45] but glib2.0 dropped binaries again in experimental? [11:45] I don't understand [11:46] nevermind [11:46] I'm sure this morning I couldn't find gir1.2-glib-2.0-dev_2.79.2-1_amd64.deb on experimental :/ [11:46] bad me [11:47] so ok, you package new gobject-introspection, and move on [11:47] I don't think Debian is set up to autoreject binaries with older versions. It's a nice feature that Launchpad does that. [11:47] looks good, specially because also Debian will do the same once new glib2.0 goes in sid? [11:47] jbicha, debian didn't have such binaries in sid, only in experimental [11:47] yes, I'm just trying to coordinate it with smcv since he understands this move better than I do. Hopefully today [11:48] so thanks for fixing it up! [11:48] yes, but we also didn't realize that my glib upload to noble would cause g-i to essentially ftbfs [12:10] -queuebot:#ubuntu-release- New binary: rust-audio-checker [amd64] (noble-proposed/universe) [0.1.0-1] (no packageset) [12:11] -queuebot:#ubuntu-release- New binary: rust-audio-checker [arm64] (noble-proposed/universe) [0.1.0-1] (no packageset) [12:11] -queuebot:#ubuntu-release- New binary: rust-audio-checker [ppc64el] (noble-proposed/universe) [0.1.0-1] (no packageset) [12:11] -queuebot:#ubuntu-release- New binary: rust-audio-checker [armhf] (noble-proposed/universe) [0.1.0-1] (no packageset) [12:12] -queuebot:#ubuntu-release- New binary: rust-octocrab [amd64] (noble-proposed/universe) [0.31.2-1] (no packageset) [12:12] -queuebot:#ubuntu-release- New binary: rust-audio-checker [s390x] (noble-proposed/universe) [0.1.0-1] (no packageset) [12:12] -queuebot:#ubuntu-release- New binary: rust-octocrab [armhf] (noble-proposed/universe) [0.31.2-1] (no packageset) [12:13] -queuebot:#ubuntu-release- New binary: rust-octocrab [arm64] (noble-proposed/universe) [0.31.2-1] (no packageset) [12:13] -queuebot:#ubuntu-release- New binary: rust-octocrab [ppc64el] (noble-proposed/universe) [0.31.2-1] (no packageset) [12:15] -queuebot:#ubuntu-release- New binary: rust-octocrab [s390x] (noble-proposed/universe) [0.31.2-1] (no packageset) [12:39] release team members: did you see stgraber's email to ubuntu-release@lists.u.c about queuebot? if its still useful i'd be happy to help take over operating it from stgraber if theres no objections [12:55] -queuebot:#ubuntu-release- New binary: rust-octocrab [riscv64] (noble-proposed/universe) [0.31.2-1] (no packageset) === pushkarnk1 is now known as pushkarnk [13:00] ubuntu-archive please? old binaries left on armhf: libopen3d0.17 (from 0.17.0+ds-9build2) [13:00] NBS cleanup [13:02] what is left for libgssglue promotion? LP: #2044535 [13:02] -ubottu:#ubuntu-release- Launchpad bug 2044535 in gsasl (Ubuntu) "[MIR] libgssglue" [Undecided, New] https://launchpad.net/bugs/2044535 [13:35] LocutusOfBorg, gone === mfo_ is now known as mfo [14:24] hey ubuntu-release folks, quick followup about the poppler transition for noble: is now a good time to do the transition? [14:25] we were thinking of doing it last week (or the week before?) but decided to hold off a bit, and e.g. the perl transition has finished now [15:21] -queuebot:#ubuntu-release- New: accepted rust-octocrab [arm64] (noble-proposed) [0.31.2-1] [15:21] -queuebot:#ubuntu-release- New: accepted rust-octocrab [riscv64] (noble-proposed) [0.31.2-1] [15:21] -queuebot:#ubuntu-release- New: accepted rust-octocrab [ppc64el] (noble-proposed) [0.31.2-1] [15:21] -queuebot:#ubuntu-release- New: accepted rust-octocrab [s390x] (noble-proposed) [0.31.2-1] [15:21] -queuebot:#ubuntu-release- New: accepted cdogs-sdl [ppc64el] (noble-proposed) [1.5.0+dfsg-1] [15:21] -queuebot:#ubuntu-release- New: accepted rust-audio-checker [amd64] (noble-proposed) [0.1.0-1] [15:21] -queuebot:#ubuntu-release- New: accepted rust-audio-checker [armhf] (noble-proposed) [0.1.0-1] [15:21] -queuebot:#ubuntu-release- New: accepted rust-audio-checker [s390x] (noble-proposed) [0.1.0-1] [15:21] -queuebot:#ubuntu-release- New: accepted rust-octocrab [armhf] (noble-proposed) [0.31.2-1] [15:21] -queuebot:#ubuntu-release- New: accepted halide [amd64] (noble-proposed) [17.0.0-1] [15:21] -queuebot:#ubuntu-release- New: accepted rust-audio-checker [ppc64el] (noble-proposed) [0.1.0-1] [15:21] -queuebot:#ubuntu-release- New: accepted rust-audio-checker [arm64] (noble-proposed) [0.1.0-1] [15:21] -queuebot:#ubuntu-release- New: accepted rust-octocrab [amd64] (noble-proposed) [0.31.2-1] [15:22] teward: seen and will work on a response. I think the "right" answer is for us to run this as a service in the Canonical cloud on a stand-alone instance, so that release team and/or archive admins have direct admin oversight of it. [15:23] teward: but we may wind up with a gap here requiring at least stopgap hosting given the deadline, in which case support would be appreciated [15:24] vorlon: ack, yeah if IS and Canonical can run it that saves time, but in the interim I have the resources to assist between deadline and Canonical readiness :) [15:24] Canonical IS can *host* it. we would have to *run* it ;) [15:24] :P [15:25] vorlon: yep, still happy to help if I can in the interim until that's ready [15:25] depends on how fast stgraber wants to push the operation off :) [15:26] just let me know how Release and AAs want to proceed always happy to give more resources to assist :) [15:26] I can certainly be convinced to keep the thing running a couple more weeks if that's enough to get it running on Canonical infra [15:26] doesn't make too much sense to have it moved twice in rapid succession [15:26] teward: did you see the scrollback yesterday here about the surprising outcome that having 'lubuntu-iso-managers' be the product owner in the iso tracker means 120+ developers now have the ability to trigger lubuntu respins vs the iso-managers->lubuntu-dev->core-dev membership? [15:27] vorlon: no because IRCCloud told me to die [15:27] that's a problem [15:27] teward: when you gave me the team name I assumed it was going to have as members just the short list of people mentioned should have access [15:27] heh [15:27] i can strip coredev [15:27] and lubuntu-dev [15:27] no [15:27] that's not hard [15:27] i didn't set it up [15:27] stripping lubuntu-dev yes [15:27] but don't strip core-dev from lubuntu-dev :) [15:27] no i meant from iso managers [15:27] i created and handed off because i had things that time guess there's an oversight 1 moment [15:27] *grabs the flamethrower* [15:28] yes I'm saying core-dev is not a direct member, you can only remove it by removing lubuntu-dev, don't remove core-dev from lubuntu-dev [15:28] vorlon: last night after i logged out was busy :P [15:28] so i didn't see the scrollback yet [15:28] helping to get some stuff moved on IS for the email chaos that GMail and Yahoo are causing [15:28] (and are already triggering boucnes on some of the Lubuntu lists) [15:30] vorlon: lubuntu-dev removed; arraybolt3, kc2bez, wxl, myself, and tsimonq2 as direct members. Also indirect members are Lubuntu Council which also just makes sense. [15:30] so Council members can poke it too [15:30] as soon as that syncs up it should be good to go :0 [15:47] teward: ok perfect [16:21] stgraber: yeah i think if you can wait for Canonical and Release/AA to get it up and running and hold out a few extra weeks that'd be great, saves having to move it twice. I think the only concern was whether that deadline was firm or mutable. :) [16:21] (though I am currently bringing chaos via Philipp to IS for email stuff too so) [17:17] ubuntu-release: bump about my earlier question about whether it's a good time to do the poppler transition in noble now, in case any release team members are still around [17:51] bandali: as part of the transition don't upload no-change rebuilds for any packages currently in -proposed [17:55] vorlon, ack, thanks. is that because those -proposed packages would be later "rebuilt" anyway upon acceptance into the archive? [17:55] bandali: it's because the packages currently in -proposed are 90% certain to be there because they are entangled in existing transitions (python3, glib2.0, ruby) [17:56] so clobbering the current builds would cause work for us to untangle those transitions again [17:57] ahh okay gotcha gotcha, makes sense. thanks for explaining :) [18:32] -queuebot:#ubuntu-release- New binary: antlr4-cpp-runtime [armhf] (noble-proposed/universe) [4.10+dfsg-1] (no packageset) [18:32] -queuebot:#ubuntu-release- New binary: antlr4-cpp-runtime [ppc64el] (noble-proposed/universe) [4.10+dfsg-1] (no packageset) [18:33] -queuebot:#ubuntu-release- New binary: antlr4-cpp-runtime [arm64] (noble-proposed/universe) [4.10+dfsg-1] (no packageset) [18:34] -queuebot:#ubuntu-release- New binary: antlr4-cpp-runtime [s390x] (noble-proposed/universe) [4.10+dfsg-1] (no packageset) [18:35] -queuebot:#ubuntu-release- Unapproved: rejected ceph [source] (jammy-proposed) [17.2.7-0ubuntu0.22.04.1] [18:42] -queuebot:#ubuntu-release- New binary: antlr4-cpp-runtime [amd64] (noble-proposed/universe) [4.10+dfsg-1] (no packageset) [19:16] vorlon: all the language-packs are also phasing but I guess it'll sort it self over the weekend [19:18] bdmurray: ok. is that something it would make sense to implement as policy in the code? [19:18] (langpacks to 100%) [19:19] and maybe even for cd-boot-images [19:20] The phased-updater code or the sru-release code? [19:20] Oh right sru team members can't set the p-u-p [19:20] wah-wah [19:22] yeah [19:26] -queuebot:#ubuntu-release- New binary: poppler [i386] (noble-proposed/main) [24.02.0-1ubuntu1] (desktop-core, i386-whitelist, ubuntu-server) [19:28] -queuebot:#ubuntu-release- New binary: poppler [amd64] (noble-proposed/main) [24.02.0-1ubuntu1] (desktop-core, i386-whitelist, ubuntu-server) [19:28] -queuebot:#ubuntu-release- New binary: poppler [s390x] (noble-proposed/main) [24.02.0-1ubuntu1] (desktop-core, i386-whitelist, ubuntu-server) === chris14_ is now known as chris14 [19:29] -queuebot:#ubuntu-release- New binary: poppler [arm64] (noble-proposed/main) [24.02.0-1ubuntu1] (desktop-core, i386-whitelist, ubuntu-server) [19:29] -queuebot:#ubuntu-release- New binary: poppler [ppc64el] (noble-proposed/main) [24.02.0-1ubuntu1] (desktop-core, i386-whitelist, ubuntu-server) [19:29] -queuebot:#ubuntu-release- New binary: poppler [armhf] (noble-proposed/main) [24.02.0-1ubuntu1] (desktop-core, i386-whitelist, ubuntu-server) [19:30] well steve there is this FULLY_PHASED_PACKAGES variable in the phased-updater [19:30] He said after only looking himself. [19:54] -queuebot:#ubuntu-release- Unapproved: dovecot (jammy-proposed/main) [1:2.3.16+dfsg1-3ubuntu2.2 => 1:2.3.16+dfsg1-3ubuntu2.3] (ubuntu-server) [19:55] livecd-rootfs/ubuntustudio fail *sad trombone noises* [19:56] Yes, I know it needs to migrate. [20:31] bdmurray: certainly - I didn't think the implementation would be challenging, I was asking it as a question wrt if you thought it should be a policy :) [20:32] vorlon: I do, so I'm working on an MP. [20:32] -queuebot:#ubuntu-release- New binary: gnome-snapshot [ppc64el] (noble-proposed/universe) [45.2+vendored-0ubuntu1] (no packageset) [20:33] -queuebot:#ubuntu-release- New binary: gnome-snapshot [amd64] (noble-proposed/universe) [45.2+vendored-0ubuntu1] (no packageset) [20:34] -queuebot:#ubuntu-release- New binary: gnome-snapshot [arm64] (noble-proposed/universe) [45.2+vendored-0ubuntu1] (no packageset) [20:38] -queuebot:#ubuntu-release- New binary: gnome-snapshot [s390x] (noble-proposed/universe) [45.2+vendored-0ubuntu1] (no packageset) [20:42] -queuebot:#ubuntu-release- New binary: gnome-snapshot [armhf] (noble-proposed/universe) [45.2+vendored-0ubuntu1] (no packageset) [21:17] -queuebot:#ubuntu-release- Unapproved: update-notifier (jammy-proposed/main) [3.192.54.6 => 3.192.54.7] (ubuntu-desktop, ubuntu-server) [21:30] -queuebot:#ubuntu-release- Unapproved: update-notifier (bionic-proposed/main) [3.192.1.19 => 3.192.1.20] (ubuntu-desktop, ubuntu-server) [21:33] vorlon I see you did rollback libguestfs to allow perl migration, can I now upload it again (no changes) to add support for ruby 3.2 and php 8.3? [21:35] kanashiro: perl is done but I think it's still entangled with python which I'm hoping for us to finish soon [21:35] kanashiro: nevermind, it looks like it was only entangled with perl. yes, you're clear to upload [21:37] and I swear the list of autopkgtest regressions for python3-defaults is longer now than it was yesterday morning :P [21:39] vorlon thanks! [21:42] -queuebot:#ubuntu-release- Unapproved: update-notifier (xenial-proposed/main) [3.168.20 => 3.168.21] (ubuntu-desktop, ubuntu-server) [21:45] -queuebot:#ubuntu-release- Unapproved: update-notifier (focal-proposed/main) [3.192.30.17 => 3.192.30.18] (ubuntu-desktop, ubuntu-server) [21:48] -queuebot:#ubuntu-release- New: accepted antlr4-cpp-runtime [amd64] (noble-proposed) [4.10+dfsg-1] [21:48] -queuebot:#ubuntu-release- New: accepted antlr4-cpp-runtime [armhf] (noble-proposed) [4.10+dfsg-1] [21:48] -queuebot:#ubuntu-release- New: accepted antlr4-cpp-runtime [s390x] (noble-proposed) [4.10+dfsg-1] [21:48] -queuebot:#ubuntu-release- New: accepted antlr4-cpp-runtime [arm64] (noble-proposed) [4.10+dfsg-1] [21:48] -queuebot:#ubuntu-release- New: accepted antlr4-cpp-runtime [ppc64el] (noble-proposed) [4.10+dfsg-1] [21:57] -queuebot:#ubuntu-release- New source: msgraph (noble-proposed/primary) [0.1.0-0ubuntu1] [22:10] -queuebot:#ubuntu-release- Unapproved: rejected gjs [source] (jammy-proposed) [1.72.4-0ubuntu0.22.04.1~really.is.1.72.3.0ubuntu0.22.04.1] [22:10] -queuebot:#ubuntu-release- Unapproved: rejected gjs [source] (jammy-proposed) [1.72.4-0ubuntu0.22.04.2~really.is.1.72.3.0ubuntu0.22.04.1] [22:11] -queuebot:#ubuntu-release- Unapproved: rejected gjs [source] (jammy-proposed) [1.72.4-0ubuntu0.22.04.2~really.is.1.72.2.0ubuntu2] [22:25] -queuebot:#ubuntu-release- New binary: antlr4-cpp-runtime [riscv64] (noble-proposed/universe) [4.10+dfsg-1] (no packageset) [23:02] -queuebot:#ubuntu-release- New binary: gnome-snapshot [riscv64] (noble-proposed/universe) [45.2+vendored-0ubuntu1] (no packageset) [23:19] -queuebot:#ubuntu-release- New binary: h2orestart [amd64] (noble-proposed/universe) [0.6.0-1] (no packageset) [23:21] -queuebot:#ubuntu-release- New binary: python-whey [amd64] (noble-proposed/universe) [0.0.24-1] (no packageset) [23:21] -queuebot:#ubuntu-release- New binary: r-cran-intergraph [amd64] (noble-proposed/universe) [2.0-4-1] (no packageset) [23:21] -queuebot:#ubuntu-release- New binary: r-cran-areal [amd64] (noble-proposed/universe) [0.1.8+dfsg-1] (no packageset) [23:42] -queuebot:#ubuntu-release- New binary: poppler [riscv64] (noble-proposed/main) [24.02.0-1ubuntu1] (desktop-core, i386-whitelist, ubuntu-server)