Package: bugs.debian.org
Trying to find a way to track packages using (temporary) work-arounds to build;
if successful, propose it as a policy.
Some packages use work-arounds to prevent build failures, because these expose
bugs in the build tools; these work-arounds are usually not reverted, and not
tracked, or badly tracked (changelogs commenting on "new version of gcc").
These work-arounds should be tracked in the package applying the work-around,
and having `blocked-by' link to the relevant bug report of the build tool.
Work-arounds could be
- use of a non-default compiler [1]
- lowering/changing optimization defaults
- disabling some feature
For GCC specific reports, this could be done with a user tag
(work-around-applied) and a user (debian-gcc), but there might be work-arounds
applied as well for non GCC issues. Are user tags still the right way to track
and query these issues, independent of the user they are filed for?
Matthias
[1]
http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=non-standard-compiler;tag=gcc-4.4;users=debian-...@lists.debian.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
