[00:00] -queuebot:#ubuntu-release- New binary: rust-aliasable [riscv64] (jammy-proposed/universe) [0.1.3-1] (no packageset)
[00:02] -queuebot:#ubuntu-release- New binary: rust-compare [riscv64] (jammy-proposed/universe) [0.1.0-1] (no packageset)
[00:03] -queuebot:#ubuntu-release- New binary: rust-exitfailure [riscv64] (jammy-proposed/universe) [0.5.1-1] (no packageset)
[00:03] -queuebot:#ubuntu-release- New binary: rust-gcd [riscv64] (jammy-proposed/universe) [2.0.2-1] (no packageset)
[00:04] -queuebot:#ubuntu-release- New binary: rust-minimal-lexical [riscv64] (jammy-proposed/universe) [0.2.1-1] (no packageset)
[00:05] -queuebot:#ubuntu-release- New binary: rust-inflector [riscv64] (jammy-proposed/universe) [0.11.4-1] (no packageset)
[00:05] -queuebot:#ubuntu-release- New binary: rust-os-display [riscv64] (jammy-proposed/universe) [0.1.3-1] (no packageset)
[00:07] -queuebot:#ubuntu-release- New binary: rust-gdk4-sys [riscv64] (jammy-proposed/universe) [0.3.1-1] (no packageset)
[00:11] -queuebot:#ubuntu-release- New binary: rust-z85 [riscv64] (jammy-proposed/universe) [3.0.4-1] (no packageset)
[00:12] -queuebot:#ubuntu-release- New binary: rust-utf8-width [riscv64] (jammy-proposed/universe) [0.1.5-1] (no packageset)
[00:12] -queuebot:#ubuntu-release- New: accepted rust-utf8-width [riscv64] (jammy-proposed) [0.1.5-1]
[00:13] -queuebot:#ubuntu-release- New: accepted rust-gdk4-sys [riscv64] (jammy-proposed) [0.3.1-1]
[00:13] -queuebot:#ubuntu-release- New: accepted rust-minimal-lexical [riscv64] (jammy-proposed) [0.2.1-1]
[00:13] -queuebot:#ubuntu-release- New: accepted rust-z85 [riscv64] (jammy-proposed) [3.0.4-1]
[00:13] -queuebot:#ubuntu-release- New: accepted rust-inflector [riscv64] (jammy-proposed) [0.11.4-1]
[00:13] -queuebot:#ubuntu-release- New binary: rust-tree-sitter-config [riscv64] (jammy-proposed/universe) [0.19.0-1] (no packageset)
[00:13] -queuebot:#ubuntu-release- New: accepted rust-os-display [riscv64] (jammy-proposed) [0.1.3-1]
[00:13] -queuebot:#ubuntu-release- New: accepted rust-aliasable [riscv64] (jammy-proposed) [0.1.3-1]
[00:13] -queuebot:#ubuntu-release- New: accepted rust-exitfailure [riscv64] (jammy-proposed) [0.5.1-1]
[00:13] -queuebot:#ubuntu-release- New: accepted rust-compare [riscv64] (jammy-proposed) [0.1.0-1]
[00:13] -queuebot:#ubuntu-release- New: accepted rust-gcd [riscv64] (jammy-proposed) [2.0.2-1]
[00:35] <vorlon> bryceh: I don't follow what you mean by uwsgi-plugin-php not being a proper package; what's improper about it?
[00:40] <vorlon> oh great, android-platform-tools, a completely new source package that a) ftbfs with LTO and b) ftbfs with glibc 2.34+
[01:08] <bryceh> vorlon, the uwsgi-plugin-php source package is empty except for a debian/ dir, so it has to be generated in conjunction with uwsgi in some fashion.  Perhaps it is more obvious to you what needs done to get it resolved.
[01:20] <vorlon> bryceh: um oh eew
[01:21] <vorlon> bryceh: why the heck didn't they just do this from the same source package then
[01:21] <vorlon> bryceh: anyway I'm perfectly fine with removing this if you want
[01:21] <vorlon> just give me a bug w/ ubuntu-archive subscribed
[05:17] -queuebot:#ubuntu-release- New binary: ffms2 [amd64] (jammy-proposed/universe) [2.40+git20211209-2] (i386-whitelist, ubuntustudio)
[05:17] -queuebot:#ubuntu-release- New binary: ffms2 [i386] (jammy-proposed/universe) [2.40+git20211209-2] (i386-whitelist, ubuntustudio)
[05:19] -queuebot:#ubuntu-release- New binary: ffms2 [armhf] (jammy-proposed/universe) [2.40+git20211209-2] (i386-whitelist, ubuntustudio)
[05:34] -queuebot:#ubuntu-release- New binary: ffms2 [s390x] (jammy-proposed/universe) [2.40+git20211209-2] (i386-whitelist, ubuntustudio)
[05:35] -queuebot:#ubuntu-release- New binary: ffms2 [ppc64el] (jammy-proposed/universe) [2.40+git20211209-2] (i386-whitelist, ubuntustudio)
[05:47] -queuebot:#ubuntu-release- New binary: ffms2 [riscv64] (jammy-proposed/universe) [2.40+git20211209-2] (i386-whitelist, ubuntustudio)
[09:57] -queuebot:#ubuntu-release- Unapproved: fwupd-signed (impish-proposed/main) [1.40 => 1.42~ubuntu21.10.1] (core)
[09:59] -queuebot:#ubuntu-release- Unapproved: fwupd-signed (focal-proposed/main) [1.27.1ubuntu5 => 1.27.1ubuntu6] (core)
[10:46] <tjaalton> sil2100: I noticed there's no oem kernel on the focal daily image, though I'm not sure if there even should be anymore..
[11:27] <juliank> Removed all i386 tests and only requeued the ones that are not "always failed" to help catch up a bit
[11:28] <juliank> Perl transition huge, and 3/4 of the tests do not influence the migration at all
[11:28] <juliank> like 3000 out of 4000
[11:31] <juliank> maybe I should have cancelled them fully and only restart them after amd64 is done
[11:36] <juliank> I'm occasionally filtering duplicate requests from the queues too
[11:58] -queuebot:#ubuntu-release- Unapproved: fwupd-signed (focal-proposed/main) [1.27.1ubuntu5 => 1.27.1ubuntu6] (core)
[11:58] -queuebot:#ubuntu-release- Unapproved: fwupd-signed (impish-proposed/main) [1.40 => 1.42~ubuntu21.10.1] (core)
[12:06] -queuebot:#ubuntu-release- New source: adsys (focal-proposed/primary) [0.8+22.04]
[12:10] -queuebot:#ubuntu-release- New: rejected adsys [source] (focal-proposed) [0.8+22.04]
[12:12] -queuebot:#ubuntu-release- New source: adsys (focal-proposed/primary) [0.8~22.04]
[12:32] -queuebot:#ubuntu-release- Unapproved: rejected fwupd-signed [source] (impish-proposed) [1.42~ubuntu21.10.1]
[12:33] -queuebot:#ubuntu-release- Unapproved: rejected fwupd-signed [source] (focal-proposed) [1.27.1ubuntu6]
[12:57] -queuebot:#ubuntu-release- Unapproved: virtualbox-ext-pack (focal-proposed/multiverse) [6.1.26-2~ubuntu<IP_ADDRESS> => 6.1.32-1~ubuntu<IP_ADDRESS>] (no packageset)
[12:57] -queuebot:#ubuntu-release- Unapproved: virtualbox-hwe (focal-proposed/multiverse) [6.1.26-dfsg-3~ubuntu<IP_ADDRESS> => 6.1.32-dfsg-2~ubuntu<IP_ADDRESS>] (kernel-dkms)
[12:57] <LocutusOfBorg> arighi, ^^
[12:58] -queuebot:#ubuntu-release- Unapproved: virtualbox (focal-proposed/multiverse) [6.1.26-dfsg-3~ubuntu<IP_ADDRESS> => 6.1.32-dfsg-1~ubuntu<IP_ADDRESS>] (kernel-dkms, ubuntu-cloud)
[12:59] -queuebot:#ubuntu-release- Unapproved: virtualbox-guest-additions-iso (focal-proposed/multiverse) [6.1.26-1~ubuntu<IP_ADDRESS> => 6.1.32-1~ubuntu<IP_ADDRESS>] (no packageset)
[13:01] -queuebot:#ubuntu-release- Unapproved: virtualbox-ext-pack (impish-proposed/multiverse) [6.1.26-2 => 6.1.32-1~ubuntu<IP_ADDRESS>] (no packageset)
[13:01] -queuebot:#ubuntu-release- Unapproved: virtualbox-guest-additions-iso (impish-proposed/multiverse) [6.1.26-1 => 6.1.32-1~ubuntu<IP_ADDRESS>] (no packageset)
[13:02] -queuebot:#ubuntu-release- Unapproved: virtualbox (impish-proposed/multiverse) [6.1.26-dfsg-4 => 6.1.32-dfsg-1~ubuntu<IP_ADDRESS>] (kernel-dkms, ubuntu-cloud)
[13:04] -queuebot:#ubuntu-release- Unapproved: virtualbox-hwe (impish-proposed/multiverse) [6.1.26-dfsg-4ubuntu<IP_ADDRESS> => 6.1.32-dfsg-2~ubuntu<IP_ADDRESS>] (kernel-dkms)
[13:28] -queuebot:#ubuntu-release- New source: fwupd-efi (focal-proposed/primary) [1:1.2-2~20.04.1]
[13:28] -queuebot:#ubuntu-release- New source: fwupd-efi (impish-proposed/primary) [1:1.2-2~21.10.1]
[13:28] -queuebot:#ubuntu-release- Unapproved: accepted inkscape [source] (focal-backports) [1.1.1-3ubuntu1~bpo20.04.1]
[14:31] <tjaalton> sil2100: mesa/libdrm are good, updating the bug
[14:32] <tjaalton> LocutusOfBorg: when can we expect to see llvm-13 migrate to jammy? :)
[14:38] <tjaalton> sil2100: one issue with mesa is that jammy still has 21.2.2, all newer uploads ended up being stuck in proposed for whatever the reason
[14:39] <tjaalton> sil2100: so if it would make you more happy, I could upload mesa which reverts back to llvm-12 again
[14:39] <tjaalton> that should be able to migrate
[14:39] <tjaalton> within days
[14:52] -queuebot:#ubuntu-release- New: rejected fwupd-efi [source] (impish-proposed) [1:1.1-3~21.10.1]
[14:54] -queuebot:#ubuntu-release- New: rejected fwupd-efi [source] (focal-proposed) [1:1.1-3~20.04.1]
[14:59] -queuebot:#ubuntu-release- New: accepted fwupd-efi [source] (impish-proposed) [1:1.2-2~21.10.1]
[15:01] -queuebot:#ubuntu-release- New binary: fwupd-efi [amd64] (impish-proposed/none) [1:1.2-2~21.10.1] (no packageset)
[15:06] -queuebot:#ubuntu-release- New binary: fwupd-efi [arm64] (impish-proposed/none) [1:1.2-2~21.10.1] (no packageset)
[15:06] -queuebot:#ubuntu-release- New binary: fwupd-efi [armhf] (impish-proposed/none) [1:1.2-2~21.10.1] (no packageset)
[15:07] -queuebot:#ubuntu-release- New: rejected fwupd-efi [source] (focal-proposed) [1:1.2-2~20.04.1]
[15:08] -queuebot:#ubuntu-release- New source: fwupd-efi (focal-proposed/primary) [1:1.2-2~20.04.1]
[15:11] -queuebot:#ubuntu-release- New: accepted fwupd-efi [source] (focal-proposed) [1:1.2-2~20.04.1]
[15:14] -queuebot:#ubuntu-release- New binary: fwupd-efi [amd64] (focal-proposed/none) [1:1.2-2~20.04.1] (no packageset)
[15:17] -queuebot:#ubuntu-release- New: accepted fwupd-efi [amd64] (impish-proposed) [1:1.2-2~21.10.1]
[15:17] -queuebot:#ubuntu-release- New: accepted fwupd-efi [armhf] (impish-proposed) [1:1.2-2~21.10.1]
[15:17] -queuebot:#ubuntu-release- New: accepted fwupd-efi [arm64] (impish-proposed) [1:1.2-2~21.10.1]
[15:17] -queuebot:#ubuntu-release- New binary: fwupd-efi [arm64] (focal-proposed/universe) [1:1.2-2~20.04.1] (no packageset)
[15:18] -queuebot:#ubuntu-release- New binary: fwupd-efi [armhf] (focal-proposed/universe) [1:1.2-2~20.04.1] (no packageset)
[15:18] -queuebot:#ubuntu-release- New: accepted fwupd-efi [amd64] (focal-proposed) [1:1.2-2~20.04.1]
[15:18] -queuebot:#ubuntu-release- New: accepted fwupd-efi [armhf] (focal-proposed) [1:1.2-2~20.04.1]
[15:18] -queuebot:#ubuntu-release- New: accepted fwupd-efi [arm64] (focal-proposed) [1:1.2-2~20.04.1]
[15:22] <sil2100> tjaalton: \o/ I mean hm, do you think the -proposed mesa's in jammy will migrate before FF?
[15:23] <sil2100> Since I think as long as we are 110% sure that we will have those mesa version migrated before release (best before FF), I think this shouldn't be a blocker
[15:24] <tjaalton> sil2100: ah ok, well I'm targeting 22.0.x for jammy
[15:25] <tjaalton> still in rc
[15:42] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [source] (impish-proposed) [1.7.3-1~21.10.1]
[15:47] -queuebot:#ubuntu-release- New binary: fwupd [ppc64el] (impish-proposed/main) [1.7.3-1~21.10.1] (core)
[15:53] -queuebot:#ubuntu-release- Unapproved: fwupd (impish-proposed/main) [1.5.11-0ubuntu2 => 1.7.4-1~21.10.1] (core)
[15:57] -queuebot:#ubuntu-release- New binary: fwupd [s390x] (impish-proposed/main) [1.7.3-1~21.10.1] (core)
[16:13] -queuebot:#ubuntu-release- Unapproved: fwupd (impish-proposed/main) [1.7.3-1~21.10.1 => 1.7.4-1~21.10.1] (core)
[16:16] -queuebot:#ubuntu-release- Unapproved: rejected fwupd [source] (impish-proposed) [1.7.4-1~21.10.1]
[16:17] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [source] (impish-proposed) [1.7.4-1~21.10.1]
[16:21] -queuebot:#ubuntu-release- New binary: fwupd [ppc64el] (impish-proposed/main) [1.7.4-1~21.10.1] (core)
[16:21] -queuebot:#ubuntu-release- New binary: fwupd [s390x] (impish-proposed/main) [1.7.4-1~21.10.1] (core)
[16:23] -queuebot:#ubuntu-release- Unapproved: fwupd (focal-proposed/main) [1.5.11-0ubuntu1~20.04.2 => 1.7.4-1~20.04.1] (core)
[16:24] -queuebot:#ubuntu-release- Unapproved: rejected fwupd [source] (focal-proposed) [1.7.4-1~20.04.1]
[16:28] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [source] (focal-proposed) [1.7.4-1~20.04.1]
[16:30] -queuebot:#ubuntu-release- Unapproved: accepted python-apt [source] (focal-proposed) [2.0.0ubuntu<IP_ADDRESS>]
[16:33] -queuebot:#ubuntu-release- New binary: fwupd [amd64] (impish-proposed/main) [1.7.4-1~21.10.1] (core)
[16:33] -queuebot:#ubuntu-release- New binary: fwupd [armhf] (impish-proposed/main) [1.7.4-1~21.10.1] (core)
[16:34] -queuebot:#ubuntu-release- New binary: fwupd [arm64] (impish-proposed/main) [1.7.4-1~21.10.1] (core)
[16:36] -queuebot:#ubuntu-release- Unapproved: accepted fwupd-signed [source] (impish-proposed) [1.42~ubuntu21.10.1]
[16:37] -queuebot:#ubuntu-release- New binary: fwupd [ppc64el] (focal-proposed/main) [1.7.4-1~20.04.1] (core)
[16:37] -queuebot:#ubuntu-release- New binary: fwupd [s390x] (focal-proposed/main) [1.7.4-1~20.04.1] (core)
[16:38] -queuebot:#ubuntu-release- Unapproved: accepted fwupd-signed [source] (focal-proposed) [1.27.1ubuntu6]
[16:40] -queuebot:#ubuntu-release- New binary: fwupd [amd64] (focal-proposed/main) [1.7.4-1~20.04.1] (core)
[16:43] -queuebot:#ubuntu-release- New binary: fwupd [arm64] (focal-proposed/main) [1.7.4-1~20.04.1] (core)
[16:43] -queuebot:#ubuntu-release- New binary: fwupd [armhf] (focal-proposed/main) [1.7.4-1~20.04.1] (core)
[16:46] -queuebot:#ubuntu-release- New binary: abseil [amd64] (jammy-proposed/main) [0~20210324.2-2] (i386-whitelist, ubuntu-desktop)
[16:47] -queuebot:#ubuntu-release- New: accepted adsys [source] (focal-proposed) [0.8~22.04]
[16:47] -queuebot:#ubuntu-release- New binary: abseil [s390x] (jammy-proposed/main) [0~20210324.2-2] (i386-whitelist, ubuntu-desktop)
[16:48] -queuebot:#ubuntu-release- New binary: abseil [i386] (jammy-proposed/main) [0~20210324.2-2] (i386-whitelist, ubuntu-desktop)
[16:49] -queuebot:#ubuntu-release- New: accepted fwupd [amd64] (focal-proposed) [1.7.4-1~20.04.1]
[16:49] -queuebot:#ubuntu-release- New: accepted fwupd [armhf] (focal-proposed) [1.7.4-1~20.04.1]
[16:49] -queuebot:#ubuntu-release- New: accepted fwupd [s390x] (focal-proposed) [1.7.4-1~20.04.1]
[16:49] -queuebot:#ubuntu-release- New: accepted fwupd [arm64] (focal-proposed) [1.7.4-1~20.04.1]
[16:49] -queuebot:#ubuntu-release- New: accepted fwupd [ppc64el] (focal-proposed) [1.7.4-1~20.04.1]
[16:49] -queuebot:#ubuntu-release- New: accepted fwupd [ppc64el] (impish-proposed) [1.7.3-1~21.10.1]
[16:49] -queuebot:#ubuntu-release- New: accepted fwupd [amd64] (impish-proposed) [1.7.4-1~21.10.1]
[16:49] -queuebot:#ubuntu-release- New: accepted fwupd [armhf] (impish-proposed) [1.7.4-1~21.10.1]
[16:49] -queuebot:#ubuntu-release- New: accepted fwupd [s390x] (impish-proposed) [1.7.4-1~21.10.1]
[16:49] -queuebot:#ubuntu-release- New: accepted fwupd [s390x] (impish-proposed) [1.7.3-1~21.10.1]
[16:49] -queuebot:#ubuntu-release- New: accepted fwupd [ppc64el] (impish-proposed) [1.7.4-1~21.10.1]
[16:49] -queuebot:#ubuntu-release- New: accepted fwupd [arm64] (impish-proposed) [1.7.4-1~21.10.1]
[16:52] -queuebot:#ubuntu-release- New binary: adsys [amd64] (focal-proposed/none) [0.8~22.04] (no packageset)
[16:52] <LocutusOfBorg> vorlon, hello, please process LP: #1959182 ?
[16:52] -queuebot:#ubuntu-release- New binary: abseil [ppc64el] (jammy-proposed/main) [0~20210324.2-2] (i386-whitelist, ubuntu-desktop)
[16:53] <ahasenack> libcxl
[16:54] -queuebot:#ubuntu-release- New: accepted adsys [amd64] (focal-proposed) [0.8~22.04]
[16:54] -queuebot:#ubuntu-release- New binary: adsys [s390x] (focal-proposed/none) [0.8~22.04] (no packageset)
[16:54] -queuebot:#ubuntu-release- New binary: adsys [ppc64el] (focal-proposed/none) [0.8~22.04] (no packageset)
[16:56] -queuebot:#ubuntu-release- New binary: adsys [arm64] (focal-proposed/none) [0.8~22.04] (no packageset)
[16:59] -queuebot:#ubuntu-release- New: accepted adsys [arm64] (focal-proposed) [0.8~22.04]
[16:59] -queuebot:#ubuntu-release- New: accepted adsys [s390x] (focal-proposed) [0.8~22.04]
[16:59] -queuebot:#ubuntu-release- New: accepted adsys [ppc64el] (focal-proposed) [0.8~22.04]
[17:03] -queuebot:#ubuntu-release- Unapproved: systemd (impish-proposed/main) [248.3-1ubuntu8.2 => 248.3-1ubuntu8.3] (core, i386-whitelist)
[17:21] -queuebot:#ubuntu-release- New binary: abseil [arm64] (jammy-proposed/main) [0~20210324.2-2] (i386-whitelist, ubuntu-desktop)
[17:21] -queuebot:#ubuntu-release- New binary: abseil [armhf] (jammy-proposed/main) [0~20210324.2-2] (i386-whitelist, ubuntu-desktop)
[17:46] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (focal-proposed/main) [1:20.04.36 => 1:20.04.37] (core)
[18:26] <vorlon> bryceh: great, so I synced php-pecl-http, and the new version, which has a version number of 4.2.1+php8-2, has gotten a dependency on the nonexistent php7.4-http
[18:27] <bdmurray> 8-2 is 6?
[18:45] <bryceh> vorlon, fun times.  I have seen that sometimes Debian sets packages back intentionally because they haven't defaulted to 8.1 yet
[18:45] <bryceh> the pecl stuff is a bit thorny in general
[18:48] <bryceh> hmm, looking at it, php-pecl-http has indeed been targeted to 8.1, and I don't see a direct b-d on anything 7.4-ish
[18:51] <bryceh>  php-http : Depends: php7.4-http but it is not installable
[19:17] -queuebot:#ubuntu-release- Unapproved: rsync (bionic-proposed/main) [3.1.2-2.1ubuntu1.2 => 3.1.2-2.1ubuntu1.3] (core)
[19:19] -queuebot:#ubuntu-release- Unapproved: rsync (focal-proposed/main) [3.1.3-8ubuntu0.1 => 3.1.3-8ubuntu0.2] (core, i386-whitelist)
[19:29] -queuebot:#ubuntu-release- New binary: abseil [riscv64] (jammy-proposed/main) [0~20210324.2-2] (i386-whitelist, ubuntu-desktop)
[19:42] <vorlon> bryceh: debian/rules has a hard-coded reference to 7.4 :P
[19:42] <vorlon> php-pecl-http seems to have no reverse-dependencies
[19:42] <vorlon> seems like I should just axe it for now
[19:55] <bryceh> vorlon, aha you're right:  PHP_DEFAULT_VERSION_OVERRIDE := 7.4
[19:58] <bryceh> I can upload a fix for that and let debian know of the error
[20:04] <vorlon> bryceh: ok
[20:04] <bryceh> thx, uploaded
[20:07] <bdmurray> vorlon: I uploaded a build3 of minimap2 but it was rejected because https://launchpad.net/ubuntu/+source/minimap2/2.17+dfsg-12build3 it already existed. Would just trying to rebuild it work out? (provided it builds ;-)
[20:09] <vorlon> bdmurray: well you would need to resurrect that source version into -proposed first since it was superseded
[20:09] <vorlon> you should be able to do the copy-package, or I can if you prefer
[20:10] <bdmurray> If you could that would be great
[20:10] <vorlon> copy-package -e 2.17+dfsg-12build3 -s jammy-proposed --to-suite jammy-proposed --force-same-destination --auto-approve minimap2 -y
[20:11] <vorlon> bdmurray: you should be able to retry the builds now I think
[20:12] <bdmurray> thanks
[20:22] <vorlon> bdmurray: which you'll do for all archs, right? :)
[20:27] <vorlon> bdmurray: ok it bothered me having those not retried, I've retried the other archs now
[20:28] -queuebot:#ubuntu-release- Unapproved: keepalived (focal-proposed/main) [1:2.0.19-2ubuntu0.1 => 1:2.0.19-2ubuntu0.2] (ubuntu-server)
[20:48] <Eickmeyer> ubuntu-archive: Looking for a review for phinger-cursor-theme soon if possible (should be easy), and bismuth if anyone gets a chance.
[20:49] <bdmurray> vorlon: I was getting to it!
[20:51] -queuebot:#ubuntu-release- New: accepted abseil [amd64] (jammy-proposed) [0~20210324.2-2]
[20:51] -queuebot:#ubuntu-release- New: accepted abseil [armhf] (jammy-proposed) [0~20210324.2-2]
[20:51] -queuebot:#ubuntu-release- New: accepted abseil [ppc64el] (jammy-proposed) [0~20210324.2-2]
[20:51] -queuebot:#ubuntu-release- New: accepted abseil [s390x] (jammy-proposed) [0~20210324.2-2]
[20:51] -queuebot:#ubuntu-release- New: accepted abseil [arm64] (jammy-proposed) [0~20210324.2-2]
[20:51] -queuebot:#ubuntu-release- New: accepted abseil [riscv64] (jammy-proposed) [0~20210324.2-2]
[20:51] -queuebot:#ubuntu-release- New: accepted abseil [i386] (jammy-proposed) [0~20210324.2-2]
[20:51] -queuebot:#ubuntu-release- New: accepted ffms2 [amd64] (jammy-proposed) [2.40+git20211209-2]
[20:51] -queuebot:#ubuntu-release- New: accepted ffms2 [i386] (jammy-proposed) [2.40+git20211209-2]
[20:51] -queuebot:#ubuntu-release- New: accepted ffms2 [riscv64] (jammy-proposed) [2.40+git20211209-2]
[20:52] -queuebot:#ubuntu-release- New: accepted rust-tree-sitter-config [riscv64] (jammy-proposed) [0.19.0-1]
[20:52] -queuebot:#ubuntu-release- New: accepted ffms2 [armhf] (jammy-proposed) [2.40+git20211209-2]
[20:52] -queuebot:#ubuntu-release- New: accepted ffms2 [s390x] (jammy-proposed) [2.40+git20211209-2]
[20:52] -queuebot:#ubuntu-release- New: accepted ffms2 [ppc64el] (jammy-proposed) [2.40+git20211209-2]
[21:07] <bryceh> vorlon, I wonder if we can just drop uwsgi-plugin-php binaries and source entirely.  I'm not spotting any rdeps, and it looks like debian hits the same migration error as us (https://ci.debian.net/packages/u/uwsgi-plugin-php/unstable/amd64/).  Kinda feels like it is maybe vestigial.
[21:09] <vorlon> bryceh: yes, bug report please and I'll remove it :)
[21:09] <bryceh> ok will do
[21:16] <bryceh> vorlon, https://bugs.launchpad.net/ubuntu/+source/uwsgi-plugin-php/+bug/1960356
[21:47] <bryceh> vorlon, btw the deb bug for php-pecl-http is #1005198
[21:50] <bryceh> I've retriggered all the symfony/doctrine stuff, but I doubt that'll untangle it.  Guessing there's still some package interdependences.
[22:00] <vorlon> Eickmeyer: what is debian/LICENSE.source?  this is not part of standard Debian packaging.  And I don't understand why debian/README.debian is provided, all the information in there seems to be better presented elsewhere (such as a debian/README.source, which is a standard file and is clear that it doesn't need to be included as user-facing documentation in the binary package)
[22:01] <Eickmeyer> vorlon: I copied LICENSE.source from the LICENSE file in the github repository.
[22:01] <vorlon> Eickmeyer: if debian/LICENSE.source is a copy of the upstream license file from the git repo, I think it's pointless to include it here. debian/copyright is authoritative
[22:01] <vorlon> Eickmeyer: also this package does not build, the paths in debian/docs are wrong (they are relative to the debian/ subdir and should be relative to the package root)
[22:01] <Eickmeyer> vorlon: Ok, that makes sense. If you'd like to reject, I can reupload with a version omitting that.
[22:01] <vorlon> Eickmeyer: I wouldn't have rejected just for that bit, but since the package fails to build I will
[22:02] <Eickmeyer> Ok, I'll figure out why it's failing to build.
[22:02] -queuebot:#ubuntu-release- New: rejected phinger-cursor-theme [source] (jammy-proposed) [1.1-0ubuntu1]
[22:22] -queuebot:#ubuntu-release- New source: phinger-cursor-theme (jammy-proposed/primary) [1.1-0ubuntu1]
[22:23] <Eickmeyer> vorlon: ^ Fixed, actually builds.
[22:42] -queuebot:#ubuntu-release- Unapproved: accepted monitoring-plugins [source] (impish-proposed) [2.3.1-1ubuntu2.1]
[22:44] -queuebot:#ubuntu-release- Unapproved: accepted monitoring-plugins [source] (focal-proposed) [2.2-6ubuntu1.2]
[23:02] -queuebot:#ubuntu-release- New: accepted phinger-cursor-theme [source] (jammy-proposed) [1.1-0ubuntu1]
[23:04] -queuebot:#ubuntu-release- New binary: phinger-cursor-theme [amd64] (jammy-proposed/none) [1.1-0ubuntu1] (no packageset)
[23:07] -queuebot:#ubuntu-release- New: accepted phinger-cursor-theme [amd64] (jammy-proposed) [1.1-0ubuntu1]


[16:35] <sbeattie> ahasenack: hrm, I wonder if a specialized tool for that might make sense. aa-unconfined was originally intended as a "audit my system for things to consider confining" type tool.
[16:54] <ahasenack> sbeattie: I think it does, look at what I did to check if a process was confined
[16:54] <ahasenack> sbeattie: https://pastebin.ubuntu.com/p/Z4g8c36ZWM/
[16:54] <ahasenack> and I understand there is a case where this isn't enough, when there are no (or there are) stacking lsm modules
[16:56] <sbeattie> yeah, the potential cases / logic are more complex than 15 years ago when it was just "look in /proc/pid/attr/current" and it would be good to capture them in one place.
[16:57]  * sbeattie forgets if 'ps -Z` does the right thing in the face of stacking; I think it *should* due to IIRC relying on libapparmor, but it would be worth testing.
[16:58] <sbeattie> ahasenack: please feel free to open a bug somewhere, the gitlab project would be fine.
[16:58] <ahasenack> ok
[17:11] <ahasenack> sbeattie: filed: https://gitlab.com/apparmor/apparmor/-/issues/230
[17:16] <jjohansen> ps -Z does not rely on libapparmor and it doesn't do the right thing when stacking
[17:16] <jjohansen> aa-status should do the right thing
[17:30] <sbeattie> jjohansen: ah, bummer.
[17:32] <jjohansen> newer LSM stacking patches add a context file
[17:32] <jjohansen> /proc/<pid>/attr/context which provides a compound label with \0 separated fields
[17:32] <jjohansen> so something like
[17:32] <jjohansen>   apparmor=unconfined\0selinux=unconfined_t\0smack=_
[17:33] <jjohansen> which lets applications that are aware of it get all the values in a single read, and have a unified parsing
[17:33] <jjohansen> so as long as we get patches into ps etc to use context when available they will be able to do the right thing
[17:34] <jjohansen> but afaik the userspace side of things is still a big todo


[01:49] <BigBear> what i/o scedular does ubuntu use by defualt?
[11:51] <_ruben> hrm .. i want to take an existing kernel version (say: 2.6.24-16.30), and want to roll my own version of it (including 2 small patches) .. currently im rebuilding using the old make-kpkg approach, but im having difficulties mimicing the 'standard' versioning scheme
[11:55] <alex_joni> _ruben: grab it from git, and make a custom flavour
[11:59] <_ruben> hmm .. sounds like smth i could investigate indeed
[12:00] <alex_joni> there is a quide around wiki.ubuntu.com about building kernels from git
[12:00] <alex_joni> that should get you started
[12:01] <_ruben> havent checked wiki yet, using https://help.ubuntu.com/community/Kernel/Compile now
[12:01] <alex_joni> ok, that sounds good
[12:02] <alex_joni> you need to mess with debian/binary-custom.d/
[12:03] <alex_joni> add another custom binary flavour, put you patches and config there
[12:03] <alex_joni> then build using: "AUTOBUILD=1 NOEXTRAS=1 fakeroot debian/rules custom-binary-FLAVOUR"
[12:08] <_ruben> git clone in progress
[12:14] <_ruben> hmm .. the git/flavour approach seems pretty straightforward .. nice job
[12:19] <_ruben> to get the -server config .. i'd just cat debian/config/$ARCH/config and debian/config/$ARCH/config.server to one file i guess/
[13:44] <munckfish> BenC: got a sec?
[13:45] <BenC> munckfish: sure
[13:45] <munckfish> Over the weekend I sent a pull request for Linux Ports cause I've finally managed to get together a stable build for the PS3
[13:46] <munckfish> I just wanted to know what the next steps are to get it into the intrepid repos
[13:46] <munckfish> note that I haven't been able to test build on anything but Cell
[13:46] <munckfish> so I don't know what the options are for the other arch's
[13:46] <munckfish> BenC: over
[13:47] <BenC> munckfish: I'll take a look after I catch up on email (been off for a week)
[13:47] <munckfish> BenC: sure take your time
[13:49] <_ruben> how can i get my kernel git tree to 'represent' 2.6.24-19.41 ? .. i just want to apply 2 small patches to a given kernel and not change anything else (code-wise)
[13:58]  * _ruben lacks proper git skills and background info on the kernel git tree
[13:59] <munckfish> _ruben: can you not apply them to the current development version of the kernel from the ubuntu-hardy git tree?
[14:00] <munckfish> http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=summary
[14:00] <munckfish> Or do you specifically just want to add these patches for yourself and do not intent to contribute them?
[14:05] <_ruben> munckfish: personal (testing) use only .. im interesting in performance differences :)
[14:07] <munckfish> _ruben: the easiest way is to just checkout the hardy source as is and work with the current development version
[14:07] <munckfish> _ruben: the less easy way is to create a branch starting on 2.6.24-19.41
[14:07] <_ruben> munckfish: how "less easy" would that be? :)
[14:08] <munckfish> it's worth you look at the docs for git branch and git checkout
[14:08] <_ruben> i browsed the commit log, but couldnt even pinpoint the exact commit to take as reference (19.41 is mentioned multiple times)
[14:08] <munckfish> you can reference the tag for that version
[14:08] <munckfish> see "git tag"
[14:09] <_ruben> ah, nice
[14:09] <munckfish> Stefan Bader tagged the version you want here: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=commit;h=0717f584cfe10c9772b1b5daba51485c419fbe18
[14:09] <munckfish> instead of specify a branch to to branch from
[14:09] <munckfish> give the tag name instead
[14:09] <munckfish> Git is a great great system - but it does take a while to get to grips with it
[14:10] <_ruben> seems reading up on git is smth to add on my (huge) todo list
[14:10] <munckfish> worth it though imo
[14:10] <munckfish> Yeah I'd recommend it - have you seen the Ubuntu kernel KnowledgeBase docs?
[14:11] <munckfish> they're on the wiki
[14:11] <munckfish> _ruben: you'll need to follow the instructions on the Maintenance guide to make a kernel build which ends up as a deb
[14:13] <munckfish> that is without building loads of stuff you don't need just to test something
[14:14] <_ruben> still havent checked the wiki yet .. working with https://help.ubuntu.com/community/Kernel/Compile .. will search the wiki now
[14:15] <_ruben> actually i had the wiki open as well .. just not a very helpfull page (for me) https://wiki.ubuntu.com/KernelGitGuide
[14:18] <amitk> _ruben: https://wiki.ubuntu.com/KernelMaintenance
[14:18] <_ruben> amitk: was just reading that one
[14:18] <amitk> ..if you are looking to build Ubuntu-based kernsl
[14:18] <_ruben> tho my current quest is more a git one than a kernel one i'd say :p
[14:19] <_ruben> as in: "how to gt my git tree to represent 2.6.24-19.41 instead of head"
[14:19] <_ruben> but kernel.org isnt liking me thusfar (for the git docs)
[14:24] <amitk> _ruben: any reason you do not want to clone the kernel tree from kernel.ubuntu.com?
[14:25] <_ruben> amitk: i am using that, mentioned kernel.org wrt documentation of git :)
[14:36] <_ruben> hmm .. my custom kernel build (based on uptodate git tree) has a linux-headers packages which depends on linux-headers-2.6.24-22 but that one doesnt get build
[14:45] <_ruben> debian/rules binary-headers seems to do that trick :)
[15:10] <munckfish> _ruben: unless you really need the headers you should just be able to install the linux-image-* package
[15:11] <_ruben> munckfish: i needed the headers to recompile a kmod .. but i succeeded at that .. and so far im not seeing any performance difference .. so this little project goes in the fridge for now :)
[15:12] <munckfish> ok
[15:13] <_ruben> thanks for the help/pointers tho


[04:11] <vibhav> pitti: /win 5
[04:11] <vibhav> oops
[04:11] <vibhav> pitti: Sorry for the unnecessary hilight
[04:28] <pitti> Good morning
[04:28] <pitti> vibhav: I like to win 5 :)
[04:29] <vibhav> haha
[04:29] <vibhav> pitti: btw, I am writing tests for libacpi
[04:30] <vibhav> almost done
[04:30] <pitti> vibhav: nice!
[04:30] <pitti> vibhav: btw, can we please catch up with submitting the other tests to Debian? like libcaca?
[04:30] <vibhav> Doing that right now
[04:31] <pitti> vibhav: so, I'm updating my VM in the meantime to be ready for testing
[04:31] <vibhav> :)
[04:33] <vibhav> pitti: forwarded libaca
[04:33] <vibhav> libcaca*
[04:35] <pitti> vibhav: thanks
[04:38] <vibhav> pitti: https://code.launchpad.net/~vibhavp/ubuntu/raring/libacpi/add-autopkkgtest/+merge/150487
[04:38] <vibhav> pitti: btw, pkg-config doesn't support libacpi, so I use -lacpi
[04:38] <pitti> yeah, whatever the library recommends
[04:39] <vibhav> and as always, Ive added -Wall -Werror for extra scrutiny
[04:54] <pitti> vibhav: please fix the "installe" typo in the tests' comment header
[04:56] <vibhav> pitti: done
[05:07] <pitti> vibhav: and uploaded, thanks! please send Debianwards
[05:07] <vibhav> Doin that right now
[05:07] <vibhav> doing*
[05:08] <tancash1> Hello all! I was instructed earlier to post within here, and so that is what I am doing.
[05:12] <tancash1> In that resounding response, I guess I will elaborate. I recently signed up for the mailing list and inquired into the QA team, and that's when Nicholas Skaggs told me to introduce myself in here.
[05:12] <vibhav> tancash1: Welcome!
[05:13] <vibhav> tancash1: So, what are you planning to contribute to?
[05:14] <tancash1> Well, to be honest I'm not sure. I want to help out wherever I can, and within the next few weeks I plan on doing a bit more learning than contributing.
[05:14] <pitti> hello tancash1!
[05:14] <tancash1> Hello!
[05:24] <tancash1> So what can everyone tell me about themselves?
[05:30] <pitti> I'm working in Canonical's QA team on developing test technologies, GNOME/linux plumbing upstream QA, and autopkgtests
[05:31] <tancash1> That's cool
[05:33] <tancash1> So how does the autopkgtests work?
[05:34] <pitti> tancash1: http://developer.ubuntu.com/packaging/html/auto-pkg-test.html describes how to create and run them
[05:35] <pitti> tancash1: https://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/ are the currently existing ones which we run on every upload
[05:35] <pitti> a lot of them are broken right now unfortunately, we need some help there
[05:41] <tancash1> Okay, that helps a lot
[05:43] <tancash1> What is something easy I can start out with? Something basic I can do to help. Where exactly do we need the most help?
[07:22] <dholbach> good morning
[08:02] <vibhav> pitti: ping
[08:02] <pitti> hey vibhav
[08:03] <vibhav> pitti: pm?
[08:03] <pitti> vibhav: just do it :)
[08:08] <pitti> vibhav: https://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/job/raring-adt-libacpi/ :)
[08:09] <vibhav> \o/
[08:09]  * vibhav cheers
[08:17]  * dholbach notices an upwards trend on http://daniel.holba.ch/autopkgtests/ :)
[08:19] <vibhav> \o/
[08:49] <vibhav> pitti: https://code.launchpad.net/~vibhavp/ubuntu/raring/libiptcdata/add-autopkgtest/+merge/150504
[08:55] <pitti> vibhav: thanks! followed up
[08:57] <vibhav> pitti: thanks
[09:42] <vibhav> pitti: Ive fixed the errors
[09:44] <vibhav> pitti: btw, you wrote the endorsement?
[09:44] <pitti> vibhav: what's the copyright and TM of the tux logo?
[09:45] <pitti> vibhav: I really think it's better to create a tiny dummy image in gimp
[09:45] <pitti> vibhav: no, I've a tab open for it
[09:45] <vibhav> ah ok
[09:45] <vibhav> The copyright holder of this file allows anyone to use it for any purpose, provided that the copyright holder is properly attributed. Redistribution, derivative work, commercial use, and all other use is permitted.
[09:45] <vibhav> pitti: ^
[09:46] <pitti> vibhav: so, please do attribute :)
[09:46] <vibhav> sure
[09:46] <pitti> debian/tests/tux.jpg.README or so
[09:47] <pitti> vibhav: also, assert(buf != NULL); makes no sense, buf is a static array
[09:47] <pitti> vibhav: I think you rather want something like assert(strcmp(buf, "expected contents") == 0) or so
[09:49] <vibhav> pitti: Nope, I dont know the Metadata contained in the file
[09:50] <vibhav> pitti: Also, one would need to decode it, but thats unnessary since we only need compile/link/run tests
[09:50] <pitti> vibhav: you could print it once, and then put that back in as expected rsult?
[09:50] <pitti> vibhav: yeah, just a suggestion; that's usually the kind of thing that belongs into the upstream test suite
[09:53] <vibhav> pitti: iptc_data_new_from_data() decodes buf
[09:58] <vibhav> pitti: Okay, so Ive revised stuff and pushed
[10:23] <pitti> vibhav: MP updated
[10:24] <vibhav> pitti: a fix is on the way
[10:29] <vibhav> pitti: pushed!
[10:30] <pitti> vibhav: please bzr add sample.jpeg and fix the path in the script, so that the test actually works
[10:32]  * vibhav bangs head
[10:33] <vibhav> pitti: done
[10:34] <vibhav> There shouldnt be mistakes now
[10:35] <pitti> vibhav: still missing bzr add sample.jpg, copy&paste epub comment
[10:36] <vibhav> pitti: I created the jpeg in GIMP
[10:37] <jibel> pitti, are you on the jhbuild  today? I'd like to push a new version of the charm that builds modules in parallel and don't want to interrupt anything you'd be working on.
[10:37] <pitti> jibel: not today, I need a day for some pygobject bug fixing
[10:37] <vibhav> pitti: added and pushed
[10:37] <jibel> pitti, good, thanks
[16:35] <vibhav> pitti: Thanks for notifying me. I'll have a look ASAP (exams begin from tomorrow)
[16:36] <SergioMeneses> morning!
[16:58] <SergioMeneses> balloons, phillw around?
[17:29] <leadsled>  in Lubuntu 13.04 live cd I have had problem with system-config-printer detecting the printer giving a cups error. I have not filed a bug yet, was wondering if any other testers experienced this problem?
[17:39] <SergioMeneses> leadsled, and what information about the bug did you see?
[17:39] <SergioMeneses> or message
[17:41]  * SergioMeneses lunch time
[17:53] <leadsled> SergioMeneses: the first message Printer Service not available. Start the service on this computer or connect to another server.  Then after clicking the connect button twice this appears: There was an error during the CUPS operation: 'failed to connect server'
[18:11] <SergioMeneses> phillw, did you get a bug like this? ↑↑↑
[18:12] <SergioMeneses> leadsled, I can work on it but tonight :S
[18:41] <leadsled> when shutting down live cd in Lubuntu 13.04 there is not a prompt to remove media and press enter
[19:43] <Noskcaj> is anyone able to run a lubuntu daily?