Mark,

On Fri, 27 Sep 2019, Mark Hindley wrote:
> 
> Thanks. The aim of preventing accidental removal of systemd is very 
> reasonable. However, using this approach the hurdle you create even 
> to a user who really wants to uninstall is pretty high. Few people 
> will continue having seen the 'You are about to do something 
> potentially harmful' warning.
> 
> I think the effect we are after is rather closer to that of apt-mark 
> hold systemd or dpkg --set-selections systemd hold. Once held, 
> uninstalling the package requires a specific request to apt.  But I 
> realise this approach will also prevent upgrades.

What about doing this as a three steps operation?

1. install sysvinit-core; that removes systemd-sysv but nothing else 
   systemd related
2. reboot; init should now be sysv init
3. install libelogind0 libpam-elogind elogind

Souldn't that work?

But some stuff needs to be addressed first.  Some 100 packages would 
be removed on my system:

,----
| The following packages will be REMOVED:
|   akonadi-server* breeze* drkonqi* ettercap-graphical* ffmpegthumbs*
|   frameworkintegration* gdebi* isenkram* k3b* kactivitymanagerd* kaffeine*
|   kamera* kamoso* kcachegrind* kde-cli-tools* kde-config-cddb*
|   kde-config-screenlocker* kde-runtime* kde-style-breeze* kdeconnect*
|   kdelibs5-plugins* kdesudo* kinit* kio* kmahjongg* kmenuedit* kommander*
|   kpat* krusader* kwin-common* kwin-style-breeze* libcolorcorrect5* libk3b7*
|   libkf5akonadicore5abi2* libkf5akonadiwidgets5abi1* libkf5auth5*
|   libkf5authcore5* libkf5bookmarks5* libkf5cddb5* libkf5configwidgets5*
|   libkf5declarative5* libkf5iconthemes5* libkf5kcmutils5* libkf5kdegames7*
|   libkf5kdelibs4support5* libkf5kdelibs4support5-bin* libkf5kiocore5*
|   libkf5kiofilewidgets5* libkf5kiogui5* libkf5kiowidgets5*
|   libkf5kmahjongglib5* libkf5newstuff5* libkf5newstuffcore5*
|   libkf5notifyconfig5* libkf5parts5* libkf5plasma5* libkf5plasmaquick5*
|   libkf5purpose-bin* libkf5purpose5* libkf5quickaddons5* libkf5runner5*
|   libkf5sane5* libkf5style5* libkf5texteditor-bin* libkf5texteditor5*
|   libkf5textwidgets5* libkf5wallet-bin* libkf5xmlgui5* libkf5xmlrpcclient5*
|   libkscreenlocker5* libkwin4-effect-builtins1* libokular5core8*
|   libpam-systemd* libpolkit-qt-1-1* libpolkit-qt5-1-1* libprocessui7*
|   libtaskmanager6* libvirt-daemon-system* libweather-ion7* milou* okular*
|   packagekit* plasma-desktop* plasma-framework* plasma-integration*
|   plasma-workspace* policykit-1* polkit-kde-agent-1*
|   qml-module-org-kde-draganddrop* qml-module-org-kde-kconfig*
|   qml-module-org-kde-kcoreaddons* qml-module-org-kde-kquickcontrols*
|   qml-module-org-kde-kquickcontrolsaddons* qml-module-org-kde-kwindowsystem*
|   qml-module-org-kde-purpose* qml-module-org-kde-qqc2desktopstyle* rasdaemon*
|   skanlite* skrooge* systemd* udisks2*
`----

most of them KDE related, but not only.  Bug #925344 (filed on
Sat, 23 Mar 2019 13:33:24 +0000, 6 month ago) needs to be resolved in 
a speedy manner.  But, AFAICS, no progress was made since :(

Looking at one of the other packages, udisks2, I see direct and 
indirect dependencies to systemd:

,----
| Depends: dbus, libblockdev-part2, libblockdev-swap2, 
| libblockdev-loop2, libblockdev-fs2, libpam-systemd, parted, udev, 
|                                     ^^^^^^^^^^^^^^
| libacl1 (>= 2.2.23), libatasmart4 (>= 0.13), libblockdev-utils2 (>= 
| 2.20), libblockdev2 (>= 2.20), libc6 (>= 2.7), libglib2.0-0 (>= 2.50), 
| libgudev-1.0-0 (>= 165), libmount1 (>= 2.30), libpolkit-agent-1-0 (>= 
| 0.99), libpolkit-gobject-1-0 (>= 0.101), libsystemd0 (>= 209), 
|                                          ^^^^^^^^^^^
| libudisks2-0 (>= 2.8.3)
`----

Those need to be addressed too.


Cheers,

-- 
Cristian

Reply via email to