ubuntu 20.04: libnss-winbind:386 should remain

Bug #1861316 reported by msaxl
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
High
Rafael David Tinoco

Bug Description

Ubuntu 20.04 limits the available i386 packages.
There are some applications and its dependencies that are kept in i386.

I think libnss libraries/plugins should be available in both archs since having them only on one arch might be confusing (ex. in wine the %USERNAME% variable could be uid or the username)

since essentially libnss-winbind is compiled only the package is not assembled I think the work maintaining this package is quite low (libwbclient0:i386 already is available)

https://discourse.ubuntu.com/t/community-process-for-32-bit-compatibility/12598/57

Related branches

Paride Legovini (paride)
tags: added: server-triage-discuss
Paride Legovini (paride)
tags: removed: server-triage-discuss
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi msaxl,
some background can be found in bug 1858479 [1] which lead to upload [2] dropping the package. Thanks for already bringing it up in discourse [3] btw!

We subscribed Steve Langasek to this bug so he can consider and give you an authoritative answer since he is managing the majority of the i386 removal.

[1]: https://bugs.launchpad.net/ubuntu/+source/rdma-core/+bug/1858479
[2]: https://launchpad.net/ubuntu/+source/samba/2:4.11.1+dfsg-3ubuntu2
[3]: https://discourse.ubuntu.com/t/community-process-for-32-bit-compatibility/12598/57

Revision history for this message
Steve Langasek (vorlon) wrote : Re: [Bug 1861316] Re: ubuntu 20.04: libnss-winbind:386 should remain

The removal of libnss-winbind was based on the fact that it had not been identified as a package we wanted to keep, and it had additional dependencies that were not also included in the i386 set which made it uninstallable. If there is a reason to keep it (which from the discourse discussion and this bug I agree there is), then we can readd it and seed it so that its dependencies will also be white listed.

I don't immediately see why it was uninstallable before (and therefore removed), but I do see that at minimum we will also need to readd the winbind and samba-common-bin binary packages as well.

Bryce Harrington (bryce)
Changed in samba (Ubuntu):
importance: Undecided → High
status: New → Triaged
tags: added: server-next
Revision history for this message
Rafael David Tinoco (rafaeldtinoco) wrote :

I'll go ahead and re-add those in a MR soon, based on what @vorlon said.

Changed in samba (Ubuntu):
assignee: nobody → Rafael David Tinoco (rafaeldtinoco)
Revision history for this message
Rafael David Tinoco (rafaeldtinoco) wrote :

$ ls *common-bin*.deb *nss*.deb
libnss-winbind_4.11.1+dfsg-3ubuntu4_i386.deb samba-common-bin_4.11.1+dfsg-3ubuntu4_i386.deb

I'm pushing a MR and referring this bug for reviewing/acceptance.

Revision history for this message
Rafael David Tinoco (rafaeldtinoco) wrote :
Revision history for this message
Rafael David Tinoco (rafaeldtinoco) wrote :

Related bug:
https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1862928
As python-crypto needed a rebuild to allow libnss-winbind and winbind to be installable (due to its dependencies).

Revision history for this message
Rafael David Tinoco (rafaeldtinoco) wrote :
Changed in samba (Ubuntu):
status: Triaged → In Progress
Revision history for this message
Rafael David Tinoco (rafaeldtinoco) wrote :

I just pushed the merge and uploaded source code.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package samba - 2:4.11.1+dfsg-3ubuntu4

---------------
samba (2:4.11.1+dfsg-3ubuntu4) focal; urgency=medium

   * Ubuntu i386 binary compatibility effort: (LP: #1861316)
    - debian/rules:
        + re-enable the following binary packages generation:
          - libnss-winbind
          - samba-common-bin
          - python3-samba
          - winbind

 -- Rafael David Tinoco <email address hidden> Thu, 06 Feb 2020 14:42:38 +0000

Changed in samba (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers