Your message dated Fri, 1 Jun 2018 13:42:06 +0200
with message-id
<cafx5sbw-qizx1nzarhdj9hl5wjvbtyddvehapao+fpjguqw...@mail.gmail.com>
and subject line Re: [Pkg-samba-maint] Bug#900542: winbind: Can't upgrade
winbind to 2:4.5.12+dfsg-2+deb9u2(stretch) or 2:4.7.4+dfsg-2(buster)
has caused the Debian Bug report #900542,
regarding winbind: Can't upgrade winbind to 2:4.5.12+dfsg-2+deb9u2(stretch) or
2:4.7.4+dfsg-2(buster)
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.)
--
900542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900542
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: winbind
Version: 2:4.7.4+dfsg-2
Severity: normal
Tags: a11y
Dear Maintainer,
When I try to apt-get upgrade, winbind can't complete its process.
There are some problems.
1) Launch script can't work
error: /lib/security/pam_winbind.so not found.
However, /lib/x86_64-linux-gnu/security/pam_winbind.so exists.
2) Post install script couldn't work and apt-get upgrade failed.
When samba-ad-dc was launched, winbind is already in process and the upgrade
script try to launch winbind duplicately and failed upgrade.
3) winbind vendor preset: enable
Samba-ad-dc launch winbind as its child. It means there is no need to launch
winbind again, should be disable.
I confirmed the problem in both stretch and buster (2018-05-31)
-- Package-specific info:
* /etc/samba/smb.conf present, but not attached
* /etc/samba/dhcp.conf not present
-- System Information:
Debian Release: buster/sid
APT prefers stable
APT policy: (101, 'stable'), (100, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to ja_JP.UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to
ja_JP.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages winbind depends on:
ii libbsd0 0.9.1-1
ii libc6 2.27-3
ii libldap-2.4-2 2.4.46+dfsg-5
ii libpopt0 1.16-11
ii libtalloc2 2.1.11-2
ii libtdb1 1.3.15-4
ii libtevent0 0.9.36-2
ii libwbclient0 2:4.7.4+dfsg-2
ii lsb-base 9.20170808
ii samba-common 2:4.7.4+dfsg-2
ii samba-common-bin 2:4.7.4+dfsg-2
ii samba-libs 2:4.7.4+dfsg-2
winbind recommends no packages.
Versions of packages winbind suggests:
ii libnss-winbind 2:4.7.4+dfsg-2
ii libpam-winbind 2:4.7.4+dfsg-2
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2:4.8.0+dfsg-2
Le ven. 1 juin 2018 à 03:57, Tomoo Nomura <[email protected]> a écrit :
>
> Package: winbind
> Version: 2:4.7.4+dfsg-2
> Severity: normal
> Tags: a11y
>
> Dear Maintainer,
>
> When I try to apt-get upgrade, winbind can't complete its process.
> There are some problems.
>
> 1) Launch script can't work
> error: /lib/security/pam_winbind.so not found.
> However, /lib/x86_64-linux-gnu/security/pam_winbind.so exists.
What is your upgrade path (which origin debian version)? Can you post
/var/log/apt/term.log?
> 2) Post install script couldn't work and apt-get upgrade failed.
> When samba-ad-dc was launched, winbind is already in process and the
> upgrade script try to launch winbind duplicately and failed upgrade.
This part is fixed since 2:4.8.0+dfsg-2. Thus closing.
(https://salsa.debian.org/samba-team/samba/commit/e0dde22485ca6bfb488caa565a0ad1d199d68da9)
> 3) winbind vendor preset: enable
> Samba-ad-dc launch winbind as its child. It means there is no need to
> launch winbind again, should be disable.
>
> I confirmed the problem in both stretch and buster (2018-05-31)
Again, this is fixed in sid, soon to migrate in buster
Regards
--
Mathieu Parent
--- End Message ---
