3

I'm trying to upgrade my wheezy server to Debian 8 jessie.

I changed /etc/apt/sources.list to:

deb http://debian.mirror.serverloft.de/debian/ jessie main contrib non-free
deb http://debian.mirror.serverloft.de/debian-security/ jessie/updates main contrib non-free

Commands:

apt-get update
apt-get upgrade
apt-get dist-upgrade

This resulted in a short message about dpkg returning an error code 1.

I have a protocol, created by the script command; there I found:

Calculating upgrade... Failed
The following packages have unmet dependencies:
 udev : Breaks: plymouth (< 0.9.0-7) but 0.8.5.1-5 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

I tried to repair this:

root@myhost:~# apt-get install udev
Reading package lists... Done
Building dependency tree
Reading state information... Done
udev is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 73 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]?
Setting up plymouth (0.9.0-9) ...
update-initramfs: deferring update (trigger activated)
update-rc.d: error: expected NN after start
usage: update-rc.d [-n] [-f] <basename> remove
   update-rc.d [-n] <basename> defaults [NN | SS KK]
   update-rc.d [-n] <basename> start|stop NN runlvl [runlvl] [...] .
   update-rc.d [-n] <basename> disable|enable [S|2|3|4|5]
        -n: not really
        -f: force

The disable|enable API is not stable and might change in the future.
dpkg: error processing package plymouth (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for initramfs-tools (0.120+deb8u2) ...
Errors were encountered while processing:
 plymouth
**E: Sub-process /usr/bin/dpkg returned an error code (1)**

Information about plymouth:

root@myhost:~# dpkg -s plymouth
Package: plymouth
Status: install ok **half-configured**
Priority: optional
Section: misc
Installed-Size: 801
Maintainer: Laurent Bigonville <[email protected]>
Architecture: amd64
**Version: 0.9.0-9**
**Config-Version: 0.8.5.1-5**
Replaces: plymouth-drm (<< 0.9.0-6~), plymouth-themes (<< 0.9.0-8~)
Depends: libc6 (>= 2.14), libdrm2 (>= 2.4.25), libpng12-0 (>= 1.2.13-4), libudev1 (>= 183), initramfs-tools | dracut, init-system-helpers (>= 1.18)
Pre-Depends: multiarch-support
Suggests: desktop-base, plymouth-themes
Breaks: plymouth-drm (<< 0.9.0-6~), plymouth-themes (<< 0.9.0-8~)
Conflicts: console-common
Conffiles:
 /etc/init.d/plymouth e1440675aa15e8e43da91575295fd2d1
 /etc/init.d/plymouth-log 0f1be14b21796a952e115c03a86787e0
 /etc/plymouth/plymouthd.conf 5c2a5b4b4cb7cbbad0beaab8558200ce
Description: boot animation, logger and I/O multiplexer
 Plymouth provides a boot-time I/O multiplexing framework

Thus, plymouth can't be configured; the configured version is lower than the installed version of plymouth.

What can do to fix this? Thank you!

Update: I tried to remove plymouth:

root@myhost:~# LANG=C apt-get remove plymouth
Reading package lists... Done
Building dependency tree
Reading state information... Done
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:
 upstart : Depends: mountall but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
root@myhost:~# LANG=C apt-get purge plymouth
Reading package lists... Done
Building dependency tree
Reading state information... Done
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:
 upstart : Depends: mountall but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

root@myhost:~# LANG=C apt-get dist-upgrade
...
Get:150 http://debian.mirror.serverloft.de/debian/ jessie/main lynx all 2.8.9dev1-2+deb8u1 [232 kB]
Fetched 69.6 MB in 4s (15.6 MB/s)
Reading changelogs... Done
apt-listchanges: Mailing root: apt-listchanges: news for myhost
Extracting templates from packages: 100%
Preconfiguring packages ...
Setting up plymouth (0.9.0-9) ...
update-initramfs: deferring update (trigger activated)
update-rc.d: error: expected NN after start
usage: update-rc.d [-n] [-f] <basename> remove
   update-rc.d [-n] <basename> defaults [NN | SS KK]
   update-rc.d [-n] <basename> start|stop NN runlvl [runlvl] [...] .
   update-rc.d [-n] <basename> disable|enable [S|2|3|4|5]
        -n: not really
        -f: force

The disable|enable API is not stable and might change in the future.
dpkg: error processing package plymouth (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for initramfs-tools (0.120+deb8u2) ...
Errors were encountered while processing:
 plymouth
E: Sub-process /usr/bin/dpkg returned an error code (1)

Update 2: More things I tried but which didn't help:

apt-get dist-upgrade udev plymouth
apt-get install -f plymouth
dpkg --configure -a
apt-get install upgrade-system; upgrade-system
Stephen Kitt
  • 411,918
  • 54
  • 1,065
  • 1,164
Tobias
  • 129
  • 1
  • 8
  • I'd really like to know why my question has been down-voted; but there was no explaining comment. Vandalism? – Tobias Oct 30 '16 at 22:44
  • 1
    Have you removed all `wheezy` references from your sources? (`/etc/apt/sources.list` and files in `/etc/apt/sources.list.d`.) The initial installation of `plymouth` was the `wheezy` version, and that appears to cause issues... – Stephen Kitt Oct 31 '16 at 17:16
  • I was not aware of the directory `/etc/apt/sources.list.d/`; there was a reference to wheezy backports, and (not used anymore) `http://download.opensuse.org/repositories/isv:ownCloud:community/Debian_7.0/`. I commented them out. Doesn't seem to make a difference. – Tobias Oct 31 '16 at 23:56

5 Answers5

2

I had the same problem on a systemd-less wheezy server. The solution was to:

apt-get remove plymouth   # also removes upstart and mountall
apt-get -f install        # not sure this is necessary
apt-get upgrade
apt-get dist-upgrade
apt-get install plymouth upstart mountall  # removes systemd-sysv
apt-get remove systemd
martinwguy
  • 121
  • 3
1

Bug780443 seems your problem. Briefly, someone has solved running:

apt dist-upgrade udev plymouth

I also found this: the proposed solution is install the package upgrade-system to upgrade from Wheezy to Jessie with the command upgrade-system.

andreatsh
  • 1,985
  • 1
  • 14
  • 15
  • I tried `apt-get dist-upgrade udev plymouth` (I don't have an `apt` program; a typo, right?) - same error. I tried `upgrade-system` as well; IFAICS this doesn't tackle special problems at all but simply aids the process. – Tobias Oct 29 '16 at 19:52
  • It was not a typo, the new version of `apt` does not require `apt-get`. You can try to fix unmet dependecies, but now it's hard to understand what went wrong in your dist-upgrade. It seems there are many misconfiguration, maybe a fresh installation could be the faster and painless way to solve. It depends on how much time you want to spend on this problem. – andreatsh Oct 29 '16 at 21:14
  • This new `apt` version is part of `jessie`, rather than `wheezy`, right? However, unless something unexpected happens, I'll reset the (virtual) server to a fresh image which I expect to be `jessie`. – Tobias Nov 01 '16 at 09:25
0

You tried before updating to remove this package?

:~# apt-get remove plymouth

or

:~# apt-get purge plymouth

Try to do it, and then upgrade the system. Reply if this fixes the problem or paste what apt show on the screen.

gruntboy
  • 386
  • 2
  • 6
0

Not the answer, but useful info;

the usual way to upgrade is;

sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
> (now change the apt/sources)
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

ie you should always ensure you are on latest stable before switching any repos.

and as a first go-to for resolving dpkg issues, you can try this:

sudo dpkg --configure -a

to fix / re-try failed dpkg actions, and you can ask apt to try to fix any package issues by running:

sudo apt-get -f install

this will either get missing dependancies or it will roll back a failed install.

either way it will try to fix your apt db for you.

UPDATE:

not sure why -1, debian states the same with the addition of "apt full-upgrade".

https://www.debian.org/doc/manuals/debian-handbook/sect.dist-upgrade.en.html

also OP should be able to resolve the issue using dpkg configure / apt-get --fix-broken.

mikejonesey
  • 1,950
  • 10
  • 17
  • I don't know the reason for the down-vote either; I'd expect a comment about it. However, I don't have an `apt` program which could support an `full-upgrade` argument; and I could not find any valid command `dpkg [--]configure` or `apt-get` to support a `--fix-broken` option. – Tobias Oct 29 '16 at 19:59
  • the "full-upgrade" option is part of apt, not apt-get, (`$ which apt /usr/bin/apt`, although i've never used this option)., `$ sudo dpkg --configure -a`, and `apt-get --fix-broken install` on the other hand are both commands i use fairly often. – mikejonesey Oct 29 '16 at 21:26
  • Another try `dpkg --force-depends -P plymouth plymouth-themes` but be warned. Options with --force can be dangerous for your Package-management. Read ` dpkg --force-help` first. –  Oct 31 '16 at 09:40
  • Well, I read, and I executed. The `dist-upgrade` still doesn't work because `mountall` depends on `plymouth` which in turn is now `not installable` ... Probably I'll finally install a fresh image. – Tobias Oct 31 '16 at 23:37
  • This is wired. `apt-cache policy plymouth plymouth: Installiert: (keine) Installationskandidat: 0.9.0-9 Versionstabelle: 0.9.0-9 0 500 http://http.us.debian.org/debian/ jessie/main amd64 Package` –  Nov 01 '16 at 10:42
0

Switch you sources.list to us server. German Mirrors are often not synchronised. rm -rf /var/lib/apt/lists/* apt-get clean apt-get update && apt-get -f install and apt-get dist-upgrade

  • I replaced the hostnames by `packages.debian.org` and executed the commands; sadly, this didn't help. – Tobias Oct 30 '16 at 20:20