DU wants to remove libpam-systemd [Solved]

Started by clubex, 2014/02/12, 13:48:45

Previous topic - Next topic

clubex

Today's du want to remove libpam-systemd. Should we let it go or wait?

dibl

Better wait -- it gets worse:


The following packages will be REMOVED:
  libpam-systemd systemd-gui systemd-ui
The following NEW packages will be installed:
  libdb5.3:i386
The following packages have been kept back:
  libsystemd-daemon0 libsystemd-journal0 libsystemd-login0 systemd systemd-sysv
The following packages will be upgraded:
  libgudev-1.0-0 libltdl-dev libltdl7 libsasl2-2 libsasl2-2:i386 libsasl2-modules libsasl2-modules:i386 libsasl2-modules-db libsasl2-modules-db:i386
  libsqlite3-0 libsqlite3-0:i386 libtool libudev1 openssh-client openssh-server printer-driver-foo2zjs printer-driver-foo2zjs-common qtchooser udev
19 upgraded, 1 newly installed, 3 to remove and 5 not upgraded.
Need to get 5,614 kB of archives.
After this operation, 1,705 kB of additional disk space will be used.
Do you want to continue? [Y/n] n


System76 Oryx Pro, Intel Core i7-11800H, ASRock B860 Pro-A, Intel Core Ultra 7 265KF, Nvidia GTX-1060, SSD 990 EVO Plus.

devil

#2
Nothing gets removed here, systemd 204-7 gets installed.


  icedove iceowl-extension libgraphite2-3 libgudev-1.0-0 libltdl7 libopenconnect2 libpam-systemd libsasl2-2 libsasl2-modules
libsasl2-modules-db libsqlite3-0 libsystemd-daemon0 libsystemd-journal0 libsystemd-login0 libudev1 moc openssh-client
openssh-server printer-driver-foo2zjs printer-driver-foo2zjs-common qtchooser siduction-settings-kde-december
siduction-settings-lightdm-gtk-december systemd systemd-sysv udev usb-modeswitch usb-modeswitch-data weechat weechat-core
weechat-curses weechat-plugins weechat-scripts
33 aktualisiert, 1 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.


The only thing that gets newly installed is libdb5.3.
No problems on multiarch nor on a 64-bit-only system



dibl

North America just needs to wait for the mirrors to cycle.


root@imerabox:/# apt-cache policy systemd
systemd:
  Installed: 204-6
  Candidate: 204-7
  Version table:
     204-7 0
        500 http://ftp.us.debian.org/debian/ unstable/main amd64 Packages
        500 http://http.debian.net/debian/ unstable/main amd64 Packages
*** 204-6 0
        100 /var/lib/dpkg/status
     204-5.2 0
        500 http://packages.siduction.org/fixes/ unstable/main amd64 Packages
root@imerabox:/# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
  libdb5.1:i386
Use 'apt-get autoremove' to remove it.
The following packages will be REMOVED:
  libpam-systemd systemd-gui systemd-ui
The following NEW packages will be installed:
  libdb5.3:i386
The following packages have been kept back:
  libsystemd-daemon0 libsystemd-journal0 libsystemd-login0 systemd systemd-sysv
The following packages will be upgraded:
  libgudev-1.0-0 libltdl-dev libltdl7 libsasl2-2 libsasl2-2:i386 libsasl2-modules libsasl2-modules:i386 libsasl2-modules-db libsasl2-modules-db:i386
  libsqlite3-0 libsqlite3-0:i386 libtool libudev1 printer-driver-foo2zjs printer-driver-foo2zjs-common qtchooser udev
17 upgraded, 1 newly installed, 3 to remove and 5 not upgraded.
Need to get 4,638 kB of archives.
After this operation, 1,910 kB of additional disk space will be used.
Do you want to continue? [Y/n]
System76 Oryx Pro, Intel Core i7-11800H, ASRock B860 Pro-A, Intel Core Ultra 7 265KF, Nvidia GTX-1060, SSD 990 EVO Plus.

dibl

And BTW is is necessary to take systemd-sysv off hold to upgrade.   :-[    ;D
System76 Oryx Pro, Intel Core i7-11800H, ASRock B860 Pro-A, Intel Core Ultra 7 265KF, Nvidia GTX-1060, SSD 990 EVO Plus.

devil

Yes, not needed anymore. I still had it on hold on my main box.


greetz
devil

clubex

Thanks dibl. Removing the hold from systemd-sysv solved the problem.
If no none objects I'll  mark the topic as solved.