[05:59] <Unit193> aha<tab><tab><tab> Dang.
[08:41] <mlankhorst> seb128: https://launchpad.net/ubuntu/+source/spirv-llvm-translator-15/15.0.0-1ubuntu2 -- I'm running lunar currently, but apt policy libllvmspirvlib-15-dev:i386 still says N: Unable to locate package libllvmspirvlib-15-dev:i386
[08:42] <seb128> mlankhorst, https://bugs.launchpad.net/ubuntu/+source/spirv-llvm-translator-15/+bug/2024842 ?
[08:42] -ubottu:#ubuntu-devel- Launchpad bug 2024842 in spirv-llvm-translator-15 (Ubuntu) "i386 package still not published?" [Undecided, Incomplete]
[08:42] <mlankhorst> Yeah, current mesa needs it now
[08:43] <mlankhorst> But that explains though, I'll just upload it to my ppa
[08:43] <seb128> you can try but that's not going to work I think
[08:44] <seb128> it's not in the i386 whitelist atm
[08:44] <seb128> so it's not going to build on that arch in your ppa either
[08:44] <seb128> do you have any idea why that requirement was there in lunar mid cycle and vanished at some point?
[08:45] <mlankhorst> I'm guessing a newer mesa that required it was never uploaded
[08:45] <seb128> I've added it to the whitelist that's probably because mesa was  build-depending on it
[08:45] <seb128> tjaalton, ^ do you know what happened exactly there?
[08:47] <seb128> perhaps that change https://launchpad.net/ubuntu/+source/mesa/22.3.6-1ubuntu1 ?
[08:47] <seb128>   * rules: Drop i386 from RUSTICL_ARCHS.
[08:47] <seb128> I've no idea what RUSTICL_ARCHS is
[08:47] <seb128> mlankhorst, ^
[08:48] <mlankhorst> It's archs on which that part of mesa is enabled, but it needs that dep uncondtionally now for opencl
[08:48] <seb128> and starting with which version?
[08:48] <mlankhorst> current git
[08:49] <mlankhorst> https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/23667 I think
[08:49] -ubottu:#ubuntu-devel- Merge 23667 in mesa/mesa "compiler/clc: Move clc functions from spirv to clc" [Merged]
[08:49] <seb128> k, so I guess it was added to the whitelist because rusticl was requiring it
[08:49] <seb128> but tjaalton turned that off
[08:49] <seb128> which made it drop from the whitelist
[08:50] <seb128> so we need to bring it back now
[08:50] <mlankhorst> Would seem so, https://launchpadlibrarian.net/674089996/buildlog_ubuntu-lunar-i386.mesa_23.0.4-0ubuntu1+xe9_BUILDING.txt.gz is a snapshot of mesa.git with Xe enablement on top
[08:53] <seb128> mlankhorst, do you need it for lunar as well for your ppa?
[08:54] <mlankhorst> Just ppa is fine
[09:06] <seb128> bah, IRC not coping with IP changes :/
[09:08] <seb128> mlankhorst, my question was unclear, I was asking for which Ubuntu serie you need it. If I add it to the whitelist it will start being available only for mantic, I was asking if you want to do build on lunar/other series in your ppa
[09:08] <mlankhorst> I'm building lunar in my ppa
[09:08] <seb128> ack
[09:48] <danilogondolfo> May I ask someone to run this for me? https://autopkgtest.ubuntu.com/request.cgi?release=mantic&arch=arm64&package=libwww-mechanize-perl&trigger=libwww-mechanize-perl/2.17-1
[09:51] <mitya57> danilogondolfo: done
[09:51] <danilogondolfo> mitya57, thank you :)
[10:47] <seb128> tjaalton, mlankhorst, as a fyi https://launchpadlibrarian.net/674248608/buildlog_ubuntu-mantic-amd64.spirv-llvm-translator-15_15.0.0-1ubuntu3_BUILDING.txt.gz rebuild is failing on mantic amd64 :-/
[11:02] <sil2100> o/
[11:02] <sil2100> @pilot in
[12:11] <rbasak> doko: I just noticed that your isl uploads are all missing Launchpad-Bugs-Fixed in their changes files. I think they all need fixing.
[12:11] <rbasak> (not reviewing - I just glanced at the Trello board to make sure it's still working)
[12:12] <doko> ahh, ok. looks like I built these on unstable
[12:12] <rbasak> Should I reject them?
[12:12] <doko> yes please, will re-upload
[12:13] <rbasak> Done for J and K. I don't see any others.
[12:13] <doko> lunar?
[12:14] <rbasak> I don't see isl in Lunar unapproved at all.
[12:16] <rbasak> Oh but I did reject two in Jammy.
[12:16] <rbasak> I think one of those was intended for Lunar?
[12:16] <doko> yes, fixing that as well
[12:17] <rbasak> Thanks. I'm not reviewing SRUs today. I just happened to notice so thought I might help save some time.
[12:17] <rbasak> But I don't see the SRU information I expect in the bug either - is that yet to come?
[12:50] <mlankhorst> seb128: weird bug, especially since it has obviously been built before.. Output also seems to be weird.
[12:50] <mlankhorst> https://gitlab.freedesktop.org/mesa/piglit/-/merge_requests/821 indicates it seem to happen because spirv-as is newer
[12:50] -ubottu:#ubuntu-devel- Merge 821 in mesa/piglit "util: Pass explicit '-' for spirv-as input filename" [Merged]
[12:52] <mlankhorst> so caused by newer spirv-tools
[12:53] <seb128> mlankhorst, ah, thanks
[12:56] <mlankhorst> a local build is passing on my lunar system though, so I'm not 100% sure what's going on, since mantic seems to have same version
[12:56] <enr0n> Can a MOTU or core dev please trigger these PPA autopkgtests? TIA!
[12:56] <enr0n> https://autopkgtest.ubuntu.com/request.cgi?release=mantic&arch=arm64&package=python-test-stages&ppa=enr0n/proposed-migration&trigger=python-test-stages/0.1.1-1ubuntu1~ppa2
[12:56] <enr0n> https://autopkgtest.ubuntu.com/request.cgi?release=mantic&arch=armhf&package=python-test-stages&ppa=enr0n/proposed-migration&trigger=python-test-stages/0.1.1-1ubuntu1~ppa2
[12:56] <enr0n> https://autopkgtest.ubuntu.com/request.cgi?release=mantic&arch=amd64&package=python-test-stages&ppa=enr0n/proposed-migration&trigger=python-test-stages/0.1.1-1ubuntu1~ppa2
[12:56] <enr0n> https://autopkgtest.ubuntu.com/request.cgi?release=mantic&arch=ppc64el&package=python-test-stages&ppa=enr0n/proposed-migration&trigger=python-test-stages/0.1.1-1ubuntu1~ppa2
[12:56] <enr0n> https://autopkgtest.ubuntu.com/request.cgi?release=mantic&arch=s390x&package=python-test-stages&ppa=enr0n/proposed-migration&trigger=python-test-stages/0.1.1-1ubuntu1~ppa2
[13:10] <sil2100> o/
[13:11] <sil2100> enr0n: done o/
[13:12] <enr0n> sil2100: thanks!
[16:50] <bryceh> @pilot in
[17:23] <sil2100> @pilot out
[17:30] <enr0n> Can a motu or core dev please trigger these PPA autopkgtests? I forgot a trigger earlier :/
[17:30] <enr0n> https://autopkgtest.ubuntu.com/request.cgi?release=mantic&arch=arm64&package=python-test-stages&ppa=enr0n/proposed-migration&trigger=python-test-stages/0.1.1-1ubuntu1~ppa2&trigger=tox/4.4.6-1
[17:30] <enr0n> https://autopkgtest.ubuntu.com/request.cgi?release=mantic&arch=armhf&package=python-test-stages&ppa=enr0n/proposed-migration&trigger=python-test-stages/0.1.1-1ubuntu1~ppa2&trigger=tox/4.4.6-1
[17:30] <enr0n> https://autopkgtest.ubuntu.com/request.cgi?release=mantic&arch=amd64&package=python-test-stages&ppa=enr0n/proposed-migration&trigger=python-test-stages/0.1.1-1ubuntu1~ppa2&trigger=tox/4.4.6-1
[17:30] <enr0n> https://autopkgtest.ubuntu.com/request.cgi?release=mantic&arch=ppc64el&package=python-test-stages&ppa=enr0n/proposed-migration&trigger=python-test-stages/0.1.1-1ubuntu1~ppa2&trigger=tox/4.4.6-1
[17:30] <enr0n> https://autopkgtest.ubuntu.com/request.cgi?release=mantic&arch=s390x&package=python-test-stages&ppa=enr0n/proposed-migration&trigger=python-test-stages/0.1.1-1ubuntu1~ppa2&trigger=tox/4.4.6-1
[17:31] <bryceh> enr0n, heya
[17:32] <bryceh> enr0n, "You submitted an invalid request: tox/4.4.6-1 is not published in PPA enr0n/proposed-migration mantic"
[17:32] <bryceh> correct me if I'm wrong but I think for PPA's you don't need to be core dev, you should be able to trigger against your own PPA?
[17:34] <enr0n> bryceh: if that's true, I have wasted a lot of time in the past. I always thought you needed to be able to upload the package you are triggering, even if against your own PPA.
[17:34] <enr0n> bryceh: I will try that now
[17:35] <enr0n> Nope, not allowed
[17:35] <bryceh> ok til :-)
[17:36] <bryceh> enr0n although hm, tox is not in your ppa?
[17:37] <enr0n> bryceh: right, I only just now copied tox from mantic-proposed so that I can use it as a trigger
[17:37] <bryceh> ah there it is
[17:38] <bryceh> $ ppa tests --packages tox enr0n/proposed-migration
[17:38] <bryceh> * Triggers:
[17:38] <bryceh>   - Source tox/4.4.6-1: Pending
[17:38] <bryceh>     + Trigger basic @amd64♻️    Trigger all-proposed @amd64💍
[17:38] <bryceh>     + Trigger basic @arm64♻️    Trigger all-proposed @arm64💍
[17:38] <bryceh>     + Trigger basic @armhf♻️    Trigger all-proposed @armhf💍
[17:38] <bryceh>     + Trigger basic @i386♻️     Trigger all-proposed @i386💍
[17:38] <bryceh>     + Trigger basic @ppc64el♻️  Trigger all-proposed @ppc64el💍
[17:38] <bryceh>     + Trigger basic @s390x♻️    Trigger all-proposed @s390x💍
[17:38] <bryceh> from what I can tell, tests can't be triggered until it has status Published, rather than Pending
[17:39] <bryceh> so that probably accounts for the error I got
[17:39] <bryceh> @enr0n, what was the text of the error message you got?
[17:40] <enr0n> bryceh: yeah, I've hit that one in the past. I sometimes forget to do the copy step beforehand. This is the error I got:
[17:40] <enr0n> "You submitted an invalid request: You are not allowed to upload python-test-stages or python-test-stages to Ubuntu, thus you are not allowed to use this service."
[17:40] <bryceh> aha, interesting
[18:27] <enr0n> bryceh: tox has been published in my PPA, can you please try the trigger again?
[18:27] <bryceh> sure thing
[18:29] <bryceh> @enr0n, done, and thanks for the ping reminder
[18:29] <enr0n> bryceh: thanks!
[22:28] <bryceh> @pilot out