/srv/irclogs.ubuntu.com/2022/04/29/#ubuntu-release.txt

-queuebot:#ubuntu-release- Unapproved: linux-firmware (jammy-proposed/main) [20220329.git681281e4-0ubuntu1 => 20220329.git681281e4-0ubuntu1.1] (core, kernel)06:02
RikMillsvorlon: hey, does this need changing? https://bazaar.launchpad.net/~ubuntu-cdimage/ubuntu-cdimage/mainline/view/head:/lib/cdimage/germinate.py#L7506:10
-queuebot:#ubuntu-release- New binary: wpewebkit [armhf] (kinetic-proposed/universe) [2.36.1-1] (no packageset)07:47
* LocutusOfBorg does some syncs/merges before real opening08:22
LocutusOfBorgit would be nice to wait for amd64 to be back online before enabling autosync?08:26
-queuebot:#ubuntu-release- New binary: gnutls28 [amd64] (kinetic-proposed/main) [3.7.4-2] (core, i386-whitelist)08:35
-queuebot:#ubuntu-release- New binary: gnutls28 [s390x] (kinetic-proposed/main) [3.7.4-2] (core, i386-whitelist)08:37
-queuebot:#ubuntu-release- New binary: gnutls28 [ppc64el] (kinetic-proposed/main) [3.7.4-2] (core, i386-whitelist)08:38
-queuebot:#ubuntu-release- New binary: gnutls28 [i386] (kinetic-proposed/main) [3.7.4-2] (core, i386-whitelist)08:48
-queuebot:#ubuntu-release- New binary: gnutls28 [s390x] (kinetic-proposed/main) [3.7.4-2ubuntu1] (core, i386-whitelist)08:52
-queuebot:#ubuntu-release- New binary: gnutls28 [ppc64el] (kinetic-proposed/main) [3.7.4-2ubuntu1] (core, i386-whitelist)08:54
-queuebot:#ubuntu-release- New binary: gnutls28 [i386] (kinetic-proposed/main) [3.7.4-2ubuntu1] (core, i386-whitelist)08:55
-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)08:57
-queuebot:#ubuntu-release- New binary: gnutls28 [arm64] (kinetic-proposed/main) [3.7.4-2] (core, i386-whitelist)09:04
-queuebot:#ubuntu-release- New binary: gnutls28 [armhf] (kinetic-proposed/main) [3.7.4-2ubuntu1] (core, i386-whitelist)09:07
-queuebot:#ubuntu-release- New binary: gnutls28 [arm64] (kinetic-proposed/main) [3.7.4-2ubuntu1] (core, i386-whitelist)09:14
-queuebot:#ubuntu-release- Unapproved: apt (bionic-proposed/main) [1.6.14 => 1.6.15] (core)09:16
LocutusOfBorgdoko, gnutls28 builds fine without the reduced parallelism, see above ^^09:18
ricotzthis build doesn't look healthy :) https://launchpad.net/ubuntu/+source/gspell/1.10.0-1/+build/2357981709:30
RikMillsricotz: a fair few more like that on amd6409:44
LocutusOfBorgricotz, what about reporting on #launchpad?10:24
LocutusOfBorgbut I think they already know that10:24
-queuebot:#ubuntu-release- New binary: gnutls28 [riscv64] (kinetic-proposed/main) [3.7.4-2ubuntu1] (core, i386-whitelist)10:25
-queuebot:#ubuntu-release- Unapproved: unattended-upgrades (focal-proposed/main) [2.3ubuntu0.1 => 2.3ubuntu0.2] (core)10:29
-queuebot:#ubuntu-release- Unapproved: update-notifier (focal-proposed/main) [3.192.30.10 => 3.192.30.11] (ubuntu-desktop, ubuntu-server)10:40
ricotzLocutusOfBorg, yeah, the launchpad builder situation isn't getting any better :(11:24
-queuebot:#ubuntu-release- New sync: pytz-deprecation-shim (kinetic-proposed/primary) [0.1.0.post0-2]11:50
-queuebot:#ubuntu-release- Unapproved: unattended-upgrades (focal-proposed/main) [2.3ubuntu0.1 => 2.3ubuntu0.2] (core)12:27
slyonhey 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.12:29
-queuebot:#ubuntu-release- New binary: nodejs [ppc64el] (kinetic-proposed/universe) [16.13.2+really14.19.1~dfsg-6ubuntu1] (kubuntu)13:55
-queuebot:#ubuntu-release- Unapproved: rejected unattended-upgrades [source] (focal-proposed) [2.3ubuntu0.2]14:07
slyonthank you :)14:22
-queuebot:#ubuntu-release- New binary: nodejs [amd64] (kinetic-proposed/universe) [16.13.2+really14.19.1~dfsg-6ubuntu1] (kubuntu)14:24
ahasenackhi 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
ahasenackI will need to SRU a fix to jammy, and upload to kinetic as well of course14:45
ahasenackkinetic will be 10.6.7-3ubuntu1, or 10.6.7-3ubuntu1.22.10.1 if the jammy-proposed one does not get deleted14:46
ahasenackin which case jammy will get 10.6.7-3ubuntu1.22.04.114:46
-queuebot:#ubuntu-release- New binary: nodejs [s390x] (kinetic-proposed/universe) [16.13.2+really14.19.1~dfsg-6ubuntu1] (kubuntu)14:57
-queuebot:#ubuntu-release- New binary: nodejs [arm64] (kinetic-proposed/universe) [16.13.2+really14.19.1~dfsg-6ubuntu1] (kubuntu)15:32
-queuebot:#ubuntu-release- New source: papirus-colors (kinetic-proposed/primary) [20211230git-0ubuntu1]15:55
vorlonRikMills: it does need changing, thanks16:29
RikMillsvorlon: thanks. also step 8? https://wiki.ubuntu.com/Germinate/ConvertingToGit16:30
RikMillsmaybe that is already done16:31
vorlonRikMills: yeah I did that part16:31
RikMillscool, thabks16:31
RikMillsthanks16:31
vorlonTrevinho: 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.html17:07
Trevinhovorlon: 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... mhmh17:08
vorlonright, well, that's incorrect ;)17:08
Trevinhovorlon: 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 that17:09
vorlonyes 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 main17:09
Trevinhoor using your conditional rules17:09
Trevinhovorlon: can we define gnome-shell as the default in ubuntu instead?17:09
vorlonTrevinho: specifying it as the default has to happen in the libnotify source17:10
vorlonTrevinho: 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 as17:13
vorlonan alternative before the virtual one."17:14
Trevinhovorlon: 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:14
vorlonTrevinho: 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 germinate17:16
Trevinhomhmh, 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)17:17
=== chrisccoulson_ is now known as chrisccoulson
vorlonTrevinho: I notice that previously this was a Suggests instead of a Recommends; that would also make this a non-issue17:18
* Trevinho vorlon: it's a Suggests now https://salsa.debian.org/gnome-team/libnotify/-/commit/b31b560e7b83a2673d931fb12b492cb5d861fda217:19
ubottuCommit b31b560 in gnome-team/libnotify "debian/control: Only suggest any implementer of FDO notification daemon"17:19
vorlonTrevinho: not in the version in kinetic17:21
jbichaoh sorry, I synced the old version of libnotify. syncing now17:23
vorlonhah ok17:23
jbichaI was having a lot of trouble understanding earlier why libnotify thought it needed sugar17:23
jbichaI'm updating gnome-shell now for libgweather417:24
vorlonjbicha: cheers17:25
vorlonand looks like we need to get libgweather4 building on i38617:25
vorlonlike so https://launchpad.net/ubuntu/+source/libgweather4/4.0.0-2/+build/2358226617:28
ahasenackwhat's this "migration-reference/0" trigger in https://autopkgtest.ubuntu.com/packages/t/tinyssh/kinetic/amd64?17:31
RikMillsahasenack: https://lists.ubuntu.com/archives/ubuntu-devel/2021-November/041663.html17:33
ahasenackthanks RikMills17:34
RikMillsmy only issue is that is seems a disincentive to fix tests, but shrug17:36
-queuebot:#ubuntu-release- Unapproved: mariadb-10.6 (jammy-proposed/universe) [1:10.6.7-2ubuntu1 => 1:10.6.7-3ubuntu1] (no packageset)17:45
ahasenackhi release team, could you please remove mariadb-10.6 that I just uploaded to jammy-proposed?^17:45
ahasenackI meant for it to be kinetic17:45
ahasenackand/or SRU team ^17:46
-queuebot:#ubuntu-release- Packageset: Added libgweather4 to i386-whitelist in kinetic17:48
-queuebot:#ubuntu-release- New binary: nodejs [armhf] (kinetic-proposed/universe) [16.13.2+really14.19.1~dfsg-6ubuntu1] (kubuntu)18:52
-queuebot:#ubuntu-release- Unapproved: gnome-maps (jammy-proposed/universe) [42.0-1 => 42.1-0ubuntu1] (desktop-extra, ubuntu-budgie)19:15
-queuebot:#ubuntu-release- Unapproved: kubuntu-settings (jammy-proposed/universe) [1:22.04.9 => 1:22.04.10] (kubuntu)19:22
-queuebot:#ubuntu-release- Unapproved: software-properties (jammy-proposed/main) [0.99.22 => 0.99.22.1] (core)19:45
Eickmeyervorlon: 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?20:35
-queuebot:#ubuntu-release- Unapproved: autofs (jammy-proposed/main) [5.1.8-1ubuntu1 => 5.1.8-1ubuntu1.1] (core)21:16
-queuebot:#ubuntu-release- Unapproved: rejected im-config [source] (jammy-proposed) [0.51-1~ubuntu22.04.1]21:21
-queuebot:#ubuntu-release- Unapproved: gnome-settings-daemon (jammy-proposed/main) [42.1-1ubuntu2 => 42.1-1ubuntu2.1] (ubuntu-desktop)22:37
ahasenackI'm dumbfounded why I can't see cmake 3.23.1 in kinetic proposed with apt :/23:00
ahasenackrmadison shows it, launchpad shows it23:00
ahasenackI'm not using a mirror23:00
ahasenackbut apt just sees cmake from release23:00
ahasenackand a lp build failed because of this23:01
ahasenackThe following packages have unmet dependencies:23:01
ahasenack cmake : Depends: cmake-data (= 3.23.1-2ubuntu1) but it is not going to be installed23:01
* ahasenack retries the build and calls it a day23:02
bdmurrayEickmeyer: 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:06
Eickmeyerbdmurray: In that case, reject kubuntu-settings in jammy-unapproved23:21
Eickmeyer(yes, I have my Kubuntu hat on)23:22
sarnoldahasenack: *weird(23:23
ahasenackI think the kinetic images/chroots are not yet 100%23:24
ahasenackbuild logs are full of warnings like this23:24
ahasenackW: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:4 and /etc/apt/sources.list.d/proposed.list:123:24
ahasenacknot fatal, but I haven't seen that in other builds23:24
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, anyway23:28
ahasenackyeah23:29
ahasenackI'll let it rest over the weekend23:29
ahasenack"rest", heh23:29
EickmeyerOr... 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
ahasenackI also have a bad upload to jammy23: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 kinetic23:30
ahasenackif someone is around ^23:31

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