** Description changed:
The bin:python3-samba package built from src:samba 4.21.x needs a new
dependency on bin:python3-cryptography[1]. This version of samba is
- currently in plucky-proposed.
+ currently in plucky-proposed, and was uploaded before Feature Freeze.
src:python-cryptography[2] has last built i386 packages for bionic.
Focal and later no longer have i386 builds.
As a result, this dependency is unsatisfiable in plucky/i386.
In comment #1 I checked if we could stop building src:samba for i386
entirely, and the short answer is no.
Therefore, for i386, my plan is to stop building python3-samba.
Reverse-dependencies:
$ reverse-depends python3-samba
Reverse-Recommends
==================
* samba [amd64 arm64 armhf ppc64el riscv64 s390x]
* samba-common-bin
Reverse-Depends
===============
* adsys [amd64 arm64 armhf ppc64el riscv64 s390x]
* freeipa-client-samba [amd64 arm64 armhf ppc64el riscv64 s390x]
* samba-ad-dc [amd64 arm64 armhf ppc64el riscv64 s390x]
* samba-testsuite [amd64 arm64 armhf ppc64el riscv64 s390x]
Packages without architectures listed are reverse-dependencies in:
amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
So for i386, bin:samba-common-bin is the only reverse dependency, and my
PR will drop that.
I'm not sure why that is not captured here[3]:
python3-samba
* Extra seed
Samba, the server, is not meant to be installable on i386. There are no
server packages even. The only i386 packages provided are libraries and
some smaller client utilities, but definitely not a server. Therefore I
believe it's ok to stop building bin:python3-samba(i386). However, I do
not know of a way to verify this before uploading and letting the Ubuntu
machinery try to migrate it.
Diff:
diff --git a/debian/control b/debian/control
index 0d6dba17230..f8dd58d6548 100644
--- a/debian/control
+++ b/debian/control
@@ -178,7 +178,7 @@ Depends: samba-common (= ${source:Version}),
${misc:Depends},
${python3:Depends},
${shlibs:Depends}
-Recommends: python3-samba,
+Recommends: python3-samba [!i386],
Suggests: heimdal-clients,
# moved libnet-keytab-samba4.so.0 & libRPC-WORKER-samba4.so.0
samba-libs=>samba-common-bin in 4.19.0~r1
# moved smbcontrol samba=>samba-common-bin in 4.20.0-2
diff --git a/debian/rules b/debian/rules
index 9d14e3469d6..7207bb627b7 100755
--- a/debian/rules
+++ b/debian/rules
@@ -143,7 +143,7 @@ endif
# Ubuntu i386 binary compatibility only effort: Disable some i386 packages
and modules
ifeq (${DEB_VENDOR}-${DEB_HOST_ARCH}, Ubuntu-i386)
-omit-pkgs += ctdb libpam-winbind samba samba-ad-dc samba-testsuite
samba-vfs-modules samba-vfs-ceph samba-vfs-glusterfs
+omit-pkgs += ctdb libpam-winbind samba samba-ad-dc samba-testsuite
samba-vfs-modules samba-vfs-ceph samba-vfs-glusterfs python3-samba
endif
# we had t64 transition (libsmbclient => libsmbclient0) for trixie
Builds:
https://launchpad.net/~ahasenack/+archive/ubuntu/samba-merge/+packages
- DEP8 tests on the above PPA: TBD
+ DEP8 tests on the above PPA: ppc64el just retried (infra failure), i386
+ has always failed (see https://autopkgtest.ubuntu.com/packages/samba),
+ and the rest is green:
+
+ $ lp-test-ppa -l -r plucky ppa:ahasenack/samba-merge -p samba
+ (...)
+ Results: (from
http://autopkgtest.ubuntu.com/results/autopkgtest-plucky-ahasenack-samba-merge/?format=plain)
+ samba @ amd64:
+ 01.03.25 21:56:20 Log 🗒️ ✅ Triggers:
samba/2:4.21.4+dfsg-1ubuntu2~ppa5
+ samba @ arm64:
+ 01.03.25 22:44:29 Log 🗒️ ✅ Triggers:
samba/2:4.21.4+dfsg-1ubuntu2~ppa5
+ samba @ armhf:
+ 01.03.25 21:56:56 Log 🗒️ ✅ Triggers:
samba/2:4.21.4+dfsg-1ubuntu2~ppa5
+ samba @ i386:
+ 01.03.25 21:53:18 Log 🗒️ ❌ Triggers:
samba/2:4.21.4+dfsg-1ubuntu2~ppa5
+ 791s cifs-share-access FAIL 🟥
+ 791s cifs-share-access-uring FAIL 🟥
+ 791s python-smoke FAIL 🟥
+ 791s smbclient-anonymous-share-list FAIL 🟥
+ 791s smbclient-authenticated-share-list FAIL 🟥
+ 791s smbclient-share-access FAIL 🟥
+ 791s smbclient-share-access-uring FAIL 🟥
+ 791s samba-ad-dc-provisioning-internal-dns FAIL 🟥
+ samba @ ppc64el:
+ 02.03.25 01:39:21 Log 🗒️ ⚪ Triggers:
+ No valid results
+ samba @ riscv64:
+ 12.02.25 17:29:32 Log 🗒️ ⚪ Triggers:
samba/2:4.21.3+dfsg-6ubuntu1~ppa2
+ No valid results
+ samba @ s390x:
+ 01.03.25 21:55:39 Log 🗒️ ✅ Triggers:
samba/2:4.21.4+dfsg-1ubuntu2~ppa5
+
[ RISKS ]
- It's plausible that someone could be relying on bin:python3-samba(i386) for
an out-of-archive application. That will no longer work after this update
lands. Therefore, if this is approved, it needs to be mentioned in the Plucky
release notes.
+ It's plausible that someone could be relying on bin:python3-samba@i386 for an
out-of-archive application. That will no longer work after this update lands.
Therefore, if this is approved, it needs to be mentioned in the Plucky release
notes.
1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086768
2. https://launchpad.net/ubuntu/+source/python-cryptography
3.
https://ubuntu-archive-team.ubuntu.com/germinate-output/i386.plucky/rdepends/samba/python3-samba
[ Original Description ]
Debian bug that made bin:python3-samba grow a depends on
bin:python3-cryptography: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1086768
src:python-cryptography has last built i386 packages for bionic. Focal
and later no longer have i386 builds.
As a result, this dependency is unsatisfiable in plucky/i386.
Unsatisfied dependencies:
python3-samba:i386 : Depends: python3-cryptography:i386 but it is not
installable
Samba itself is not meant to be installable on i386. There are no server
packages even. The only i386 packages provided are libraries and some
smaller utilities, but definitely not a server.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2099895
Title:
[FFe]: python3-samba depends on python3-cryptography which is not
available on i386
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/2099895/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
