dpkg -i /var/cache/apt/archives/linux-image*.deb

I think the only power you have is to delete your own posts. Please don't.

Looks to me like the discussion is back on track, even if it's not the original track. And the last few posts have new information. It should be ok. Things usually have a way of settling themselves down.

Not all mirrors support https. If you use deb.devuan.org it may redirect you to an http mirror or an https mirror, so it will sometimes fail.

To use https, select a mirror that supports https and use that in your sources.list

Here's a list of package mirrors. Each entry shows which protocols are supported:
http://pkgmaster.devuan.org/mirror_list.txt

It doesn't always happen in a few hours. Be patient. It's coming.

Wow. It's fixed. New version should appear in repo within a few hours.

Thanks for reporting.

Like I said, it's been abandoned. We don't have an official procedure for becoming a maintainer, but you could make a personal project at git.devuan.org, make the necessary additions to the code, tell people about it here or mailing list or IRC, maybe make packages for people to test and use. And then maybe your changes will be brought into the repo.

One thing we do want from anyone who chooses to maintain a package is that you stick with it. It's no good if a package gets into the repo and then nobody updates it when it needs updating.

My personal vision for the sanity package would be to have a debconf dialog that listed all the sane changes and let you pick which ones you wanted. Obviously, there would need to be more than just one item on the list. And I don't want to do the work. I'd rather live without it than have to maintain it.

Another way to do it is with dpkg-divert, which will make a package that replaces a config file in another package. And it tells the package manager what's going on, so your custom changes don't get replaced during an upgrade.  Do you know what file in firefox stores the url for the dns server? (Knowing ff, it's probably a binary file.)

If you're using wicd or some other network manager, you should not configure /etc/network/interfaces. They will fight with each other if you do.

The most common cause for wicd to fail to see the wireless interface is that wlan0 is not set as the default wireless interface in wicd preferences. Maximize the wicd window and you'll see where to get to Preferences. (Or click on the little arrow if you can find it.) It's also possible to set the wireless interface in /etc/wicd/manager-settings.conf -
wireless_interface = wlan0

We don't have control over the mirrors' choice of providing https or not.

If you want to use https, use a mirror in your sources.list that provides https. There's a list of them here -
http://pkgmaster.devuan.org/mirror_list.txt

If you use https, your ISP won't be able to see what you're installing. Package security is provided by gpg signing keys.

Edit: Corrected links: I posted this link first. This is the list of mirrors for downloading isos, not for getting packages.
https://devuan.org/get-devuan

If you get rid of avahi-daemon, that should be enough. The library won't do anything.

If removing avahi-daemon wants to remove other things that you know you want, you can disable it with sysv-rc-conf (or update-rc.d if you like commands.)

The most likely scenario (by a long shot) is that we will continue to provide the version of firefox-esr packaged by debian, just like we do for almost all the packages we provide.

It looks like trr is turned off by default. I'm looking at ff-esr 68.4 in beowulf.
network.trr.mode;0

However, if you turn it on, you'll get cloudflare. This value can be modified. I haven't tried it.
network.trr.uri;https://mozilla.cloudflare-dns.com/dns-query

To turn it on, they say to go into Preferences, Network Settings, and then way down at the bottom is a checkbox to turn on DNS over HTTPS and a place to enter a different server.

Thanks for the info.

https://wiki.mozilla.org/Trusted_Recursive_Resolver

It might be five years. I'm not sure. The major change that I see is that jessie was 2 years late (after the release of debian jessie) ascii was one year late, and beowulf is about half a year late.  Collaborative efforts have sprung up between devuan and debian, and as a result, elogind is available in debian. I see new devuan developers who have arrived in the past year, and we continue to get new users who thought they were ok with systemd but changed their minds after they used it for some time. I think we're doing just fine.

I'm aware that almost all packages start out as upstream tarballs that get turned into debian packages by debian developers.  They also get turned into other kinds of packages for other distros. But I don't understand what you're trying to say about lxde/lxqt.

With any luck, the gtk3-nocsd package will continue to work.