[00:44] -queuebot:#ubuntu-release- New binary: gyoto [armhf] (noble-proposed/universe) [2.0.1-1] (no packageset) === chris14_ is now known as chris14 [03:25] -queuebot:#ubuntu-release- New binary: gyoto [riscv64] (noble-proposed/universe) [2.0.1-1] (no packageset) [05:26] -queuebot:#ubuntu-release- New binary: cypari2 [amd64] (noble-proposed/universe) [2.1.4-1] (no packageset) [05:53] -queuebot:#ubuntu-release- New binary: cypari2 [armhf] (noble-proposed/universe) [2.1.4-1] (no packageset) [05:53] -queuebot:#ubuntu-release- New binary: cypari2 [ppc64el] (noble-proposed/universe) [2.1.4-1] (no packageset) [05:57] -queuebot:#ubuntu-release- New binary: cypari2 [arm64] (noble-proposed/universe) [2.1.4-1] (no packageset) [06:28] -queuebot:#ubuntu-release- New binary: cypari2 [s390x] (noble-proposed/universe) [2.1.4-1] (no packageset) [08:23] -queuebot:#ubuntu-release- New: accepted cmock [amd64] (noble-proposed) [2.5.3+git40-g379a9a8-1] [08:23] -queuebot:#ubuntu-release- New: accepted cypari2 [arm64] (noble-proposed) [2.1.4-1] [08:23] -queuebot:#ubuntu-release- New: accepted cypari2 [ppc64el] (noble-proposed) [2.1.4-1] [08:23] -queuebot:#ubuntu-release- New: accepted gyoto [amd64] (noble-proposed) [2.0.1-1] [08:23] -queuebot:#ubuntu-release- New: accepted gyoto [armhf] (noble-proposed) [2.0.1-1] [08:23] -queuebot:#ubuntu-release- New: accepted gyoto [riscv64] (noble-proposed) [2.0.1-1] [08:23] -queuebot:#ubuntu-release- New: accepted python-molotov [amd64] (noble-proposed) [2.7-1] [08:23] -queuebot:#ubuntu-release- New: accepted cypari2 [amd64] (noble-proposed) [2.1.4-1] [08:23] -queuebot:#ubuntu-release- New: accepted cypari2 [s390x] (noble-proposed) [2.1.4-1] [08:23] -queuebot:#ubuntu-release- New: accepted gyoto [ppc64el] (noble-proposed) [2.0.1-1] [08:23] -queuebot:#ubuntu-release- New: accepted cypari2 [armhf] (noble-proposed) [2.1.4-1] [08:23] -queuebot:#ubuntu-release- New: accepted gyoto [s390x] (noble-proposed) [2.0.1-1] [08:23] -queuebot:#ubuntu-release- New: accepted gyoto [arm64] (noble-proposed) [2.0.1-1] [10:08] -queuebot:#ubuntu-release- New source: libxfce4windowing (noble-proposed/primary) [4.19.2-1ubuntu1] [10:10] As requested by Ubuntu Budgie ↑ [11:18] -queuebot:#ubuntu-release- Unapproved: rejected nvidia-graphics-drivers-535-server [sync] (focal-proposed) [535.104.12-0ubuntu0.20.04.2] [11:18] -queuebot:#ubuntu-release- Unapproved: rejected nvidia-graphics-drivers-535 [sync] (focal-proposed) [535.113.01-0ubuntu0.20.04.3] [12:40] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (jammy-proposed/main) [2.765.35 => 2.765.36] (desktop-core, i386-whitelist) [12:46] tjaalton vorlon As SRU vanguards today. Can you help accept `2.765.36` Jammy in to -proposed ? To address https://bugs.launchpad.net/cloud-images/+bug/2049860 [12:46] -ubottu:#ubuntu-release- Launchpad bug 2049860 in cloud-images "cloud-init cloud-config for ssh broken in jammy" [High, In Progress] [12:48] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (jammy-proposed/main) [2.765.35 => 2.765.36] (desktop-core, i386-whitelist) [14:00] -queuebot:#ubuntu-release- Unapproved: rejected zfs-linux [source] (jammy-proposed) [2.1.14-0ubuntu0.22.04.1] [14:05] philroche: there are two identical uploads of that? === caribou_ is now known as caribou [14:14] toabctl: ^ [14:15] tjaalton: Yes the first did not include the changes from 2.765.35 [14:16] which is in -proposed already [14:16] ack [14:16] so I'll reject the first one now [14:17] -queuebot:#ubuntu-release- Unapproved: rejected livecd-rootfs [source] (jammy-proposed) [2.765.36] [14:21] -queuebot:#ubuntu-release- Unapproved: accepted alsa-ucm-conf [source] (mantic-proposed) [1.2.9-1ubuntu3.2] [14:21] -queuebot:#ubuntu-release- Unapproved: accepted alsa-ucm-conf [source] (jammy-proposed) [1.2.6.3-1ubuntu1.10] [14:43] -queuebot:#ubuntu-release- Unapproved: accepted coreutils [source] (mantic-proposed) [9.1-1ubuntu2.23.10.1] [14:46] -queuebot:#ubuntu-release- Unapproved: accepted coreutils [source] (jammy-proposed) [8.32-4.1ubuntu1.1] [14:51] aciba: Hi, you have two uploads of cloud-init for f/j/m, what to do with those? [15:08] tjaalton: reject the ones ending with .1 and review and continue with the process with the ones ending with .2 [15:11] tjaalton: Hi, we expect 23.4.1-0ubuntu1~YY.MM.2 versions to accepted into -proposed, thanks. === bdmurray_ is now known as bdmurray [16:20] philroche, tjaalton: if this doesn't also fix the Ubuntu Server jammy daily image failures, then nack; we need to get that fixed sooner than an SRU verification cycle for this proposed upload, so it would be superseded anyway [16:20] we have an upcoming jammy point release, I need daily server ISOs buildable ASAP [16:30] -queuebot:#ubuntu-release- Unapproved: rejected cloud-init [source] (jammy-proposed) [23.4.1-0ubuntu1~22.04.1] [16:30] -queuebot:#ubuntu-release- Unapproved: rejected cloud-init [source] (focal-proposed) [23.4.1-0ubuntu1~20.04.1] [16:30] -queuebot:#ubuntu-release- Unapproved: rejected cloud-init [source] (mantic-proposed) [23.4.1-0ubuntu1~23.10.1] [16:33] vorlon: Ack. It does not fix your iamge failures. CPC are carrying a patch to fix the ssh pw auth regression for now so there is less urgency. I will continue to work on the fix for your Ubuntu Server jammy daily image failures fix [16:35] philroche: thanks :) [16:57] athos, since I'm tired of watching php* PRs, what about just NMU? [16:59] oh maybe now he will merge them [17:01] LocutusOfBorg: I filed BTS bugs this time =x [17:06] vorlon: when you have some time can you please have a look at https://bugs.launchpad.net/ubuntu/+source/fsvs/+bug/1875642/comments/17 specifically the "questionable to me" part please.. I will prepare the debdiff depending on what your answer to that question is [17:06] -ubottu:#ubuntu-release- Launchpad bug 1875642 in fsvs (Ubuntu Mantic) "[SRU] FSVS - not able to commit changes to remote HTTP SVN repo" [Medium, Confirmed] [17:07] athos, don't forget to ping me if no answer in ~1m [17:09] https://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu [17:09] we can go in deferred/10 with an NMU [17:09] :) [17:29] thanks!!! will do [20:03] is updating of update_excuses just delayed, or is there a real problem? [20:33] doko: hey, did you upload https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/2049715 ? It has "UNRELEASED" in d/changelog [20:33] -ubottu:#ubuntu-release- Launchpad bug 2049715 in openjdk-lts (Ubuntu) "Please merge 11.0.22+7-1 from Debian unstable" [Undecided, Fix Released] [20:34] doko: Just delayed. https://ubuntu-archive-team.ubuntu.com/proposed-migration/log/noble/2024-01-19/17:45:55.log shows it's still rolling. [20:34] Brian mentioned something about clearing queues, I wouldn't be surprised if Britney now has to re-queue quite a bit. [20:37] python3-defaults (3.11.4-5ubuntu1 to 3.12.1-0ubuntu1) hmmm yeah might be delayed slightly for the next few cycles :) nice! [20:39] ahasenack: ta, I'll follow-up on this [20:39] tsimonq2: yes, it's still in progress [20:39] doko: thx [20:43] pushkarnk: ^^^ [20:43] tsimonq2, doko: there is at least one bug with britney repeatedly requeuing tests that had already run and failed with 'unknown' version [20:44] afaik, no [20:44] but I wasn't under the impression that was a substantial fraction of tests [20:44] and in any case, long queues means britney is *waiting* for tests, so querying the status of that many outstanding tests takes time [20:45] sudip: hi, you pointed me at a link which is my own comment; and there are no later comments on that bug; are you asking me to answer my own question? [20:46] well, the problem seems to ne that btiney runs seem to be delayed by a large number of tests to be queued [20:46] doko: are you drawing that conclusion by looking at the logs? [20:47] sorry, no, not looking at logs. which logs would hat be? [20:47] the one tsimonq2 already pointed you to above [20:48] I don't know why you say it's busy queuing tests if you haven't looked at the logs [20:49] the newest package in https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses.html that just refreshed is python3-defaults, which was already there in the previous run and already had its tests queued [20:49] $ wcat https://ubuntu-archive-team.ubuntu.com/proposed-migration/log/noble/2024-01-19/17:45:55.log |grep -c 'Test.*pending.*not queueing' [20:49] 20813 [20:49] $ [20:50] $ wcat https://ubuntu-archive-team.ubuntu.com/proposed-migration/log/noble/2024-01-19/17:45:55.log |grep -c 'Requesting autopkgtest' [20:50] 4 [20:50] $ [20:50] so the time is spent checking for results on the tests already queued [20:53] ahh, britney just updated [20:53] one thing I would like to see, but have not had time to do, would be separating the test result polling out into a separate process, and let that run in a loop asynchronous with britney itself [20:53] then the britney runs would just query the current state at any point and would iterate quickly [20:53] and the test results would be pulled in in the background [20:54] and also that could be a single runner for all series and then we would only need one copy of autopkgtest.db downloaded instead of one for all series :P [21:00] @pilot out [21:00] ops [22:00] I swear I've removed python-oslo.utils/6.3.0-0ubuntu1 from the armhf queue but it seems to be coming back? [23:00] -queuebot:#ubuntu-release- Unapproved: accepted ltrace [source] (mantic-proposed) [0.7.3-6.1ubuntu6.23.10.1] [23:01] -queuebot:#ubuntu-release- Unapproved: accepted ltrace [source] (jammy-proposed) [0.7.3-6.1ubuntu6.22.04.1] [23:18] -queuebot:#ubuntu-release- New binary: pypinyin [amd64] (noble-proposed/none) [0.50.0-1] (no packageset) [23:18] -queuebot:#ubuntu-release- New binary: writeboost [amd64] (noble-proposed/none) [1.20170616-1.3] (no packageset) [23:18] -queuebot:#ubuntu-release- New binary: relic [amd64] (noble-proposed/none) [7.6.1-1] (no packageset) [23:33] -queuebot:#ubuntu-release- Unapproved: accepted openssl [source] (jammy-proposed) [3.0.2-0ubuntu1.13]