The officially official Devuan Forum!

You are not logged in.

#1 2017-07-19 05:57:13

John Franklin
Registered: 2017-03-06
Posts: 0

network-manager depends on libpam-systemd

The network-manager package for ascii depends on libpam-systemd, which prevents it from being installed.

# apt install network-manager
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:
network-manager : Depends: libpam-systemd but it is not going to be
E: Unable to correct problems, you have held broken packages.
# lsb_release -a
No LSB modules are available.
Distributor ID:    Devuan
Description:    Devuan GNU/Linux 2.0 (ascii)
Release:    2.0
Codename:    ascii


Project: devuan-packages/network-manager
Issue: #4
By: John Franklin


#2 Yesterday 09:28:41

Registered: Yesterday
Posts: 1

Re: network-manager depends on libpam-systemd


#3 Yesterday 15:15:58

From: Any witch way
Registered: 2017-07-12
Posts: 393

Re: network-manager depends on libpam-systemd

Artix uses networkmanager without systemd, OpenRC by default, and works fine for the past 6mos.    No need for wicd or connman or anything else.  But artix uses substitute libraries for dependencies.  It comes with an openrc-script but libpam is nowhere in sight.  So you may want to take a look at what the openrc script says on Artix.
Obarun that uses S6 for init, does not follow the same way, if dependencies are pointing towards systemd stuff they are just not installable, and uses Arch for everything else (95% of the system).


# Copyright (c) 2008 Saleem Abdulrasool <>
# Copyright 2013-2017 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2

description="NetworkManager daemon. The service is marked as started only \
when a network connection is established."

depend() {
	need dbus
	use consolekit elogind
	provide net

start() {
	# If we are re-called by a dispatcher event, we want to mark the service
	# as started without starting the daemon again
	yesno "${IN_BACKGROUND}" && return 0


	ebegin "Starting NetworkManager"
	start-stop-daemon --start --quiet --pidfile /run/NetworkManager/ \
		--exec /usr/bin/NetworkManager -- --pid-file /run/NetworkManager/
	local _retval=$?
	eend "${_retval}"
	if [ "x${_retval}" = 'x0' ] && ! nm-online -t "${INACTIVE_TIMEOUT}"; then
		einfo "Marking NetworkManager as inactive. It will automatically be marked"
		einfo "as started after a network connection has been established."
	return "${_retval}"

stop() {
	# If we are re-called by a dispatcher event, we want to mark the service
	# as inactive without stopping the daemon
	if yesno "${IN_BACKGROUND}"; then
		mark_service_inactive "${SVCNAME}"
		return 0

	ebegin "Stopping NetworkManager"
	local pidfile=/run/NetworkManager/
	if [ ! -e "${pidfile}" ] && [ -e /run/ ]; then 
		# Try stopping the pid file used by <0.9.7
		start-stop-daemon --stop --quiet --pidfile "${pidfile}"
		[ ${ret} = 0 ] && [ -e "${pidfile}" ] && rm "${pidfile}"
		eend ${ret}
		start-stop-daemon --stop --quiet --pidfile "${pidfile}"
		eend $?

# vim: set ft=gentoo-init-d ts=4 :


# Copyright (c) 2012 Alexandre Rostovtsev
# Released under the 2-clause BSD license.

# Ensures that the NetworkManager OpenRC service is marked as started and
# providing net only when it has a successful connection.

if [ ! -e "/run/openrc/softlevel" ]; then
	# OpenRC is not running
	exit 0

# Ensure rc-service is in PATH

# Exit if the NetworkManager OpenRC service is not running
rc-service NetworkManager status 2>&1 | grep -Eq "status: (starting|started|inactive|stopping)" || exit 0

# Call rc-service in background mode so that the start/stop functions update
# NetworkManager service status to started or inactive instead of actually
# starting or stopping the daemon

case "$2" in
	up) nm-online -t 0 -x ||
		! rc-service NetworkManager status 2>&1 | grep -q started &&
		exec rc-service NetworkManager start ;;
	down) nm-online -t 0 -x ||
		rc-service NetworkManager status 2>&1 | grep -q stopped ||
		exec rc-service NetworkManager stop ;;
	pre-sleep) rc-service NetworkManager status 2>&1 | grep -q stopped ||
		exec rc-service NetworkManager stop ;;
exit 0
# vim: set ts=4:


#4 Yesterday 22:28:23

Registered: 2016-12-05
Posts: 312

Re: network-manager depends on libpam-systemd

It was just announced today that Network Manager is now able to be installed in Ascii...

Dear D1rs, the ASCII sprint continues, and many bugs have been squashed. In particular, there is a new (installable) version of network-manager in ascii (1.6.2-3+devuan1). This solves the outstanding #133, thanks to a patch suggested by Edoardo: and a little bit of stitching. Please try it out, and report any bug on The ASCII sprint is not yet over. Please join in on #devuan-dev to help out if you like. Come on, let's put ASCII out! The Dev1Devs --

I have been Devuanated, and my practice in the art of Devuanism shall continue until my Devuanization is complete. Until then, I will strive to continue in my understanding of Devuanchology, Devuanprocity, and Devuanivity.

Veni, vidi, vici vdevuaned. I came, I saw, I Devuaned. wink


#5 Yesterday 22:41:39

Registered: 2016-11-25
Posts: 691

Re: network-manager depends on libpam-systemd

This sprint weekend has been quite productive.


Board footer