Bug#808640: [Pkg-freeipa-devel] Bug#808640: custodia: FTBFS: Could not find any downloads that satisfy the requirement sphinx<1.3.0
On Tue, Dec 29, 2015 at 08:06:06AM +0200, Timo Aaltonen wrote: > > So what's special about this build env compared to normal sbuild, where > it builds just fine? > The build runs without networking, like the main buildds, and the Ubuntu buildds. The Policy requires builds to complete without depending on external resources, and we implement this by banning networking. In this case, it looks like the package is trying to use code from pypi, (i.e. the binaries included in the package wouldn't be built from the source code in Debian), which is a serious bug. Ubuntu buildd: https://launchpad.net/ubuntu/+source/custodia/0.1.0-2/+build/8184393
Bug#805249: pyparted: FTBFS: PartedException: Unknown disk flag, 1000.
Hmm. I re-test things on my local builder before reporting them, so I've definitely been able to reproduce this failure. My builder is much more normal than jenkins: it uses apt to resolve packages, and things like that. If you don't have any ideas then I can run the build a few more times and see if I can catch what's up.
Bug#802059: Already reported against glibmm2.4
Maybe this is a duplicate of: https://bugs.debian.org/800371 ..depending on the solution they arrive at.
Bug#793319: FTBFS: ImportError: cannot import name component_re
On Wed, Aug 12, 2015 at 04:31:15PM +0300, Gediminas Paulauskas wrote: Now that Bug#779324 is fixed, a simple rebuild would fix the problem. Looks good, yep.
Bug#794372: Oh, the transition!
I have been reminded that there's a nasty C++ transition going on, so these might be transient (i.e. fixed when the upstream libraries are done transitioning). Feel free to close as invalid, drop priority, or whatever! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793518: [pkg-go] Bug#793518: FTBFS: TestString fails: ini_test.go:167: Dict cannot be stringified as expected.
On Mon, Jul 27, 2015 at 07:26:10PM +0200, Michael Stapelberg wrote: control: tags -1 + unreproducible Chris, was this an issue on your end? Or am I misinterpreting something? The problem seems to have gone away. I was running local builds in response to errors on the reproducible-builds builder. Their builder has rebuilt sucessfully since then, and I have also just rebuilt sucessfully. Perhaps it was fixed by dependency changes? Proof I'm not mad: my build log from local: https://paste.debian.net/286717/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793518: [pkg-go] Bug#793518: FTBFS: TestString fails: ini_test.go:167: Dict cannot be stringified as expected.
On Mon, Jul 27, 2015 at 10:45:17PM +0200, Michael Stapelberg wrote: Actually, my bad, the commit I referenced is already in the package in the form of a patch. In your https://paste.debian.net/286717/, I don’t see any mention of the patch, though…? Does your build environment not apply patches? When running gbp buildpackage --git-pbuilder, I see: [..] Unless I'm missing something, the patch is not in the version in unstable/testing. Looking at the git repo linked from tracker.d.o, https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-glacjay-goini.git/ the patch was added after the release was tagged. The paste link is building from unstable, so (correctly) isn't seeing the patch? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790800: ..or maybe this is just transition noise
This is happening to other packages too, and I can't find the .moc files I thought were bundled before; maybe it's just transition related and will go away? See e.g. qapt: https://reproducible.debian.net/rb-pkg/unstable/amd64/qapt.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789832: unburden-home-dir: FTBFS: t/unexpected-cases.t fails on amd64
On Thu, Jun 25, 2015 at 12:03:04AM +0200, Axel Beckert wrote: t/undo.t ... ok t/unexpected-cases.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/98 subtests thanks for the report, but I couldn't reproduce this, neither with 0.3.3 nor with the HEAD of the git repository. And https://reproducible.debian.net/rb-pkg/unstable/amd64/unburden-home-dir.html shows different tests failing, but not t/unexpected-cases.t. Can you please explain a little bit more about your setup? pbuilder or sbuild? On which file system where the tests run? (And if the reporting machine was not the same as the machine where the issue happend: Which locale was set? Which init system was used? Which kernel was running?) etc. Hah. After far too much staring, the test which is failing for me is: ok 93 - Make list file t/zo4O_qcnum/list unreadable ok 94 - Call 'perl bin/unburden-home-dir -C t/zo4O_qcnum/config -c /dev/null -L t/zo4O_qcnum/list -l /dev/null' not ok 95 - Check STDERR # Failed test 'Check STDERR' # at t/lib/Test/UBH.pm line 260. # --- Got # +++ Expected # @@ -1 +1,2 @@ # -'' # +'List file t/8mn4dawfHl/list isn\'t readable, skipping at # unburden-home-dir line n. # +' # Looks like you failed 1 test of 98. It's running chmod foo cat foo, and expecting it to fail. It succeeds for me as I have a better simulation of root: I'm running the build as very-nearly root on a VM. (root in an unpriviliged LXC container). The full build log isn't much more useful; sorry for missing some important parts in the initial report: https://paste.debian.net/260610/ My specific bug is probably invalid, in this case? I don't think we expect the builds to pass as root. Weird test, though. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
