[00:02] well https://launchpad.net/ubuntu/+source/sblim-sfcb/1.4.9-0ubuntu6/+build/22604622 just looks completely broken [00:09] mwhudson: RE: numba, looks like a new version is available and just not in sid yet. Should we, idk, just grab the source and JFDI? [00:09] Eickmeyer: does it support 3.10 yet? [00:09] Yes, that was added with 0.55.0, it's at 0.55.1 now. [00:11] https://github.com/numba/numba/releases [00:11] vorlon: wtf https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#sssd adsys/0.8 isn't a thing any more? [00:13] vorlon: maybe you should delete adsys again [00:13] Salsa down for anybody else? I'm getting a big fat 403 for no good reason. [00:14] https://lists.debian.org/debian-infrastructure-announce/2022/02/msg00000.html [00:14] Ahhhhhh yes, thanks, cjwatson. [01:36] mwhudson: I'm retrying adsys autopkgtest with --all-proposed, which given that the test passed w/ -proposed samba, that might do the trick and with less effort than deleting [01:36] (since I would need not only to delete but also block) [01:36] vorlon: ok [01:37] oh right we want sssd and samba both in triggers [01:37] ahasenack did one and i did the other [01:38] * mwhudson afk for a bit [01:44] oh look. I can't remove llvm-9 because pocl because llvm-11 because ocaml because plplot because python. [01:46] pythonshmython. who needs it. [01:46] plplot. plplot does. [01:50] mwhudson: so adsys/armhf still failed with --all-proposed https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/armhf/a/adsys/20220301_014840_f08f8@/log.gz [02:21] adsys demoted to proposed; force-skiptest added for sssd (so we don't have to wait for the archive publisher); and britney restarted again [02:27] vorlon: bla [02:28] vorlon: do you want a hint to stop adsys migrating again? [02:29] mwhudson, vorlon: I'm build testing numba in my ppa. It should solve a problem or two with some migration. Want it? [02:29] Eickmeyer: not right now i think [02:30] mwhudson: Ok. Thought I'd ask as I don't want to complicate matters. [02:31] mwhudson: I added a block-proposed bug [02:31] vorlon: ah ha [02:32] Eickmeyer: numba can't make anything worse, everything that uses it is in proposed only right now [02:34] vorlon, mwhudson: It completely ftbfs anyhow, so much for being 3.10 ready. [02:35] And yes, it was against proposed. [02:42] It's complaining about tbb being too old. [02:42] * Eickmeyer finds himself in dependency hell [02:43] ah that might need a sync maybe? [02:43] there was something on debian-python about that [02:43] Nope, sid's is too old too. [02:44] Needs 2021 update or better, and 2020 is in sid. [02:44] ah the one in experimental maybe? [02:45] I don't see one in experimental? [02:45] oh wait that's https://buildd.debian.org/status/package.php?p=onetbb&suite=experimental [02:45] is that the same thing at all? [02:45] It should be, but that means the package name changed. [02:46] ah yes http://metadata.ftp-master.debian.org/changelogs/main/o/onetbb/onetbb_2021.5.0-7_changelog [02:46] Aha!@ [02:46] I'll syncpackage that. [02:48] -queuebot:#ubuntu-release- New sync: onetbb (jammy-proposed/primary) [2021.5.0-7] [02:49] Means we should probably dummy package tbb -> onetbb [02:57] Dang, wireguard was promoted, so I can no longer upload. I guess others are watching more closely anyway though, and can take care of it. [03:01] Eickmeyer: i think the binary packages are the same [03:01] well up to SONAME [03:01] mwhudson: Yeah, in that case do we remove the old tbb in favor of onetbb from the archive? [03:33] Eickmeyer: i think that would be the usual way, yes [03:33] mwhudson: Kinda thought so. [03:37] vorlon: i think britney is trolling us again [03:37] https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#source-highlight [03:38] why is source-highlight in proposed in main? https://launchpad.net/ubuntu/+source/source-highlight [03:40] ubuntu-archive: which component should source-hightlight be in? [03:45] mwhudson: check gdb [03:47] sarnold: que? [03:48] oh i see [03:48] why does reverse-depends not see that? [03:49] usually because I forget the src: thingy :) [03:49] oh i see [03:49] gdb has dropped the dep now [03:49] so i think source-highlight can be dropped to universe now too [03:53] does something magically do that when unseeded packages are no longer required by seeded packages? [04:15] sarnold: no, members of ~ubuntu-archive do that after reading the component-mismatches report [04:16] it's on https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.html [04:19] RAOF: hi [04:19] ? [08:10] -queuebot:#ubuntu-release- New: accepted fwupd [amd64] (focal-proposed) [1.7.5-3~20.04.1] [08:10] -queuebot:#ubuntu-release- New: accepted fwupd [armhf] (focal-proposed) [1.7.5-3~20.04.1] [08:10] -queuebot:#ubuntu-release- New: accepted fwupd [riscv64] (focal-proposed) [1.7.5-3~20.04.1] [08:10] -queuebot:#ubuntu-release- New: accepted fwupd [arm64] (focal-proposed) [1.7.5-3~20.04.1] [08:10] -queuebot:#ubuntu-release- New: accepted fwupd [s390x] (focal-proposed) [1.7.5-3~20.04.1] [08:10] -queuebot:#ubuntu-release- New: accepted fwupd [ppc64el] (focal-proposed) [1.7.5-3~20.04.1] [08:11] -queuebot:#ubuntu-release- New: accepted fwupd [amd64] (impish-proposed) [1.7.5-3~21.10.1] [08:11] -queuebot:#ubuntu-release- New: accepted fwupd [armhf] (impish-proposed) [1.7.5-3~21.10.1] [08:12] -queuebot:#ubuntu-release- New: accepted fwupd [riscv64] (impish-proposed) [1.7.5-3~21.10.1] [08:12] -queuebot:#ubuntu-release- New: accepted fwupd [arm64] (impish-proposed) [1.7.5-3~21.10.1] [08:12] -queuebot:#ubuntu-release- New: accepted fwupd [s390x] (impish-proposed) [1.7.5-3~21.10.1] [08:12] -queuebot:#ubuntu-release- New: accepted fwupd [ppc64el] (impish-proposed) [1.7.5-3~21.10.1] [08:15] -queuebot:#ubuntu-release- New: accepted oem-sutton.newell-caesar-meta [sync] (focal-proposed) [20.04~ubuntu1] [08:18] -queuebot:#ubuntu-release- New binary: oem-sutton.newell-caesar-meta [amd64] (focal-proposed/none) [20.04~ubuntu1] (canonical-oem-metapackages) [08:19] -queuebot:#ubuntu-release- New: accepted oem-somerville-weedle-meta [sync] (focal-proposed) [20.04~ubuntu1] [08:21] -queuebot:#ubuntu-release- New binary: oem-somerville-weedle-meta [amd64] (focal-proposed/universe) [20.04~ubuntu1] (canonical-oem-metapackages) [08:23] please allow libxcvt on i386, it's blocking xorg-server [08:25] -queuebot:#ubuntu-release- New: accepted oem-somerville-cubone-rkl-meta [sync] (focal-proposed) [20.04~ubuntu1] [08:27] -queuebot:#ubuntu-release- New binary: oem-somerville-cubone-rkl-meta [amd64] (focal-proposed/none) [20.04~ubuntu1] (canonical-oem-metapackages) [08:32] -queuebot:#ubuntu-release- New: accepted oem-somerville-beric-amd-meta [sync] (focal-proposed) [20.04~ubuntu1] [08:34] -queuebot:#ubuntu-release- New binary: oem-somerville-beric-amd-meta [amd64] (focal-proposed/none) [20.04~ubuntu1] (canonical-oem-metapackages) [08:58] mwhudson, vorlon, the adsys release remove is a bit rude, could you at least talk to us about finding solution before removing a package that we own? [08:59] seb128: we'll put it back as soon as the python transition is done, which was hoped to be several hours ago [09:01] mwhudson, I don't understand why that was even needed, the bug mention autopkgtest failures, can't we just hint ignore those? [09:01] mwhudson, https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#source-highlight still blocks python [09:02] ricotz: we need an aa [09:02] hello seb128 mwhudson [09:02] seb128: could you move source-highlight in jammy-proposed to universe? [09:03] (it's on https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.html) [09:04] mwhudson, https://launchpad.net/ubuntu/+source/source-highlight suggests it's already in universe, also that source was in main in impish so probably is needed there? [09:04] seb128: it used to be a dependency of gdb but isn't any longer [09:04] so i think demotion is appropriate [09:05] or its deps need to be promoted again but the current situation is wrong [09:14] mwhudson, demoted [09:14] seb128: thank you [09:32] mwhudson: hmm, why did gdb drop source-highlight? [09:32] doko: i certainly have no idea [10:23] -queuebot:#ubuntu-release- New binary: ceph [amd64] (jammy-proposed/main) [17.1.0-0ubuntu1] (ubuntu-server) [10:54] the just uploaded ceph seems to have blocked python3-defaults migration? ^^ [10:58] -queuebot:#ubuntu-release- Unapproved: gst-plugins-base1.0 (focal-proposed/main) [1.16.2-4ubuntu0.1 => 1.16.3-0ubuntu1] (desktop-core, i386-whitelist, ubuntu-server) [10:59] so close :( [11:03] -queuebot:#ubuntu-release- New: accepted oem-somerville-drogo-meta [sync] (focal-proposed) [20.04~ubuntu1] [11:04] -queuebot:#ubuntu-release- New binary: oem-somerville-drogo-meta [amd64] (focal-proposed/none) [20.04~ubuntu1] (canonical-oem-metapackages) [11:05] -queuebot:#ubuntu-release- New: accepted oem-somerville-beric-amd-meta [amd64] (focal-proposed) [20.04~ubuntu1] [11:05] -queuebot:#ubuntu-release- New: accepted oem-somerville-drogo-meta [amd64] (focal-proposed) [20.04~ubuntu1] [11:05] -queuebot:#ubuntu-release- New: accepted oem-sutton.newell-caesar-meta [amd64] (focal-proposed) [20.04~ubuntu1] [11:05] -queuebot:#ubuntu-release- New: accepted oem-somerville-cubone-rkl-meta [amd64] (focal-proposed) [20.04~ubuntu1] [11:05] -queuebot:#ubuntu-release- New: accepted oem-somerville-weedle-meta [amd64] (focal-proposed) [20.04~ubuntu1] [11:09] -queuebot:#ubuntu-release- New: accepted ceph [amd64] (jammy-proposed) [17.1.0-0ubuntu1] [11:09] -queuebot:#ubuntu-release- New: accepted onetbb [sync] (jammy-proposed) [2021.5.0-7] [11:17] -queuebot:#ubuntu-release- Unapproved: gst-plugins-good1.0 (focal-proposed/main) [1.16.2-1ubuntu2.1 => 1.16.3-0ubuntu1] (desktop-core, i386-whitelist, ubuntu-server) [11:30] -queuebot:#ubuntu-release- New binary: onetbb [amd64] (jammy-proposed/universe) [2021.5.0-7] (no packageset) [11:31] -queuebot:#ubuntu-release- New: accepted onetbb [amd64] (jammy-proposed) [2021.5.0-7] [12:24] what's the eta on python3-defaults migrating, does anybody know? [12:24] I think this is the longest python migration I have ever seen [12:28] still faster than ruby-defaults ;p v*rlon was working on that, but it's now delayed by a new ceph upload [12:29] oh yeah, ruby is the champion [12:30] I fear the upcoming bug reports, when these packages finally hit the release pocket [12:30] brace for impact [12:32] why is adsys still in excuses, since it hit the release pocket yesterday? https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#adsys [12:32] and with no "prior version" listed [12:33] I guess many things beyond my understanding are entangled right now :) [12:34] oh, it moved back to proposed overnight [12:39] just a reminder :) - please allow libxcvt on i386, it's blocking xorg-server [12:47] ahasenack: previous ceth upload took 36 hrs to build on riscv64, so I wouldn't bet on any time soon if that stays in proposed [12:48] ricotz, tjaalton: libxcvt handled [12:58] seb128, great, thanks [13:00] ginggs: it looks like there was some progress on onetbb, have you been keeping tabs on it? [13:03] thanks! [13:06] -queuebot:#ubuntu-release- Packageset: Removed libnfsidmap from i386-whitelist in jammy [13:06] -queuebot:#ubuntu-release- Packageset: Added fonts-nanum to i386-whitelist in jammy [13:06] -queuebot:#ubuntu-release- Packageset: Added fonts-open-sans to i386-whitelist in jammy [13:06] -queuebot:#ubuntu-release- Packageset: Added gi-docgen to i386-whitelist in jammy [13:06] -queuebot:#ubuntu-release- Packageset: Added highlight.js to i386-whitelist in jammy [13:06] -queuebot:#ubuntu-release- Packageset: Added libxcvt to i386-whitelist in jammy === seb129 is now known as seb128 [13:17] coreycb: there was an update to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000336#101 a week ago [13:17] Debian bug 1000336 in src:numba "numba: FTBFS with Python 3.10" [Serious, Open] [13:19] I think there about 8 build failures in onetbb's reverse-build-dependencies [13:19] RikMills: I thought riscv64 was risc-free [13:20] i.e., wouldn't block anything [13:21] ahasenack: I think that is still the case for autopkgtests and build time tests, but not for missing builds [13:21] but I could be mistaken [13:22] can't wait for the rush to fix bugs once these transitions land [13:22] that will be the real ff date in practice [13:23] ahasenack: https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#netdata [13:23] example on something blocked on riscv64 [13:23] *of something [13:55] ginggs: seems to be progressing, thanks [13:56] ceph is a new upstream version after Feature Freeze? [13:57] bdmurray, the proposed version was already a git snapshot [13:57] which was uploaded before feature freeze [13:58] seb128: ah okay, I didn't look at the full publishing history [14:08] * ahasenack used the same trick with freeradius [14:09] I'm using a git snapshot of 3.0.26 [14:22] tjaalton, you can retry it now https://launchpad.net/ubuntu/+source/xorg-server/2:21.1.3-2ubuntu1/+build/23194148 [14:24] already tried once [14:25] tjaalton, but you didn't wait for the i386 build to be published ;) [14:28] right [14:28] looks good now [14:29] tjaalton, despite the build failure [15:06] jamespage: I'm backing ceph out of -proposed; this resets the entire python+perl+ocaml transition to have it there right now, and it takes days to build on riscv64. We can copy it back when the transition is done [15:41] -queuebot:#ubuntu-release- Unapproved: horizon (impish-proposed/main) [4:20.1.0-0ubuntu1 => 4:20.1.1-0ubuntu1] (openstack) [15:42] ginggs: onetbb built just fine (sans riscv64), and I've got numba test-building in my PPA wth proposed enabled. [15:48] vorlon: apologies and +1 [15:53] -queuebot:#ubuntu-release- Unapproved: heat (impish-proposed/main) [1:17.0.0-0ubuntu1 => 1:17.0.1-0ubuntu1] (openstack) [16:18] -queuebot:#ubuntu-release- Unapproved: gstreamer1.0 (focal-proposed/main) [1.16.2-2 => 1.16.3-0ubuntu1] (core, i386-whitelist) [16:36] -queuebot:#ubuntu-release- Unapproved: ceilometer (impish-proposed/main) [2:17.0.0-0ubuntu1 => 2:17.0.1-0ubuntu1] (openstack) [16:57] -queuebot:#ubuntu-release- Unapproved: cockpit (impish-backports/universe) [261-1~bpo21.10.1 => 264-1~bpo21.10.1] (no packageset) [16:58] -queuebot:#ubuntu-release- Unapproved: cockpit (focal-backports/universe) [261-1~bpo20.04.1 => 264-1~bpo20.04.1] (no packageset) [16:58] -queuebot:#ubuntu-release- Unapproved: cockpit-machines (impish-backports/universe) [260-1~bpo21.10.1 => 262-1~bpo21.10.1] (no packageset) [16:58] -queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (focal-backports) [264-1~bpo20.04.1] [16:58] -queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (impish-backports) [264-1~bpo21.10.1] [16:58] -queuebot:#ubuntu-release- Unapproved: accepted cockpit-machines [source] (impish-backports) [262-1~bpo21.10.1] [16:59] bdmurray: not sure if there is time in SRU vanguard today or not. cloud-init has a queued for -proposed (22.1-14-g2e17a0d6) that we'd like to request review for upload into (bionic|focal|impish)-proposed per https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1961446 [16:59] Launchpad bug 1961446 in cloud-init (Ubuntu Impish) "sru cloud-init (22.1 update) Bionic, Focal, Impish" [Undecided, New] [17:00] I'd also like to reject all 21.1.1 from bionic/focal/impish -proposed queues [17:02] -queuebot:#ubuntu-release- New binary: cockpit [amd64] (focal-backports/universe) [264-1~bpo20.04.1] (no packageset) [17:03] -queuebot:#ubuntu-release- New binary: cockpit [amd64] (impish-backports/universe) [264-1~bpo21.10.1] (no packageset) [17:58] -queuebot:#ubuntu-release- New: accepted cockpit [amd64] (focal-backports) [264-1~bpo20.04.1] [17:58] -queuebot:#ubuntu-release- New: accepted cockpit [amd64] (impish-backports) [264-1~bpo21.10.1] [18:22] -queuebot:#ubuntu-release- New binary: vkd3d [amd64] (jammy-proposed/universe) [1.2-11] (i386-whitelist) [18:22] -queuebot:#ubuntu-release- New binary: vkd3d [i386] (jammy-proposed/universe) [1.2-11] (i386-whitelist) [18:57] argh what somehow now the capnproto build on ppc64el is the blocker [18:59] mwhudson: numba is looking good with onetbb, it's just running dh_auto_tests now. [19:45] kj/string-test.c++:38: failed: expected ("-128 -32768 -2147483648 -9223372036854775808") == (str((signed char)-128, ' ', (signed short)-32768, ' ', ((int)-2147483647) - 1, ' ', ((long long)-9223372036854775807ll) - 1)); -128 -32768 -2147483648 -9223372036854775808; str((signed char)-128, ' ', (signed short)-32768, ' ', ((int)-2147483647) - 1, ' ', ((long long)-9223372036854775807ll) - 1) = -128 -32768 -214748364( -9223372036854775808 [19:45] stack: 8fd0a7d0c7b 8fd0a3980d7 71bf21d168b3 71bf21c8058f 71bf21d149e3 71bf21d1661f 71bf21caf643 71bf21cc1a83 71bf21c8058f 71bf21cb568b 71bf21d1314f 71bf216917a3 71bf21691987 [19:45] thanks? [19:46] huh seems to be -2147483648 vs -214748364( [19:47] that's a single bit of difference... === mfo_ is now known as mfo === haggertk_ is now known as haggertk [21:15] argh i think i may have rediscovered this https://github.com/capnproto/capnproto/commit/f94b8b1e866c2f13d646313169e3b2d3dd339b2f#diff-1efa83f8f954ff35477e3a52422534daa6b886fc93af810a4c8ea209ffafe236 [21:15] Commit f94b8b1 in capnproto/capnproto "Fix UBSAN errors." [21:54] yes seems so [22:33] -queuebot:#ubuntu-release- New source: numba (jammy-proposed/primary) [0.55.1-0ubuntu1] [22:34] ubuntu-archive: ^ That's the numba package I've been working on that should help with the python3-defaults migration, and everything else stuck in jammy-proposed waiting for it. [22:34] The packaging is nearly identical to what was in the previous version sync'd from Debian. [22:35] * RAOF has a look. [22:37] Has pull-lp-source got out of sync with launchpad's API? [22:38] RAOF: Not sure, but that might not have been a question for me. [22:38] numba was removed from jammy because it FTBFS due to Python 3.10. This version is 3.10-compatible. [22:38] Ah, no. I think it's transient launchpad weirdness. [22:38] Oh, gotcha. [22:40] RAOF, Eickmeyer: i don't think numba is anything to do with the current non-migration of python [22:40] so it's good to get this done but lets leave it in NEW for a bit please? [22:40] mwhudson: vorlon said it was a good idea. [22:40] At least, couldn't hurt. [22:40] hmm maybe it can't hurt [22:41] just feeling a bit paranoid around britney behaviour [22:42] Britney has some implicit dependency circles going on, so I get it 100%. [22:42] I can easily do the source review and then leave it in binary NEW if you like. [22:42] britney was whining yesterday about numba being missing. [22:44] But yes, mwhudson, I see your capnproto issues. [22:44] (It will go through binary NEW, right? Even though those binaries previously existed?) [22:44] It should, RAOF. [22:45] Eickmeyer: That's totally my expectation, but I've been surprised by LP behaviour in the past! [22:45] RAOF: Especially lately. :) [22:46] RAOF: I test built against all archs except riscv64 in my PPA, built against everything in proposed. === paride1 is now known as paride === falcojr9 is now known as falcojr [22:58] come on britney, do your thing [22:59] mwhudson: I feel that statement in my soul right now. [23:22] Eickmeyer: I know that you've taken the packaging from the previous Debian sync, but the debian/copyright fails to list most of the licenses involved. 🤦‍♀️ [23:24] RAOF: I blame the scientific team for failing to keep that updated then. The only whine I got from lintian was a couple of files that no longer existed. [23:24] Yeah, none of the files have copyright headers. [23:25] I didn't do a licensecheck because I assumed they kept it correct. [23:25] As far as the lack of copyright headers, doesn't it then go under the Files: * copyright? [23:25] But LICENSES.third-party lists code with MIT, BSD-3, PSF… [23:26] * Eickmeyer isn't at his main computer right now [23:27] Rather than have copyright headers, they've included relevant github URLs in the headers and then specified the corresponding licenses in LICENSES.third-party. [23:27] Salsa being down made this a lot more difficult than it should've been. [23:27] 👍️ [23:46] -queuebot:#ubuntu-release- New: rejected numba [source] (jammy-proposed) [0.55.1-0ubuntu1]