[06:02] -queuebot:#ubuntu-release- Unapproved: linux-firmware (jammy-proposed/main) [20220329.git681281e4-0ubuntu1 => 20220329.git681281e4-0ubuntu1.1] (core, kernel)
[06:10] <RikMills> vorlon: hey, does this need changing? https://bazaar.launchpad.net/~ubuntu-cdimage/ubuntu-cdimage/mainline/view/head:/lib/cdimage/germinate.py#L75
[07:47] -queuebot:#ubuntu-release- New binary: wpewebkit [armhf] (kinetic-proposed/universe) [2.36.1-1] (no packageset)
[08:22]  * LocutusOfBorg does some syncs/merges before real opening
[08:26] <LocutusOfBorg> it would be nice to wait for amd64 to be back online before enabling autosync?
[08:35] -queuebot:#ubuntu-release- New binary: gnutls28 [amd64] (kinetic-proposed/main) [3.7.4-2] (core, i386-whitelist)
[08:37] -queuebot:#ubuntu-release- New binary: gnutls28 [s390x] (kinetic-proposed/main) [3.7.4-2] (core, i386-whitelist)
[08:38] -queuebot:#ubuntu-release- New binary: gnutls28 [ppc64el] (kinetic-proposed/main) [3.7.4-2] (core, i386-whitelist)
[08:48] -queuebot:#ubuntu-release- New binary: gnutls28 [i386] (kinetic-proposed/main) [3.7.4-2] (core, i386-whitelist)
[08:52] -queuebot:#ubuntu-release- New binary: gnutls28 [s390x] (kinetic-proposed/main) [3.7.4-2ubuntu1] (core, i386-whitelist)
[08:54] -queuebot:#ubuntu-release- New binary: gnutls28 [ppc64el] (kinetic-proposed/main) [3.7.4-2ubuntu1] (core, i386-whitelist)
[08:55] -queuebot:#ubuntu-release- New binary: gnutls28 [i386] (kinetic-proposed/main) [3.7.4-2ubuntu1] (core, i386-whitelist)
[08:57] -queuebot:#ubuntu-release- New binary: gnutls28 [armhf] (kinetic-proposed/main) [3.7.4-2] (core, i386-whitelist)
[08:57] -queuebot:#ubuntu-release- New binary: gnutls28 [amd64] (kinetic-proposed/main) [3.7.4-2ubuntu1] (core, i386-whitelist)
[09:04] -queuebot:#ubuntu-release- New binary: gnutls28 [arm64] (kinetic-proposed/main) [3.7.4-2] (core, i386-whitelist)
[09:07] -queuebot:#ubuntu-release- New binary: gnutls28 [armhf] (kinetic-proposed/main) [3.7.4-2ubuntu1] (core, i386-whitelist)
[09:14] -queuebot:#ubuntu-release- New binary: gnutls28 [arm64] (kinetic-proposed/main) [3.7.4-2ubuntu1] (core, i386-whitelist)
[09:16] -queuebot:#ubuntu-release- Unapproved: apt (bionic-proposed/main) [1.6.14 => 1.6.15] (core)
[09:18] <LocutusOfBorg> doko, gnutls28 builds fine without the reduced parallelism, see above ^^
[09:30] <ricotz> this build doesn't look healthy :) https://launchpad.net/ubuntu/+source/gspell/1.10.0-1/+build/23579817
[09:44] <RikMills> ricotz: a fair few more like that on amd64
[10:24] <LocutusOfBorg> ricotz, what about reporting on #launchpad?
[10:24] <LocutusOfBorg> but I think they already know that
[10:25] -queuebot:#ubuntu-release- New binary: gnutls28 [riscv64] (kinetic-proposed/main) [3.7.4-2ubuntu1] (core, i386-whitelist)
[10:29] -queuebot:#ubuntu-release- Unapproved: unattended-upgrades (focal-proposed/main) [2.3ubuntu0.1 => 2.3ubuntu0.2] (core)
[10:40] -queuebot:#ubuntu-release- Unapproved: update-notifier (focal-proposed/main) [3.192.30.10 => 3.192.30.11] (ubuntu-desktop, ubuntu-server)
[11:24] <ricotz> LocutusOfBorg, yeah, the launchpad builder situation isn't getting any better :(
[11:50] -queuebot:#ubuntu-release- New sync: pytz-deprecation-shim (kinetic-proposed/primary) [0.1.0.post0-2]
[12:27] -queuebot:#ubuntu-release- Unapproved: unattended-upgrades (focal-proposed/main) [2.3ubuntu0.1 => 2.3ubuntu0.2] (core)
[12:29] <slyon> hey ubuntu-release! could somebody please delete my first upload of unattended-upgrades 2.3ubuntu0.2 in https://launchpad.net/ubuntu/focal/+queue?queue_state=1 ? It accidentally included my git-ubuntu history. The followup upload is clean.
[13:55] -queuebot:#ubuntu-release- New binary: nodejs [ppc64el] (kinetic-proposed/universe) [16.13.2+really14.19.1~dfsg-6ubuntu1] (kubuntu)
[14:07] -queuebot:#ubuntu-release- Unapproved: rejected unattended-upgrades [source] (focal-proposed) [2.3ubuntu0.2]
[14:22] <slyon> thank you :)
[14:24] -queuebot:#ubuntu-release- New binary: nodejs [amd64] (kinetic-proposed/universe) [16.13.2+really14.19.1~dfsg-6ubuntu1] (kubuntu)
[14:45] <ahasenack> hi release team, what will happen to the jammy-proposed mariadb-10.6 package in this list? Will it be removed? https://pastebin.ubuntu.com/p/VkCSyrX8qN/
[14:45] <ahasenack> I will need to SRU a fix to jammy, and upload to kinetic as well of course
[14:46] <ahasenack> kinetic will be 10.6.7-3ubuntu1, or 10.6.7-3ubuntu1.22.10.1 if the jammy-proposed one does not get deleted
[14:46] <ahasenack> in which case jammy will get 10.6.7-3ubuntu1.22.04.1
[14:57] -queuebot:#ubuntu-release- New binary: nodejs [s390x] (kinetic-proposed/universe) [16.13.2+really14.19.1~dfsg-6ubuntu1] (kubuntu)
[15:32] -queuebot:#ubuntu-release- New binary: nodejs [arm64] (kinetic-proposed/universe) [16.13.2+really14.19.1~dfsg-6ubuntu1] (kubuntu)
[15:55] -queuebot:#ubuntu-release- New source: papirus-colors (kinetic-proposed/primary) [20211230git-0ubuntu1]
[16:29] <vorlon> RikMills: it does need changing, thanks
[16:30] <RikMills> vorlon: thanks. also step 8? https://wiki.ubuntu.com/Germinate/ConvertingToGit
[16:31] <RikMills> maybe that is already done
[16:31] <vorlon> RikMills: yeah I did that part
[16:31] <RikMills> cool, thabks
[16:31] <RikMills> thanks
[17:07] <vorlon> Trevinho: libnotify sync regresses us by not listing gnome-shell as the preferred implementation of notification-daemon, now tries to pull python3-jarabe into main; please fix https://people.canonical.com/~ubuntu-archive/component-mismatches.html
[17:08] <Trevinho> vorlon: oh, I had discussed that with jbicha and he was telling me that there was no such problem anymore as notification-daemon is also provided by gnome-shell... mhmh
[17:08] <vorlon> right, well, that's incorrect ;)
[17:09] <Trevinho> vorlon: so I'll go back at listing manually the ones providing it as I did initially I guess, as I'd prefer to avoid having an ubuntu fork for that
[17:09] <vorlon> yes gnome-shell provides it, but packages should in general always specify a preferred implementation of a virtual package in their package relationships - especially if they're in Ubuntu main
[17:09] <Trevinho> or using your conditional rules
[17:09] <Trevinho> vorlon: can we define gnome-shell as the default in ubuntu instead?
[17:10] <vorlon> Trevinho: specifying it as the default has to happen in the libnotify source
[17:13] <vorlon> Trevinho: and while Debian policy doesn't mandate it, you /should/ always list a real package that implements the interface, before the virtual package, in Debian as well as Ubuntu in order to have consistent, predictable behavior.  Debian Policy 7.5: "To specify which of a set of real packages should be the default to satisfy a particular dependency on a virtual package, list the real package as
[17:14] <vorlon> an alternative before the virtual one."
[17:14] <Trevinho> vorlon: I see, I guess it's fine to set shell on debian too then, given that plasma-desktop for example will just ignore it no?
[17:16] <vorlon> Trevinho: if you are installing libnotify4 and some package is already on the system that provides notification-daemon, then gnome-shell will not be pulled in.  The default only affects what happens when you're installing this package on a system that doesn't already have a notification-daemon... such as when bootstrapping an image, or doing dependency resolution for a virtual system like germinate
[17:17] <Trevinho> mhmh, I see, well that's probaby a bit too much to install that, but being suggested I suppose it's not happening on regular users (let's say a server user who wants to just send notifications to a remote dbus instance.... not sure how real it is but it's technically possible)
=== chrisccoulson_ is now known as chrisccoulson
[17:18] <vorlon> Trevinho: I notice that previously this was a Suggests instead of a Recommends; that would also make this a non-issue
[17:19]  * Trevinho vorlon: it's a Suggests now https://salsa.debian.org/gnome-team/libnotify/-/commit/b31b560e7b83a2673d931fb12b492cb5d861fda2
[17:19] <ubottu> Commit b31b560 in gnome-team/libnotify "debian/control: Only suggest any implementer of FDO notification daemon"
[17:21] <vorlon> Trevinho: not in the version in kinetic
[17:23] <jbicha> oh sorry, I synced the old version of libnotify. syncing now
[17:23] <vorlon> hah ok
[17:23] <jbicha> I was having a lot of trouble understanding earlier why libnotify thought it needed sugar
[17:24] <jbicha> I'm updating gnome-shell now for libgweather4
[17:25] <vorlon> jbicha: cheers
[17:25] <vorlon> and looks like we need to get libgweather4 building on i386
[17:28] <vorlon> like so https://launchpad.net/ubuntu/+source/libgweather4/4.0.0-2/+build/23582266
[17:31] <ahasenack> what's this "migration-reference/0" trigger in https://autopkgtest.ubuntu.com/packages/t/tinyssh/kinetic/amd64?
[17:33] <RikMills> ahasenack: https://lists.ubuntu.com/archives/ubuntu-devel/2021-November/041663.html
[17:34] <ahasenack> thanks RikMills
[17:36] <RikMills> my only issue is that is seems a disincentive to fix tests, but shrug
[17:45] -queuebot:#ubuntu-release- Unapproved: mariadb-10.6 (jammy-proposed/universe) [1:10.6.7-2ubuntu1 => 1:10.6.7-3ubuntu1] (no packageset)
[17:45] <ahasenack> hi release team, could you please remove mariadb-10.6 that I just uploaded to jammy-proposed?^
[17:45] <ahasenack> I meant for it to be kinetic
[17:46] <ahasenack> and/or SRU team ^
[17:48] -queuebot:#ubuntu-release- Packageset: Added libgweather4 to i386-whitelist in kinetic
[18:52] -queuebot:#ubuntu-release- New binary: nodejs [armhf] (kinetic-proposed/universe) [16.13.2+really14.19.1~dfsg-6ubuntu1] (kubuntu)
[19:15] -queuebot:#ubuntu-release- Unapproved: gnome-maps (jammy-proposed/universe) [42.0-1 => 42.1-0ubuntu1] (desktop-extra, ubuntu-budgie)
[19:22] -queuebot:#ubuntu-release- Unapproved: kubuntu-settings (jammy-proposed/universe) [1:22.04.9 => 1:22.04.10] (kubuntu)
[19:45] -queuebot:#ubuntu-release- Unapproved: software-properties (jammy-proposed/main) [0.99.22 => 0.99.22.1] (core)
[20:35] <Eickmeyer> vorlon: RE: upload of kubuntu-settings: I forgot the # before the bug number in the changelog, which means the bot won't mark it as released automatically. Is that a blocker for the SRU do you think?
[21:16] -queuebot:#ubuntu-release- Unapproved: autofs (jammy-proposed/main) [5.1.8-1ubuntu1 => 5.1.8-1ubuntu1.1] (core)
[21:21] -queuebot:#ubuntu-release- Unapproved: rejected im-config [source] (jammy-proposed) [0.51-1~ubuntu22.04.1]
[22:37] -queuebot:#ubuntu-release- Unapproved: gnome-settings-daemon (jammy-proposed/main) [42.1-1ubuntu2 => 42.1-1ubuntu2.1] (ubuntu-desktop)
[23:00] <ahasenack> I'm dumbfounded why I can't see cmake 3.23.1 in kinetic proposed with apt :/
[23:00] <ahasenack> rmadison shows it, launchpad shows it
[23:00] <ahasenack> I'm not using a mirror
[23:00] <ahasenack> but apt just sees cmake from release
[23:01] <ahasenack> and a lp build failed because of this
[23:01] <ahasenack> The following packages have unmet dependencies:
[23:01] <ahasenack>  cmake : Depends: cmake-data (= 3.23.1-2ubuntu1) but it is not going to be installed
[23:02]  * ahasenack retries the build and calls it a day
[23:06] <bdmurray> Eickmeyer: Yes, not having the a linked to bug for an SRU is a blocker as there is no way to track when verification is done or what verification is required.
[23:21] <Eickmeyer> bdmurray: In that case, reject kubuntu-settings in jammy-unapproved
[23:22] <Eickmeyer> (yes, I have my Kubuntu hat on)
[23:23] <sarnold> ahasenack: *weird(
[23:24] <ahasenack> I think the kinetic images/chroots are not yet 100%
[23:24] <ahasenack> build logs are full of warnings like this
[23:24] <ahasenack> W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:4 and /etc/apt/sources.list.d/proposed.list:1
[23:24] <ahasenack> not fatal, but I haven't seen that in other builds
[23:28] <sarnold> *maybe* it's just down to the funky launchpad builders / publishing in the last week or two -- launchpad sure thinks it's published it, but the archive's kinetic-proposed Packages.gz sure hasn't heard of it.. but it's got 300+ other packages, so it's kinda-sorta working, anyway
[23:29] <ahasenack> yeah
[23:29] <ahasenack> I'll let it rest over the weekend
[23:29] <ahasenack> "rest", heh
[23:30] <Eickmeyer> Or... ubuntu-archive: can I get a quick reject on kubuntu-settings so I can reupload with a proper changelog entry?
[23:30] <Eickmeyer> (jammy unapproved)
[23:30] <ahasenack> I also have a bad upload to jammy
[23:30] <ahasenack> <ahasenack> hi release team, could you please remove mariadb-10.6 that I just uploaded to jammy-proposed?^
[23:30] <ahasenack> <ahasenack> I meant for it to be kinetic
[23:31] <ahasenack> if someone is around ^