[From nobody Tue Sep  1 07:35:05 2026
Received: (at 1129666-done) by bugs.debian.org; 1 Sep 2026 06:32:21 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 required=4.0 tests=BAYES_00,DKIM_SIGNED,
 DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS
 autolearn=ham autolearn_force=no
 version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 25; hammy, 123; neutral, 21; spammy,
 0. spammytokens: hammytokens:0.000-+--manpage, 0.000-+--H*F:U*mjt,
 0.000-+--H*F:D*tls.msk.ru, 0.000-+--H*RU:isrv.corpit.ru,
 0.000-+--H*RU:mjt@tls.msk.ru
Return-path: <mjt@tls.msk.ru>
Received: from isrv.corpit.ru ([212.248.84.144]:50325)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from <mjt@tls.msk.ru>) id 1x1I2f-009nEk-1e
 for 1129666-done@bugs.debian.org; Tue, 01 Sep 2026 06:32:21 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tls.msk.ru; s=202602;
 t=1788244326; bh=2YjzdhweKTnpQTOABZ9PUOErqoUuC+EKXvDMQA0mO84=;
 h=Date:To:References:Subject:From:In-Reply-To;
 b=l0YyhaP2xHvNYiasSiGpIEBuQSnTkcRH1pVgM1L+qvHB71ytNbYaXh9fH2H4+PqDM
 ejya4jj+NI8WZYaEvcBm1PtQ3paQEhMt5v7j0JT30OinE5JIcvKoGzbjCtfOFai1qX
 L+5P/Zzc09PvbMvy7FRKTBFBKiI8h2ZGvM9mDk4SZ6Vk+2B2V8TevszmY+5q7z3ZR6
 FYKNso8fYHF8g2VZknZWh3gAn6SWeSg2v3Aj4XPtvRWdajX7tYwVmPM/cPO6hhXXrp
 S4fWXmUemkP9Mqj2NVqz9Rf+i9N3riHK14PYVoqASXJQvpmzqD9WV0r2VOD3BYGYxU
 Hb+FiifV+33Zg==
Received: from tsrv.corpit.ru (tsrv.tls.msk.ru [192.168.177.2])
 by isrv.corpit.ru (Postfix) with ESMTP id BE2D01D0746
 for <1129666-done@bugs.debian.org>; Tue, 01 Sep 2026 09:32:06 +0300 (MSK)
Received: from [192.168.177.130] (mjt.wg.tls.msk.ru [192.168.177.130])
 by tsrv.corpit.ru (Postfix) with ESMTP id 2117141DA4B
 for <1129666-done@bugs.debian.org>; Tue, 01 Sep 2026 09:32:19 +0300 (MSK)
Message-ID: <f0aeabd3-3a76-46ce-becb-2fe9a05943ce@tls.msk.ru>
Date: Tue, 1 Sep 2026 09:32:19 +0300
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: 1129666-done@bugs.debian.org
References: <2113a48e-2d31-48ed-8e35-22f5fce27ec1@gmx.de>
 <2113a48e-2d31-48ed-8e35-22f5fce27ec1@gmx.de>
Subject: Re: libsmbclient0 incompatibility on multi-arch
Content-Language: en-US, ru-RU
From: Michael Tokarev <mjt@tls.msk.ru>
In-Reply-To: <2113a48e-2d31-48ed-8e35-22f5fce27ec1@gmx.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On Wed, 4 Mar 2026 17:01:27 +0100 Wolfgang Thumser <wothumser@gmx.de> 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]