Hi, Harald Dunkel wrote: > I think you underestimate the problem.
Nope. > The next unattended upgrade (using the 2nd set of new samba 4.2 > packages) ran into a dependency problem: > Unpacking samba-libs:amd64 (2:4.2.10+dfsg-0+deb8u2) over > (2:4.2.10+dfsg-0+deb8u1) ... > dpkg: error processing archive > /var/cache/apt/archives/samba-libs_2%3a4.2.10+dfsg-0+deb8u2_amd64.deb > (--unpack): > trying to overwrite '/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0', > which is also in package samba 2:4.2.10+dfsg-0+deb8u1 > dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) [...] > Errors were encountered while processing: > /var/cache/apt/archives/samba-libs_2%3a4.2.10+dfsg-0+deb8u2_amd64.deb That's a known issue and probably will be fixed with a further regression update. > This won't go away. In another mail to this bug report, someone said, "apt-get install -f" fixed it for him. > Even worse, after this the samba package > seems to have lost the "automatically installed" flag: > > # dpkg -l samba [...] > iU samba 2:4.2.10+dfs amd64 SMB/CIFS file, print, and login s dpkg doesn't know anything about an "automatically installed" flag. Only apt, aptitude and friends do. Regards, Axel -- ,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE