[05:23] -queuebot:#ubuntu-release- New binary: cpupower-gui [amd64] (mantic-proposed/none) [0.7.2-2.1] (no packageset)
[05:23] -queuebot:#ubuntu-release- New binary: cpupower-gui [ppc64el] (mantic-proposed/none) [0.7.2-2.1] (no packageset)
[05:25] -queuebot:#ubuntu-release- New binary: cpupower-gui [s390x] (mantic-proposed/none) [0.7.2-2.1] (no packageset)
[05:26] -queuebot:#ubuntu-release- New binary: cpupower-gui [arm64] (mantic-proposed/none) [0.7.2-2.1] (no packageset)
[05:26] -queuebot:#ubuntu-release- New binary: cpupower-gui [armhf] (mantic-proposed/none) [0.7.2-2.1] (no packageset)
[05:39] -queuebot:#ubuntu-release- New binary: cpupower-gui [riscv64] (mantic-proposed/universe) [0.7.2-2.1] (no packageset)
[11:38] <ItzSwirlz> vorlon, so im going on vacation for next week (which sounds like I won't do anything, but I do have plenty of downtime in early mornings since everyone will still be sleeping), before I turn off my bouncer and pack up, anything you need from me until 2 PM EDT
[11:40] <ItzSwirlz> ig all i can do now is wait for the next livefs build that picks up the changes
[12:24] <ItzSwirlz> well anyways - you got my email if you need anything
[13:12] <kathenas> I see some of the mesa updtes are passing to 22.04 systems and breaking booting to GDM etc. Have we an issue or am I asking in the wrong place?
[13:12] <kathenas> s/updtes/updates
[13:19] <kathenas> https://pasteboard.co/CFoO1ojsLGbG.png
[17:22] -queuebot:#ubuntu-release- New binary: chkservice [amd64] (mantic-proposed/none) [0.3-1.1] (no packageset)
[17:23] -queuebot:#ubuntu-release- New binary: chkservice [ppc64el] (mantic-proposed/none) [0.3-1.1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: chkservice [arm64] (mantic-proposed/none) [0.3-1.1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: chkservice [s390x] (mantic-proposed/none) [0.3-1.1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: chkservice [armhf] (mantic-proposed/none) [0.3-1.1] (no packageset)
[17:41] -queuebot:#ubuntu-release- New binary: chkservice [riscv64] (mantic-proposed/none) [0.3-1.1] (no packageset)
[18:03] -queuebot:#ubuntu-release- New: accepted chkservice [amd64] (mantic-proposed) [0.3-1.1]
[18:03] -queuebot:#ubuntu-release- New: accepted chkservice [armhf] (mantic-proposed) [0.3-1.1]
[18:03] -queuebot:#ubuntu-release- New: accepted chkservice [riscv64] (mantic-proposed) [0.3-1.1]
[18:03] -queuebot:#ubuntu-release- New: accepted cpupower-gui [arm64] (mantic-proposed) [0.7.2-2.1]
[18:03] -queuebot:#ubuntu-release- New: accepted cpupower-gui [riscv64] (mantic-proposed) [0.7.2-2.1]
[18:03] -queuebot:#ubuntu-release- New: accepted chkservice [arm64] (mantic-proposed) [0.3-1.1]
[18:03] -queuebot:#ubuntu-release- New: accepted chkservice [s390x] (mantic-proposed) [0.3-1.1]
[18:03] -queuebot:#ubuntu-release- New: accepted chkservice [ppc64el] (mantic-proposed) [0.3-1.1]
[18:03] -queuebot:#ubuntu-release- New: accepted cpupower-gui [armhf] (mantic-proposed) [0.7.2-2.1]
[18:03] -queuebot:#ubuntu-release- New: accepted cpupower-gui [amd64] (mantic-proposed) [0.7.2-2.1]
[18:03] -queuebot:#ubuntu-release- New: accepted cpupower-gui [s390x] (mantic-proposed) [0.7.2-2.1]
[18:03] -queuebot:#ubuntu-release- New: accepted cpupower-gui [ppc64el] (mantic-proposed) [0.7.2-2.1]
[18:03] <ahasenack> debian has removed the armhf build of blender (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024626)
[18:03] -ubottu:#ubuntu-release- Debian bug 1024626 in src:blender "blender FTBFS on 32bit" [Important, Open]
[18:03] <ahasenack> rmadison confirms it
[18:03] <ahasenack> but I don't see anything in its d/control to not build on armhf
[18:04] <ahasenack> for ubuntu, do we just remove the armhf builds too (old ones in mantic: current one doesn't build anymore), or do we need to omit armhf in d/control and do the same in debian?
[18:04] <ahasenack> iirc if we just pull the debian source, we will try to build everywhere d/control allows it, right
[18:10] <Eickmeyer> ahasenack: I could be wrong, but afaik, if Debian removes an upstream build, we remove the build as well and then just hint Britney so that it's not a migration blocker.
[18:11] <ahasenack> it's not a migration issue, it doesn't build
[18:11] <ahasenack> ah, maybe I see what you mean
[18:11] <Eickmeyer> Right, but Britney will freak out if it's missing a build.
[18:11] <ahasenack> britney will say "missing build on X", but that will be ignored
[18:11] <Eickmeyer> Right.
[18:11] <ahasenack> let me see if there is an example in the hints repo
[18:12] <ahasenack> # We no longer produce armhf builds for this package.
[18:12] <ahasenack> force-badtest nvidia-graphics-drivers-390/all/armhf
[18:12] <ahasenack> maybe that
[18:12] <Eickmeyer> Yep. That sounds right.
[18:13] <Eickmeyer> I mean, I'm not release team, but I have interest in Blender since it's in Studio and have a rudimentary knowledge on how this works.
[18:13] <ahasenack> so are you aware upstream doesn't support 32bit anymore?
[18:13] <ahasenack> I was fixing an ftbfs in mantic due to other issues, and now I see it doesn't build on armhf
[18:14] <ahasenack> and found https://archive.blender.org/lists/bf-committers/2019-August/050124.html
[18:14] <Eickmeyer> Yes, 100%. Studio really doesn't care since we only support amd64 as an arch.
[18:14] <ahasenack> and a corresponding debian bug
[18:14] <ahasenack> ok
[18:14] <ahasenack> I'll PR a hint change
[18:14] <Eickmeyer> I *do* care when thinks fail to migrate, as you might imagine. :)
[18:15] <Eickmeyer> 👍
[18:21] <ahasenack> it ftbfs on s390x now: https://bugs.launchpad.net/ubuntu/+source/blender/+bug/2030291
[18:22] -ubottu:#ubuntu-release- Launchpad bug 2030291 in blender (Ubuntu) "FTBFS on s390x" [Undecided, New]
[18:22] <ahasenack> https://launchpad.net/ubuntu/+source/blender/3.4.1+dfsg-2ubuntu1 armhf should be taked care of by that hints pr
[18:22] <ahasenack> arm64 should build, riscv64 should also build eventually ;)
[18:22] <Eickmeyer> That's unexpected (s390x). Same issue in Debian?
[18:23] <ahasenack> no, but the last build there was months ago
[18:23] <ahasenack> https://buildd.debian.org/status/package.php?p=blender
[18:24] <Eickmeyer> I see that, was just looking myself and answered my own question.
[18:25] <Eickmeyer> Very old version, they're being molasses slow on updating it. Just checked salsa, and same issue there.
[18:25] <ahasenack> what did you see in salsa?
[18:26] <Eickmeyer> https://salsa.debian.org/multimedia-team/blender/ is where they do the packaging.
[18:26] <Eickmeyer> No updates for 6 months.
[18:37] <ginggs> ahasenack: your hint would work if the autopkgtest was failing on armhf
[18:39] <ahasenack> ginggs: I copied what apw did for nvidia, pasted above
[18:39] <ginggs> but it's a FTBFS, so would need an AA to remove the armhf binaries from mantic-release
[18:39] <RikMills> blender in the release pocket already fails on armhf so looks good I think as is
[18:39] <ginggs> but i think this has already been done
[18:39] <ahasenack> ginggs: right, but how to keep the armhf build from being tried again when debian updates?
[18:40] <ginggs> you don't need to, it will just fail
[18:40] <ahasenack> and so it did, I just uploaded https://launchpad.net/ubuntu/+source/blender/3.4.1+dfsg-2ubuntu1
[18:40] <ahasenack> question is if that failure (armhf) will prevent migration
[18:40] <RikMills> it won't
[18:40] <ahasenack> but since s390x failed too, that might prevent the migration instead
[18:41] <ahasenack> ah, I see in https://launchpad.net/ubuntu/+source/blender/3.4.1+dfsg-2build3 that armhf already failed, ok, I missed that
[18:41] <ginggs> no, britney already does not complain about armhf:
[18:41] <ginggs> missing build on amd64: blender, blender-data (from 3.4.1+dfsg-2build3)
[18:41] <ginggs> missing build on arm64: blender (from 3.4.1+dfsg-2build3)
[18:41] <ginggs> missing build on ppc64el: blender (from 3.4.1+dfsg-2build3)
[18:41] <ginggs> missing build on riscv64: blender (from 3.4.1+dfsg-2build3)
[18:41] <ginggs> missing build on s390x: blender (from 3.4.1+dfsg-2build3)
[18:42] <ahasenack> ok, so just s390x needs a real fix
[18:42] <ginggs> but s390x will be an issue, then an AA needs to remove the binaries from mantic (or the build fixed)
[18:43] <ginggs> fwiw, blender/armhf was already removed in kinetic https://launchpad.net/ubuntu/kinetic/armhf/blender
[18:45] <ahasenack> ok, that's sorted then
[18:46] <ahasenack> I only touched blender because of my patch pilot shift yesterday :)
[18:52] <Eickmeyer> ahasenack: I appreciate your work. :)
[19:56] -queuebot:#ubuntu-release- New binary: ktextaddons [amd64] (mantic-proposed/universe) [1.4.0-0ubuntu1] (no packageset)
[19:56] -queuebot:#ubuntu-release- New binary: ktextaddons [s390x] (mantic-proposed/universe) [1.4.0-0ubuntu1] (no packageset)
[19:58] -queuebot:#ubuntu-release- New binary: ktextaddons [ppc64el] (mantic-proposed/universe) [1.4.0-0ubuntu1] (no packageset)
[20:00] -queuebot:#ubuntu-release- New binary: ktextaddons [arm64] (mantic-proposed/universe) [1.4.0-0ubuntu1] (no packageset)
[20:03] -queuebot:#ubuntu-release- New binary: ktextaddons [armhf] (mantic-proposed/universe) [1.4.0-0ubuntu1] (no packageset)
[20:43] -queuebot:#ubuntu-release- New binary: ktextaddons [riscv64] (mantic-proposed/universe) [1.4.0-0ubuntu1] (no packageset)