Simon McVittie <s...@debian.org> writes: > On 19/08/14 09:33, Matthias Klose wrote: > [Nikolaus Rath wrote:] >>> That's a bug in the test (race condition) rather than in the program. >>> It's fixed upstream. >> >> [...] If you don't care >> about the autopkg tests, and if you are not ready to fix these but rather >> wait >> for the fixes from upstream (and maybe new bugs), then I think it's better to >> drop the autopkg tests. > > There are always at least two possible reasons for a failing test: "the > code under test is wrong" or "the test is wrong". > > The most important thing is that someone with knowledge of the package > has looked at the failure report and triaged it, i.e. assigned it an > appropriate priority based on their knowledge of the package. It appears > Nikolaus has done this, and it will be dealt with when it's dealt with. > I don't think there's a problem here.
If someone cares deeply about this, the necessary patch is at https://bitbucket.org/nikratio/s3ql/commits/9a8c0ebbff390555e63b7e203b999b89aabbb86e/raw/. I did not add it to the debian package yet because I considered it a minor issue that I did not want to bug my sponsor with. But if some DD wants to sponsor a new upload right away to get this fixed, I'm happy to update the package in SVN. Otherwise I'll wait for a new upstream version. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87mwazahl6....@vostro.rath.org
