Bug#855349: Your mail
On Sat, 1 Jul 2017 20:55:01 +0200 pressy@terta.de wrote:
> for me an
>
>
> $ apt-get remove kscreensaver kscreensaver-xsavers
>
> and
>
> $ apt autoremove
>
> solved the issue.
>
Nothing worked for me while I had the stretch repositories in my
/etc/apt/sources.list.
Once I went back to strictly jessie entries and did an update then I
could finally remove the
problematic kde packages and *then* add back in the stretch entries
and finally update
I ended up removing
dolphin kdepimlibs-kio-plugins thunderbird
and then did the
apt-get autoremove
Then added back in the stretch (but not stretch/updates) repository entry
Then got:
...
Selecting previously unselected package udev.
dpkg: regarding .../udev_232-25+deb9u2_amd64.deb containing udev:
udev conflicts with hal
hal (version 0.5.14-8) is present and installed.
dpkg: error processing archive
/var/cache/apt/archives/udev_232-25+deb9u2_amd64.deb (--unpack):
conflicting packages - not installing udev
dpkg: considering deconfiguration of ifupdown, which would be broken
by installation of systemd ...
dpkg: yes, will deconfigure ifupdown (broken by systemd)
Preparing to unpack .../systemd_232-25+deb9u2_amd64.deb ...
De-configuring ifupdown (0.7.53.1) ...
Unpacking systemd (232-25+deb9u2) over (215-17+deb8u8) ...
Preparing to unpack .../ifupdown_0.8.19_amd64.deb ...
Unpacking ifupdown (0.8.19) over (0.7.53.1) ...
Preparing to unpack .../liblvm2app2.2_2.02.168-2_amd64.deb ...
Unpacking liblvm2app2.2:amd64 (2.02.168-2) over (2.02.111-2.2+deb8u1) ...
Preparing to unpack .../lvm2_2.02.168-2_amd64.deb ...
Unpacking lvm2 (2.02.168-2) over (2.02.111-2.2+deb8u1) ...
Preparing to unpack .../libdevmapper1.02.1_2%3a1.02.137-2_amd64.deb ...
Unpacking libdevmapper1.02.1:amd64 (2:1.02.137-2) over
(2:1.02.90-2.2+deb8u1) ...
Preparing to unpack .../dmsetup_2%3a1.02.137-2_amd64.deb ...
Unpacking dmsetup (2:1.02.137-2) over (2:1.02.90-2.2+deb8u1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Errors were encountered while processing:
/var/cache/apt/archives/udev_232-25+deb9u2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Then did the suggested
apt-get install -f
....
175 upgraded, 68 newly installed, 52 to remove and 2146 not upgraded.
305 not fully installed or removed.
Need to get 0 B/97.9 MB of archives.
After this operation, 177 MB disk space will be freed.
Do you want to continue? [Y/n]
Reading changelogs... Done
Extracting templates from packages: 100%
Preconfiguring packages ...
setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file
(Reading database ... 403552 files and directories currently installed.)
Removing jackd2-firewire (1.9.10+20150825git1ed50c92~dfsg-5) ...
(Reading database ... 403547 files and directories currently installed.)
Preparing to unpack .../klibc-utils_2.0.4-9_amd64.deb ...
Adding 'diversion of /usr/share/initramfs-tools/hooks/klibc to
/usr/share/initramfs-tools/ho....
....
Then I got
...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-3.16.0-7-amd64
W: initramfs-tools configuration sets
RESUME=UUID=09d39f7b-2f6e-4cfc-86fe-97da40d7b784
W: but no matching swap device is available.
I: The initramfs will attempt to resume from /dev/sdd3
I: (UUID=8ace5863-41ee-4d43-8dc3-d0b2aa9bf7ef)
I: Set the RESUME variable to override this.
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.36.5-2+deb9u2) ...
Processing triggers for dbus (1.10.26-0+deb9u1) ...
Processing triggers for menu (2.1.47) ...
Errors were encountered while processing:
rpcbind
nfs-common
nfs-kernel-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
An apt-get install -f
failed intermediately again
and apt-get autoremove also gives similar errors
Setting up rpcbind (0.2.3-0.6) ...
A dependency job for rpcbind.service failed. See 'journalctl -xe' for details.
invoke-rc.d: initscript rpcbind, action "start" failed.
● rpcbind.service - RPC bind portmap service
Loaded: loaded (/lib/systemd/system/rpcbind.service; enabled;
vendor preset: enabled)
Active: active (exited) since Tue 2002-01-01 11:03:19 AEDT; 17
years 0 months ago
Docs: man:rpcbind(8)
CGroup: /system.slice/portmap.service
Jan 18 13:14:58 azza systemd[1]: rpcbind.service changed dead -> running
Jan 18 13:20:12 azza systemd[1]: rpcbind.service changed dead -> running
Jan 18 13:20:26 azza systemd[18724]: Executing: /etc/init.d/rpcbind stop
Jan 18 13:20:31 azza systemd[1]: rpcbind.service changed dead -> exited
Jan 18 17:54:03 azza systemd[1]: Dependency failed for RPC bind portmap service.
Jan 18 17:54:03 azza systemd[1]: rpcbind.service: Job
rpcbind.service/start failed wit…ncy'.
Jan 18 17:57:31 azza systemd[1]: Dependency failed for RPC bind portmap service.
Jan 18 17:57:31 azza systemd[1]: rpcbind.service: Job
rpcbind.service/start failed wit…ncy'.
Jan 18 17:58:08 azza systemd[1]: Dependency failed for RPC bind portmap service.
Jan 18 17:58:08 azza systemd[1]: rpcbind.service: Job
rpcbind.service/start failed wit…ncy'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package rpcbind (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of nfs-common:
nfs-common depends on rpcbind; however:
Package rpcbind is not configured yet.
dpkg: error processing package nfs-common (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of nfs-kernel-server:
nfs-kernel-server depends on nfs-common (= 1:1.3.4-2.1); however:
Package nfs-common is not configured yet.
dpkg: error processing package nfs-kernel-server (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
rpcbind
nfs-common
nfs-kernel-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
apt remove rpcbind
and
apt-get autoremove
Then things seem ok
The apt dist-upgrade seems to kick off ok
Then added in stretch/updates and kicked off another dist-upgrade
which was also successful.
Reply to: