Your message dated Tue, 1 Sep 2026 09:32:19 +0300
with message-id <[email protected]>
and subject line Re: libsmbclient0 incompatibility on multi-arch
has caused the Debian Bug report #1129666,
regarding libsmbclient0 incompatibility on multi-arch
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.)
--
1129666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1129666
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libsmbclient0:amd64, libsmbclient0:i386
Version: 2:4.23.6+dfsg-1+b1
Architectures amd64 and i386 share man page
/usr/share/man/man7/libsmbclient.7.gz
which are different w.r.t. the last date line:
03/03/2026 vs. 02/03/2026
This prevents the installation from completion with severe consequences for
all related packages depending on it.
I am using Debian GNU/Linux 6.19, kernel 6.19.3-1-siduction-amd64.
--- End Message ---
--- Begin Message ---
On Wed, 4 Mar 2026 17:01:27 +0100 Wolfgang Thumser <[email protected]> wrote:
Package: libsmbclient0:amd64, libsmbclient0:i386
Version: 2:4.23.6+dfsg-1+b1
Please note the +b1 suffix in the version number.
Architectures amd64 and i386 share man page
/usr/share/man/man7/libsmbclient.7.gz
which are different w.r.t. the last date line:
03/03/2026 vs. 02/03/2026
This is not a samba bug. This is a debian infrastructure bug.
The bin-NMU uploads for different architectures should be done
at exactly the same time, or with a fixed timestamp, to prevent
such issues.
The problem here is that the changelog for bin-NMU has different
timestamp, which is reflected in the manpage date.
Thanks,
/mjt
--- End Message ---
