Your message dated Thu, 14 May 2009 17:57:55 +0200
with message-id <[email protected]>
and subject line Re: Bug#528429: [Pkg-samba-maint] Bug#528429: samba: 3.3.3-1
BPO: pam_smbpass dependency and X86 Vista lsass.exe crash
has caused the Debian Bug report #528429,
regarding samba: 3.3.3-1 BPO: pam_smbpass dependency and X86 Vista lsass.exe
crash
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.)
--
528429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528429
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: samba
Version: 2:3.3.3-1~bpo50+1
Severity: minor
Hi, thanks for the upload to backports. Unfortunately the 3.3.3-1 can be
very helpfull for using KDE4's kmail or other programs creating (lock-)
files with strange names. This now really works, my CIFSxxxx files are
gone. BUT:
1) pam_smbpass.so has a dependency that removes the lenny pam package. My
workaround was to keep the old copy in /lib/security. Very odd please
Fix!
2) Bug#526905: samba: Vista also seen on x86. This is just for
information. A vista x86 ultimate installed in VirtualBox 2.1.4 ose gets
killed when booted after having joined the samba domain if the network
is connected at boot time.
Thanks again, 3.3.3-1 works fine, Vista is not important anyhow.
-- System Information:
Debian Release: 5.0.1
APT prefers proposed-updates
APT policy: (500, 'proposed-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-15-x86 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages samba depends on:
ii adduser 3.110 add and remove users and groups
ii debconf [debcon 1.5.24 Debian configuration management sy
ii libacl1 2.2.47-2 Access control list shared library
ii libattr1 1:2.4.43-2 Extended attribute shared library
ii libc6 2.7-18 GNU C Library: Shared libraries
ii libcap2 2.11-2 support for getting/setting POSIX.
ii libcomerr2 1.41.3-1 common error description library
ii libcups2 1.3.8-1lenny5 Common UNIX Printing System(tm) -
ii libgnutls26 2.4.2-6+lenny1 the GNU TLS library - runtime libr
ii libkrb53 1.6.dfsg.4~beta1-5lenny1 MIT Kerberos runtime libraries
ii libldap-2.4-2 2.4.11-1 OpenLDAP libraries
ii libpam-modules 1.0.1-5+lenny1 Pluggable Authentication Modules f
ii libpam-runtime 1.0.1-5+lenny1 Runtime support for the PAM librar
ii libpam0g 1.0.1-5+lenny1 Pluggable Authentication Modules l
ii libpopt0 1.14-4 lib for parsing cmdline parameters
ii libtalloc1 1.2.0~git20080616-1 hierarchical pool based memory all
ii libwbclient0 2:3.3.3-1~bpo50+1 Samba winbind client library
ii logrotate 3.7.1-5 Log rotation utility
ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip
ii procps 1:3.2.7-11 /proc file system utilities
ii samba-common 2:3.3.3-1~bpo50+1 common files used by both the Samb
ii update-inetd 4.31 inetd configuration file updater
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime
samba recommends no packages.
Versions of packages samba suggests:
pn ctdb <none> (no description available)
pn ldb-tools <none> (no description available)
ii openbsd-inetd [inet-superse 0.20080125-2 The OpenBSD Internet Superserver
pn smbldap-tools <none> (no description available)
-- debconf information excluded
--- End Message ---
--- Begin Message ---
Quoting Steve Langasek ([email protected]):
> > I'm tempted to close this bug report, though it's good to know that
> > libpam-smbpass from bacports.org is not usable....
>
> If you think the report should be closed, I'm happier for it; I wasn't going
> to presume to close it myself, because I wasn't sure if this was one of the
> conditions for packages being included on bpo.
Closing now. I don't remember seeing any requirement to track down
bugs in bpo through the BTS.
Still, I'll consider trying to make libpam-smbpass usable on
backports.
After all, it just needs to unmerge the change which added support for
pam-authupdate. If that seems easy to maintain in the long term, I'll
try the opportunity of the preparation of the 3.3.4-1 backport (which
I can prepare now as that version just entered testing).
signature.asc
Description: Digital signature
--- End Message ---