vasilito
cb424d7448
verify-patch-sanity.py validates every active recipe .patch has internally- consistent hunk line counts — catching the 'malformed patch at line N' failure at commit/CI/preflight time instead of hours into a cook. This cycle hit that class three times (qtwaylandscanner, sddm, xwayland), each only discovered when cookbook tried to apply the patch. Running it across the repo found 29 latent malformed patches (validated against GNU patch: e.g. relibc/P3-sysv-ipc reproduces 'malformed patch at line 22'). They were harmless only because they sit in vendored recipes (baked, not re- applied) — but would fail on any version-bump re-derivation. --fix recounts the hunk headers (body untouched) and repaired all 29. Wired into build-preflight.sh (Phase 1.0D) and redbear-ci.yml, with a unit test (test-patch-sanity.sh). Skips archived/legacy trees and unvalidatable formats (empty placeholders, bare-@@ git hunks).
27 lines
1.2 KiB
ReStructuredText
27 lines
1.2 KiB
ReStructuredText
Report a Bug
|
|
============
|
|
|
|
To file a Mesa bug, go to `GitLab on
|
|
freedesktop.org <https://gitlab.freedesktop.org/mesa/mesa/-/issues>`__.
|
|
|
|
Please follow these bug reporting guidelines:
|
|
|
|
- Check if a new version of Mesa is available which might have fixed
|
|
the problem.
|
|
- Check if your bug is already reported in the database.
|
|
- Monitor your bug report for requests for additional information, etc.
|
|
- Attach the output of running glxinfo or wglinfo. This will tell us
|
|
the Mesa version, which device driver you're using, etc.
|
|
- If you're reporting a crash, try to use your debugger (gdb) to get a
|
|
stack trace. Also, recompile Mesa in debug mode to get more detailed
|
|
information.
|
|
- Describe in detail how to reproduce the bug, especially with games
|
|
and applications that the Mesa developers might not be familiar with.
|
|
- Provide an `apitrace <https://github.com/apitrace/apitrace>`__ or
|
|
simple GLUT-based test program if possible.
|
|
|
|
The easier a bug is to reproduce, the sooner it will be fixed. Please do
|
|
everything you can to facilitate quickly fixing bugs. If your bug report
|
|
is vague or your test program doesn't compile easily, the problem may
|
|
not be fixed very quickly.
|