/srv/irclogs.ubuntu.com/2024/03/30/#ubuntu-release.txt

tomreynit ia also listed at https://wiki.ubuntu.com/SecurityTeam/FAQ#GPG_Keys_used_by_Ubuntu00:00
jbichashould we update the channel topics again for the new archive freeze?00:01
vorlonjbicha: thanks, doing00:06
=== vorlon changed the topic of #ubuntu-release to: Released: 23.10 Mantic Minotaur, 22.04.4 Jammy Jellyfish | Archive: freeze for xz-utils mitigation | Highlight ubuntu-archive for archive admin help | We accept payment in cash, cheque or scotch | melius malum quod cognoscis | infinity, you are missed
-queuebot:#ubuntu-release- Unapproved: octave-control (noble-proposed/universe) [4.0.1-1 => 4.0.1-1ubuntu1] (no packageset)00:25
-queuebot:#ubuntu-release- Unapproved: libpng1.6 (noble-proposed/main) [1.6.43-3 => 1.6.43-5] (core, i386-whitelist) (sync)00:28
-queuebot:#ubuntu-release- Unapproved: kbuild (noble-proposed/universe) [1:0.1.9998svn3589+dfsg-1 => 1:0.1.9998svn3604+dfsg-1] (no packageset) (sync)00:28
=== chris14_ is now known as chris14
vorlonwould still be a good idea for someone to see if they can reproduce that debootstrap failure.  Here, I'm hitting an unrelated failure04:11
vorlonjuliank: apt/armhf test failure with the reverted xz-utils https://autopkgtest.ubuntu.com/packages/a/apt/noble/armhf05:37
=== alucardromero2 is now known as alucardromero
-queuebot:#ubuntu-release- Unapproved: ukui-panel (noble-proposed/universe) [4.0.0.2-1build1 => 4.0.0.4-1] (ubuntukylin) (sync)06:57
LocutusOfBorg2024-03-30 04:05:13 CETPublishedNobleupdatesmainmisc1.6.42-107:13
LocutusOfBorg 2024-03-28 08:53:09 CETPublishedNoblereleasemainmisc1.6.43-307:13
LocutusOfBorgOMG what does this mean?07:13
LocutusOfBorglibpng1.6 has higher version in noble-updates07:13
LocutusOfBorgand a non-renamed library in updates?07:14
vorlonLocutusOfBorg: this is rollback for xz-utils07:31
LocutusOfBorgok07:31
LocutusOfBorgI'm trying to fix haskell, I got a fix, but the archive looks meh07:31
vorlonwe're using the noble-updates pocket to be able to have last-known-good amd64 binaries available, in parallel with the latest versions on all other architectures07:31
LocutusOfBorghttps://launchpad.net/~costamagnagianfranco/+archive/ubuntu/costamagnagianfranco-ppa/+sourcepub/15894110/+listing-archive-extra07:31
vorlonso that we don't have to re-bootstrap armhf for time_t07:31
LocutusOfBorgFYI ^^07:31
LocutusOfBorghaskell-haskell-gi suffered a failure due to newer glib2.007:32
LocutusOfBorgvorlon, it's ok for me :)07:32
LocutusOfBorgjust maybe mention some uninstallabilities, or archive inconsistencies on topic?07:32
LocutusOfBorgbut as long as this is something you are aware of, I go back to haskell07:33
vorlonwhat uninstallabilities specifically?07:33
LocutusOfBorgI mean version lower in updates w.r.t. release pocket07:36
LocutusOfBorgI don't know if I can upload an haskell fix and start give backs, or should I wait07:37
LocutusOfBorghaskell can take few days to build on risc and armhf, the sooner we start, the better07:37
LocutusOfBorg(I mean haskell-gi-* foobar is really long)07:37
LocutusOfBorgbtw I fixed in my libpng1.6 the udeb uninstallability issue due to renaming, I don't think this is an Ubuntu issue, but also I'm scared if this can be the culprit of the issues you are having07:38
vorlonyou can upload; stuff in the queue will be released once we're ready to go with rebuilding everything07:50
-queuebot:#ubuntu-release- Unapproved: haskell-charsetdetect-ae (noble-proposed/universe) [1.1.0.4-5 => 1.1.0.4-6] (no packageset) (sync)07:57
-queuebot:#ubuntu-release- Unapproved: haskell-fgl (noble-proposed/universe) [5.8.0.0-1 => 5.8.1.1-1] (no packageset) (sync)07:57
-queuebot:#ubuntu-release- Unapproved: haskell-hoogle (noble-proposed/universe) [5.0.18.3+dfsg1-4build1 => 5.0.18.3+dfsg1-5] (no packageset) (sync)07:57
-queuebot:#ubuntu-release- Unapproved: pkg-haskell-tools (noble-proposed/universe) [0.12.4build1 => 0.12.5] (no packageset) (sync)07:58
-queuebot:#ubuntu-release- Unapproved: haskell-haskell-gi (noble-proposed/universe) [0.26.7-2build1 => 0.26.7-2ubuntu1] (no packageset)08:00
mitya57vorlon: I also have one issue on amd64: https://launchpadlibrarian.net/721969472/buildlog_ubuntu-noble-amd64.qttools-opensource-src_5.15.13-1_BUILDING.txt.gz08:02
mitya57It looks like libwacom-common is available in both -release and -updates (with -release having newer version), while libwacom9 is available only in -updates (and the version mismatches libwacom-common in -release).08:02
mitya57Maybe related to the fact that one of them is arch:all and another arch:any (and arch:any amd64 binaries were deleted from -release?)08:02
vorlonyes08:03
vorlonthose should all shake out when the rebuilds happen in -proposed08:04
mitya57Ah, okay08:04
vorlonthere may be a few cases where we have to drop the Arch: all package from the release pocket as well to let new amd64 build, but that should be rare08:04
mitya57vorlon: By the way, how much chances I have to get new Qt 5 patch release in noble? I thought I would try to manage to get it prepared before beta freeze, but with this xz rollback and yet another world rebuild maybe I should give up?08:05
* mitya57 started preparing it in a ppa as usual: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4979/+packages08:06
-queuebot:#ubuntu-release- Unapproved: connectagram (noble-proposed/universe) [1.3.5-1ubuntu1 => 1.3.5-2] (no packageset) (sync)08:15
-queuebot:#ubuntu-release- Unapproved: indi-gige (noble-proposed/universe) [0.1+20221223115700-1ubuntu1 => 0.1+20221223115700-2] (no packageset) (sync)08:16
-queuebot:#ubuntu-release- Unapproved: entropybroker (noble-proposed/universe) [2.9-7ubuntu1 => 2.9-8] (no packageset) (sync)08:16
-queuebot:#ubuntu-release- Unapproved: glibc (noble-proposed/main) [2.39-0ubuntu7 => 2.39-0ubuntu8] (core, i386-whitelist)08:33
-queuebot:#ubuntu-release- Unapproved: accepted glibc [source] (noble-proposed) [2.39-0ubuntu8]08:46
LocutusOfBorg[1;91mERROR: [97mcouldn't find API description for GLib.time_t[22;94m08:53
LocutusOfBorgLOL08:53
lotuspsychjeim getting a weird error and depend on trying to install nmap on noble, can anyone test that?09:41
lotuspsychjeits a conflict between nmap-common versions09:49
RikMillslotuspsychje: that is not surprising, as there is currently a mass removal of amd64 binaries that were built after the compromised xz-utils was published09:53
lotuspsychjeok tnx RikMills just wanted to report09:54
RikMillslotuspsychje: np. when the (7000 ish) packages get rebuilt in due course, should all get fixed09:56
lotuspsychjephew good luck to all09:56
-queuebot:#ubuntu-release- Unapproved: xubuntu-default-settings (noble-proposed/universe) [24.04.2 => 24.04.3] (xubuntu)10:57
-queuebot:#ubuntu-release- Unapproved: google-android-installers (noble-proposed/multiverse) [1707406511ubuntu3 => 1710437545-3] (no packageset) (sync)11:15
-queuebot:#ubuntu-release- Unapproved: newlib (noble-proposed/universe) [3.3.0-1.3 => 4.4.0.20231231-2] (no packageset) (sync)12:01
-queuebot:#ubuntu-release- Unapproved: gcc-14 (noble-proposed/main) [14-20240315-1ubuntu1 => 14-20240330-1ubuntu1] (i386-whitelist)13:05
-queuebot:#ubuntu-release- Unapproved: gcc-14 (noble-proposed/main) [14-20240315-1ubuntu1 => 14-20240330-1ubuntu1] (i386-whitelist)13:16
-queuebot:#ubuntu-release- Unapproved: rejected gcc-14 [source] (noble-proposed) [14-20240330-1ubuntu1]13:17
-queuebot:#ubuntu-release- Unapproved: gcc-13 (noble-proposed/main) [13.2.0-23ubuntu2 => 13.2.0-23ubuntu3] (i386-whitelist)13:35
-queuebot:#ubuntu-release- Unapproved: isc-kea (noble-proposed/main) [2.4.1-2build1 => 2.4.1-3] (no packageset) (sync)13:59
dokois somebody running a script to retry builds?  please stop that for now14:22
dokovorlon: binutils unfortunately built on amd6414:23
adriendoko: well, there's the fallout management from the xz-utils backdoor14:26
dokosure, but cancelled builds are not retried on it's own14:26
adrienah, ok; I know apw was looking at something but I can't tell if it's related for sure14:30
dokolooks like the package was has been built with the restored amd64 binaries14:44
ahasenackhi ubuntu-release, I synced https://launchpad.net/debian/+source/isc-kea/2.4.1-3 to fix https://launchpad.net/bugs/205515114:59
-ubottu:#ubuntu-release- Launchpad bug 2055151 in isc-kea (Ubuntu) "kea-ctrl-agent segfault in ppc64el dep8 test" [High, Fix Committed]14:59
bdmurrayI've targetted bug 2055151 for the beta so we don't lose track of it.15:01
-ubottu:#ubuntu-release- Bug 2055151 in isc-kea (Ubuntu) "kea-ctrl-agent segfault in ppc64el dep8 test" [High, Fix Committed] https://launchpad.net/bugs/205515115:01
ahasenackthanks15:02
vorlondoko: I built binutils15:55
dokovorlon: I was assuming that. next gcc-13 is dep-wait with ghostscript uninstallabilities.15:56
vorlonyes. looking to see what arch: all package needs removed15:56
vorlonalso lol ubuntu-build is broken because the archive is in pre-releaze freeze sigh15:57
dokoI can prepare an upload doing without graphviz and ghostscript15:57
vorlonno, we shouldn't need any more bootstrap builds here, just need the archive tuned15:57
vorlonwhich is faster overall15:57
vorlonI'll also look ahead at glibc build-dep installability16:08
vorlonlooks ok actually16:09
dokowhen you start gcc-13, please also accept gcc-14 for the shared libs16:09
vorlondoko: I've set the starting of gcc-13 on a trigger so I may be afk when it accepts (and ubuntu-build doesn't give me useful return codes for scripting this); but I'll accept gcc-14 asap after16:18
vorlonmoving ghostscript to the top of my list for rebuilds as well.  its build-deps look clean16:18
vorlonand texinfo, whose Arch: all I had to remove last night for binutils16:19
vorlon(this doesn't matter for the amd64 builds, but will matter for getting other archs built faster, including riscv64)16:21
vorlonlooking for someone to un-freeze noble now. there may be some packages that fail to build due to archive inconsistency, but there is no ongoing concern about tainted builds16:33
vorlon(we want gcc to finish building but that will be done soon)16:33
-queuebot:#ubuntu-release- Unapproved: accepted edubuntu-meta [source] (noble-proposed) [24.04.12.1]16:35
-queuebot:#ubuntu-release- Unapproved: accepted ubuntu-mate-meta [source] (noble-proposed) [1.294.1]16:35
-queuebot:#ubuntu-release- Unapproved: accepted ubuntu-unity-meta [source] (noble-proposed) [0.17]16:35
-queuebot:#ubuntu-release- Unapproved: accepted ubuntukylin-meta [source] (noble-proposed) [0.57]16:35
-queuebot:#ubuntu-release- Unapproved: accepted xubuntu-meta [source] (noble-proposed) [2.261]16:35
-queuebot:#ubuntu-release- Unapproved: accepted ubuntucinnamon-meta [source] (noble-proposed) [24.04.3.1]16:35
-queuebot:#ubuntu-release- Unapproved: accepted ubuntu-meta [source] (noble-proposed) [1.538]16:35
-queuebot:#ubuntu-release- Unapproved: accepted ubuntustudio-meta [source] (noble-proposed) [24.04.18]16:35
vorlonheh, xz-utils amd64 binaries in -proposed got caught up by the removal script; restoring them16:38
vorlonhaving a look at autopkgtest queues (we should dump any tests triggered by glibc 2.39-0ubuntu7 which is now obsolete)16:49
ahasenackis noble release still a bit inconsistent?17:00
ahasenack elinks | 0.16.1.1-4.1ubuntu1 | noble-updates/universe | source17:00
ahasenack elinks | 0.16.1.1-4.1ubuntu2 | noble/universe         | source17:00
ahasenackwhy would updates have a lower version than release17:00
ahasenack(and why would updates be populated at this stage)17:00
RikMills<vorlon> we're using the noble-updates pocket to be able to have last-known-good amd64 binaries available, in parallel with the latest versions on all other architectures17:02
RikMillsahasenack: ^^17:02
ahasenackah17:02
ahasenackI got this weird depwait in a ppa build: Missing build dependencies: elinks-data (= 0.16.1.1-4.1ubuntu1)17:03
RikMillsyeah, it makes some issues with versioned depends on arch:all packages17:04
vorlonyeah. wrt ppas, these will shake out in the next couple of days as we're able to get rebuilds done in -proposed and then migrated back to the release pocket.  The critical chain here at the moment is publication of libgs10-common removal -> gcc-13 build -> glibc build -> upload the world17:05
vorlon(don't worry, it's "only" 7172 packages to upload)17:06
vorlonwill aim to get some clearer messaging published about this, but well, holiday weekend17:07
ahasenacknp17:07
-queuebot:#ubuntu-release- Unapproved: isc-kea (noble-proposed/main) [2.4.1-2build1 => 2.4.1-3] (no packageset) (sync)17:12
wxlthe Lubuntu ISO failed for an interesting reason today: livecd-rootfs has no installation candidate17:17
* Eickmeyer just is expecting image build failures for the next couple days while everything gets sorted17:33
-queuebot:#ubuntu-release- Unapproved: isc-kea (noble-proposed/main) [2.4.1-2build1 => 2.4.1-3] (no packageset) (sync)17:45
=== bdmurray changed the topic of #ubuntu-release to: Released: 23.10 Mantic Minotaur, 22.04.4 Jammy Jellyfish | Archive: Feature Freeze | Highlight ubuntu-archive for archive admin help | We accept payment in cash, cheque or scotch | melius malum quod cognoscis | infinity, you are missed
vorlongcc-13 is building, should be done in a couple of hours18:19
vorlonaccepting gcc-14 now18:19
vorlonarchive is unfrozen again but it's advisable to wait until gcc-13 and glibc are published before uploading stuff so that it gets built with the latest toolchain18:20
-queuebot:#ubuntu-release- Unapproved: accepted gcc-14 [source] (noble-proposed) [14-20240330-1ubuntu1]18:20
vorlongoing ahead and uploading livecd-rootfs, it's arch: any but doesn't build any binary artifacts18:24
vorlondoesn't mean image builds will start working but it can be unblocked all the same18:25
-queuebot:#ubuntu-release- Unapproved: accepted isc-kea [sync] (noble-proposed) [2.4.1-3]18:29
-queuebot:#ubuntu-release- Unapproved: rejected isc-kea [sync] (noble-proposed) [2.4.1-3]18:29
-queuebot:#ubuntu-release- Unapproved: accepted isc-kea [sync] (noble-proposed) [2.4.1-3]18:29
vorlonaccidentally clicked accept on isc-kea when I meant to click reject on the duplicate uploads in the queue; oops oh well18:29
mitya57vorlon: Hi! Not sure if you saw my question about Qt above, but let me try again:18:49
mitya57- Currently noble has Qt 5.15.12 but 5.15.13 was published earlier this month. Do I have chances to squeeze it in for noble, or we should better stick to 5.15.12?18:49
mitya57- If I have chances: I started preparing packages in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4979 but some packages there were built yesterday, which is with liblzma 5.4.5. Should I start from scratch in a new PPA?18:49
dokowell, if you built the *source* with new xz-utils, it should be fine? independent of the new subminor version18:51
mitya57By source you mean *+dfsg.orig.tar.xz? Then I built it for Debian and it was a few weeks ago.18:53
dokoisn't debian.tar.xz also compressed with lzma?18:56
mitya57doko: Yes it is. Do we have any evidence that these files may be infected/screwed up, and/or a way to check that?18:58
vorlonmitya57: we don't have a way to check that no.  The *known* attack is sophisticated enough that we assume there are others and we have not yet characterized them19:20
vorlonmitya57: but building yesterday with liblzma 5.4.5 is fine? it's 5.6.x that is the known problem19:20
vorlonmitya57: and as for having time to squeeze things in, well I have no idea at this point.  I don't expect beta to be possible in 6 days but we haven't had a chance to assess full impact since the mitigation work is still ongoing19:21
mitya57vorlon: "but building yesterday with liblzma 5.4.5 is fine" — ah, right. I didn't see the +really suffix so was confused. But still, there are .debian.tar.xz copied from Debian which were built with 5.6.x.19:25
vorlonmitya57: that's not a vector that we're currently intending to do anything about.  But if you ask the question "should we trust it?" the answer is "no"19:25
mitya57Okay. I will probably continue copying stuff from Debian to my PPA and in case we know that .xz files are affected, I'll be able to do *build1 uploads at any time.19:27
vorlonmitya57: *however*, I will say that in terms of strategy, "injecting code into liblzma to compromise sshd" and "causing liblzma to generate broken compressed files that can then be used to compromise other systems via an undisclosed vulnerability in the decompressor" are quite disjoint19:27
mitya57Ack. Thanks for your answers (and work on this).19:27
vorlongcc-13 almost done (currently at pkgstriptranslations)19:42
vorlongonna go ahead and skiptest livecd-rootfs. the autopkgtests don't provide us any additional surety here19:43
vorlon(the one in release pocket has been removed on amd64 so obviously we can't regress buildability right now!)19:45
vorlonjuliank: I think I've lost track of what's happening with the migration-reference/0 tests.  We will want to preempt these now due to the xz-utils rebuilds.  Did you want these requeued afterwards? At that point I'm not sure it really matters20:15
juliankvorlon: yeah still *some* time to analyse any regressions we introduced between beta and release20:16
vorlonjuliank: well effectively, tests are going to be retriggered for the world against the packages in -proposed, and if those show up as regressions britney will do its own migration-reference/0 triggers where necessary?20:16
juliankTo some extent yes20:19
juliankMy concern was all-proposed testing with partial migration causing hidden regressions20:20
juliankOh? Are they still running, I thought they'd be killed already20:21
vorlonxz-utils revdep autopkgtest regressions caused by libevent, that's fine; releasing xz-utils now20:21
vorlonjuliank: killing them requires someone to actively do so, and no one has gotten to it yet :) I'll do it now20:22
juliankRegardless of what I want, you can kill any reference tests, the script will pick that up and add them to the to-be-scheduled output again20:22
juliankI made magic20:22
vorlonack20:23
vorlonI thought I remembered that was the case but wanted to double-check20:23
vorlonarm64 queue still won't be quite zeroed, but20:24
vorlonman, component-mismatches is seriously confused20:24
juliankThe builds happen in chroots, right?20:24
vorlonyes20:25
juliankDebian seems to consider to rebuild the machines the chroots are on as well20:25
cjwatsonthe builds are also in ephemeral VMs20:25
vorlon^20:25
juliankAh20:25
juliankSo you boot a VM, and then a chroot in it, fun20:25
vorlonyeah build isolation has been a concern for a long time, on account of the fact that we have ppas :)20:25
juliankRight20:25
cjwatsonand the build chain for those VMs didn't involve noble last time I checked, which I doubt very much has changed since November20:25
vorlonindeed it has not20:25
juliankVery good20:26
vorlonand the buildd chroots in launchpad haven't been updated ;P20:26
juliankHeh20:26
cjwatsonI wrote down how to do that in my handover notes I think20:28
cjwatsonSo if the current LP team is lost, that's where to point them ...20:29
vorlonack :)20:29
vorlonbuilding glibc21:22
bdmurrayI sorted out some issues with arm64 queue processing a bit ago.22:10
bdmurraya bit being like 3 hours ago22:11
vorlonjuliank: https://lists.ubuntu.com/archives/ubuntu-devel/2024-March/042955.html seems like it should be a bug report against gst-plugins-good1.0?22:19
vorlonglibc built22:21
ricotzhello ubuntu-archive, would it be possible to delete this source - https://launchpad.net/ubuntu/+source/libreoffice/4:24.2.2-0ubunut123:01
vorlonhaha23:01
vorlonok23:01
ricotzthanks! and yeah, the typo is one thing :\23:02
ricotzvorlon, regarding the amd64/arm64 failures, is the archive in a bad state currently?23:02
vorlonricotz: mostly on amd6423:02
vorlonlots of comments on it in scrollback, but basically this is mitigation of the amd64-specific xz-utils backdoor23:03
vorlonwe've rolled back 7k source packages to their pre-xz-utils versions in noble-updates, deleted amd64 binaries from noble and noble-proposed, and that means some packages are uninstallable because of arch: all packages being newer than their arch: amd64 packages23:04
vorlonand that's not something we'll resolve with blanket removals of arch: all packages because that makes the situation worse for all the other archs, including the much-slower riscv6423:04
ricotzok, I see, so uploading e.g. libreoffice won't result in proper build any time soon then23:05
vorlonanyway, just as soon as glibc publishes (which should be very very soon), I'll be kicking off mass rebuilds23:05
vorlonoh in fact it looks like glibc is published23:05
vorlon(to ftpmaster.internal; not to the public mirrors)23:06
ricotzah ok, so it won't hurt me uploading it23:06
vorlonso here we goooooo23:06
LocutusOfBorgvorlon, can we ask Santa to have binNMU per arch the way Debian has? it would have helped on this issue a lot I guess23:08
LocutusOfBorg(also time64_t)23:08
ricotz(debian versions are fun, I would not have expected that 0.19.2-3+b1 is higher than 0.19.2-3build2)23:08
vorlonLocutusOfBorg: it wouldn't have helped with *this* issue.  And we would've wanted rebuilds on all archs for time_t as well, to ensure switching to the new library packages on upgrade (to not island users on the old package which gets no security updates).  And binNMUs also bring challenges with multiarch co-installability (sometimes Debian winds up doing binNMUs on all architectures for this).  So23:10
vorlonit's not something I regard as a priority23:10
jbichaLocutusOfBorg: I've heard people in Debian wish that they only used Ubuntu-style binNMUs23:10
vorlonah shoot I thought glibc was in this latest publisher run but it's not23:11
vorlonholding off for the next one (hopefully quick)23:11
vorlonjbicha: hiya. is https://lists.ubuntu.com/archives/ubuntu-devel/2024-March/042955.html anything you want to look at? :)23:12
jbichathat requires more concentration than I have this weekend :)23:14
vorlonfair!23:16
vorlonLocutusOfBorg: ok actually I suppose it would have helped with this issue; but the arch:any/arch:all skew thing would've still needed dealing with23:18
vorlonglibc is published.  Mass rebuilds incoming.23:49
vorlonaccepting all from the unapproved queue23:55
-queuebot:#ubuntu-release- Unapproved: accepted haskell-charsetdetect-ae [sync] (noble-proposed) [1.1.0.4-6]23:56
-queuebot:#ubuntu-release- Unapproved: accepted haskell-hoogle [sync] (noble-proposed) [5.0.18.3+dfsg1-5]23:56
-queuebot:#ubuntu-release- Unapproved: accepted libpng1.6 [sync] (noble-proposed) [1.6.43-5]23:56
-queuebot:#ubuntu-release- Unapproved: accepted ukui-panel [sync] (noble-proposed) [4.0.0.4-1]23:56
-queuebot:#ubuntu-release- Unapproved: accepted haskell-fgl [sync] (noble-proposed) [5.8.1.1-1]23:56
-queuebot:#ubuntu-release- Unapproved: accepted octave-control [source] (noble-proposed) [4.0.1-1ubuntu1]23:56
-queuebot:#ubuntu-release- Unapproved: accepted kbuild [sync] (noble-proposed) [1:0.1.9998svn3604+dfsg-1]23:56
-queuebot:#ubuntu-release- Unapproved: accepted pkg-haskell-tools [sync] (noble-proposed) [0.12.5]23:56
-queuebot:#ubuntu-release- Unapproved: accepted connectagram [sync] (noble-proposed) [1.3.5-2]23:57
-queuebot:#ubuntu-release- Unapproved: accepted gcc-13 [source] (noble-proposed) [13.2.0-23ubuntu3]23:57
-queuebot:#ubuntu-release- Unapproved: rejected haskell-haskell-gi [source] (noble-proposed) [0.26.7-2ubuntu1]23:57
-queuebot:#ubuntu-release- Unapproved: accepted newlib [sync] (noble-proposed) [4.4.0.20231231-2]23:57
-queuebot:#ubuntu-release- Unapproved: accepted entropybroker [sync] (noble-proposed) [2.9-8]23:57
-queuebot:#ubuntu-release- Unapproved: accepted indi-gige [sync] (noble-proposed) [0.1+20221223115700-2]23:57
-queuebot:#ubuntu-release- Unapproved: accepted google-android-installers [sync] (noble-proposed) [1710437545-3]23:57
-queuebot:#ubuntu-release- Unapproved: accepted xubuntu-default-settings [source] (noble-proposed) [24.04.3]23:57

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!