Unable to install anything - apt-get install systemd broken

[kedaha]

It seems you may have multiple problems here so you may have to work through them one at a time.

You are probably right. I thought there might be some easy way to reset apt-get using a live cd or files from the internet, so I can install other packages again. I didn't add any repositories. afaik it came preinstalled with the ubuntu wine repositories. I was able to download packages before just fine. Maybe there was a mismatch between my old debian version and the ubuntu wine repository.

Raspbian Jessie or whatever unofficial Debian spin it is—run-wine-on-raspberry-pi—is not a Debian release and as other forum members have commented is quite old based, as it is, on Debian Jessie, which is now oldoldstable. You might like to consider installing Buster as detailed, for example at itsfoss.com/debian-raspberry-pi.
Adding unofficial third-party repositories and installing their packages, apart from any security concerns, may cause breakage so they should be replaced with the official ones provided by Debian. But I think that Raspbian is probably a better choice if your main interest is running wine programs and applications.

[jacky1980]

Try

Code: Select all

apt-get dist-upgrade

Code: Select all

pi@raspberrypi:/ $ sudo apt-get dist-upgrade                         
Reading package lists... Done
Building dependency tree       
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
 systemd : Depends: libsystemd0 (= 215-17+deb8u2) but 215-17+deb8u13 is installed
           Recommends: libpam-systemd but it is not installed
 systemd-sysv : Depends: systemd (= 215-17+deb8u7) but 215-17+deb8u2 is installed
E: Unmet dependencies. Try using -f.

I think I need the systemd package before I can use apt-get for anything else .


The reason why I run the old stable version is because of the emulated x86 architecture. It is the only image currently supportex by exagear. It doesn't look like there will be an update soon. I was able to install other packages before wine just fine. Maybe the reason is because wine is from a different source (ubuntu).

The PPAs are likely the culprit and may have broken the system but, assuming you also have aptitude installed, what does this command show?

Code: Select all

$ aptitude search '?narrow(?installed, ~Oppa)'

Code: Select all

pi@raspberrypi:/ $ aptitude search '?narrow(?installed, ~Oppa)'
bash: aptitude: command not found

Sorry I didn't have aptitude installed. There is no way to install new packages at the moment. Everything else is running fine. Maybe I can edit the PPA files from outside the debian image. I have full access to all files inside the Debian8 with my Raspbian distro.

[kedaha]

Looks like there's a mismatch between the installed version of systemd:
Installed: 215-17+deb8u2
Candidate: 215-17+deb8u7
And libsystemd0
Installed: 215-17+deb8u13
You can confirm this with the command:

Code: Select all

# apt-cache policy systemd libsystemd0

The current installed versions should be identical.
And, while you are about it, unless you have cleaned out the cache, see if you have the previous version of libsystemd0

Code: Select all

# ls /var/cache/apt/archives |grep libsystemd0

[jacky1980]

You can confirm this with the command:

Code: Select all

# apt-cache policy systemd libsystemd0

The current installed versions should be identical.

It looks like they are not identical. At least the security patch version (deb8u2 and deb8u13) are a mismatch.

Code: Select all

pi@raspberrypi:~ $ apt-cache policy systemd libsystemd0
systemd:
  Installed: 215-17+deb8u2
  Candidate: 215-17+deb8u13
  Version table:
     215-17+deb8u13 0
        500 http://security.debian.org/ jessie/updates/main i386 Packages
     215-17+deb8u7 0
        500 http://deb.debian.org/debian/ jessie/main i386 Packages
 *** 215-17+deb8u2 0
        100 /var/lib/dpkg/status
libsystemd0:
  Installed: 215-17+deb8u13
  Candidate: 215-17+deb8u13
  Version table:
 *** 215-17+deb8u13 0
        500 http://security.debian.org/ jessie/updates/main i386 Packages
        100 /var/lib/dpkg/status
     215-17+deb8u7 0
        500 http://deb.debian.org/debian/ jessie/main i386 Packages

And, while you are about it, unless you have cleaned out the cache, see if you have the previous version of libsystemd0

Code: Select all

# ls /var/cache/apt/archives |grep libsystemd0

I might have cleaned my cache trying to fix this mess :/

Code: Select all

pi@raspberrypi:~ $  ls /var/cache/apt/archives |grep libsystemd0
libsystemd0_215-17+deb8u13_i386.deb

only the new version seems to be left

[kedaha]

From your earlier post:

Code: Select all

    /var/cache/apt/archives $ sudo apt-get -f install
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    Correcting dependencies... Done
    The following extra packages will be installed:
      systemd
    Suggested packages:
      systemd-ui
    Recommended packages:
      libpam-systemd
    The following packages will be upgraded:
      systemd
    1 upgraded, 0 newly installed, 0 to remove and 74 not upgraded.
    Need to get 0 B/2574 kB of archives.
    After this operation, 10.2 kB of additional disk space will be used.
    Do you want to continue? [Y/n] y
    (Reading database ... 15446 files and directories currently installed.)
    Preparing to unpack .../systemd_215-17+deb8u7_i386.deb ...
    Unpacking systemd (215-17+deb8u7) over (215-17+deb8u2) ...
    dpkg: error processing archive /var/cache/apt/archives/systemd_215-17+deb8u7_i386.deb (--unpack):
     error creating directory `./etc/systemd/user': Not a directory
    The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
    Alias= settings in the [Install] section, and DefaultInstance= for template
    units). This means they are not meant to be enabled using systemctl.
     
    Possible reasons for having this kind of units are:
    • A unit may be statically enabled by being symlinked from another unit's
      .wants/ or .requires/ directory.
    • A unit's purpose may be to act as a helper for some other unit which has
      a requirement dependency on it.
    • A unit may be started when needed via activation (socket, path, timer,
      D-Bus, udev, scripted systemctl call, ...).
    • In case of template units, the unit is meant to be enabled with some
      instance name specified.
    Processing triggers for dbus (1.8.22-0+deb8u1) ...
    Errors were encountered while processing:
     /var/cache/apt/archives/systemd_215-17+deb8u7_i386.deb
    E: Sub-process /usr/bin/dpkg returned an error code (1)

Code: Select all

dpkg: error processing archive /var/cache/apt/archives/systemd_215-17+deb8u7_i386.deb 

Looks like the wrong architecture for a raspberry pi if you ask me.
Maybe this will help: how-do-i-remove-all-i386-architecture-packages-from-my-debian-installation

[jacky1980]

Looks like the wrong architecture for a raspberry pi if you ask me.
Maybe this will help: how-do-i-remove-all-i386-architecture-packages-from-my-debian-installation

It's an emulated environment for the i386 architecture. The x86 packages are correct (see screenshot) https://i.imgur.com/cgtX1UJ.jpg . I specifically want to be able to run x86 applications otherwise not supported on the ARM architecture.

[kedaha]

Exagear isn't a proper forum topic for discussion here because it's a third-party setup, not official Debian.
It's outside my field so all I can suggest is that you search for, and try options to try and solve the issue of "unmet dependencies." See for instance what-is-the-step-by-step-procedure-to-fix-the-the-following-packages-have-unmet-dependences.

[jacky1980]

Okay, thank you for your help. I think I learned a lot through this process.


I will try purging systemd and init using

Code: Select all

 apt purge systemd