Anno domini 2020 Tue, 1 Sep 12:59:58 -0700 William Morder via trinity-users scripsit: > > On Tuesday 01 September 2020 12:51:40 Dr. Nikolaus Klepp wrote: > > Anno domini 2020 Tue, 1 Sep 12:25:43 -0700 > > > > William Morder via trinity-users scripsit: > > > On Tuesday 01 September 2020 09:33:08 Dr. Nikolaus Klepp wrote: > > > > Anno domini 2020 Tue, 1 Sep 06:39:01 -0700 > > > > > > > > William Morder via trinity-users scripsit: > > > > > 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 Beowul repo for trinity is just a link to the Buster Repo. Just use > > > > Buster, it's OK. > > > > > > > > > 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) > > > > > > > > Ok. That is most likely your troublemaker. You'll need to get rid of > > > > all packages from that repo - that will cause some TDE packags to be > > > > removed, too, due to dependencies. Identify one of the deb-multimedia > > > > packages, then use "apt-show-versions" (most likely you'll need to > > > > install it first) and grep for the extensions. This is a tediouse > > > > process, I've been through it a couple of times. The only thing you > > > > maybe miss is libdvdcss2. I think I installed it from the sources. > > > > > > > > Nik > > > > > > Nope. Nothing was installed from that repo (yet), and now it's disabled, > > > once again I updated the sources.list, but apt-get keeps returning the > > > same message: > > > > > > The following packages have unmet dependencies: > > > network-manager : Depends: libpam-systemd > > > E: Unable to correct problems, you have held broken packages. > > > > > > Bill > > > > > > > > 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/de bian buster main > > > > > deb-src > > > > > http://mirror.ppa.trinitydesktop.org/trinity/trinity-builddeps-r14.0. > > > > >0/de bian 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 > > > > Let's check: I get these dependencies for network-mananger. As you see, > > it's homepage is the lore of GNOMEs, so it's deeply entangled with systemd. > > libsystemd0 is a functionless wrapper (on devuan) and libpam-systemd is a > > dummy. If you want to use it, you'll need these 2 packages, too. But I > > don't see systemd in my list. > > > > $ LANGUAGE=en aptitude show network-manager > > Package: network-manager > > Version: 1.14.6-2+deb10u1 > > State: installed > > Automatically installed: yes > > Priority: optional > > Section: net > > Maintainer: Utopia Maintenance Team > > <pkg-utopia-maintainers@...> Architecture: amd64 > > Uncompressed Size: 11,9 M > > Depends: libaudit1 (>= 1:2.2.1), libbluetooth3 (>= 4.91), libc6 (>= 2.26), > > libcurl3-gnutls (>= 7.16.3), libglib2.0-0 (>= 2.43.2), libgnutls30 (>= > > 3.6.5), libjansson4 (>= 2.0.1), libmm-glib0 (>= 1.0.0), libndp0 (>= 1.2), > > libnewt0.52 (>= 0.52.20), libnm0 (= 1.14.6-2+deb10u1), libpolkit-agent-1-0 > > (>= 0.99), libpolkit-gobject-1-0 (>= 0.104), libpsl5 (>= 0.13.0), > > libreadline7 (>= 6.0), libselinux1 (>= 1.32), libsystemd0 (>= 221), > > libteamdctl0 (>= 1.9), libudev1 (>= 183), libuuid1 (>= 2.16), lsb-base, > > wpasupplicant, dbus, udev, adduser, libpam-systemd, policykit-1 PreDepends: > > init-system-helpers (>= 1.54~) > > Recommends: ppp, dnsmasq-base, iptables, modemmanager, crda, > > isc-dhcp-client Suggests: libteam-utils > > Conflicts: network-manager:i386 > > Breaks: ppp (>= 2.4.7-3~), ppp:i386 (>= 2.4.7-3~), ppp (< 2.4.7-2+~), > > ppp:i386 (< 2.4.7-2+~) Description: network management framework (daemon > > and userspace tools) > > > > Homepage: https://wiki.gnome.org/Projects/NetworkManager > > Tags: implemented-in::c, interface::daemon, network::configuration, > > protocol::dhcp, protocol::ip, role::program, use::configuring > > > > nik@t61:~$ LANGUAGE=en aptitude show libpam-systemd > > No candidate version found for libpam-systemd > > Package: libpam-systemd > > State: not a real package > > Provided by: libpam-elogind (241.4-2) > > nik@t61:~$ LANGUAGE=en aptitude show libsystemd0 > > Package: libsystemd0 > > Version: 241-7~deb10u4 > > State: not installed > > Multi-Arch: same > > Priority: optional > > Section: libs > > Maintainer: Debian systemd Maintainers > > <pkg-systemd-maintainers@...> Architecture: amd64 > > Uncompressed Size: 786 k > > PreDepends: libc6 (>= 2.28), libgcrypt20 (>= 1.8.0), liblz4-1 (>= > > 0.0~r122), liblzma5 (>= 5.1.1alpha+20120614) Breaks: libsystemd0:i386 (!= > > 241-7~deb10u4) > > Replaces: libsystemd0:i386 (< 241-7~deb10u4) > > Provided by: libelogind0 (241.4-2) > > Description: systemd utility library > > > > Homepage: https://www.freedesktop.org/wiki/Software/systemd > > Tags: role::shared-lib > > > > That's all very interesting, but I still can't install the tdenetworkmanager. > > :-> > > If it is just a wrapper, and not an actual package, then why can we have some > sort of wrapper-systemd-trinity to circumvent the issue? Or why does > tdenetworkmanager have to depend on outside packages at all? > > As for wicd, it would be an adequate replacement in the meanwhile, but even > wicd is only half-working, since now I must reboot a few times every day, > just because I want to switch from online to offline, then switch back again. > > Bill This is also in my system: # cat /etc/apt/apt.conf.d/01norecommend APT::Install-Recommends "false"; APT::Install-Suggests "false"; APT::AutoRemove::RecommendsImportant "false"; APT::AutoRemove::SuggestsImportant "false"; > > > Bill > > --------------------------------------------------------------------- > To unsubscribe, e-mail: trinity-users-unsubscribe@... > For additional commands, e-mail: trinity-users-help@... > 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 > > -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...