Control: reassign -1 custodia Control: severity -1 serious On 22-Apr-2018, Ben Finney wrote: > Control: severity -1 normal > > On 25-Feb-2018, Adrian Bunk wrote: > > Source: custodia > > Version: 0.5.0-3 > > Severity: serious > > This bug report affects only the upstream unit tests suite, and (as > reported) shows no effect on the run-time use of the package.
Oh, I see now that the report was against ‘custodia’ as a FTBFS *because of* the failed test suite. That does warrant “Severity: serious” as originally reported. Given that the failure is caused by the ‘custodia’ test suite's invocation of Coverage.py, I am re-assigning this back to ‘custodia’. The ‘custodia’ test suite needs to be corrected so that it does not cause that error; and until then, that test suite could be disabled in Debian (to allow the package to build from source. -- \ “If you don't know what your program is supposed to do, you'd | `\ better not start writing it.” —Edsger W. Dijkstra | _o__) | Ben Finney <[email protected]>
signature.asc
Description: PGP signature
