On Fri, Apr 27, 2012 at 12:04:29PM +, Adam Conrad wrote:
Closing this bug, as it was discovered that the failing binaries
in question were from debian-ports, not from debian.org. Maintaining
backward compat with non-official archives is a non-starter, and
hopefully most people know how to
On Sun, Apr 29, 2012 at 04:57:03PM +0200, Philipp Kern wrote:
On Fri, Apr 27, 2012 at 12:04:29PM +, Adam Conrad wrote:
Closing this bug, as it was discovered that the failing binaries
in question were from debian-ports, not from debian.org. Maintaining
backward compat with non-official
On Sun, Apr 29, 2012 at 04:13:17PM +0100, Steve McIntyre wrote:
On Sun, Apr 29, 2012 at 04:57:03PM +0200, Philipp Kern wrote:
However it would be nice if you could avoid breaking all our official
buildds in the process next time. I.e. a notice *before* breaking the
ports' users would've
On Sun, 29 Apr 2012, Adam Conrad wrote:
To be fair, I had no way of knowing that the Debian buildds were running
binaries from debian-ports (or, more accurately, binaries built against
debian-ports by DSA).
DSA didn't build these binaries. schroot on armhf comes from the
buildd.d.o
Package: libc6
Version: 2.13-30
Severity: grave
Dear Maintainer,
In debugging why /usr/sbin/samhain returned 'No such file or directory', it
became
evident that the symlink in the subject line is not set:
lfilipoz@hasse:~$ ldd /usr/sbin/samhain
...
/lib/ld-linux.so.3 =
5 matches
Mail list logo
