ubuntu-packaging-guide-team team mailing list archive

[Noel McLoughlin <noel.mcloughlin@xxxxxxxxx>]

Public bug reported:

Ubuntu 16.04 just works: Winbind was a smooth experience. We install
`winbind`, `libnss-winbind`, and `libpam-winbind` using APT
successfully, join the Domain/Realm, and start winbind with systemd!

Ubuntu 18.04 is regression: The `winbind` package breaks APT/DPGK
package manager because `/var/lib/dpkg/info/winbind.postinst` is trying
to start the service - that's bad regression.

I need package-manager (apt/dpkg) to handle packages, and service-
manager (systemd/upstart) to manage services. Can the winbind package
maintainer do anything to reverse the regression?

I have been reading up on debhelper but cannot find a way to prevent
breaking apt.

```
~$ dpkg-query --list | grep winbind
iU  libnss-winbind:amd64                       2:4.7.6+dfsg~ubuntu-0ubuntu2.6      amd64        Samba nameservice integration plugins
iU  libpam-winbind:amd64                       2:4.7.6+dfsg~ubuntu-0ubuntu2.6      amd64        Windows domain authentication integration plugin
ii  libwbclient0:amd64                         2:4.7.6+dfsg~ubuntu-0ubuntu2.6      amd64        Samba winbind client library
iF  winbind                                    2:4.7.6+dfsg~ubuntu-0ubuntu2.6      amd64        service to resolve user and gro

... trace ...

Active: failed (Result: exit-code) since Sun 2019-03-03 11:30:11 MST; 19ms ago
     Docs: man:winbindd(8)
           man:samba(7)
           man:smb.conf(5)
  Process: 43699 ExecStart=/usr/sbin/winbindd --foreground --no-process-group $WINBINDOPTIONS (code=exited, status=1/FAILURE)
 Main PID: 43699 (code=exited, status=1/FAILURE)

Mar 03 11:30:11 myhost1 systemd[1]: Starting Samba Winbind Daemon...
Mar 03 11:30:11 myhost1 winbindd[43699]: [2019/03/03 11:30:11.597251,  0] ../source3/winbindd/winbindd_cache.c:3170(initialize_winbindd_cache)
Mar 03 11:30:11 myhost1 winbindd[43699]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
Mar 03 11:30:11 myhost1 winbindd[43699]: [2019/03/03 11:30:11.600710,  0] ../source3/winbindd/winbindd_util.c:891(init_domain_list)
Mar 03 11:30:11 myhost1 winbindd[43699]:   Could not fetch our SID - did we join?
Mar 03 11:30:11 myhost1 winbindd[43699]: [2019/03/03 11:30:11.600854,  0] ../source3/winbindd/winbindd.c:1366(winbindd_register_handlers)
Mar 03 11:30:11 myhost1 winbindd[43699]:   unable to initialize domain list
Mar 03 11:30:11 myhost1 systemd[1]: winbind.service: Main process exited, code=exited, status=1/FAILURE
Mar 03 11:30:11 myhost1 systemd[1]: winbind.service: Failed with result 'exit-code'.
Mar 03 11:30:11 myhost1 systemd[1]: Failed to start Samba Winbind Daemon.
dpkg: error processing package winbind (--configure):
 installed winbind package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of libpam-winbind:amd64:
 libpam-winbind:amd64 depends on winbind (= 2:4.7.6+dfsg~ubuntu-0ubuntu2.6); however:
  Package winbind is not configured yet.

dpkg: error processing package libpam-winbind:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libnss-winbind:amd64:
 libnss-winbind:amd64 depends on winbind (= 2:4.7.6+dfsg~ubuntu-0ubuntu2.6); however:
  Package winbind is not configured yet.

dpkg: error processing package libnss-winbind:amd64 (--configure):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Errors were encountered while processing:
 winbind
 libpam-winbind:amd64
 libnss-winbind:amd64
```

** Affects: ubuntu-packaging-guide
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Packaging Guide Team, which is subscribed to Ubuntu Packaging Guide.
https://bugs.launchpad.net/bugs/1818431

Title:
  Regression in winbind package postinstall script

Status in Ubuntu Packaging Guide:
  New

Bug description:
  Ubuntu 16.04 just works: Winbind was a smooth experience. We install
  `winbind`, `libnss-winbind`, and `libpam-winbind` using APT
  successfully, join the Domain/Realm, and start winbind with systemd!

  Ubuntu 18.04 is regression: The `winbind` package breaks APT/DPGK
  package manager because `/var/lib/dpkg/info/winbind.postinst` is
  trying to start the service - that's bad regression.

  I need package-manager (apt/dpkg) to handle packages, and service-
  manager (systemd/upstart) to manage services. Can the winbind package
  maintainer do anything to reverse the regression?

  I have been reading up on debhelper but cannot find a way to prevent
  breaking apt.

  ```
  ~$ dpkg-query --list | grep winbind
  iU  libnss-winbind:amd64                       2:4.7.6+dfsg~ubuntu-0ubuntu2.6      amd64        Samba nameservice integration plugins
  iU  libpam-winbind:amd64                       2:4.7.6+dfsg~ubuntu-0ubuntu2.6      amd64        Windows domain authentication integration plugin
  ii  libwbclient0:amd64                         2:4.7.6+dfsg~ubuntu-0ubuntu2.6      amd64        Samba winbind client library
  iF  winbind                                    2:4.7.6+dfsg~ubuntu-0ubuntu2.6      amd64        service to resolve user and gro

  ... trace ...

  Active: failed (Result: exit-code) since Sun 2019-03-03 11:30:11 MST; 19ms ago
       Docs: man:winbindd(8)
             man:samba(7)
             man:smb.conf(5)
    Process: 43699 ExecStart=/usr/sbin/winbindd --foreground --no-process-group $WINBINDOPTIONS (code=exited, status=1/FAILURE)
   Main PID: 43699 (code=exited, status=1/FAILURE)

  Mar 03 11:30:11 myhost1 systemd[1]: Starting Samba Winbind Daemon...
  Mar 03 11:30:11 myhost1 winbindd[43699]: [2019/03/03 11:30:11.597251,  0] ../source3/winbindd/winbindd_cache.c:3170(initialize_winbindd_cache)
  Mar 03 11:30:11 myhost1 winbindd[43699]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
  Mar 03 11:30:11 myhost1 winbindd[43699]: [2019/03/03 11:30:11.600710,  0] ../source3/winbindd/winbindd_util.c:891(init_domain_list)
  Mar 03 11:30:11 myhost1 winbindd[43699]:   Could not fetch our SID - did we join?
  Mar 03 11:30:11 myhost1 winbindd[43699]: [2019/03/03 11:30:11.600854,  0] ../source3/winbindd/winbindd.c:1366(winbindd_register_handlers)
  Mar 03 11:30:11 myhost1 winbindd[43699]:   unable to initialize domain list
  Mar 03 11:30:11 myhost1 systemd[1]: winbind.service: Main process exited, code=exited, status=1/FAILURE
  Mar 03 11:30:11 myhost1 systemd[1]: winbind.service: Failed with result 'exit-code'.
  Mar 03 11:30:11 myhost1 systemd[1]: Failed to start Samba Winbind Daemon.
  dpkg: error processing package winbind (--configure):
   installed winbind package post-installation script subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of libpam-winbind:amd64:
   libpam-winbind:amd64 depends on winbind (= 2:4.7.6+dfsg~ubuntu-0ubuntu2.6); however:
    Package winbind is not configured yet.

  dpkg: error processing package libpam-winbind:amd64 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of libnss-winbind:amd64:
   libnss-winbind:amd64 depends on winbind (= 2:4.7.6+dfsg~ubuntu-0ubuntu2.6); however:
    Package winbind is not configured yet.

  dpkg: error processing package libnss-winbind:amd64 (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Errors were encountered while processing:
   winbind
   libpam-winbind:amd64
   libnss-winbind:amd64
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-packaging-guide/+bug/1818431/+subscriptions