The officially official Devuan Forum!

You are not logged in.

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

John Franklin
d1g
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
installed
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

Offline

#2 2017-12-17 09:28:41

etrapani
Member
Registered: 2017-12-17
Posts: 1

Re: network-manager depends on libpam-systemd

Offline

#3 2017-12-17 15:15:58

fungus
Member
From: Any witch way
Registered: 2017-07-12
Posts: 454
Website

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).

/etc/conf.d/NetworkManager

#!/usr/bin/openrc-run
# Copyright (c) 2008 Saleem Abdulrasool <compnerd@compnerd.org>
# 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

	[ -z "${INACTIVE_TIMEOUT}" ] && INACTIVE_TIMEOUT="1"

	ebegin "Starting NetworkManager"
	start-stop-daemon --start --quiet --pidfile /run/NetworkManager/NetworkManager.pid \
		--exec /usr/bin/NetworkManager -- --pid-file /run/NetworkManager/NetworkManager.pid
	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."
		mark_service_inactive
	fi
	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
	fi

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

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

/etc/NetworkManager/dispatcher.d/10-openrc-status

#!/bin/sh
# 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
fi

# Ensure rc-service is in PATH
PATH="${PATH}:/usr/bin:/usr/bin"

# 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
export IN_BACKGROUND=YES

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 ;;
esac
exit 0
# vim: set ts=4:

Offline

#4 2017-12-17 22:28:23

MiyoLinux
Member
Registered: 2016-12-05
Posts: 376

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: http://bugs.devuan.org//cgi/bugreport.cgi?bug=133 and a little bit of stitching. Please try it out, and report any bug on bugs.devuan.org. 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

Offline

#5 2017-12-17 22:41:39

golinux
Administrator
Registered: 2016-11-25
Posts: 727

Re: network-manager depends on libpam-systemd

This sprint weekend has been quite productive.

Offline

#6 2017-12-18 22:09:50

fungus
Member
From: Any witch way
Registered: 2017-07-12
Posts: 454
Website

Re: network-manager depends on libpam-systemd

Suspecting that nm comes from the same source of all evil, what are the alternatives these days to no-nm
What is the simplest minimal equivalent to eth/wifi connection?

Offline

#7 2017-12-18 22:39:40

MiyoLinux
Member
Registered: 2016-12-05
Posts: 376

Re: network-manager depends on libpam-systemd

If one only installs the base system from a netinstall and builds on top of that...and if one only uses a wired connection...there is no need for network manager, wicd, connman, etc.

May not be the answer you're looking for...  tongue


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

Offline

#8 2017-12-18 23:07:39

golinux
Administrator
Registered: 2016-11-25
Posts: 727

Re: network-manager depends on libpam-systemd

fungus wrote:

Suspecting that nm comes from the same source of all evil, what are the alternatives these days to no-nm
What is the simplest minimal equivalent to eth/wifi connection?

Take a look at KatolaZ netset I think it's in the repos but certainly in git.

Offline

#9 2017-12-18 23:11:48

fungus
Member
From: Any witch way
Registered: 2017-07-12
Posts: 454
Website

Re: network-manager depends on libpam-systemd

I am a bit confused on the networking tools, from disto to distro, what is the base?
Where does wpa_supplicant stand in, etc.
I don't think wicd/connman would work without a networking infrastructure already in place.

Offline

#10 2017-12-19 02:36:46

ralph.ronnquist
Administrator
From: Clifton Hill, Victoria, AUS
Registered: 2016-11-30
Posts: 137

Re: network-manager depends on libpam-systemd

For me, the easiest thing is to drop some lines into '/etc/network/interfaces' to declare the access points, and then use the ifup/ifdown commands to operate the interface. For example, you might have this in the file:

iface hemma inet dhcp
    wpa-ssid hemma
    wpa-psk 0123456789abcdef9876543210

The you bring up the interface with this:

# ifup wlan0=hemma

etc (include obvious generalization here)


Contradicting myself, on some systems, I use wicd-cli, which I suppose would be next in line for me. Mostly because it doesn't depend on much. That's the wicd daemon with its ncurses based operator interface (it was called "graphical interface" some few years ago).

Offline

Board footer