Your message dated Fri, 12 Jul 2024 13:29:06 +0300
with message-id <[email protected]>
and subject line Re: [Pkg-samba-maint] Bug#1076196: samba-ad-dc: Samba AD-DC
does not start due to missing files
has caused the Debian Bug report #1076196,
regarding samba-ad-dc: Samba AD-DC does not start due to missing files
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.)
--
1076196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076196
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: samba-ad-dc
Version: 2:4.17.12+dfsg-0+deb12u1
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
The change due to #1051770 which moved crucial domain controller files
to the previously optional metapackage has caused our Samba domain
controller to fail to start. So far a minor inconvenience, one could
blame us for not having samba-ad-dc installed.
However, installing the samba-ad-dc package did no fix the problem,
because for some reason the older package from stable was selected
(samba-ad-dc 4.17) instead of the one in the backport repo. It is
necessary to specify the version to have APT install it.
To avoid existing systems breaking I would like to recommend either
setting a hard dependecy between versions of samba-ad-dc and samba to ensure
that the older samba-ad-dc (<= 4.19) metapackage is not installed alongside
the newer samba (>4.20) package, or reverting the change due to #1051770
The following command outputs show the issue: samba-ad-dc 4.20 is not
selected alongside samba even though it had since been installed.
root@dc-01-prod:~# apt-cache policy samba
samba:
Installed: 2:4.19.6+dfsg-3~bpo12+1
Candidate: 2:4.20.2+dfsg-2~bpo12+2
Version table:
2:4.20.2+dfsg-2~bpo12+2 100
100 http://deb.debian.org/debian bookworm-backports/main amd64 Packages
*** 2:4.19.6+dfsg-3~bpo12+1 100
100 /var/lib/dpkg/status
2:4.17.12+dfsg-0+deb12u1 500
500 http://deb.debian.org/debian bookworm/main amd64 Packages
500 http://security.debian.org/debian-security bookworm-security/main
amd64 Packages
2:4.17.9+dfsg-0+deb12u3 500
500 http://deb.debian.org/debian bookworm-updates/main amd64 Packages
root@dc-01-prod:~# apt-cache policy samba samba-ad-dc
samba:
Installed: 2:4.19.6+dfsg-3~bpo12+1
Candidate: 2:4.20.2+dfsg-2~bpo12+2
Version table:
2:4.20.2+dfsg-2~bpo12+2 100
100 http://deb.debian.org/debian bookworm-backports/main amd64 Packages
*** 2:4.19.6+dfsg-3~bpo12+1 100
100 /var/lib/dpkg/status
2:4.17.12+dfsg-0+deb12u1 500
500 http://deb.debian.org/debian bookworm/main amd64 Packages
500 http://security.debian.org/debian-security bookworm-security/main
amd64 Packages
2:4.17.9+dfsg-0+deb12u3 500
500 http://deb.debian.org/debian bookworm-updates/main amd64 Packages
samba-ad-dc:
Installed: 2:4.17.12+dfsg-0+deb12u1
Candidate: 2:4.17.12+dfsg-0+deb12u1
Version table:
2:4.20.2+dfsg-2~bpo12+2 100
100 http://deb.debian.org/debian bookworm-backports/main amd64 Packages
*** 2:4.17.12+dfsg-0+deb12u1 500
500 http://deb.debian.org/debian bookworm/main amd64 Packages
500 http://security.debian.org/debian-security bookworm-security/main
amd64 Packages
100 /var/lib/dpkg/status
2:4.17.9+dfsg-0+deb12u3 500
500 http://deb.debian.org/debian bookworm-updates/main amd64 Packages
root@dc-01-prod:~# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
python3-anyio python3-click python3-colorama python3-dnspython python3-h11
python3-h2 python3-hpack python3-httpcore
python3-httpx python3-hyperframe python3-markdown-it python3-mdurl
python3-requests-toolbelt python3-rfc3986 python3-rich
python3-sniffio
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
linux-image-6.1.0-22-amd64
The following packages will be upgraded:
base-files bash curl distro-info-data dns-root-data intel-microcode
krb5-locales krb5-user libbluetooth3 libcurl3-gnutls
libcurl4 libfreetype6 libglib2.0-0 libglib2.0-data libgnutls30
libgssapi-krb5-2 libgssrpc4 libk5crypto3 libkadm5clnt-mit12
libkadm5srv-mit12 libkdb5-10 libkrb5-3 libkrb5support0 libldb2 libltdl7
libndp0 libnss-systemd libnss-winbind libpam-systemd
libpam-winbind libpq5 libpython3.11 libpython3.11-minimal
libpython3.11-stdlib libseccomp2 libssl3 libsystemd-shared
libsystemd0 libudev1 libwbclient0 linux-image-amd64 nano openssh-client
openssh-server openssh-sftp-server openssl postfix
postfix-pcre python3-idna python3-ldb python3-samba python3.11
python3.11-minimal qemu-guest-agent samba samba-ad-provision
samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules
systemd systemd-sysv udev winbind wpasupplicant
66 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 121 MB of archives.
After this operation, 413 MB of additional disk space will be used.
Do you want to continue? [Y/n] ^C
-- System Information:
Debian Release: 12.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-21-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages samba-ad-dc depends on:
ii samba 2:4.19.6+dfsg-3~bpo12+1
ii samba-dsdb-modules 2:4.19.6+dfsg-3~bpo12+1
ii samba-vfs-modules 2:4.19.6+dfsg-3~bpo12+1
ii winbind 2:4.19.6+dfsg-3~bpo12+1
Versions of packages samba-ad-dc recommends:
ii libnss-winbind 2:4.19.6+dfsg-3~bpo12+1
ii libpam-winbind 2:4.19.6+dfsg-3~bpo12+1
ii samba-ad-provision 2:4.19.6+dfsg-3~bpo12+1
samba-ad-dc suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
12.07.2024 12:50, Béla Becker wrote:
Package: samba-ad-dc
Version: 2:4.17.12+dfsg-0+deb12u1
You file a bug against backports version but not against
the version you specified. JFYI.
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
The change due to #1051770 which moved crucial domain controller files
to the previously optional metapackage has caused our Samba domain
controller to fail to start. So far a minor inconvenience, one could
blame us for not having samba-ad-dc installed.
However, installing the samba-ad-dc package did no fix the problem,
because for some reason the older package from stable was selected
(samba-ad-dc 4.17) instead of the one in the backport repo. It is
necessary to specify the version to have APT install it.
To avoid existing systems breaking I would like to recommend either
setting a hard dependecy between versions of samba-ad-dc and samba to ensure
that the older samba-ad-dc (<= 4.19) metapackage is not installed alongside
the newer samba (>4.20) package, or reverting the change due to #1051770
I understand what you're writing about.
Neither of these will be done, like it or not.
You're using backports. This is sort of like unstable, because essentially
it is a rebuild from unstable, just done at times when it seems to be more
stable than completely unstable. You have to understand a little bit how
these things work. But this is not the point really.
The point is that once you use backports, again, because this is how backports
work, you have to understand how to install ADDITIONAL packages from there.
Including this samba-ad-dc package which was entirely optional before (I
wanted it to be like now even in bookworm, but it was too close to the freeze).
In particular, you have to install the right version of samba-ad-dc.
The minimal what I can add is to mention this (bpo) in the warning message
and in the NEWS file.
I can't change current samba-ad-dc package in bookworm pro-actively. It
will be the way it is now, - first, since it is arch-all, I can't depend
on the same version anyway, and even if I did, changing it in the next point-
release of bookworm wont fix multiple installations which don't update to
point releases.
This problem happens with backports only - because of the very specific
way how backports work. It wont happen when you upgrade from bookworm to
trixie, since there, default release will be trixie already and apt will
choose the right version of samba-ad-dc automatically (and it already
prefers to install packages of the same version).
So if anything, the package version of this bug report is specified wrongly.
And no, I definitely wont revert the change just because someone does
not know how to use backports.
Thanks, and sorry for being unhelpful here. Unfortunately, as they say,
it's impossible to help everyone since each one has different, often
contradictional, requirements.
/mjt
--- End Message ---
