You are not logged in.
This tries to remove my wine installation
No it doesn't, it just marks the packages as auto-removable — they won't actually be removed until you use apt autoremove (or aptitude, which auto-autoremoves).
This thread from fdn explains how to deal with situations like this:
Brianna Ghey — Rest In Power
Offline
Try apt-get install libelogind0=241.1-1 (Maybe need to do the same for elogind, too.) I'm guessing that there were some changes in dependencies in the interim versions of libelogind0 and you two are caught in some kind of twilight zone.
Another thing you (sgage) could try if the 250 packages are going to be set to autoremoval (as opposed to actually being removed) is to remove libsystemd0 and then install libelogind0 (even if it's already installed). Since libelogind0 Provides libsystemd0, all those packages that want lsd0 will be happy and will be taken off the autoremove list. Maybe.
I just tried this, and got everything squared away (apt-get install libelogind0=241.1-1). I did reinstall libelogind0 (it was already installed, but I re-did it). And finally I had to install wine32:i386 to make wine work. So now I see:
sgage@wulf:~$ sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
sgage@wulf:~$
Thanks for the guidance!
Offline
Shall I risk this and re-install wine afterwards?
Rolf
It worked for me. I just had to reinstall wine32:386 afterwards to get wine working.
Offline
just saw this,
`apt install elogind` && accept libsystemd0 removal
does the trick, nothing else needed.
Offline
Ok, done, looks like everything is fixed now. Did an immediate re-install of wine32.
The process left shim-signed on an old version. Just removed this package, no harm.
Thank you all for your contributions, learned a lot.
Rolf
Offline