Le 06/08/2019 à 15:09, Santiago Vila a écrit : > In a general sense, the DFSG requires that packages build in the same > distribution as they are present, so we can't fix a FTBFS in stretch > (still a supported distribution) by fixing the bug only in buster. > > Release Policy says that packages in stretch must build in stretch and > without failure. Because the tests are part of the build, their failure > counts as a build failure. > > Do you think I should ask Release Managers before reporting more bugs > like this one? (I only found a handful of them)
If the release managers knowingly let the issue slip into the release (because an RC issue was already reported at the time of the release) I don't think it's worth bothering them again with it. If a build issue appeared *after* the release, due to a regression caused by a point release, then yes I think the issue is worth reporting (but I wouldn't bother reporting minor test failures that can be easily skipped to rebuild from sources). Emmanuel Bourg __ This is the maintainer address of Debian's Java team <https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-java-maintainers>. Please use debian-j...@lists.debian.org for discussions and questions.