No apologies needed.
None whatsoever.

No scratches registered either. 
All's well ...

I was just taking the piss.  8^°

But we are far from the original thread subject now.
So just to clarify.

One WiCD package (1.7.4+tb2-6+devuan1.1) uses python-wicd and should work if you have python 2.7.16-1 installed.
Another WiCD package (1.7.4+tb2-6+devuan2) is the one that I previously referred to, the transitional package.

With respect to the other WiCD package (1.7.4+tb2+2019.09.18git2e0ba579-1) the changelog.Debian file reads:

If it actually runs in Deadalus, it will be as any software running on unstable, prone to have problems.

The WiCD package (1.7.4+tb2-6+devuan2) actually starts whatever you have decided to install (ie: network-manager-gnome | network-manager, etc.), so stopping it and starting WiCD would start the transitioned package again.

No matter, I still have time to think up something else.

Thanks for your input.

Best,

A.

I just downloaded these packages and installed them in my Daedalus.
This procedure is probably easier for me to do because of the full-fledged DE. There is a package manager that opens them by clicking in the file manager window, can simply do a test without installation, open a file for viewing or a window of a dependent package.

In the end, everything was installed, I stopped the network-manager service, started the wicd service and everything worked.
I don’t know if this is necessary. Just showed one of the options.

Regards.

P.S.In addition to the packages in the link, a couple of python packages from the  Daedalus repository were required/

Let me see ....
Yes, although it was not pertinent to the original subject matter, I did answer the question.

See?
Now, just to settle the confusion and nothing more:

Have a look here.

As you can see that package is WiCD only by name.

It is just a transitional package that works as a front end to any one of its listed dependencies:
ie: network-manager-gnome | network-manager | connman-gtk | cmst | connman-ui

From the README.Devuan file:

That said, it seems that Debian had a Python 3 version of WiCD in its experimental repository accepted in late 2019.

But it has not had any attention paid to it since then and something tells me that it will remain so.

Thanks for your input.

TG.

I have used WiCD for quite a few years now, quickly became second nature to do so.

Since the guy didn’t deign to answer the question “What to do in 3 months?”...

Wicd taken from here
https://ftp.debian.org/debian/pool/main/w/wicd/
works on Daedalus out of the box. Look at package dependencies, any python...
Here is a screenshot of the terminal and the Wi-Fi network scanned.
image hosting

Indeed ...
Could be.

I have not used WiFi in my box for the longest while now, only with my Asus 1000HE when there is some issue with my telco's ADSL and I get to borrow my next door neighbour's WiFi to check something.

Like many here, I have used WiCD for quite a few years now, quickly became second nature to do so.
Its main feature being that it is light, fast and, in all hese years, it always worked properly and never caused me the sort of grief I read about with other connection managers.

Not using WiFi in my box, maybe I should resort to something even simpler, such as a CLI start/stop connection
I recall a couple of frequent posters (not seen for a while now) speaking wonders of that approach.

I'll have to think about it.

Thanks for your input.

Best regards,

A.

Right ...

Another possible solution.
I'll have a look at that one too.

Thanks a lot for your input.

Best,

A.

Hmm ...
Don't sell your self short ...  8^P

Thanks for the heads up.
I'll have a look at it.

Best,

A.

As for Wi-Fi, if we are talking about connecting only to a home router, then you can use wpa_supplicant, available in any distribution.
If necessary, there is a GUI for it.
Set it up once and forget it.

I refuse to deal with the useless bloat that is Network-Manager, so I will stick with Devuan Beowulf and WiCD.

There is a better solution:

# apt install connman-gtk connman-ui

And, optionally, connman-vpn.

Then, for better Devuan compatibility, make this configuration change:
https://dev1galaxy.org/viewtopic.php?pid=48040#p48040

Now remove all wicd-related packages.

This may be enough:

# apt remove wicd-gtk

Reboot.

Optional:

Before doing all of the above, run this command:

# aptitude -d install wicd-gtk

That will ensure that wicd-gtk and its dependencies are present in the package cache. In the unlikely event that something goes wrong and you lose internet connectivity, this will allow you to easily reinstall wicd-gtk.

It has already made it to Debian trixie and as a result, to Devuan ceres.

If it's already in unstable, 99% of the work is done and the best option is probably a simple backport.

That's only because the binary was built against that version, a problem which will go away by itself if you recompile it as above.

Good question.

I first came across Network-Manager long ago, when I moved around looking for a distribution that I felt comfortable with.
From what I have read on the forum lately, it seems it has only gotten worse.

Unfortunately, WiCD has been in abandoned state for the last 12 years or so.
There have been timid attempts to do something but without any result, like if it was a curse.

I'll have to see about something else.
But not Network-Manager.

So does xarchiver, it was a question of being able to 'Compress ...' from the PCManFM drop down menu and add a password just like you could do it when opening the application directly.

All it took was a suggestion to the maintainer who very rapidly acted on what he (also) thought was a good idea* and that was it.
* instead of replying something to the effect of why don't you do it yourself.   

Thanks for your input.

Best,

A.

Seems all rather complex for my pay grade.
Still getting over having installed it.  8^°

That's about it.

I only want a certain level of system compliance (to call it something) and have apt, aptitude and synaptic properly know about it.

Thanks for the heads up.
I'll look into it.

Unless I am mistaken, xarchiver is added to the Devuan repositories without intervention as it is not dependent on or require the presence of systemd in the system. That being so, I may only have to wait a bit till this last version makes it into Debian (stable or testing) just and install it.

Note: It has already made it to Debian trixie and as a result, to Devuan ceres.

That would replace the one I installed and solve (?) the issue as long as the dependencies remain the same.

Would there be a problem with that?

----
Edit:
Yes.
gdebi says there is a dependency problem - version of libc6 needs to be higher than the one installed.
ie: higher than libc6 2.28-10+deb10u2   
----

Thanks to both for your input.

Best,

A.

Okay, it's your choice and non-negotiable.
But Beowulf support will end in 3 months and then what?
Just information, the ark archiver in TDE and KDE5 supports a password when archived “out of the box”

Regards.

Suggestion 2: If all you want is a .deb and you don't care how nice it is (or intend to redistribute it), just use checkinstall. Does much as boughtonp described above, but with more magic and less manually finding all the files 'make install' drops.