Congratualtions! Go ahead and annoy people.
That is exactly the way to build community! --- Or you just add* e.g. the -*Dmaven.test.skip=true parameter, and it will build fine. But apparently you do not care about importance of bugs at all, only about processes and your personal opinion. Heck, it would have been much faster to fix the bug, than to bother me again and again when I don't have time to waste, like you apparently have. ******* Stop wasting time. Fix bugs instead! ******* Thank you. Regards, Erich On Wed, Mar 8, 2017 at 1:20 AM, Santiago Vila <sanv...@unex.es> wrote: > severity 843038 serious > thanks > > Dear maintainer: > > I expected a general guideline from Release Managers regarding > packages which FTBFS randomly like this one, but that will most surely > not happen for stretch. > > So, the only guideline I have left is the one expressed by Julien > Cristau (one of the RMs) in Bug #844264: > > "if the failure rate is low enough I think a lower severity can make > sense" > > I posted a list of bugs which FTBFS more than 10% of the time and > several people agreed on -devel that they should be serious and > maintainers should ask for stretch-ignore tag in case the bug should > not be RC (most bugs are about failing tests so this should not be > needed in general). > > In the latest tests I made, this package fails for me more than 55% of > the time, and it also fails (always, apparently) in the reproducible > builds autobuilders, in all architectures: > > https://tests.reproducible-builds.org/debian/rb-pkg/ > unstable/amd64/elki.html > > This may affect any user trying to build this package (for example, > after making a change), our downstreams, and the Security Team once > that stretch is stable. > > For this reason I'm raising this to serious again. > > Sorry for the long explanation. > > Thanks. >
