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

Jean-Marc LACROIX jeanmarc.lacroix at free.fr
Sun Sep 8 16:53:27 BST 2019


Dimitry,
Thank for your reply.

 > 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
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
   mixmaster torbrowser-launcher socat tor-arm apparmor-utils obfs4proxy
Recommended packages:
   tor-geoipdb torsocks
The following NEW packages will be installed:
   tor
0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded.
Need to get 1706 kB of archives.
After this operation, 4872 kB of additional disk space will be used.
Get:1 http://ftp.debian.org/debian buster/main arm64 tor arm64 0.3.5.8-1 
[1706 kB]
Fetched 1706 kB in 1s (2008 kB/s)
Selecting previously unselected package tor.
(Reading database ... 102649 files and directories currently installed.)
Preparing to unpack .../tor_0.3.5.8-1_arm64.deb ...
Unpacking tor (0.3.5.8-1) ...
Setting up tor (0.3.5.8-1) ...
Something or somebody made /var/lib/tor disappear.
Creating one for you again.
Something or somebody made /var/log/tor disappear.
Creating one for you again.
Created symlink /etc/systemd/system/multi-user.target.wants/tor.service 
→ /lib/systemd/system/tor.service.
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for systemd (241-5) ...
ansible at pinebook:~$

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


 > Please:
 >   * Replace `*systemd*' with `systemd' (without wildcard) in your
 >     apt-pinnings and try installing sysvinit-core again.
 >

ansible at pinebook:~$ cat 
/etc/apt/preferences.d/preferences_debian_v_10_buster_no_systemd.pref 
|grep -v "#"

Package: systemd
Pin: release *
Pin-Priority: -1

then update/upgrade....

ansible at pinebook:~$ sudo apt update && sudo apt upgrade
Get:1 http://ftp.fr.debian.org/debian buster-backports InRelease [46.7 kB]
Hit:2 http://security.debian.org buster/updates InRelease 

Hit:3 http://ftp.debian.org/debian buster InRelease 

Get:4 http://ftp.fr.debian.org/debian buster-updates InRelease [49.3 kB] 

Ign:5 http://ftp.debian.org/debian stretch InRelease
Hit:6 http://ftp.debian.org/debian stretch Release
Fetched 96.0 kB in 3s (36.8 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
3 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
   libpam-systemd libsystemd0
The following packages will be upgraded:
   systemd-sysv
1 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Need to get 98.8 kB of archives.
After this operation, 1024 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ftp.debian.org/debian buster/main arm64 systemd-sysv arm64 
241-7~deb10u1 [98.8 kB]
Fetched 98.8 kB in 0s (626 kB/s)
(Reading database ... 102692 files and directories currently installed.)
Preparing to unpack .../systemd-sysv_241-7~deb10u1_arm64.deb ...
Unpacking systemd-sysv (241-7~deb10u1) over (241-5) ...
Setting up systemd-sysv (241-7~deb10u1) ...
Processing triggers for man-db (2.8.5-2) ...
ansible at pinebook:~$

ansible at pinebook:~$ cat /etc/debian_version
10.1

...and of course without any errors ...

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
+++-===========================================================-============================-============-===============================================================================

Now, according Debian doc, i try to install sysvinit

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 ?????

ansible at pinebook:~$ cat /etc/apt/sources.list.d/debian_apt_v_10_buster_* 
|grep -v "#" |grep -v "^$"
deb http://ftp.fr.debian.org/debian buster-backports main contrib non-free
deb http://ftp.debian.org/debian/ buster main contrib non-free
deb http://ftp.debian.org/debian/ stretch main contrib non-free
deb http://security.debian.org buster/updates main contrib non-free
deb http://ftp.fr.debian.org/debian buster-updates main contrib non-free

ansible at pinebook:~$ apt-cache search sysvinit
git-daemon-sysvinit - fast, scalable, distributed revision control 
system (git-daemon service)
live-config-sysvinit - Live System Configuration Components (sysvinit 
backend)
sysvinit-core - System-V-like init utilities
sysvinit-utils - System-V-like utilities

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.

Le 01/09/2019 à 15:23, Dmitry Bogatov a écrit :
> 
> control: tags -1 +moreinfo
> 
> [2019-08-30 16:44] Jean-Marc LACROIX <jeanmarc.lacroix at free.fr>
>> Package: sysvinit
>> Version: 2.93-8
>> Severity: grave
>>
>> Dear maintainers,
>>
>> It seems there is a dependency issue when installing sysvinit-core as
>> indicated in following trace
>> [...]
>> Package: *systemd*
>> Pin: release *
>> Pin-Priority: -1
> 
> I think problem is here. *systemd* matches `libsystemd0`, and given that
> even apt depends on `libsystemd0`, you are unlikely to solve any
> dependency.
> 
> Please:
> 
>   * Try installing something else, like `tor'. I expect you will get
>     similar error (`tor' depends on libsystemd0, sigh)
>   * Replace `*systemd*' with `systemd' (without wildcard) in your
>     apt-pinnings and try installing sysvinit-core again.
> 




More information about the Debian-init-diversity mailing list