Control: severity -1 important On Wed, Mar 23, 2016 at 02:18:20PM +0100, Santiago Vila wrote: > I have at least one "successful" build log for each of the listed > packages which is not really successful because of errors in doxygen > that were not trapped. The build logs are similar to the ones I already > attached for "apt".
Thank you for doing this QA. Did you find some time filing those bugs already? > All those packages are indirectly violating Policy 4.6 because of this. > As I think this is the kind of bug that in no way should not be present > in stretch when it becomes stable, I'm setting the severity accordingly. I discussed this with the release team and we evaluated the bug against the rc policy[1]. We concluded that this bug is not release critical. The rationale essentially is that it matches none of the problem categories from the rc policy. Furthermore, I note that policy item 4.6 appears to be neglected throughout the archive and a significant fraction of packages - sadly - violate it. Fixing policy 4.6 issues looks like a laudable goal, but one that is not actively pursued by anyone. Helmut [1] https://release.debian.org/stretch/rc_policy.txt
