I don't know, if it is important, because new things will be install:
Die folgenden Pakete werden ENTFERNT:
libndr-standard0 libndr0 libsamba-credentials0 libsamba-hostconfig0 libsamba-util0 samba-tools
Die folgenden NEUEN Pakete werden installiert:
libbasicusageenvironment0 libcrack2 libgroupsock1 liblivemedia13 libpwquality-common libpwquality1 libsubunit0 libusageenvironment1
python-crypto python-samba samba-dsdb-modules samba-libs
I won't try it and will wait a little time.
Ich weiß nicht, ob es wirklich wichtig ist, weil auch neue Pakete eingepflegt werden. Trotzdem werde ich erst einmal die Füsse stillhalten.
Greeting from the voyager
sidlix
Similar removals here:
Calculating upgrade... Done
The following packages will be REMOVED:
libndr0 libsamba-credentials0 libsamba-hostconfig0 libsamba-util0 samba-tools swat
The following NEW packages will be installed:
libhdb9-heimdal libkdc2-heimdal libsubunit0 python-crypto python-samba samba-dsdb-modules samba-libs tdb-tools
The following packages have been kept back:
libxvmcnvidia1
The following packages will be upgraded:
libnss-winbind libpam-winbind libsmbclient libwbclient0 samba samba-common samba-common-bin smbclient winbind
9 upgraded, 8 newly installed, 6 to remove and 1 not upgraded.
Something to do with moving to a "unified" samba-package I think - if I interpret the info digged out of packages.samba.org correctly...
Quote
samba (2:4.0.10+dfsg-2) unstable; urgency=low
* First upload the unified samba 4.x package to unstable.
Thanks to everyone who worked on these packages all these years.
* Remove Noël from uploaders. Thanks for you work on the samba packages.
* Add myself to uploaders.
-- Ivo De Decker <ivo> Sat, 12 Oct 2013 11:05:55 +0200
apt-show-versions samba
samba:amd64/unstable 2:3.6.19-1 upgradeable to 2:4.0.10+dfsg-2
Short update:
I let d-u get on with the removals and at least in my setup nothing broke :)