Can not update util-linux from v2.27.1-1.0nosystemd to v2.27.1-2.1.0nosystemd:
$>sudo apt-get install util-linux
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:
util-linux : PreDepends: libudev (>= 1) but it is not installable
E: Unable to correct problems, you have held broken packages.
Similar issue w/libmount. I have the latest libudev0 v175-7.2 and libudev1 v228-4 installed.
topic title: [SOLVED] Can not upgrade util-linux
7 posts
• Page 1 of 1
-
Posts: 119
- Joined: 31 May 2014
#1
Last edited by wildstar84 on 26 Aug 2016, 22:54, edited 1 time in total.
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#2
Install eudev.
use-eudev-t6057.html
I need to rebuild the nosystemd version of util-linux. (2 days after the previous upgrade - sigh). Bear with me.
use-eudev-t6057.html
I need to rebuild the nosystemd version of util-linux. (2 days after the previous upgrade - sigh). Bear with me.
-
Posts: 119
- Joined: 31 May 2014
#3
No prob. w/the wait, but now, after reading the link, I'm hesitant a/b installing eudev and bricking my install:"If you have removed any nosystemd stuff from the default apt, then this will almost certainly brick your install." I don't think I've"removed" any"nosystemd" pkgs I've installed, not sure what the"default apt" is? Any additional suggestions or warnings/caveats a/b installing this package? Is it even worth it? - I've got a tone of time and effort invested in this install!
-
Posts: 60
- Joined: 07 Oct 2015
#4
Can not update
„sudo dpkg --configure -a”
Console onto the above command, initiates an endless loop
systemd-helper:32: not found - Cpu 70% Ram 90%
MX15.1 -64bit. Duo CPU E8500 3.16GHz 4GB Ram
NAME
deb-systemd-helper - subset of systemctl for machines not running
systemd
SYNOPSIS
deb-systemd-helper
enable|disable|mask|unmask|is-enabled|was-enabled|debian-installed|update-state|reenable
unit file ...
DESCRIPTION
deb-systemd-helper is a Debian-specific helper script which re-
implements the enable, disable, is-enabled and reenable commands from
systemctl.
The"enable" action will only be performed once (when first installing
the package). On the first"enable", an state file is created which
will be deleted upon"disable", but only when
_DEB_SYSTEMD_HELPER_PURGE=1 to distinguish purge from remove.
The"mask" action will keep state on whether the service was
enabled/disabled before and will properly return to that state on
"unmask".
The"was-enabled" action is not present in systemctl, but is required
in Debian so that we can figure out whether a service was enabled
before we installed an updated service file. See
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://bugs.debian.org/717603"
linktext was:"http://bugs.debian.org/717603"
====================================
for details.
The"debian-installed" action is also not present in systemctl. It
returns 0 if the state file of at least one of the given units is
present.
The"update-state" action is also not present in systemctl. It updates
deb-systemd-helper 's state file, removing obsolete entries (eg
service files that are no longer shipped by the package) and adding new
entries (eg new service files shipped by the package) without
enabling them.
deb-systemd-helper is intended to be used from maintscripts to enable
systemd unit files. It is specifically NOT intended to be used
interactively by users. Instead, users should run systemd and use
systemctl, or not bother about the systemd enabled state in case they
are not running systemd.
ENVIRONMENT
_DEB_SYSTEMD_HELPER_DEBUG
If you export _DEB_SYSTEMD_HELPER_DEBUG=1, deb-systemd-helper will
print debug messages to stderr (thus visible in dpkg runs). Please
include these when filing a bugreport.
AUTHOR
Michael Stapelberg < stapelberg@debian.org >
„sudo dpkg --configure -a”
Console onto the above command, initiates an endless loop
systemd-helper:32: not found - Cpu 70% Ram 90%
MX15.1 -64bit. Duo CPU E8500 3.16GHz 4GB Ram
NAME
deb-systemd-helper - subset of systemctl for machines not running
systemd
SYNOPSIS
deb-systemd-helper
enable|disable|mask|unmask|is-enabled|was-enabled|debian-installed|update-state|reenable
unit file ...
DESCRIPTION
deb-systemd-helper is a Debian-specific helper script which re-
implements the enable, disable, is-enabled and reenable commands from
systemctl.
The"enable" action will only be performed once (when first installing
the package). On the first"enable", an state file is created which
will be deleted upon"disable", but only when
_DEB_SYSTEMD_HELPER_PURGE=1 to distinguish purge from remove.
The"mask" action will keep state on whether the service was
enabled/disabled before and will properly return to that state on
"unmask".
The"was-enabled" action is not present in systemctl, but is required
in Debian so that we can figure out whether a service was enabled
before we installed an updated service file. See
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://bugs.debian.org/717603"
linktext was:"http://bugs.debian.org/717603"
====================================
for details.
The"debian-installed" action is also not present in systemctl. It
returns 0 if the state file of at least one of the given units is
present.
The"update-state" action is also not present in systemctl. It updates
deb-systemd-helper 's state file, removing obsolete entries (eg
service files that are no longer shipped by the package) and adding new
entries (eg new service files shipped by the package) without
enabling them.
deb-systemd-helper is intended to be used from maintscripts to enable
systemd unit files. It is specifically NOT intended to be used
interactively by users. Instead, users should run systemd and use
systemctl, or not bother about the systemd enabled state in case they
are not running systemd.
ENVIRONMENT
_DEB_SYSTEMD_HELPER_DEBUG
If you export _DEB_SYSTEMD_HELPER_DEBUG=1, deb-systemd-helper will
print debug messages to stderr (thus visible in dpkg runs). Please
include these when filing a bugreport.
AUTHOR
Michael Stapelberg < stapelberg@debian.org >
-
Posts: 119
- Joined: 31 May 2014
#5
WHUT????? :/
-
Posts: 60
- Joined: 07 Oct 2015
#6
Excuse me, maybe that I put it onto bad place because of lingual troubles!
But meanwhile onto a new one setup solved the problem. Bar it MX15.1 install the grubot did not put it up now, on the other hand this not big trouble, because there is partedmagic pendriver, which is grub, doctor implies a program.
But meanwhile onto a new one setup solved the problem. Bar it MX15.1 install the grubot did not put it up now, on the other hand this not big trouble, because there is partedmagic pendriver, which is grub, doctor implies a program.
-
Posts: 119
- Joined: 31 May 2014
#7
@Blurey: None of this makes any sense to me, nor does it answer my questions. I'm simply wanting to know if it is possible, and if so, how to properly upgrade these specific packages WITHOUT the risk of bricking my system. Please stick to topic!
Regards,
Jim
Regards,
Jim