[01:23] -queuebot:#ubuntu-release- Unapproved: civicrm (jammy-proposed/universe) [5.33.2+dfsg1-1build1 => 5.33.2+dfsg1-1ubuntu1] (no packageset) [01:24] -queuebot:#ubuntu-release- Unapproved: accepted civicrm [source] (jammy-proposed) [5.33.2+dfsg1-1ubuntu1] [02:07] -queuebot:#ubuntu-release- Unapproved: libgweather4 (jammy-proposed/universe) [4.0.0-1 => 4.0.0-2] (no packageset) (sync) [02:08] -queuebot:#ubuntu-release- Unapproved: accepted libgweather4 [sync] (jammy-proposed) [4.0.0-2] [04:02] -queuebot:#ubuntu-release- Unapproved: osmo-pcu (jammy-proposed/universe) [0.8.0-3build3 => 0.8.0-3ubuntu1] (no packageset) [04:03] -queuebot:#ubuntu-release- Unapproved: accepted osmo-pcu [source] (jammy-proposed) [0.8.0-3ubuntu1] === tomreyn_ is now known as tomreyn [07:08] hello, please [07:08] old binaries left on riscv64: liblldb-dev, libllvm-ocaml-dev, libomp-dev, libomp5, lld, lldb, python3-lldb (from 0.55~exp1) [07:12] hum, what are those recent empty emails on the changes list? where packages copied over themselves for some reason? but that shouldn't trigger an email? [07:18] seb128: it's to do with "do they build on i386 or not" in some direction or other i think [07:20] mwhudson, weird, I enabled the i386 of some of those and did the copy to got them built, I wonder what was wrong or missing [07:20] I guess that's a question for vorlon [07:20] mwhudson, thanks [07:20] seb128: yeah i don't know how this works in practice [07:34] seb128, hello, do you know why debhelper is not installable on i386 in 20.04? [07:34] LocutusOfBorg, release or backport? [07:34] backport [07:34] LocutusOfBorg, https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965800 [07:34] Launchpad bug 1965800 in debugedit (Ubuntu) "debhelper in focal-backports not usable for i386 package building (missing dependency)" [Undecided, New] [07:36] LocutusOfBorg, basically the new version depends on debugedit which is built from the rpm source on focal and Steve said rpm wasn't something we wanted built on i386 [07:36] so its being worked on, nice thanks! [07:36] LocutusOfBorg, discussions were to backport a split debugedit as in newer series or to revert that depends [07:37] I guess, I'm not involved into fixing it, I just know about the topic because I got pinged about adding the missing depends on i386 [07:37] seb128, btw we don't need to bring rpm on i386, we can backport debugedit from jammy? [07:37] debugedit has its own package now [07:37] LocutusOfBorg, that's what I just wrote 3 lines up? [07:37] oh yes indeed [07:38] let me grab some coffee then :) [07:38] thanks [07:38] np! [07:38] so we need this change on focal https://launchpad.net/ubuntu/+source/rpm/4.16.1.2+dfsg1-3ubuntu1 [07:38] (in case we want to do the split) [08:03] -queuebot:#ubuntu-release- Unapproved: accepted python-openstackclient [source] (jammy-proposed) [5.8.0-0ubuntu1] [08:04] -queuebot:#ubuntu-release- Unapproved: accepted ibus [sync] (jammy-proposed) [1.5.26-3] [08:04] -queuebot:#ubuntu-release- Unapproved: accepted nautilus-share [source] (jammy-proposed) [0.7.3-2ubuntu6] [08:04] -queuebot:#ubuntu-release- Unapproved: accepted lm-sensors [source] (jammy-proposed) [1:3.6.0-7ubuntu1] [08:05] -queuebot:#ubuntu-release- Unapproved: accepted mate-tweak [source] (jammy-proposed) [22.04.8-0ubuntu2] [08:05] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-settings [source] (jammy-proposed) [22.04.6] [08:05] -queuebot:#ubuntu-release- Unapproved: accepted python-ovsdbapp [source] (jammy-proposed) [1.15.1-0ubuntu2] [08:05] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (jammy-proposed) [2:20.0.0-0ubuntu2] [08:05] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-mate-artwork [source] (jammy-proposed) [22.04.13] [08:25] sil2100, hey, do you think we could have a langpack update? did we stop the weekly job before beta? Gunnar did tweaks to fix gnome-desktop missing after the package was renamed and I would like to confirm that it's resolved [08:25] seb128: hey! I think there should be one automatic happening today! [08:25] ah, great, thanks! [08:25] I re-enabled the automatic updates yesterday and I think those are planned on Tuesdays [08:26] I'll make sure to check up on if it's happening or not later today o/ [08:29] doko: I see a mercurial 6.1 sync by you, but no FFe, and it ftbfs? [08:30] 7 tests failed :( [08:32] various new features, backwards incompatible changes [08:35] it seems we're down to 6 packages from the ppc64el rebuild that have not migrated yet [08:35] tmux is regressed only on ppc64el, which is dubious [11:02] ubuntu-archive please NBS cleanup old binaries left on riscv64: liblldb-dev, libllvm-ocaml-dev, libomp-dev, libomp5, lld, lldb, python3-lldb (from 0.55~exp1) [11:37] -queuebot:#ubuntu-release- Unapproved: dask (jammy-proposed/universe) [2022.01.0+dfsg-1 => 2022.01.0+dfsg-1ubuntu1] (no packageset) [11:38] -queuebot:#ubuntu-release- Unapproved: accepted dask [source] (jammy-proposed) [2022.01.0+dfsg-1ubuntu1] [11:39] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (jammy-proposed) [22.04.11] [11:39] -queuebot:#ubuntu-release- Unapproved: accepted zenity [sync] (jammy-proposed) [3.42.0-1] [11:45] -queuebot:#ubuntu-release- Unapproved: qt6-webengine (jammy-proposed/universe) [6.2.4+dfsg-1ubuntu1 => 6.2.4+dfsg-1ubuntu2] (no packageset) (sync) [11:46] -queuebot:#ubuntu-release- Unapproved: accepted qt6-webengine [sync] (jammy-proposed) [6.2.4+dfsg-1ubuntu2] [12:35] -queuebot:#ubuntu-release- Unapproved: mate-power-manager (jammy-proposed/universe) [1.26.0-1 => 1.26.0-1ubuntu0] (ubuntu-mate) [12:37] -queuebot:#ubuntu-release- Unapproved: ubuntu-mate-artwork (jammy-proposed/universe) [22.04.13 => 22.04.14] (ubuntu-mate) [12:39] -queuebot:#ubuntu-release- Unapproved: ayatana-indicator-power (jammy-proposed/universe) [22.2.0-1 => 22.2.0-1ubuntu0] (ubuntu-mate) [12:41] Please accept mate-power-manager 1.26.0-1ubuntu0 and ubuntu-mate-artwork 22.04.14 and ayatana-indicator-power 22.2.0-1ubuntu0, they are all fixes for #1967854 [12:45] -queuebot:#ubuntu-release- Unapproved: php-malkusch-lock (jammy-proposed/universe) [2.2+ds.1-2build1 => 2.2+ds.1-2ubuntu1] (no packageset) [12:45] -queuebot:#ubuntu-release- Unapproved: accepted php-malkusch-lock [source] (jammy-proposed) [2.2+ds.1-2ubuntu1] [12:51] -queuebot:#ubuntu-release- Unapproved: libnotify (jammy-proposed/main) [0.7.9-3ubuntu4 => 0.7.9-3ubuntu5] (desktop-core, i386-whitelist) [13:01] -queuebot:#ubuntu-release- Unapproved: wpewebkit (jammy-proposed/universe) [2.36.0-1 => 2.36.0-2ubuntu1] (no packageset) [13:01] -queuebot:#ubuntu-release- Unapproved: accepted wpewebkit [source] (jammy-proposed) [2.36.0-2ubuntu1] [13:33] -queuebot:#ubuntu-release- Unapproved: shotwell (jammy-proposed/main) [0.30.14-1ubuntu4 => 0.30.14-1ubuntu5] (ubuntu-desktop) [13:36] -queuebot:#ubuntu-release- Unapproved: network-manager (jammy-proposed/main) [1.36.4-1ubuntu1 => 1.36.4-2ubuntu1] (desktop-core, i386-whitelist) [13:41] sil2100, hi! Do you know if headers/footers like https://cdimage.ubuntu.com/releases/jammy/beta/HEADER.html are maintained in VCS somewhere? [13:41] sil2100, I kind of remember you editing one, but I'm not sure of where/how [13:42] paride: hey! Not really, those are edited by the ubuntu-cdimage code dynamically and/or edited manually (when tweaks are needed) [13:42] Do you want something changed? [13:42] sil2100, yep, we want to remove POWER8 from the Jammy server images pages [13:43] paride: on it! [13:43] Ah, right, baseline bump, forgot that we mention it here [13:45] sil2100, I'm not sure on how stuff is moved around. Maybe we should update https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/HEADER.html and that will end in https://cdimage.ubuntu.com/ubuntu/releases/jammy/beta and /release automatically? [14:16] juliank: 6.0.1 even ftbfs with python 3.10 ... [14:33] doko: everything ftbfs, the world is broken! [14:34] doko: still, that needed a ffe? [14:35] -queuebot:#ubuntu-release- Unapproved: scikit-learn (jammy-proposed/universe) [0.23.2-5ubuntu5 => 0.23.2-5ubuntu6] (no packageset) [14:36] -queuebot:#ubuntu-release- Unapproved: accepted scikit-learn [source] (jammy-proposed) [0.23.2-5ubuntu6] [14:47] paride: it's a bit ugly, but basically whenever cdimage publishes some images, it generates those dynamically based on what images it wants to publish (what image types, arches, series etc.) [14:47] (apologies, was in a meeting!) [14:47] I have changes to cdimage to tweak this for the future, but also will tweak the beta released tree manually [14:47] (since those won't be updated unless we publish some new beta images ;p) [14:48] sil2100, that sounds good, thanks! [14:59] -queuebot:#ubuntu-release- Unapproved: backport-iwlwifi-dkms (jammy-proposed/universe) [9858-0ubuntu1 => 9858-0ubuntu2] (no packageset) [14:59] -queuebot:#ubuntu-release- Unapproved: accepted backport-iwlwifi-dkms [source] (jammy-proposed) [9858-0ubuntu2] [15:06] -queuebot:#ubuntu-release- Unapproved: backport-iwlwifi-dkms (impish-proposed/universe) [9340-0ubuntu4 => 9580-0ubuntu1~21.10.1.1] (no packageset) [15:09] -queuebot:#ubuntu-release- Unapproved: backport-iwlwifi-dkms (focal-proposed/universe) [8324-0ubuntu3~20.04.4 => 9580-0ubuntu1~20.04.1.1] (no packageset) [15:09] LocutusOfBorg: NBS done [15:12] Wimpy: weird version number! 1.26.0-1ubuntu0 [15:13] Wimpy: I must say that I never saw ubuntu0 being used before [15:13] -queuebot:#ubuntu-release- Unapproved: accepted mate-power-manager [source] (jammy-proposed) [1.26.0-1ubuntu0] [15:13] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-mate-artwork [source] (jammy-proposed) [22.04.14] [15:14] -queuebot:#ubuntu-release- Unapproved: update-notifier (jammy-proposed/main) [3.192.53 => 3.192.54] (ubuntu-desktop, ubuntu-server) [15:14] Actually, maybe that's even wrong to use here, hmm, might have not accepted those [15:14] -queuebot:#ubuntu-release- Unapproved: accepted ayatana-indicator-power [source] (jammy-proposed) [22.2.0-1ubuntu0] [15:14] Oh well! [15:15] sil2100, why would it be wrong? [15:15] it's a bit weird but 1ubuntu0 < 1ubuntu1 [15:16] so it's a clear update path [15:16] you then have to sru it as 1ubuntu0~20.04.1 or something instead of being able to use 1ubuntu0.20.04.1, but meh [15:17] seb128: stylistically mostly! But there is an edge case I can think of - if someone would like to backport 22.2.0-1ubuntu0 in the normal SRU versioning of 22.2.0-1ubuntu0.1 or 22.2.0-1ubuntu0.series, this wouldn't work anymore [15:17] Yeah, as juliank mentioned [15:17] But essentially, nothing super wrong in it [15:19] -queuebot:#ubuntu-release- Unapproved: accepted libnotify [source] (jammy-proposed) [0.7.9-3ubuntu5] [15:19] sil2100: Thanks. I use ubuntu0 to denote ubuntu uploads where I've already pushed commits to Debian. So I can easily see what to sync next cycle. [15:22] Wimpy, if you don't have a delta you want to keep you can upload a revision without 'ubuntu' so it autosync, like 1+fakesync1 [15:25] Oh? That's a neat trick! [15:26] yes, the autosync job only skip versions which include 'ubuntu' [15:27] seb128: Thanks for the tip! [15:27] np! [15:29] Anyone on release duty that has a spare cycle please? Ubuntu Budgie jammy daily has failed again today ... 3rd time in a row. Doesn't feel like a glitch to me. [15:31] fossfreedom: how did it fail? Do you have a build log handy? [15:31] Found it [15:32] eh, it's the same issue as always - problem opening the seeds [15:32] I sadly have no workaround for this besides re-trying the build - let me do that [15:32] that is the same infra issue that cjwatson has been tracking [15:32] -queuebot:#ubuntu-release- Unapproved: sra-sdk (jammy-proposed/universe) [2.11.3+dfsg-1 => 2.11.3+dfsg-1ubuntu1] (no packageset) [15:32] Are we just incredibly unlucky? [15:32] fossfreedom: yes [15:33] 😞 [15:33] Fair enough. Thx. [15:33] -queuebot:#ubuntu-release- Unapproved: accepted sra-sdk [source] (jammy-proposed) [2.11.3+dfsg-1ubuntu1] [15:33] fossfreedom: rebuild requested [15:33] I have plenty of emails saying the kubuntu build failed for that reason [15:34] a retry may or may not succeed [15:35] in fact, it is mildly surprising budgie had not seen this much until now [15:35] as it has been an issue for some time [15:42] -queuebot:#ubuntu-release- Unapproved: ddcci-driver-linux (focal-proposed/universe) [0.3.3-1 => 0.3.3-1ubuntu0.1] (kernel-dkms) [15:58] ginggs: looks like python3-stdlib-extensions is currently blocked by python3.9 removal, and python3.9 has a few revdeps still. Any help needed there? [16:15] -queuebot:#ubuntu-release- Unapproved: manila (impish-proposed/universe) [1:13.0.0-0ubuntu2 => 1:13.0.2-0ubuntu1] (openstack) [16:46] -queuebot:#ubuntu-release- Unapproved: waitress (jammy-proposed/main) [1.4.4-1.1 => 1.4.4-1.1ubuntu1] (no packageset) [18:53] an easy action for someone would be to clean up mythexport so that it is not building on architectures where it will be uninstallable https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy_uninst.txt [18:59] huh wonder how I ended up deleting libpth20:i386 when gcc-9 needed it [19:03] vorlon: there are some things still on https://people.canonical.com/~ubuntu-archive/transitions/html/python3.10-only.html that more eyes on would be great [19:04] scikit-learn should be fixed by my last upload [19:04] thrift's binaries need accepting [19:05] looking [19:05] gudhi OOM'd on amd64, but after fixing that locally, it now seems to FTBFS due to the latest qt5 upload [19:05] -queuebot:#ubuntu-release- New: accepted thrift [arm64] (jammy-proposed) [0.16.0-2] [19:05] -queuebot:#ubuntu-release- New: accepted thrift [riscv64] (jammy-proposed) [0.16.0-2] [19:06] -queuebot:#ubuntu-release- New: accepted thrift [armhf] (jammy-proposed) [0.16.0-2] [19:06] gudhi FTBFS everywhere now, that is [19:06] vorlon: thanks :) [19:06] -queuebot:#ubuntu-release- New: accepted thrift [amd64] (jammy-proposed) [0.16.0-2] [19:06] -queuebot:#ubuntu-release- New: accepted thrift [s390x] (jammy-proposed) [0.16.0-2] [19:06] -queuebot:#ubuntu-release- New: accepted thrift [ppc64el] (jammy-proposed) [0.16.0-2] [19:07] khmer has an incomplete patch in debian bug #1008402 [19:07] Debian bug 1008402 in src:khmer "khmer: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p '3.10 3.9' returned exit code 13" [Serious, Open] https://bugs.debian.org/1008402 [19:23] vorlon, what were those 'no content' emails on j-changes list yesterday your evening? [19:30] seb128: I'm not subscribed, can you give me a pointer? [19:33] seb128: I guess https://lists.ubuntu.com/archives/jammy-changes/2022-April/013299.html might be an example - I had run i386 binary removals with incorrect setup, so then I had to restore them. These were binary self-copies of the packages already in the jammy release pocket [19:34] vorlon, ah ok, thanks. and yes that's one example [19:35] vorlon, I was mostly asking because taking session-migration as an example I did add it to the whitelest and copied over doing 'copy-package -b --force-same-destination -e $version $pkg' but that didn't trigger a changes email [19:35] vorlon, so I was wondering if I did something wrong you had to fix or if we were doing things differently [19:35] hmm! that should be effectively equivalent to the command I ran [19:36] k, weird, maybe the freeze is making a difference there? [19:36] I did the enabling before we were frozen [19:36] really have no idea, sorry [19:36] no worry, I was just checking [19:36] thanks! [19:42] seb128: speaking of, now that jxrlib has been bootstrapped, can you please add it directly to the seed so that it can be dropped from the code? lp:~ubuntu-core-dev/ubuntu-seeds/+git/i386 [19:47] doko: you added strace back to the manual whitelist for i386; there is no rationale given in the code or the commit log and if I remove it from the code it drops out of the seed. I think we may have discussed this once before, but I don't remember the details. If this is a package you're saying needs to be available for its own purpose without revdeps, please move it to the seed; otherwise, can [19:47] this be dropped? [19:59] -queuebot:#ubuntu-release- Packageset: Removed libdmx from i386-whitelist in jammy [20:08] vorlon, sorry I don't really understand how the i386 whitelisting is working, I documented what I get on https://wiki.ubuntu.com/ArchiveAdministration#i386_whitelist_updates , I would welcome you tweaking that to add more knowledge if possible [20:08] like why do we need to add things to the code sometime if we have a seed? [20:08] seb128: because seeds only operate on binary packages that already exist; so a code override is needed for bootstrapping [20:09] let's see if I can log in to the wiki, there's an RT about that currently [20:09] so the instructions should be to remove from the code directly after bootstrapping and edit the seed? [20:09] if so why do we have such a list still in the code? [20:09] thanks! [20:10] $ grep -c newSet update-i386-whitelist [20:10] 37 [20:10] well I just removed some of them ;) [20:11] and then some of them are special cases to let the ubuntu-toolchain PPA build packages in series for which the source package doesn't exist in the main archive [20:11] from what you wrote I would understand that the steps are 'add special case, run script, wait for build, remove from code and add to seed' [20:11] and then some of them are... incomplete [20:11] yeah, that's how I would describe it [20:11] so I would expect that list to be always ~0 [20:12] I meant outside of the period it takes to bootstrap an addition [20:12] and yeah I can't log in to the wiki [20:12] :( [20:12] my goal is that every exception in that script is either removed, or clearly documented. We are.. far from that [20:13] right, and I'm responsible for some of those since I didn't really understand the process, sorry [20:14] I could log into the wiki btw [20:14] -queuebot:#ubuntu-release- Packageset: Added rpcbind to i386-whitelist in jammy [20:15] still timing out for me [20:16] vorlon, the last edit on https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/i386/tree/i386 is from july, doesn't sound right? [20:17] seb128: that's actually what I see as well. It's infrequent that we update the seed, because only things that we *directly* declare that we support end up there - not new dependencies/build-dependencies that get bootstrapped [20:19] ah, I see [20:20] vorlon, https://wiki.ubuntu.com/ArchiveAdministration?action=diff&rev2=321&rev1=320 , feel free to tweak later once you can connect again if needed [20:21] cheers [20:22] -queuebot:#ubuntu-release- Unapproved: wpewebkit (jammy-proposed/universe) [2.36.0-2ubuntu1 => 2.36.0-2ubuntu2] (no packageset) [20:23] -queuebot:#ubuntu-release- Unapproved: accepted wpewebkit [source] (jammy-proposed) [2.36.0-2ubuntu2] [20:45] ginggs: curiously the list of packages you gave wrt the transition appears to be disjoint from the set returned by 'reverse-depends src:python3.9' [20:45] I guess that transition is maybe only looking at deps on *python3* (>= 3.9)? [20:49] the blockers I see are esys-particle, csound, gyoto [20:58] -queuebot:#ubuntu-release- Unapproved: gnuradio (jammy-proposed/universe) [3.10.1.1-1 => 3.10.1.1-1ubuntu1] (no packageset) [20:59] -queuebot:#ubuntu-release- Unapproved: accepted gnuradio [source] (jammy-proposed) [3.10.1.1-1ubuntu1] [21:16] -queuebot:#ubuntu-release- Unapproved: accepted waitress [source] (jammy-proposed) [1.4.4-1.1ubuntu1] [21:17] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (jammy-proposed) [3.192.54] [21:17] -queuebot:#ubuntu-release- Unapproved: accepted network-manager [source] (jammy-proposed) [1.36.4-2ubuntu1] [21:17] -queuebot:#ubuntu-release- Unapproved: accepted shotwell [source] (jammy-proposed) [0.30.14-1ubuntu5] [22:09] -queuebot:#ubuntu-release- Unapproved: lxc (jammy-proposed/universe) [1:4.0.12-0ubuntu2 => 1:5.0.0~git2209-g5a7b9ce67-0ubuntu1] (ubuntu-server) [23:03] vorlon: do you have any obvious targets for +1 time this week? [23:03] there [23:04] there's a bunch of garbage in proposed but most of it looks pretty garbagey to me [23:04] mwhudson: well, I'd like less garbage in -proposed generally; but in particular I would like beignet ftbfs in -proposed fixed so I can remove llvm-9 which is gone from Debian [23:05] i guess there are some power9 rebuilds that might be interesting [23:06] vorlon: yikes [23:07] oh wait that's a binary that's the output of the build failing, i thought it was making gcc explode at first [23:15] mwhudson: also there was my hint somewhere in scrollback that someone could clean mythexport up off of https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy_uninst.txt by not having the package build on archs where it won't be installable [23:33] ack [23:34] i do wonder about things like that. if someone builds mythtv or whatever for riscv64 do we need to come back and remember to change mythexport again? [23:35] mwhudson: my preferred solution here is to update the package so the build-dependencies reflect the runtime dependencies; i.e. if it's mythtv that's missing and making it uninstallable, stick it in build-deps and then we don't have to worry about arch variation over time [23:36] vorlon: ah, neat [23:36] the only thing I *won't* do is delete the binaries that are currently there, without a sourceful change, since they'll just grow back on the next upload :) [23:51] -queuebot:#ubuntu-release- Unapproved: rejected ubuntu-drivers-common [source] (focal-proposed) [1:0.9.0~0.20.04.7]