Bug#818382: tracker.debian.org: False positive: "Problems while searching for new upstream version"

Package: tracker.debian.org Severity: normal Hi, For at least some packages, there's a consistent false positive when running uscan (e.g. https://tracker.debian.org/pkg/s3ql): | uscan had problems while searching for a new upstream version: | No upstream tarball downloaded. No further processi

Bug#780587: wheezy pbuilder fails to build some packages as tests involving network fail

> Also, I see the exact same issue on my laptop, so it's not just happening on > jenkins.debian.net - though granted, they both run stable and have been > set up by me :-) Wild guess: could it be related to the kernel version? After all, it seems to be related to loopback networking... Best, -Nik

Re: Testing for FUSE in ci tests

Antonio Terceiro writes: > On Thu, Jul 10, 2014 at 11:06:59PM -0700, Nikolaus Rath wrote: >> On Thu, 17 Apr 2014 15:15:00 -0300, Antonio Terceiro wrote: >> > On Wed, Apr 16, 2014 at 06:49:41PM -0700, Nikolaus Rath wrote: >> >> Currently the S3QL CI tests fail because

Re: Testing for FUSE in ci tests

On Thu, 17 Apr 2014 15:15:00 -0300, Antonio Terceiro wrote: > On Wed, Apr 16, 2014 at 06:49:41PM -0700, Nikolaus Rath wrote: >> Currently the S3QL CI tests fail because the test runner does not have >> permission to access the /dev/fuse device >> (http://ci.debian.net/data/un

Testing for FUSE in ci tests

Hello, Currently the S3QL CI tests fail because the test runner does not have permission to access the /dev/fuse device (http://ci.debian.net/data/unstable-amd64/packages/s/s3ql/2014-04-10.log). Nothing wrong with that, but the test already goes out of its way to determine if it ought to be able