Your message dated Wed, 25 Apr 2012 11:26:59 +0200
with message-id <[email protected]>
and subject line Re: Bug#669606: Acknowledgement (nmu:
samba4_4.0.0~alpha19+dfsg1-5)
has caused the Debian Bug report #669606,
regarding nmu: samba4_4.0.0~alpha19+dfsg1-5
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
669606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669606
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: binnmu
nmu samba4_4.0.0~alpha19+dfsg1-5 . amd64 . -m "rebuild against libldb1 1:1.1.6"
samba4 (4.0.0~alpha19+dfsg1-5) was uploaded about 2.5 hours after
ldb (1:1.1.6-1).
Depending on the timing it was built against 1.1.5 or 1.1.6.
There is a strict versioned dependency of libsamdb0 against the upstream
version of ldb used at build time, making libsamdb0 uninstallable in
unstable (amd64 at least):
Package: libsamdb0
Version: 4.0.0~alpha19+dfsg1-5
Depends: libldb1 (<< 1:1.1.6~), libldb1 (>> 1:1.1.5~), ...
A rebuild in a clean sid chroot works fine.
I don't know if any other architectures than amd64 (maintainer supplied
binaries, probably built while 1.1.6 was not on the mirrors, yet) are
affected by this and need to be rebuild, too.
How could I check this?
Andreas
--- End Message ---
--- Begin Message ---
Version: 4.0.0~alpha19+dfsg1-6
fixed by sourceful upload
Andreas
--- End Message ---
