On 25/07/12 14:05, Georges Khaznadar wrote:
Hello Lucas, the bug you reported does not seems to be reproducible.
The error during the creation of a directory refers to a directory named
/sbuild-nonexistent, which is referred by no environment variable when I
attempt a pbuilder login.
The
On 25/07/12 at 14:05 +0200, Georges Khaznadar wrote:
Hello Lucas, the bug you reported does not seems to be reproducible.
The error during the creation of a directory refers to a directory named
/sbuild-nonexistent, which is referred by no environment variable when I
attempt a pbuilder
Hello Sebastian,
I suspected some behavior like this.
However when I launch pbuilder, the variable $HOME is not set to
/sbuild-nonexistent but it is set to /root (which exists).
So I have two and a half questions:
- which is the tool used to check the packages? I currently use
pbuilder, but
Hi Georges,
On 25/07/12 14:50, Georges Khaznadar wrote:
- which is the tool used to check the packages? I currently use
pbuilder, but the errors are reported from some other tool.
sbuild. You should be able to reproduce the problem with pbuilder as well. Just
set HOME to something
Source: pycode-browser
Version: 20120614+git+b041dd2-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120724 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
5 matches
Mail list logo
