trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: September 2020

network-manager-tde - dependency issues - update

From: "William Morder via trinity-users" <trinity-users@...>
Date: Tue, 1 Sep 2020 06:39:01 -0700

On Tuesday 01 September 2020 05:30:03 Dr. Nikolaus Klepp wrote:
> 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
> >
> >
> >
> >

So, I tried to change the Trinity repos from Buster to Beowulf, updated my 
sources.list, and that didn't work at all. Trinity only recognizes Buster. I 
also tried to "pin" the packages to Beowulf (using the option -t beowulf in 
apt-get), to no avail. 

The problem currently remains the same, as related below. 

Hi Nik! Thanks for your help. 

Buster is named only for some oddball third-party stuff; except, that is, for 
Trinity-TDE repos themselves (for which, see below). 

deb-multimedia repos (for ? I forget) 
I could disable them unless I need a specific package; but I seem to recall 
that apt would try to uninstall whatever it was, if the repo is not enabled. 
deb http://www.deb-multimedia.org stable main 
deb-src http://www.deb-multimedia.org stable main 

the repos for Vivaldi (but I could disable these unless I want to upgrade)
deb http://repo.vivaldi.com/snapshot/deb/ stable main


the Tor project

deb http://deb.torproject.org/torproject.org buster stable main
deb-src http://deb.torproject.org/torproject.org buster stable main

Maybe Trinity itself, as I wasn't sure whether to insert Buster or Beowulf. I 
noticed some repositories seem to redirect, but others want it specified, one 
or the other. When I read the instructions and comments on the wiki page, it 
said something about devuan users should "just use debian", etc. 

deb http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/debian buster 
main
deb-src http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/debian 
buster main
deb 
http://mirror.ppa.trinitydesktop.org/trinity/trinity-builddeps-r14.0.0/debian 
buster main
deb-src 
http://mirror.ppa.trinitydesktop.org/trinity/trinity-builddeps-r14.0.0/debian 
buster main

deb http://mirror.ppa.trinitydesktop.org/trinity-sb buster main-r14 deps-r14
deb-src http://mirror.ppa.trinitydesktop.org/trinity-sb buster main-r14 
deps-r14

Bill