01.08.2024 15:02, antonio wrote:
Package: samba-common
Version: 2:4.21.0~rc1+dfsg-1
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
to inform that the latest updates of "samba" packages are blocked because
"samba-common" rel. 2:4.21.0~rc1+really4.20.2+dfsg-11 does not seem to be
present in Debian/sid repository (even if it is present on
"https://packages.debian.org/sid/samba-common"; it is present and on
"snapshot.debian.org
"https://snapshot.debian.org/archive/debian/20240730T204830Z/pool/main/s/samba/samba-
common_4.21.0~rc1%2Breally4.20.2%2Bdfsg-11_all.deb") so I had to manually
download this package from the snapshot site for continue the updates.
The prob here is quite a bit complex.
Initial issue was me uploading 4.21.0-rc1 to unstable instead of experimental
(a mistake easy to make), noticing this immediately and trying to cancel the
upload (upload queue processing is delayed, and I had plenty of time to cancel
it). Unfortunately due to a combination of issues, the cancel didn't work,
despite me asking for additional help in time, and the upload has been accepted.
Next I tried my best to fix it by re-uploading 4.20 pretending to be 4.21
(hence the fancy version number). But since ldb components use their own
version number, it also didn't work right. Here, it is quite difficult to
find out why the builds which are successful aren't installed into the archive,
and even already installed builds gets removed as you found out, - it turns
out the reason is that ldb version in the new 4.20 upload is less than already
existing ldb from 4.21, so the upload is cancelled in this strange way.
Unless there's a more accurate way to work around these debian infrastructure
issues, I'll keep samba broken in unstable until the next upstream release
candidate within 2 weeks, and will upload the regular rc2 to unstable,
despite it isn't ready for production yet and I planned to upload 4.21 to
unstable no earlier than 4.21.1.
Thanks,
/mjt
