| ogayot | Hello, may I kindly ask somebody to trigger this autopkgtest for me? I would appreciate it! https://autopkgtest.ubuntu.com/request.cgi?release=mantic&arch=amd64&package=python-ansible-pygments&ppa=ogayot%2Fmantic-proposed&trigger=python-ansible-pygments%2F0.1.1-5ubuntu1~ppa1 | 07:35 |
|---|---|---|
| ginggs | ogayot: . | 08:43 |
| ogayot | ginggs: thanks! | 08:48 |
| bluca | are there infra issues in the autopkgtest farm? | 10:41 |
| bluca | autopkgtest [02:16:20]: ERROR: unexpected error: OSError: [Errno 28] No space left on device | 10:41 |
| bluca | all systemd CI jobs seems stuck | 10:41 |
| bluca | https://autopkgtest.ubuntu.com/running#pkg-systemd-upstream | 10:41 |
| bluca | I have the script to retry the jobs, but is there an API to instead cancel them? | 10:43 |
| ahasenack | tjaalton: I'm still gonna check the curl sru, I wanted to do that yesterday, but the day ended too fast | 12:27 |
| ahasenack | (unapproved) | 12:27 |
| tjaalton | ahasenack: yeah, I skipped that one | 12:27 |
| ahasenack | thx | 12:27 |
| tjaalton | ahasenack: also, if you don't mind looking at jammy:mesa ;) | 12:27 |
| ahasenack | I can, I want to work 2h on srus today, I spent 2h on interviews yesterday | 12:27 |
| tjaalton | cool | 12:27 |
| tjaalton | thanks | 12:27 |
| ahasenack | I have since blocked my sru shift day to avoid such things | 12:28 |
| ahasenack | (in the calendar) | 12:28 |
| ahasenack | tjaalton: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2013128 needs a lunar and mantic upload still, right? I see kinetic is being skipped on purpose | 13:40 |
| -ubottu:#ubuntu-devel- Launchpad bug 2013128 in mesa (Ubuntu Jammy) "mesa: set info.separate_shader for ARB programs" [Undecided, In Progress] | 13:40 | |
| ogayot | The last autopkgtest run I requested didn't run against pygments from -proposed. Can someone retrigger it using this link instead please? I hope that'll work better: https://autopkgtest.ubuntu.com/request.cgi?release=mantic&arch=amd64&package=python-ansible-pygments&ppa=ogayot%2Fmantic-proposed&trigger=python-ansible-pygments%2F0.1.1-5ubuntu1~ppa1&trigger=pygments/2.15.1%2Bdfsg-1 Thanks! | 13:41 |
| tjaalton | ahasenack: no it's fixed in lunar and up | 13:41 |
| ahasenack | I checked the pkg, that bool is to false in lunar+ (after patches are applied) | 13:41 |
| tjaalton | hmm | 13:42 |
| ahasenack | https://git.launchpad.net/ubuntu/+source/mesa/tree/src/mesa/program/prog_to_nir.c?h=applied/ubuntu/devel#n1039 | 13:43 |
| ahasenack | (that's mantic) | 13:43 |
| ahasenack | that commit (7e68cf91d74e6bd9a88c2b52417451d9afec4782) is in 23.1.0 | 13:46 |
| ahasenack | $ git tag --contains 7e68cf91d74e6bd9a88c2b52417451d9afec4782 | 13:47 |
| ahasenack | 23.1-branchpoint | 13:47 |
| ahasenack | mesa-23.1.0 | 13:47 |
| ahasenack | (...) | 13:47 |
| tjaalton | yes and should be backported to the stable series, but 22.2.x was dead already back then | 13:47 |
| tjaalton | but, still looking | 13:47 |
| tjaalton | because it's in 22.3.x | 13:48 |
| tjaalton | kinda remarkable if it's not in 23.0.x | 13:48 |
| tjaalton | I could upload 23.1.0 to mantic, but it still leaves lunar. I'd rather fix that once the final version of 23.0.x is available | 13:50 |
| tjaalton | asking the upstream stable maintainer about what happened here | 13:53 |
| ahasenack | isn't it the same diff for lunar? | 13:54 |
| ahasenack | that one liner? | 13:54 |
| tjaalton | yes | 13:55 |
| tjaalton | okay | 13:55 |
| xypron | I am looking for a sponsor for LP #2019319. Fixing FTBFS (in testing phase) by disabling LTO | 13:55 |
| -ubottu:#ubuntu-devel- Launchpad bug 2019319 in aespipe (Ubuntu) "FTBFS: building with LTO fails" [Undecided, New] https://launchpad.net/bugs/2019319 | 13:55 | |
| tjaalton | .pick_status.json says | 13:55 |
| tjaalton | "notes": "\nCauses virgl regressions, probably needs a groundwork patch in virgl" | 13:55 |
| ahasenack | is that about switching it to true? "s->info.separate_shader = true;"? | 13:56 |
| tjaalton | yes | 13:56 |
| ahasenack | want to give up on that one for the sru? | 13:57 |
| tjaalton | it's for this proposed stable commit, and the reason why it didn't get applied to 23.0 | 13:57 |
| tjaalton | yeah | 13:57 |
| ahasenack | ok, reject and new upload? | 13:57 |
| ahasenack | w/o this? | 13:57 |
| tjaalton | sure | 13:57 |
| ahasenack | ok | 13:57 |
| enr0n | I am looking for a MOTU or core dev to sponsor a few syncs: bug 2019241, bug 2019242, bug 2019243, and bug 2019245 | 14:11 |
| -ubottu:#ubuntu-devel- Bug 2019241 in golang-github-hashicorp-go-slug (Ubuntu) "Please sync golang-github-hashicorp-go-slug 0.9.1-2 from Debian unstable" [Undecided, New] https://launchpad.net/bugs/2019241 | 14:12 | |
| -ubottu:#ubuntu-devel- Bug 2019242 in mit-scheme (Ubuntu) "Please sync mit-scheme 12.1-3 from Debian unstable" [Undecided, New] https://launchpad.net/bugs/2019242 | 14:12 | |
| -ubottu:#ubuntu-devel- Bug 2019243 in prometheus-ipmi-exporter (Ubuntu) "Please sync prometheus-ipmi-exporter 1.6.1-2 from Debian unstable" [Undecided, New] https://launchpad.net/bugs/2019243 | 14:12 | |
| -ubottu:#ubuntu-devel- Bug 2019245 in python-uvicorn (Ubuntu) "Please sync python-uvicorn 0.17.6-1 from Debian unstable" [Undecided, New] https://launchpad.net/bugs/2019245 | 14:12 | |
| ahasenack | tjaalton: what do the resolution codes mean in pick_status.json? | 14:50 |
| tjaalton | ahasenack: 0 and 1 are pretty clear, but no idea what 4 means | 19:00 |
| bluca | bdmurray: we are seeing autopkgtest failures due to no space left, any idea if there are issues? | 19:28 |
| bluca | all systemd CI jobs seem stuck today | 19:28 |
| bluca | https://autopkgtest.ubuntu.com/running#pkg-systemd-upstream | 19:29 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!