Package: release.debian.org
Severity: normal
Tags: moreinfo
User: release.debian.org@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: mesa@packages.debian.org, Timo Aaltonen <tjaalton@debian.org>
Should the mesa source package be unblocked for bullseye? It was uploaded
to unstable several months ago.
Please note that I am not a Mesa maintainer, and I don't know whether
the uploader (cc'd) intended this to be for bullseye or not. I've tagged
this bug as moreinfo until Mesa maintainers confirm whether they want
this in bullseye.
If we're too late for 11.0, another option would be to convert this into
a mesa/20.3.5-0+deb11u1 upload targeting point release 11.1.
[ Reason ]
New upstream stable release with various bug fixes. The one I'm
particularly interested in is https://bugs.debian.org/983390 which causes
crashes and hangs when using third-party Vulkan layers like MangoHUD, but
there are lots of bugfixes listed in the upstream release notes.
[ Impact ]
Users of bullseye who run games etc. will experience various crashes,
hangs and rendering artifacts that could have been avoided.
[ Tests ]
I don't know, I'm not the maintainer. Presumably a lot of users of
unstable have been using this version to run games and other
graphically-intensive programs in the 116 days since it was uploaded.
There don't seem to be any RC bugs open. The Mesa maintainers would know
better than I do whether there have been non-RC regression reports.
[ Risks ]
It's a key package, involved in providing hardware support.
If the changes that upstream made in their development branch and then
backported into their stable branch are not all correct, then this version
could introduce new crashes, hangs and artifacts of a scope similar to the
ones it's fixing.
[ Checklist ]
[ ] all changes are documented in the d/changelog
- debian/patches/llvm-12-build-fix.diff is not explicitly documented
[ ] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
The attached debdiff is lightly filtered to remove changes that appear to
be irrelevant (a copy of debian/patches/llvm-12-build-fix.diff in an
unintended location, and the JSON file that upstream use to track which
commits should/shouldn't be cherry-picked from their development branch).
Thanks,
smcv
Attachment:
mesa_20.3.5-1-filtered.diff.gz
Description: application/gzip