Discussion:
Bug#1077749: samba-common: is missing its sid/repository (but is present in snapshot.debian.org)
(too old to reply)
antonio
2024-08-01 12:10:02 UTC
Permalink
Package: samba-common
Version: 2:4.21.0~rc1+dfsg-1
Severity: normal
X-Debbugs-Cc: ***@gmail.com

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.
Thanks,
Antonio


-- Package-specific info:
* /etc/samba/smb.conf present, but not attached

-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (700, 'unstable'), (520, 'stable-security'), (500, 'stable-updates'), (500, 'stable'), (100, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.9.12-1-liquorix-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages samba-common depends on:
ii ucf 3.0043+nmu1

Versions of packages samba-common recommends:
ii samba-common-bin 2:4.21.0~rc1+dfsg-1

samba-common suggests no packages.

-- Configuration Files:
/etc/samba/gdbcommands [Errno 2] File o directory non esistente: '/etc/samba/gdbcommands'

-- debconf information excluded
Antonio
2024-08-01 12:40:02 UTC
Permalink
$ apt policy samba-common
samba-common:
 Installato: 2:4.21.0~rc1+dfsg-1
 Candidato:  2:4.21.0~rc1+dfsg-1
 Tabella versione:
*** 2:4.21.0~rc1+dfsg-1 100
       100 /var/lib/dpkg/status
    2:4.17.12+dfsg-0+deb12u1 520
       500 https://deb.debian.org/debian stable/main amd64 Packages
       520 https://security.debian.org/debian-security
stable-security/main amd64 Packages
    2:4.17.9+dfsg-0+deb12u3 500
       500 https://deb.debian.org/debian stable-updates/main amd64 Packages

$ apt policy samba-common-bin
samba-common-bin:
 Installato: 2:4.21.0~rc1+dfsg-1
 Candidato:  2:4.21.0~rc1+dfsg-1
 Tabella versione:
*** 2:4.21.0~rc1+dfsg-1 700
       700 https://deb.debian.org/debian sid/main amd64 Packages
       100 /var/lib/dpkg/status
    2:4.17.12+dfsg-0+deb12u1 520
       500 https://deb.debian.org/debian stable/main amd64 Packages
       520 https://security.debian.org/debian-security
stable-security/main amd64 Packages
    2:4.17.9+dfsg-0+deb12u3 500
       500 https://deb.debian.org/debian stable-updates/main amd64 Packages

# Sid
Types: deb
URIs: https://deb.debian.org/debian
Suites: sid
Components: main contrib non-free non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
Michael Tokarev
2024-08-02 08:40:01 UTC
Permalink
Post by antonio
Package: samba-common
Version: 2:4.21.0~rc1+dfsg-1
Severity: normal
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

Loading...