Re: [DNG] packages held back due to conflict with libsystemd0
On Sun, Nov 08, 2020 at 02:17:24PM +0100, Arnt Karlsen wrote: > On Sun, 8 Nov 2020 06:51:07 -0500, Hendrik wrote in message > <20201108115107.bvcwzgsfasqvz...@topoi.pooq.com>: > > > On Sun, Nov 08, 2020 at 05:48:49AM -0300, Eike Lantzsch via Dng wrote: > > > Hi Arnt! > > > > > > On Saturday, 7 November 2020 21:56:38 -03 Arnt Karlsen wrote: > > > > On Sat, 07 Nov 2020 19:11:45 -0300, Eike wrote in message > > ... > > > > > ...with apt* et al. Is why I propose dpkg -P --force-* trains. > > > > > > > > .."-P" == "--purge", I failed to include that, I thought it was > > > > obvious in the context of your thread here, my bad. > > > > > > > > ..by "just line or pile 'em up", I meant line up --force-* options > > > > after "dpkg -P trumpackage" until it does obey your stupid > > > > command. (It will still whine, because breaking your box is > > > > generally considered stupid if you don't know how to fix it.) > > > > I presume "trumpackage" is the one you want to get rid of. > > Don't use purge on the packages you'll want to reinstall -- you > > probably want to retain their configurations. > > ..works best IME when you back those configs up first, then > do the mercyless purgatory thing to the trumpage. ;o) It isn't always obvious which configuration files go with which packages. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] packages held back due to conflict with libsystemd0
On Sun, 8 Nov 2020 06:51:07 -0500, Hendrik wrote in message <20201108115107.bvcwzgsfasqvz...@topoi.pooq.com>: > On Sun, Nov 08, 2020 at 05:48:49AM -0300, Eike Lantzsch via Dng wrote: > > Hi Arnt! > > > > On Saturday, 7 November 2020 21:56:38 -03 Arnt Karlsen wrote: > > > On Sat, 07 Nov 2020 19:11:45 -0300, Eike wrote in message ... > > > ...with apt* et al. Is why I propose dpkg -P --force-* trains. > > > > > > .."-P" == "--purge", I failed to include that, I thought it was > > > obvious in the context of your thread here, my bad. > > > > > > ..by "just line or pile 'em up", I meant line up --force-* options > > > after "dpkg -P trumpackage" until it does obey your stupid > > > command. (It will still whine, because breaking your box is > > > generally considered stupid if you don't know how to fix it.) > > I presume "trumpackage" is the one you want to get rid of. > Don't use purge on the packages you'll want to reinstall -- you > probably want to retain their onfigurations. ..works best IME when you back those configs up first, then do the mercyless purgatory thing to the trumpage. ;o) -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] packages held back due to conflict with libsystemd0
Hi Eike,
On 8/11/20 9:48, Eike Lantzsch via Dng wrote:
I still have snapshots around of my former ASCII installation and as
soon as I find the time I shall go through the process again and see
where it goes wrong or where I made a mistake.
The origin of the problem might be between:
{ elogind, libpolkit-backend-elogind-1.0, libpolkit-gobject-elogind-1.0 }
and:
{ consolekit, libpolkit-backend-consolekit-1.0,
libpolkit-gobject-consolekit-1.0 }
Try upgrading the following packages first:
# apt install --upgrade libpolkit-backend-elogind-1.0
libpolkit-gobject-elogind-1.0
before upgrading the whole system.
Similar issue: http://dev1galaxy.org/viewtopic.php?pid=8496
Hope this helps,
Aitor.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] packages held back due to conflict with libsystemd0
On Sun, Nov 08, 2020 at 05:48:49AM -0300, Eike Lantzsch via Dng wrote: > Hi Arnt! > > On Saturday, 7 November 2020 21:56:38 -03 Arnt Karlsen wrote: > > On Sat, 07 Nov 2020 19:11:45 -0300, Eike wrote in message > > > > <1837090.H3z0i6zCVW@lxcl01>: > > > Hi Arnt, > > > > > > thanks for answering and for the extra recommendations. > > > > > > On Saturday, 7 November 2020 18:38:48 -03 Arnt Karlsen wrote: > > > > On Sat, 07 Nov 2020 16:22:24 -0300, Eike wrote in message > > > > > > > > <1632636.6XzDy3geBR@lxcl01>: > > > > > On Saturday, 7 November 2020 15:52:25 -03 Ludovic Bellière > > > > > > > > > > wrote: > > > > > > Hi Eike, > > > > > > > > > > > > Install libelogind0 first, so it takes precedence over > > > > > > systemd, > > > > > > then > > > > > > elogind. > > > > > > > > > > Thanks - but -> > > > > > That is impossible because of a catch-22.It is not even possible > > > > > to deinstall/purge libsystemd0it seems to be there to haunt me. > > > > > > > > > > Copy and paste off aptitude introduced some not-so-nice > > > > > esc-sequences > > > > > into the text. I hope that it will not mess-up the message too > > > > > much. > > > > > > > > ..2 main ways: use aptitude to pick the version you want. > > > > > > aptitude isn't good at hen-and-egg-problems > > > > ..I find it's pretty good at showing you solutions; break some > > package, when it whines "Broken package", hit "e" and "." or "," to > > browse thru to some solution as close as possible to what you want, > > and mod that to what you want. Rip out stuff you want gone with dpkg > > --force-* trains. > > > > ..if aptitude's error handling fails to find a solution, try apt > > > > and apt-get, they do things differently, and if those fail, we > > > > have > > > > rpm-style nuclear --force purge options to find with dpkg --help > > > > and dpkg --force-help, just line or pile 'em up. ;o) > > > > > > Good grief! > > > > > > Yep apt does things differently. > > > apt: ""You are about to do something potentially harmful." > > > I typed "Yes, yadda yadda ..." > > > It deinstalled hundreds of packages, just as I instructed it to do, > > > > ...with apt* et al. Is why I propose dpkg -P --force-* trains. > > > > .."-P" == "--purge", I failed to include that, I thought it was > > obvious in the context of your thread here, my bad. > > > > ..by "just line or pile 'em up", I meant line up --force-* options > > after "dpkg -P trumpackage" until it does obey your stupid command. > > (It will still whine, because breaking your box is generally > > considered stupid if you don't know how to fix it.) I presume "trumpackage" is the one you want to get rid of. Don't use purge on the packages you'll want to reinstall -- you probably want to retain their onfigurations. > > > > ..once you've ripped out the trumpy stuff, your box is broken, fix > > it with e.g. aptitude and dpkg --configure -a replacing the missing > > trumpy bits you threw out, with whatever you want instead. > > Yes, I'll go for that route as soon as I find some time to do it. > Just now I'm doing a little bit of forensics on the matter, but only at > the side while occupied with other stuff. > > When installing Beowulf with netinstall, libsystemd0 is being > deinstalled by dpkg and directly after libelogind0 installed also with > dpkg. > That is the step which my upgrade from ASCII to Beowulf missed. > > I was reading up the upgrade procedure again on > https://www.devuan.org/os/documentation/dev1fanboy/en/upgrade-to-beowulf > but did not see a hint that this was necessary to perform manually. > As far as I can recall I followed the procedure when upgrading my ASCII > installation. > I still have snapshots around of my former ASCII installation and as > soon as I find the time I shall go through the process again and see > where it goes wrong or where I made a mistake. > > > > > including apt, aptitude and deselect. Tad! > > > I had a snapshot and restored it. > > > Now, there is obviously no way out of this - so be it. > > > I will do a fresh install of Beowulf because I really have more > > > important things to do. > Done, for result please see further up > > > > > > > ..once you've thrown out the trump you want out, refer back to > > > > Ludovic's advice. ;o) > > > > > > not biting the hook ... > > .. ;o) > > > Thank you for your help and consideration. > Eike > -- > Eike Lantzsch ZP6CGE > > > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] packages held back due to conflict with libsystemd0
Hi Arnt! On Saturday, 7 November 2020 21:56:38 -03 Arnt Karlsen wrote: > On Sat, 07 Nov 2020 19:11:45 -0300, Eike wrote in message > > <1837090.H3z0i6zCVW@lxcl01>: > > Hi Arnt, > > > > thanks for answering and for the extra recommendations. > > > > On Saturday, 7 November 2020 18:38:48 -03 Arnt Karlsen wrote: > > > On Sat, 07 Nov 2020 16:22:24 -0300, Eike wrote in message > > > > > > <1632636.6XzDy3geBR@lxcl01>: > > > > On Saturday, 7 November 2020 15:52:25 -03 Ludovic Bellière > > > > > > > > wrote: > > > > > Hi Eike, > > > > > > > > > > Install libelogind0 first, so it takes precedence over > > > > > systemd, > > > > > then > > > > > elogind. > > > > > > > > Thanks - but -> > > > > That is impossible because of a catch-22.It is not even possible > > > > to deinstall/purge libsystemd0it seems to be there to haunt me. > > > > > > > > Copy and paste off aptitude introduced some not-so-nice > > > > esc-sequences > > > > into the text. I hope that it will not mess-up the message too > > > > much. > > > > > > ..2 main ways: use aptitude to pick the version you want. > > > > aptitude isn't good at hen-and-egg-problems > > ..I find it's pretty good at showing you solutions; break some > package, when it whines "Broken package", hit "e" and "." or "," to > browse thru to some solution as close as possible to what you want, > and mod that to what you want. Rip out stuff you want gone with dpkg > --force-* trains. > > > ..if aptitude's error handling fails to find a solution, try apt > > > and apt-get, they do things differently, and if those fail, we > > > have > > > rpm-style nuclear --force purge options to find with dpkg --help > > > and dpkg --force-help, just line or pile 'em up. ;o) > > > > Good grief! > > > > Yep apt does things differently. > > apt: ""You are about to do something potentially harmful." > > I typed "Yes, yadda yadda ..." > > It deinstalled hundreds of packages, just as I instructed it to do, > > ...with apt* et al. Is why I propose dpkg -P --force-* trains. > > .."-P" == "--purge", I failed to include that, I thought it was > obvious in the context of your thread here, my bad. > > ..by "just line or pile 'em up", I meant line up --force-* options > after "dpkg -P trumpackage" until it does obey your stupid command. > (It will still whine, because breaking your box is generally > considered stupid if you don't know how to fix it.) > > ..once you've ripped out the trumpy stuff, your box is broken, fix > it with e.g. aptitude and dpkg --configure -a replacing the missing > trumpy bits you threw out, with whatever you want instead. Yes, I'll go for that route as soon as I find some time to do it. Just now I'm doing a little bit of forensics on the matter, but only at the side while occupied with other stuff. When installing Beowulf with netinstall, libsystemd0 is being deinstalled by dpkg and directly after libelogind0 installed also with dpkg. That is the step which my upgrade from ASCII to Beowulf missed. I was reading up the upgrade procedure again on https://www.devuan.org/os/documentation/dev1fanboy/en/upgrade-to-beowulf but did not see a hint that this was necessary to perform manually. As far as I can recall I followed the procedure when upgrading my ASCII installation. I still have snapshots around of my former ASCII installation and as soon as I find the time I shall go through the process again and see where it goes wrong or where I made a mistake. > > > including apt, aptitude and deselect. Tad! > > I had a snapshot and restored it. > > Now, there is obviously no way out of this - so be it. > > I will do a fresh install of Beowulf because I really have more > > important things to do. Done, for result please see further up > > > > > ..once you've thrown out the trump you want out, refer back to > > > Ludovic's advice. ;o) > > > > not biting the hook ... > .. ;o) > Thank you for your help and consideration. Eike -- Eike Lantzsch ZP6CGE ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] packages held back due to conflict with libsystemd0
On Sat, 07 Nov 2020 19:11:45 -0300, Eike wrote in message <1837090.H3z0i6zCVW@lxcl01>: > Hi Arnt, > > thanks for answering and for the extra recommendations. > > On Saturday, 7 November 2020 18:38:48 -03 Arnt Karlsen wrote: > > On Sat, 07 Nov 2020 16:22:24 -0300, Eike wrote in message > > > > <1632636.6XzDy3geBR@lxcl01>: > > > On Saturday, 7 November 2020 15:52:25 -03 Ludovic Bellière > > > wrote: > > > > Hi Eike, > > > > > > > > Install libelogind0 first, so it takes precedence over systemd, > > > > then > > > > elogind. > > > > > > Thanks - but -> > > > That is impossible because of a catch-22.It is not even possible > > > to deinstall/purge libsystemd0it seems to be there to haunt me. > > > > > > Copy and paste off aptitude introduced some not-so-nice > > > esc-sequences > > > into the text. I hope that it will not mess-up the message too > > > much. > > > > ..2 main ways: use aptitude to pick the version you want. > aptitude isn't good at hen-and-egg-problems ..I find it's pretty good at showing you solutions; break some package, when it whines "Broken package", hit "e" and "." or "," to browse thru to some solution as close as possible to what you want, and mod that to what you want. Rip out stuff you want gone with dpkg --force-* trains. > > ..if aptitude's error handling fails to find a solution, try apt > > and apt-get, they do things differently, and if those fail, we have > > rpm-style nuclear --force purge options to find with dpkg --help > > and dpkg --force-help, just line or pile 'em up. ;o) > > Good grief! > > Yep apt does things differently. > apt: ""You are about to do something potentially harmful." > I typed "Yes, yadda yadda ..." > It deinstalled hundreds of packages, just as I instructed it to do, ...with apt* et al. Is why I propose dpkg -P --force-* trains. .."-P" == "--purge", I failed to include that, I thought it was obvious in the context of your thread here, my bad. ..by "just line or pile 'em up", I meant line up --force-* options after "dpkg -P trumpackage" until it does obey your stupid command. (It will still whine, because breaking your box is generally considered stupid if you don't know how to fix it.) ..once you've ripped out the trumpy stuff, your box is broken, fix it with e.g. aptitude and dpkg --configure -a replacing the missing trumpy bits you threw out, with whatever you want instead. > including apt, aptitude and deselect. Tad! > I had a snapshot and restored it. > Now, there is obviously no way out of this - so be it. > I will do a fresh install of Beowulf because I really have more > important things to do. > > > ..once you've thrown out the trump you want out, refer back to > > Ludovic's advice. ;o) > not biting the hook ... .. ;o) > Cheers to all and also all the best > Eike > > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] packages held back due to conflict with libsystemd0
Hi Arnt, thanks for answering and for the extra recommendations. On Saturday, 7 November 2020 18:38:48 -03 Arnt Karlsen wrote: > On Sat, 07 Nov 2020 16:22:24 -0300, Eike wrote in message > > <1632636.6XzDy3geBR@lxcl01>: > > On Saturday, 7 November 2020 15:52:25 -03 Ludovic Bellière wrote: > > > Hi Eike, > > > > > > Install libelogind0 first, so it takes precedence over systemd, > > > then > > > elogind. > > > > Thanks - but -> > > That is impossible because of a catch-22.It is not even possible to > > deinstall/purge libsystemd0it seems to be there to haunt me. > > > > Copy and paste off aptitude introduced some not-so-nice > > esc-sequences > > into the text. I hope that it will not mess-up the message too much. > > ..2 main ways: use aptitude to pick the version you want. aptitude isn't good at hen-and-egg-problems > > ..if aptitude's error handling fails to find a solution, try apt > and apt-get, they do things differently, and if those fail, we have > rpm-style nuclear --force purge options to find with dpkg --help > and dpkg --force-help, just line or pile 'em up. ;o) Good grief! Yep apt does things differently. apt: ""You are about to do something potentially harmful." I typed "Yes, yadda yadda ..." It deinstalled hundreds of packages, just as I instructed it to do, including apt, aptitude and deselect. Tad! I had a snapshot and restored it. Now, there is obviously no way out of this - so be it. I will do a fresh install of Beowulf because I really have more important things to do. > ..once you've thrown out the trump you want out, refer back to > Ludovic's advice. ;o) not biting the hook ... Cheers to all and also all the best Eike ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] packages held back due to conflict with libsystemd0
On Sat, 07 Nov 2020 16:22:24 -0300, Eike wrote in message <1632636.6XzDy3geBR@lxcl01>: > On Saturday, 7 November 2020 15:52:25 -03 Ludovic Bellière wrote: > > Hi Eike, > > > > Install libelogind0 first, so it takes precedence over systemd, then > > elogind. > Thanks - but -> > That is impossible because of a catch-22.It is not even possible to > deinstall/purge libsystemd0it seems to be there to haunt me. > > Copy and paste off aptitude introduced some not-so-nice esc-sequences > into the text. I hope that it will not mess-up the message too much. ..2 main ways: use aptitude to pick the version you want. ..if aptitude's error handling fails to find a solution, try apt and apt-get, they do things differently, and if those fail, we have rpm-style nuclear --force purge options to find with dpkg --help and dpkg --force-help, just line or pile 'em up. ;o) ..once you've thrown out the trump you want out, refer back to Ludovic's advice. ;o) > *libsystemd0 (remove, 241-7~deb10u4)* will be removed. The following > packages depend on *libsystemd0 (remove, 241-7~deb10u4)* and will be > broken by its removal: > * * *libaccountsservice0 (held/unchanged, 0.6.45-2) *depends on* > libsystemd0 (>= 209) (provided by libelogind0 241.4-2) > * * *libapt-pkg5.0 (held/unchanged, 1.8.2.1) *depends on* libsystemd0 > (>= 221) (provided by libelogind0 241.4-2) > * * *libpulse0 (held/unchanged, 12.2-4+deb10u1) *depends on* > libsystemd0 (provided by libelogind0 241.4-2) > * * *network-manager (held/unchanged, 1.14.6-2+deb10u1) *depends on* > libsystemd0 (>= 221) (provided by libelogind0 241.4-2) > * * *openssh-server (held/unchanged, 1:7.9p1-10+deb10u2) *depends on* > libsystemd0 (provided by libelogind0 241.4-2) > * * *pulseaudio (held/unchanged, 12.2-4+deb10u1) *depends on* > libsystemd0 (provided by libelogind0 241.4-2) > * * *rsyslog (held/unchanged, 8.1901.0-1+devuan3~beowulf1) *depends > on* libsystemd0 (provided by libelogind0 241.4-2) > * * *samba-libs (held/unchanged, 2:4.9.5+dfsg-5+deb10u1) *depends on* > libsystemd0 (provided by libelogind0 241.4-2) > * * *sane-utils (held/unchanged, 1.0.27-3.2) *depends on* > libsystemd0 (provided by libelogind0 241.4-2) > * * *sddm (held/unchanged, 0.18.0-1+deb10u1) *depends on* libsystemd0 > (provided by libelogind0 241.4-2) > * * *vlc-plugin-base (held/unchanged, 3.0.11-0+deb10u1) *depends on* > libsystemd0 (provided by libelogind0 241.4-2) > * * *xserver-xorg-core (held/unchanged, 2:1.20.4-1+deb10u1) *depends > on* libsystemd0 (provided by libelogind0 241.4-2) > > > I have no idea how or why this situation came to be. > > > > On Sat, 07 Nov 2020 10:41:47 -0300 > > Eike Lantzsch via Dng wrote: > > > > > > > Hi!Maybe somebody can add some cheese to my whine: > > > For months I am not able to resolve this catch-22 in Beowulf: > > > The following packages have been kept back: > > > Description: user, seat and session management library > > > Homepage: https://github.com/elogind/elogind > > > Multi-Arch: same > > > Priority: optional > > > Section: libs > > > Maintainer: Mark Hindley > > > Architecture: amd64 > > > Compressed Size: 224 k > > > Uncompressed Size: 852 k > > > Source Package: elogind > > > Label: Devuan > > > Origin: Devuan:3.0/stable [amd64] > > > Origin URI: > > > http://deb.devuan.org/merged/pool/DEVUAN/main/e/elogind/ > > > > > > libelogind0_241.4-2_amd64.deb > > > --\ Depends (2) > > > --- libc6 (>= 2.28) > > > --- libcap2 (>= 1:2.10) > > > --\ Conflicts (2) > > > --- libsystemd0 (UNSATISFIED) > > > --- libsystemd0 (UNSATISFIED) > > > --\ Breaks (1) > > > --- libelogind0 (!= 241.4-2) > > > --\ Replaces (3) > > > --- libelogind0 (< 241.4-2) > > > --- libsystemd0 > > > --- libsystemd0 > > > --- Package names provided by libelogind0 (1) > > > --- Packages which depend on libelogind0 (5) > > > --\ Versions of libelogind0 (2) > > > i234.4-2 > > > p241.4-2 > > > > > > I had similar situations with Debian Sid and Testing during mayor > > > changes and upgrades but was always able to resolve the issues by > > > patience and diligently purging and reinstalling packges - but > > > with Devuan Beowulf: NOT - no way. > > > > > > I am about to ditch my Beowulf installation and install from > > > scratch. > Before I do this, has anybody have a hint what I still > > > might do over which solution I didn't happen to stumble or I > > > overlooked? > -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] packages held back due to conflict with libsystemd0
On Saturday, 7 November 2020 17:35:07 -03 tito via Dng wrote: > On Sat, 07 Nov 2020 10:41:47 -0300 > > Eike Lantzsch via Dng wrote: > > Hi!Maybe somebody can add some cheese to my whine: > > > > For months I am not able to resolve this catch-22 in Beowulf: > > > > The following packages have been kept back: > > Description: user, seat and session management library > > > > Homepage: https://github.com/elogind/elogind > > Multi-Arch: same > > Priority: optional > > Section: libs > > Maintainer: Mark Hindley > > Architecture: amd64 > > Compressed Size: 224 k > > Uncompressed Size: 852 k > > Source Package: elogind > > Label: Devuan > > Origin: Devuan:3.0/stable [amd64] > > Origin URI: > > http://deb.devuan.org/merged/pool/DEVUAN/main/e/elogind/ > > > > libelogind0_241.4-2_amd64.deb > > > > --\ Depends (2) > > > > --- libc6 (>= 2.28) > > --- libcap2 (>= 1:2.10) > > > > --\ Conflicts (2) > > > > --- libsystemd0 (UNSATISFIED) > > --- libsystemd0 (UNSATISFIED) > > > > --\ Breaks (1) > > > > --- libelogind0 (!= 241.4-2) > > > > --\ Replaces (3) > > > > --- libelogind0 (< 241.4-2) > > --- libsystemd0 > > --- libsystemd0 > > > > --- Package names provided by libelogind0 (1) > > --- Packages which depend on libelogind0 (5) > > --\ Versions of libelogind0 (2) > > > > i234.4-2 > > p241.4-2 > > > > I had similar situations with Debian Sid and Testing during mayor > > changes and upgrades but was always able to resolve the issues by > > patience and diligently purging and reinstalling packges - but with > > Devuan Beowulf: NOT - no way. > > Just out of curiosity are upgrading from a previous devuan version , > migrating from debian, or did you install from scratch ? > > Ciao, > Tito Ciao Tito, upgraded from Devuan-Ascii to Beowulf.I used the crowbar now"You are about to do something potentially harmful. A più tardi!Eike ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] packages held back due to conflict with libsystemd0
On Sat, 07 Nov 2020 10:41:47 -0300 Eike Lantzsch via Dng wrote: > Hi!Maybe somebody can add some cheese to my whine: > > For months I am not able to resolve this catch-22 in Beowulf: > > The following packages have been kept back: > > Description: user, seat and session management library > > Homepage: https://github.com/elogind/elogind > Multi-Arch: same > Priority: optional > Section: libs > Maintainer: Mark Hindley > Architecture: amd64 > Compressed Size: 224 k > Uncompressed Size: 852 k > Source Package: elogind > Label: Devuan > Origin: Devuan:3.0/stable [amd64] > Origin URI: http://deb.devuan.org/merged/pool/DEVUAN/main/e/elogind/ > libelogind0_241.4-2_amd64.deb > --\ Depends (2) > --- libc6 (>= 2.28) > --- libcap2 (>= 1:2.10) > --\ Conflicts (2) > --- libsystemd0 (UNSATISFIED) > --- libsystemd0 (UNSATISFIED) > --\ Breaks (1) > --- libelogind0 (!= 241.4-2) > --\ Replaces (3) > --- libelogind0 (< 241.4-2) > --- libsystemd0 > --- libsystemd0 > --- Package names provided by libelogind0 (1) > --- Packages which depend on libelogind0 (5) > --\ Versions of libelogind0 (2) > i234.4-2 > p241.4-2 > > I had similar situations with Debian Sid and Testing during mayor > changes and upgrades but was always able to resolve the issues by > patience and diligently purging and reinstalling packges - but with > Devuan Beowulf: NOT - no way. Just out of curiosity are upgrading from a previous devuan version , migrating from debian, or did you install from scratch ? Ciao, Tito > I am about to ditch my Beowulf installation and install from scratch. > Before I do this, has anybody have a hint what I still might do over > which solution I didn't happen to stumble or I overlooked? > > CheersEike > -- > Eike Lantzsch ZP6CGE > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] packages held back due to conflict with libsystemd0
Ludovis, first of all: thank you for taking the time to ponder over my plight and to answer. On Saturday, 7 November 2020 16:42:33 -03 Ludovic Bellière wrote: > Eike, > > The message tells you that packages depends on libsystemd0, but that > requirement is provided by libelogind0. In any case, libelogind0 will > be a stand-in for libsystemd0. If apt chose to remove packages you > use, you can still install them back after. I understand that but neither apt nor aptitude understand that. There is no artificial intelligence built into the package managers which say: "Ah, OK, libelogind0 is replacing libsystemd0 and it provides the same services and APIs." Neither is apt capable of deinstalling libsystemd0 nor installing libelogind0. Apt nor aptitude neither are able to deinstall all the dependant packages even if I would like them to be deinstalled. Although deinstallation of openssh-server also is a no-no if one relys on a remote ssh connection - not? But whatever ... > > The warning is of no consequence here because you're replacing a > library with its counterpart. This is not a warning, it is an error-message which tells me that apt is unable to resolve the situation no matter what. It does not warn me that I'm about to delete all those packages but that it right away refuses to do anything of the kind. I would be happy if it at least deinstalled all the dependencies. I could handle that. But it refuses. This is a hen-and-egg-problem. The problem is not that I do not understand warnings but that I am confronted with a situation of a circle-dependency which cannot be resolved by neither apt nor aptitude. I'm on a merry-go-round and can't get off. I'll try to purge --force-depends libsystemd0. But for doing this I first have to download the package (and libelogind0) because I autocleaned /var/cache/apt/archives. Hand over to me the crowbar, please! > > On Sat, 07 Nov 2020 16:22:24 -0300 > > Eike Lantzsch via Dng wrote: > > On Saturday, 7 November 2020 15:52:25 -03 Ludovic Bellière wrote: > > > Hi Eike, > > > > > > Install libelogind0 first, so it takes precedence over systemd, > > > then > > > elogind. > > > > Thanks - but -> > > That is impossible because of a catch-22.It is not even possible to > > deinstall/purge libsystemd0it seems to be there to haunt me. > > > > Copy and paste off aptitude introduced some not-so-nice > > esc-sequences > > into the text. I hope that it will not mess-up the message too much. > > > > *libsystemd0 (remove, 241-7~deb10u4)* will be removed. The following > > packages depend on *libsystemd0 (remove, 241-7~deb10u4)* and will be > > broken by its removal: > > * * *libaccountsservice0 (held/unchanged, 0.6.45-2) *depends on* > > libsystemd0 (>= 209) (provided by libelogind0 241.4-2) > > * * *libapt-pkg5.0 (held/unchanged, 1.8.2.1) *depends on* > > libsystemd0 > > (>= 221) (provided by libelogind0 241.4-2) > > * * *libpulse0 (held/unchanged, 12.2-4+deb10u1) *depends on* > > libsystemd0 (provided by libelogind0 241.4-2) > > * * *network-manager (held/unchanged, 1.14.6-2+deb10u1) *depends on* > > libsystemd0 (>= 221) (provided by libelogind0 241.4-2) > > * * *openssh-server (held/unchanged, 1:7.9p1-10+deb10u2) *depends > > on* > > libsystemd0 (provided by libelogind0 241.4-2) > > * * *pulseaudio (held/unchanged, 12.2-4+deb10u1) *depends on* > > libsystemd0 (provided by libelogind0 241.4-2) > > * * *rsyslog (held/unchanged, 8.1901.0-1+devuan3~beowulf1) *depends > > on* libsystemd0 (provided by libelogind0 241.4-2) > > * * *samba-libs (held/unchanged, 2:4.9.5+dfsg-5+deb10u1) *depends > > on* > > libsystemd0 (provided by libelogind0 241.4-2) > > > > * * *sane-utils (held/unchanged, 1.0.27-3.2) *depends on* > > > > libsystemd0 (provided by libelogind0 241.4-2) > > * * *sddm (held/unchanged, 0.18.0-1+deb10u1) *depends on* > > libsystemd0 > > (provided by libelogind0 241.4-2) > > * * *vlc-plugin-base (held/unchanged, 3.0.11-0+deb10u1) *depends on* > > libsystemd0 (provided by libelogind0 241.4-2) > > * * *xserver-xorg-core (held/unchanged, 2:1.20.4-1+deb10u1) *depends > > on* libsystemd0 (provided by libelogind0 241.4-2) > > > > I have no idea how or why this situation came to be. -- Eike Lantzsch ZP6CGE Snail-Mail from Europe: AS91527 Eike Lantzsch Calle Diderot 11, NAVE 20A, poligono de Guadalhorce 29004 Málaga España / Spanien Snail-Mail from U.S.A. and Canada: AS91527 Eike Lantzsch 8221 NW 30th Terrace FL 33122-1913 MIAMI United States of America SIPgate: +49-4131-9279632 Land-line: +595-21-553984 Cell-phone: +595-971-696909 Skype: eikelan WIRE: @eikelantzsch ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] packages held back due to conflict with libsystemd0
Eike, The message tells you that packages depends on libsystemd0, but that requirement is provided by libelogind0. In any case, libelogind0 will be a stand-in for libsystemd0. If apt chose to remove packages you use, you can still install them back after. The warning is of no consequence here because you're replacing a library with its counterpart. On Sat, 07 Nov 2020 16:22:24 -0300 Eike Lantzsch via Dng wrote: > On Saturday, 7 November 2020 15:52:25 -03 Ludovic Bellière wrote: > > Hi Eike, > > > > Install libelogind0 first, so it takes precedence over systemd, then > > elogind. > Thanks - but -> > That is impossible because of a catch-22.It is not even possible to > deinstall/purge libsystemd0it seems to be there to haunt me. > > Copy and paste off aptitude introduced some not-so-nice esc-sequences > into the text. I hope that it will not mess-up the message too much. > > *libsystemd0 (remove, 241-7~deb10u4)* will be removed. The following > packages depend on *libsystemd0 (remove, 241-7~deb10u4)* and will be > broken by its removal: > * * *libaccountsservice0 (held/unchanged, 0.6.45-2) *depends on* > libsystemd0 (>= 209) (provided by libelogind0 241.4-2) > * * *libapt-pkg5.0 (held/unchanged, 1.8.2.1) *depends on* libsystemd0 > (>= 221) (provided by libelogind0 241.4-2) > * * *libpulse0 (held/unchanged, 12.2-4+deb10u1) *depends on* > libsystemd0 (provided by libelogind0 241.4-2) > * * *network-manager (held/unchanged, 1.14.6-2+deb10u1) *depends on* > libsystemd0 (>= 221) (provided by libelogind0 241.4-2) > * * *openssh-server (held/unchanged, 1:7.9p1-10+deb10u2) *depends on* > libsystemd0 (provided by libelogind0 241.4-2) > * * *pulseaudio (held/unchanged, 12.2-4+deb10u1) *depends on* > libsystemd0 (provided by libelogind0 241.4-2) > * * *rsyslog (held/unchanged, 8.1901.0-1+devuan3~beowulf1) *depends > on* libsystemd0 (provided by libelogind0 241.4-2) > * * *samba-libs (held/unchanged, 2:4.9.5+dfsg-5+deb10u1) *depends on* > libsystemd0 (provided by libelogind0 241.4-2) > * * *sane-utils (held/unchanged, 1.0.27-3.2) *depends on* > libsystemd0 (provided by libelogind0 241.4-2) > * * *sddm (held/unchanged, 0.18.0-1+deb10u1) *depends on* libsystemd0 > (provided by libelogind0 241.4-2) > * * *vlc-plugin-base (held/unchanged, 3.0.11-0+deb10u1) *depends on* > libsystemd0 (provided by libelogind0 241.4-2) > * * *xserver-xorg-core (held/unchanged, 2:1.20.4-1+deb10u1) *depends > on* libsystemd0 (provided by libelogind0 241.4-2) > > I have no idea how or why this situation came to be. > pgpPIf_6q2dfM.pgp Description: Signature digitale OpenPGP ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] packages held back due to conflict with libsystemd0
On Saturday, 7 November 2020 15:52:25 -03 Ludovic Bellière wrote: > Hi Eike, > > Install libelogind0 first, so it takes precedence over systemd, then > elogind. Thanks - but -> That is impossible because of a catch-22.It is not even possible to deinstall/purge libsystemd0it seems to be there to haunt me. Copy and paste off aptitude introduced some not-so-nice esc-sequences into the text. I hope that it will not mess-up the message too much. *libsystemd0 (remove, 241-7~deb10u4)* will be removed. The following packages depend on *libsystemd0 (remove, 241-7~deb10u4)* and will be broken by its removal: * * *libaccountsservice0 (held/unchanged, 0.6.45-2) *depends on* libsystemd0 (>= 209) (provided by libelogind0 241.4-2) * * *libapt-pkg5.0 (held/unchanged, 1.8.2.1) *depends on* libsystemd0 (>= 221) (provided by libelogind0 241.4-2) * * *libpulse0 (held/unchanged, 12.2-4+deb10u1) *depends on* libsystemd0 (provided by libelogind0 241.4-2) * * *network-manager (held/unchanged, 1.14.6-2+deb10u1) *depends on* libsystemd0 (>= 221) (provided by libelogind0 241.4-2) * * *openssh-server (held/unchanged, 1:7.9p1-10+deb10u2) *depends on* libsystemd0 (provided by libelogind0 241.4-2) * * *pulseaudio (held/unchanged, 12.2-4+deb10u1) *depends on* libsystemd0 (provided by libelogind0 241.4-2) * * *rsyslog (held/unchanged, 8.1901.0-1+devuan3~beowulf1) *depends on* libsystemd0 (provided by libelogind0 241.4-2) * * *samba-libs (held/unchanged, 2:4.9.5+dfsg-5+deb10u1) *depends on* libsystemd0 (provided by libelogind0 241.4-2) * * *sane-utils (held/unchanged, 1.0.27-3.2) *depends on* libsystemd0 (provided by libelogind0 241.4-2) * * *sddm (held/unchanged, 0.18.0-1+deb10u1) *depends on* libsystemd0 (provided by libelogind0 241.4-2) * * *vlc-plugin-base (held/unchanged, 3.0.11-0+deb10u1) *depends on* libsystemd0 (provided by libelogind0 241.4-2) * * *xserver-xorg-core (held/unchanged, 2:1.20.4-1+deb10u1) *depends on* libsystemd0 (provided by libelogind0 241.4-2) > I have no idea how or why this situation came to be. > On Sat, 07 Nov 2020 10:41:47 -0300 > Eike Lantzsch via Dng wrote: > > > > Hi!Maybe somebody can add some cheese to my whine: > > For months I am not able to resolve this catch-22 in Beowulf: > > The following packages have been kept back: > > Description: user, seat and session management library > > Homepage: https://github.com/elogind/elogind > > Multi-Arch: same > > Priority: optional > > Section: libs > > Maintainer: Mark Hindley > > Architecture: amd64 > > Compressed Size: 224 k > > Uncompressed Size: 852 k > > Source Package: elogind > > Label: Devuan > > Origin: Devuan:3.0/stable [amd64] > > Origin URI: > > http://deb.devuan.org/merged/pool/DEVUAN/main/e/elogind/ > > > > libelogind0_241.4-2_amd64.deb > > --\ Depends (2) > > --- libc6 (>= 2.28) > > --- libcap2 (>= 1:2.10) > > --\ Conflicts (2) > > --- libsystemd0 (UNSATISFIED) > > --- libsystemd0 (UNSATISFIED) > > --\ Breaks (1) > > --- libelogind0 (!= 241.4-2) > > --\ Replaces (3) > > --- libelogind0 (< 241.4-2) > > --- libsystemd0 > > --- libsystemd0 > > --- Package names provided by libelogind0 (1) > > --- Packages which depend on libelogind0 (5) > > --\ Versions of libelogind0 (2) > > i234.4-2 > > p241.4-2 > > > > I had similar situations with Debian Sid and Testing during mayor > > changes and upgrades but was always able to resolve the issues by > > patience and diligently purging and reinstalling packges - but with > > Devuan Beowulf: NOT - no way. > > > > I am about to ditch my Beowulf installation and install from > > scratch. Before I do this, has anybody have a hint what I still > > might do over which solution I didn't happen to stumble or I > > overlooked? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] packages held back due to conflict with libsystemd0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Eike, Install libelogind0 first, so it takes precedence over systemd, then elogind. On Sat, 07 Nov 2020 10:41:47 -0300 Eike Lantzsch via Dng wrote: > Hi!Maybe somebody can add some cheese to my whine: > > For months I am not able to resolve this catch-22 in Beowulf: > > The following packages have been kept back: > > Description: user, seat and session management library > > Homepage: https://github.com/elogind/elogind > Multi-Arch: same > Priority: optional > Section: libs > Maintainer: Mark Hindley > Architecture: amd64 > Compressed Size: 224 k > Uncompressed Size: 852 k > Source Package: elogind > Label: Devuan > Origin: Devuan:3.0/stable [amd64] > Origin URI: http://deb.devuan.org/merged/pool/DEVUAN/main/e/elogind/ > libelogind0_241.4-2_amd64.deb > --\ Depends (2) > --- libc6 (>= 2.28) > --- libcap2 (>= 1:2.10) > --\ Conflicts (2) > --- libsystemd0 (UNSATISFIED) > --- libsystemd0 (UNSATISFIED) > --\ Breaks (1) > --- libelogind0 (!= 241.4-2) > --\ Replaces (3) > --- libelogind0 (< 241.4-2) > --- libsystemd0 > --- libsystemd0 > --- Package names provided by libelogind0 (1) > --- Packages which depend on libelogind0 (5) > --\ Versions of libelogind0 (2) > i234.4-2 > p241.4-2 > > I had similar situations with Debian Sid and Testing during mayor > changes and upgrades but was always able to resolve the issues by > patience and diligently purging and reinstalling packges - but with > Devuan Beowulf: NOT - no way. > > I am about to ditch my Beowulf installation and install from scratch. > Before I do this, has anybody have a hint what I still might do over > which solution I didn't happen to stumble or I overlooked? > > CheersEike > -- > Eike Lantzsch ZP6CGE > -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEhJ0DCOrV8MPFuM4uvCvwxohusTIFAl+m7OkACgkQvCvwxohu sTJONg//X0ie3rdD53pm2hAWmNtDWsBrEsE2TbHtLa0nI2jc3ZuSHtjnNWwn6+5F dOtv+jFBVOETQoi9mVqIQMjW1kOU0AF2P8KZ89lB5jpubPi//+jqYFUatTBIG1uB 5yH0fviyrIDxFC3u1Yoa39EZLAQ8EQU+JOTDOmEdekC8ExBAScqTklvDG0lCQxs3 i8+LUbppHmvgxdxv8v4+18mfq3qDRsVy51eno14nFYp5qbOHCeDqEERdz3s62DjJ rcl2NyIkookOZURH4XglsBy4Vep/uImKHtlJAVL/IkCPaLifGsN/7/Nw13GtWgVl pyQkIltE8rMzYO+b4cl2NlyVlWqISFn0fxfOQorzCtU1gAt+tmExbGNr/2+P+uAH 8JBtbQvypWRzVnLGSaLM8ui6b2+Db5INDsuQjvL7/8RhBvpukeDOdpgnn6dltVry MAc8UEXW0sHuzn3aUSOGiuk0VB6fiMaitq5XavjXPR2flYF2zECUa2bOTEZUiGlk iG8OqsMM97fVKsCbvPLyUgwfIInr2UweBRzPHbu2J/BV2MxRlwPa005bB6155+JM xwHMsfgWiUYeebONCYE4rK/eUaBJVhfeB8qAmTpjhiE4Qq32MIcacCGr/Huj0ZR/ zrWIr1lQxmWILWsOcvMqT6lx4UBieLKKSoqdyNceoqM/8ePRimM= =yCtn -END PGP SIGNATURE- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
