Anno domini 2020 Tue, 1 Sep 05:20:27 -0700 William Morder via trinity-users scripsit:
Another new problem, and I swear, this one is not of my own making; unless of course you mean that I am one of those no-systemd devuan dissidents.
So far, in my new Beowulf installation, I've been using wicd to connect; not because I prefer it, but only because it's there. When I was running Jessie, over the past few years tdenetworkmanager and wicd seemed to fight it out, and I couldn't figure out the cause. Sometimes, on a fresh installation, I would be able to use tdenetworkmanager; sometimes not. On the whole, I ended up using wicd about 3/4 of the time. But anyway, at least I could connect, and had no serious issues. It was more a matter of preference. One thing I did notice, though, is that wicd somehow would assume root privileges, even though I did not run it as root.
Anyway, so in my new installation, I would like to use tdenetworkmanager, but now I get these error messages. I list them in order of discovery:
1 - network-manager-tde depends on network-manager (Yeah, I knew that, but huh?) The following packages have unmet dependencies: network-manager-tde : Depends: network-manager (>= 0.7.0) but it is not going to be installed E: Unable to correct problems, you have held broken packages. 2 - Let's grab that dependency ... The following packages have unmet dependencies: network-manager : Depends: libpam-systemd
3 - Let's try to build-dep ... The following packages have unmet dependencies: builddeps:network-manager : Depends: libpolkit-agent-1-dev (>= 0.97) but it is not going to be installed Depends: systemd (>= 185) but it is not installable
4 - Why can't I build-dep for network-manager? The following packages have unmet dependencies: builddeps:network-manager : Depends: libpolkit-agent-1-dev (>= 0.97) but it is not going to be installed Depends: systemd (>= 185) but it is not installable E: Unable to correct problems, you have held broken packages.
So the only answer I get is that I must install systemd in order to run tdenetworkmanager? I've already tried some command-line voodoo to force installation, ignore held packages, all that good stuff.
I would just give up for the present, and rely on wicd, which at least has always worked pretty well. It's been my #2 choice, when I've had issues with tdenetworkmanager, which has been about 3/4 of the past couple years. It may be an issue with Debian, because technically TDE-Trinity uses Debian Buster packages, not Devuan Beowulf; they are the same, mostly, but not always.
Now my problem is, once I go online, thereafter I cannot go offline. When I try, I usually find that I still have an active connection that won't die; when I do succeed in going offline, after that I cannot get back online, but must reboot in order to get a connection again.
My verdict is, something's wrong.
:)
tdenetworkmanager works on beowulf, wicd does not - that's what I found when I upgraded. But there should not be any systemd dependecy when you are on devuan. Could you check if that you do not have accidentally activated some debian repository?
Nik
Bill
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting