-queuebot:#ubuntu-release- New binary: libarcus [riscv64] (mantic-proposed/universe) [5.0.0-3] (no packageset) | 00:17 | |
vorlon | LocutusOfBorg: `reverse-depends src:eccodes -a armhf` is non-trivial; can you file a bug report and walk the reverse-dep tree to confirm they can all be removed and also don't require changes to prevent them from reappearing on rebuild? | 00:43 |
---|---|---|
vorlon | LocutusOfBorg: before I would ignore the redmine autopkgtest failure for nginx, why did it fail in https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/ppc64el/r/redmine/20230701_062850_45aa7@/log.gz ? | 00:47 |
=== chris14_ is now known as chris14 | ||
LocutusOfBorg | vorlon, the rouge gem is too new | 05:46 |
LocutusOfBorg | 1989s [31mCould not find gem 'rouge (~> 3.28)' in cached gems or installed locally. | 05:46 |
vorlon | yes, but why does it get pulled in from -proposed | 05:46 |
LocutusOfBorg | (why there is not a strict dependency on rouge with versioned dep, but fails the postinst its foo) | 05:46 |
LocutusOfBorg | maybe my trigger was wrong? I don't really get it | 05:46 |
vorlon | no | 05:47 |
LocutusOfBorg | maybe we should kick redmine out? | 05:47 |
vorlon | the logs show a large number of tests correctly pulling from release pocket; then one test fails to resolve the deps against the release pocket and falls back to pulling everything from -proposed | 05:47 |
LocutusOfBorg | ok got it I guess | 05:50 |
LocutusOfBorg | ruby-mail/mantic ruby-nokogiri/mantic needs too | 05:50 |
LocutusOfBorg | mmm I rebuild rails, it picked up a ruby-rack 3.0.8 dependency | 05:56 |
LocutusOfBorg | this might explain | 05:56 |
-queuebot:#ubuntu-release- New: accepted libarcus [riscv64] (mantic-proposed) [5.0.0-3] | 06:05 | |
juergh | bdmurray: verfied kinetic (again) and added a comment. | 06:10 |
-queuebot:#ubuntu-release- New: accepted mesa [amd64] (jammy-proposed) [23.0.4-0ubuntu1~22.04.1] | 08:10 | |
-queuebot:#ubuntu-release- New: accepted mesa [armhf] (jammy-proposed) [23.0.4-0ubuntu1~22.04.1] | 08:10 | |
-queuebot:#ubuntu-release- New: accepted mesa [ppc64el] (jammy-proposed) [23.0.4-0ubuntu1~22.04.1] | 08:10 | |
-queuebot:#ubuntu-release- New: accepted mesa [arm64] (jammy-proposed) [23.0.4-0ubuntu1~22.04.1] | 08:10 | |
-queuebot:#ubuntu-release- New: accepted mesa [s390x] (jammy-proposed) [23.0.4-0ubuntu1~22.04.1] | 08:10 | |
-queuebot:#ubuntu-release- New: accepted mesa [i386] (jammy-proposed) [23.0.4-0ubuntu1~22.04.1] | 08:10 | |
=== guiverc2 is now known as guiverc | ||
juliank | ubuntu-sru should be aware that due to an apt bug (LP: #2025462), future updates to gnome-shell should only be released after the matching mutter update has finished phasing | 10:19 |
-ubottu:#ubuntu-release- Launchpad bug 2025462 in apt (Ubuntu Mantic) "Apt deletes ubuntu-desktop during dist-upgrade" [Critical, In Progress] https://launchpad.net/bugs/2025462 | 10:19 | |
juliank | The APT fix will be delivered in APT SRUs shortly, I'm hoping to get a review upstream first | 10:20 |
=== mirespace_ is now known as mirespace | ||
mirespace | Hi, I'm looking for someone in +1 maintenance in the incoming weeks, preferreably in CEST time (UTC/GMT +2) or close, who I can shadow for learning purposes (I promise not to bother too much) | 12:05 |
mirespace | If anyone is interested, please ping me ... thank you | 12:05 |
-queuebot:#ubuntu-release- New binary: pipewire [amd64] (mantic-proposed/main) [0.3.72-1] (desktop-core, i386-whitelist) | 14:12 | |
-queuebot:#ubuntu-release- New binary: pipewire [i386] (mantic-proposed/main) [0.3.72-1] (desktop-core, i386-whitelist) | 14:12 | |
-queuebot:#ubuntu-release- Unapproved: rejected gnutls28 [source] (focal-proposed) [3.6.13-2ubuntu1.9] | 14:13 | |
-queuebot:#ubuntu-release- New binary: pipewire [arm64] (mantic-proposed/main) [0.3.72-1] (desktop-core, i386-whitelist) | 14:13 | |
-queuebot:#ubuntu-release- New binary: pipewire [ppc64el] (mantic-proposed/main) [0.3.72-1] (desktop-core, i386-whitelist) | 14:13 | |
-queuebot:#ubuntu-release- New binary: pipewire [armhf] (mantic-proposed/main) [0.3.72-1] (desktop-core, i386-whitelist) | 14:13 | |
-queuebot:#ubuntu-release- New binary: pipewire [s390x] (mantic-proposed/main) [0.3.72-1] (desktop-core, i386-whitelist) | 14:13 | |
-queuebot:#ubuntu-release- New binary: pipewire [riscv64] (mantic-proposed/main) [0.3.72-1] (desktop-core, i386-whitelist) | 15:20 | |
-queuebot:#ubuntu-release- Unapproved: python-ovsdbapp (jammy-proposed/main) [1.15.1-0ubuntu2 => 1.15.3-0ubuntu1] (openstack) | 15:54 | |
-queuebot:#ubuntu-release- New: accepted pipewire [amd64] (mantic-proposed) [0.3.72-1] | 16:00 | |
-queuebot:#ubuntu-release- New: accepted pipewire [armhf] (mantic-proposed) [0.3.72-1] | 16:00 | |
-queuebot:#ubuntu-release- New: accepted pipewire [ppc64el] (mantic-proposed) [0.3.72-1] | 16:00 | |
-queuebot:#ubuntu-release- New: accepted pipewire [s390x] (mantic-proposed) [0.3.72-1] | 16:00 | |
-queuebot:#ubuntu-release- New: accepted pipewire [arm64] (mantic-proposed) [0.3.72-1] | 16:00 | |
-queuebot:#ubuntu-release- New: accepted pipewire [riscv64] (mantic-proposed) [0.3.72-1] | 16:00 | |
-queuebot:#ubuntu-release- New: accepted pipewire [i386] (mantic-proposed) [0.3.72-1] | 16:00 | |
LocutusOfBorg | vorlon, I think some redmine hint is needed, all my efforts failed | 17:14 |
-queuebot:#ubuntu-release- New binary: r-cran-chk [amd64] (mantic-proposed/none) [0.9.0-1] (no packageset) | 17:19 | |
-queuebot:#ubuntu-release- New binary: snac2 [amd64] (mantic-proposed/none) [2.25-3] (no packageset) | 17:19 | |
vorlon | LocutusOfBorg: you shouldn't be including ruby-rouge in the triggers anyway, you should only use package versions from -proposed in triggers | 17:24 |
LocutusOfBorg | it failed also without | 17:25 |
-queuebot:#ubuntu-release- New binary: snac2 [ppc64el] (mantic-proposed/none) [2.25-3] (no packageset) | 17:29 | |
-queuebot:#ubuntu-release- New binary: snac2 [s390x] (mantic-proposed/universe) [2.25-3] (no packageset) | 17:32 | |
-queuebot:#ubuntu-release- New: accepted r-cran-chk [amd64] (mantic-proposed) [0.9.0-1] | 17:34 | |
-queuebot:#ubuntu-release- New: accepted snac2 [ppc64el] (mantic-proposed) [2.25-3] | 17:34 | |
-queuebot:#ubuntu-release- New: accepted snac2 [amd64] (mantic-proposed) [2.25-3] | 17:34 | |
-queuebot:#ubuntu-release- New: accepted snac2 [s390x] (mantic-proposed) [2.25-3] | 17:34 | |
-queuebot:#ubuntu-release- New binary: snac2 [arm64] (mantic-proposed/universe) [2.25-3] (no packageset) | 17:41 | |
-queuebot:#ubuntu-release- New binary: snac2 [armhf] (mantic-proposed/universe) [2.25-3] (no packageset) | 17:41 | |
-queuebot:#ubuntu-release- New: accepted snac2 [arm64] (mantic-proposed) [2.25-3] | 17:52 | |
-queuebot:#ubuntu-release- New: accepted snac2 [armhf] (mantic-proposed) [2.25-3] | 17:52 | |
vorlon | LocutusOfBorg: $ retry-autopkgtest-regressions --blocks nginx | sed -e's,$,\&trigger=libnginx-mod-http-echo/1:0.63-4,' | xargs -rn1 -P10 curl --cookie ~/.cache/autopkgtest.cookie -o /dev/null --silent --head --write-out '%{url_effective} : %{http_code}\n' | 18:31 |
vorlon | LocutusOfBorg: one way of working this out is by looking at the successful run on amd64, before ruby-rouge was updated, and see what packages were actually downloaded from mantic-proposed: wzcat https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/r/redmine/20230629_013102_9c9f9@/log.gz | grep -E 'mantic-proposed.*amd64.*(amd64|all)' | 18:34 |
-queuebot:#ubuntu-release- Packageset: Removed fonts-liberation2 from i386-whitelist in mantic | 19:29 | |
-queuebot:#ubuntu-release- Packageset: Removed isa-support from i386-whitelist in mantic | 19:29 | |
-queuebot:#ubuntu-release- Packageset: Added fonts-liberation to i386-whitelist in mantic | 19:29 | |
-queuebot:#ubuntu-release- Packageset: Added libavtp to i386-whitelist in mantic | 19:29 | |
-queuebot:#ubuntu-release- Packageset: Added openh264 to i386-whitelist in mantic | 19:29 | |
-queuebot:#ubuntu-release- New source: golang-1.20 (focal-proposed/primary) [1.20.5-1ubuntu0.1~20.04.1] | 19:45 | |
-queuebot:#ubuntu-release- New source: golang-1.20 (jammy-proposed/primary) [1.20.5-1ubuntu0.1~22.04.1] | 19:46 | |
kanashiro[m] | vorlon: I need to backport golang-1.20 to Jammy and Focal to be able to backport the container stack (containerd requires a newer golang version than what we have in those releases). Since you are an AA and also SRU team member, could you please take a look at them? ^ | 19:47 |
vorlon | kanashiro[m]: isn't this something zhsj should be driving? | 19:50 |
kanashiro[m] | vorlon: last time I needed this (golang backport) I was told I could do it myself, has this changed? The backport was not too complicated, so I went ahead and did it myself | 19:52 |
vorlon | kanashiro[m]: I don't know when you were last told this or by whom; we have a Toolchain Team within Foundations which owns delivery of the toolchains, including golang, including in SRU. zhsj did sign off on 1.20_1.20.3-1ubuntu0.1~22.04 which is already in the queue, is there a reason not to accept that one instead? | 19:53 |
vorlon | (yours is the only golang-1.20 in the queue for focal) | 19:54 |
kanashiro[m] | vorlon: I was told by someone from Foundations but I do not remember if at that time the toolchain team was in place. Oh sorry, I did not notice it was in the queue already, that would work for me as well | 19:55 |
-queuebot:#ubuntu-release- New: rejected golang-1.20 [source] (jammy-proposed) [1.20.5-1ubuntu0.1~22.04.1] | 19:58 | |
-queuebot:#ubuntu-release- Packageset: Added spirv-llvm-translator-16 to i386-whitelist in mantic | 20:14 | |
vorlon | kanashiro[m]: I've accepted 1.20.3-1ubuntu0.1~22.04 but of course the 1.20.5 you uploaded to focal would then be a higher version number than jammy; can you work with zhsj to sort this out for focal? | 20:46 |
-queuebot:#ubuntu-release- New: accepted golang-1.20 [source] (jammy-proposed) [1.20.3-1ubuntu0.1~22.04] | 20:46 | |
kanashiro[m] | vorlon: sure, I will talk to him. Thanks for accepting the jammy version already :) | 20:47 |
-queuebot:#ubuntu-release- New binary: golang-1.20 [amd64] (jammy-proposed/universe) [1.20.3-1ubuntu0.1~22.04] (no packageset) | 20:57 | |
-queuebot:#ubuntu-release- New: accepted golang-1.20 [amd64] (jammy-proposed) [1.20.3-1ubuntu0.1~22.04] | 20:58 | |
-queuebot:#ubuntu-release- New binary: golang-1.20 [s390x] (jammy-proposed/universe) [1.20.3-1ubuntu0.1~22.04] (no packageset) | 21:00 | |
-queuebot:#ubuntu-release- New binary: golang-1.20 [ppc64el] (jammy-proposed/universe) [1.20.3-1ubuntu0.1~22.04] (no packageset) | 21:01 | |
-queuebot:#ubuntu-release- New: accepted golang-1.20 [ppc64el] (jammy-proposed) [1.20.3-1ubuntu0.1~22.04] | 21:03 | |
-queuebot:#ubuntu-release- New binary: golang-1.20 [arm64] (jammy-proposed/universe) [1.20.3-1ubuntu0.1~22.04] (no packageset) | 21:03 | |
-queuebot:#ubuntu-release- New: accepted golang-1.20 [s390x] (jammy-proposed) [1.20.3-1ubuntu0.1~22.04] | 21:03 | |
-queuebot:#ubuntu-release- New binary: golang-1.20 [armhf] (jammy-proposed/universe) [1.20.3-1ubuntu0.1~22.04] (no packageset) | 21:05 | |
-queuebot:#ubuntu-release- New: accepted golang-1.20 [arm64] (jammy-proposed) [1.20.3-1ubuntu0.1~22.04] | 21:14 | |
-queuebot:#ubuntu-release- New: accepted golang-1.20 [armhf] (jammy-proposed) [1.20.3-1ubuntu0.1~22.04] | 21:14 | |
liushuyu | Hi Release Team, I need help overriding the autopkgtest result for cargo (when testing against rustc/1.68.0+dfsg0ubuntu1-0ubuntu1). The cargo source package has been merged into rustc, so the individual source package for cargo is no longer available since rustc/1.68.0+dfsg0ubuntu1-0ubuntu1 | 21:31 |
vorlon | looking | 21:32 |
vorlon | hint added | 21:33 |
liushuyu | vorlon: should I request a test-rerun for this to take effect or it's already taking effect? | 21:34 |
vorlon | liushuyu: the hint takes effect as part of the proposed-migration machinery (britney); there's no reason to re-test, the tests would just fail the same way | 21:34 |
liushuyu | vorlon: Thank you! | 21:35 |
-queuebot:#ubuntu-release- Unapproved: qemu (jammy-proposed/main) [1:6.2+dfsg-2ubuntu6.11 => 1:6.2+dfsg-2ubuntu6.12] (ubuntu-server, virt) | 23:55 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!