Bug#938952: [debian Buster] [arm64 pinebook] [sysvinit-core] libsoup2.4-1 : Depends: glib-networking (>= 2.32.0) but it is not going to be installed
Dmitry Bogatov
KAction at disroot.org
Tue Sep 10 12:35:02 BST 2019
[2019-09-08 17:53] Jean-Marc LACROIX <jeanmarc.lacroix at free.fr>
> > Please:
> >
> > * Try installing something else, like `tor'. I expect you will get
> > similar error (`tor' depends on libsystemd0, sigh)
>
> ansible at pinebook:~$ sudo apt install tor
> [...]
Okay, tor installs fine with your apt-pinning. My guess was wrong.
> ansible at pinebook:~$ dpkg -l |grep -v ii
> Desired=Unknown/Install/Remove/Purge/Hold
> |
> Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name Version
> Architecture Description
> +++-===========================================================-============================-============-===========================
> ====================================================
> ansible at pinebook:~$ dpkg -l |grep systemd
> ii dbus-user-session
> 1.12.16-1 arm64 simple interprocess messaging
> system (systemd --user integration)
> ii libpam-systemd:arm64 241-5
> arm64 system and service manager - PAM module
> ii libsystemd0:arm64 241-5
> arm64 systemd utility library
> ii syslog-ng-mod-journal 3.19.1-5
> arm64 Enhanced system logging daemon
> (systemd journal plugin)
> ii systemd 241-5
> arm64 system and service manager
> ii systemd-sysv 241-5
> arm64 system and service manager - SysV links
Okay, on this stage you have systemd as pid1 implementation.
> [...]
> Now, according Debian doc, i try to install sysvinit
Which exactly doc? I guess it needs to be adjusted.
> ansible at pinebook:~$ sudo apt install sysvinit sysvinit-utils
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Package sysvinit is not available, but is referred to by another package.
> This may mean that the package is missing, has been obsoleted, or
> is only available from another source
> However the following packages replace it:
> sysvinit-core:armhf systemd-sysv:armhf sysvinit-core systemd-sysv
>
> E: Package 'sysvinit' has no installation candidate
>
> It seems on Debian 10.1, there is now one new package name ?????
> [...]
There were no package renaming at least last year.
> ansible at pinebook:~$ sudo apt install sysvinit-core sysvinit-utils
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> sysvinit-utils is already the newest version (2.93-8).
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
> dconf-service : Depends: default-dbus-session-bus or
> dbus-session-bus
> libsoup2.4-1 : Depends: glib-networking (>= 2.32.0) but it is not
> going to be installed
> E: Error, pkgProblemResolver::Resolve generated breaks, this may be
> caused by held packages.
Wait, do you have installation of "recommends" disabled? If I try to
install "dconf-service" on my system (antiX + Devuan + Debian,
pid1=runit-init), I too get resolution error, but
# apt-get install dconf-service --no-install-recommends
resolves fine. Please, try this. Otherwise, your better bet would
be to reassign to libelogind or dbus or something like this.
sysvinit-core only depends on libc and libselinux (sigh), so it can't
cause conflicts with packages you show.
--
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.
More information about the Debian-init-diversity
mailing list