Hi mknoop, I did some more digging and discovered that...

Synaptic says I only have dhcpcd-base, not dhcpcd (the available dhcpd is a curious 'variation', so...?)
which dhcpcd-base = nothing (Huh?)
which dhcpcd = yes (Oh!)

... so that cleared up that mis-direction, kinda. Anyhow, I do have dhcpd after all.

As a result of this 'discovery' I have now been able to reconstruct my tethering script using dhcpd, if, ifconfig, & curl, and it's working ok on both the stripped down Daedalus & the full Excalibur OSs, just needing a few more experiments and tweaks to get a reliable working tool.

Thanks for the ideas and nudges guys. :)

Suite freia is currently in "testing mode" and testing is merely a symbolic link in the remote repository to freia to indicate that. You don't declare testing as a package repository. There's a great big bag of confusion lingering in using it as source point even when it perhaps seems to work fine right now.

Suite ceres, which you don''t have a stanza for, is now and always in "unstable mode" and unstable is merely a symbolic link in the repository repository to ceres. You don't declare unstable as package repository. The lingering confusion bag is somewhat smaller, but still, don't.

Note that "unstable mode" means that there is no dust of promise that the collective of package versions work together. Perhaps often they do, and where it's discovered they don't, it called a bug and it causes a flurry of activities for the package developers attempting to deal with it.

... you need to change "deb.devuan.org" to "archive.devuan.org" ...

Thanks, that made it work.

Regardless of that, any updates will likely be too late. I just copy the yt-dlp script to my user's bin/ so I don't have to be root to update it, and I update it whenever I use it. (run: yt-dlp -U)
From here: https://github.com/yt-dlp/yt-dlp

this aligns with "next-testing" and "testing" from the reportbug-window in gui-mode.

have included reference to the 3 packages, but the rest is up to the responsible persones.
if the program is included int the repos, it should be able to run - no questions asked - that is maybe universally agreeable.

thank you again for letting  know of the program and proposing a "fix".

zk is not available in the official Debian repositories, which is the reason for it not being in the Devuan repositories.

If and when it gets included in the Debian repositories and has no 'unfixable' dependencies on systemd, you will find it after a few days in the Devuan repositories.

Until then, you (most probably) have the option of building it from source.

Best,

A.

Recompiling a debian package for devuan makes no sense. For 99% of the packages in the repository, that's like saying you want to recompile a debian package for debian. They are the exact same packages. Whenever you install something in devuan, if it's not one of our forked packages, apt pulls it from the debian repository. Amprolla stands between you and the debian repo to filter out the banned packages.

Certainly, if you want to change something in the package, then yeah, you can recompile it with your changes.

That's what we do with the packages we fork. We recompile them to remove the systemd dependency.
Here's some documentation about that: https://git.devuan.org/devuan/documenta … ngGuide.md

What a terrible idea. IOW, probably what they are doing.

Note it is still available for "bleeding edge" Debian sid, so there must be some other die-hards out there.

I've installed debfoster, and I'll play around with it.
It didn't show up o google searches, or in a synaptic search, so something new learned.
I'll mark this "closed".

Sorry, I thought I'd answered to the "did you update" question above, but apparently I forgot to post or did something wrong :-/

Then, typically, a version code without "devuan" in it indicates that the package is directly a Debian package, whereas a package with "devuan" in it is a Devuan package; i.e., forked typically from Debian packaging sources, modified and built in the Devuan build pipeline and published in the Devuan specific repository overlay.

After boot:

$ sudo ./ps_mem.py -p "`pgrep -f -d, 'wicd|NetworkManager|nm-applet'`"
 Private  +   Shared  =  RAM used	Program
 16.0 KiB + 843.5 KiB = 859.5 KiB	wicd-client
984.0 KiB + 513.5 KiB =   1.5 MiB	python3.13
  1.9 MiB + 642.5 KiB =   2.5 MiB	nm-applet
  2.8 MiB + 661.5 KiB =   3.5 MiB	wicd
  4.0 MiB + 762.5 KiB =   4.7 MiB	NetworkManager

After some time:

984.0 KiB + 429.5 KiB =   1.4 MiB	python3.13
  1.3 MiB + 843.5 KiB =   2.1 MiB	wicd-client
  2.0 MiB + 583.5 KiB =   2.5 MiB	nm-applet
  2.8 MiB + 576.5 KiB =   3.3 MiB	wicd
  3.3 MiB + 307.5 KiB =   3.6 MiB	NetworkManager

With Wicd GUI window open and Wifi networks shown:

  1.6 MiB + 815.5 KiB =   2.4 MiB	python3.13
  2.2 MiB + 597.5 KiB =   2.8 MiB	nm-applet
  2.5 MiB + 346.5 KiB =   2.9 MiB	NetworkManager
  5.9 MiB +   1.0 MiB =   6.9 MiB	wicd
 37.3 MiB +   5.9 MiB =  43.2 MiB	wicd-client

Wicd GUI closed (hidden), nm-applet showing Available networks->

  1.6 MiB + 815.5 KiB =   2.4 MiB	python3.13
  2.8 MiB + 346.5 KiB =   3.2 MiB	NetworkManager
  5.9 MiB +   1.0 MiB =   6.9 MiB	wicd
  5.7 MiB +   2.7 MiB =   8.5 MiB	nm-applet
 36.7 MiB +   4.9 MiB =  41.6 MiB	wicd-client

(After a while...) Wicd GUI closed (hidden), nm-applet showing Available networks->

  1.6 MiB + 814.5 KiB =   2.4 MiB	python3.13
  2.8 MiB + 346.5 KiB =   3.2 MiB	NetworkManager
  6.0 MiB +   1.0 MiB =   7.0 MiB	wicd
  5.9 MiB +   2.7 MiB =   8.7 MiB	nm-applet
 36.7 MiB +   4.9 MiB =  41.6 MiB	wicd-client

Running wicd-curses:

  1.5 MiB + 673.5 KiB =   2.2 MiB	python3.13
  2.8 MiB + 337.5 KiB =   3.1 MiB	NetworkManager
  7.1 MiB + 881.5 KiB =   7.9 MiB	wicd
  5.9 MiB +   2.7 MiB =   8.6 MiB	nm-applet
 27.5 MiB +   2.4 MiB =  29.9 MiB	wicd-curses
 34.8 MiB +   4.6 MiB =  39.4 MiB	wicd-client

(30 minutes later...) wicd-curses is running:

  1.5 MiB + 437.5 KiB =   1.9 MiB	python3.13
 44.0 KiB +   2.0 MiB =   2.0 MiB	wicd-client
  2.4 MiB + 905.5 KiB =   3.3 MiB	nm-applet
  4.0 MiB + 201.5 KiB =   4.2 MiB	NetworkManager
  6.0 MiB + 859.5 KiB =   6.8 MiB	wicd
  5.6 MiB +   1.8 MiB =   7.4 MiB	wicd-curses

This might be irrelevant, but it is part of the NM-suite.

400.0 KiB + 115.5 KiB = 515.5 KiB    ModemManager

PS. I don't know how to memory test ephemeral process like wicd-cli.