You are not logged in.
Posting for clarity that in Devuan we advise not to use the Suite designations because doing so can cause unexpected "breakage". Here's why:
Codenames or suites?
The release codenames or suite designations in /etc/apt/sources.list indicate which release will be used when updating and upgrading packages. Note that the suite names stable and testing will refer to different releases over time.
As of this writing, stable refers to Devuan ASCII (Debian Stretch) and testing refers to Devuan Beowulf (Debian Buster). Once Beowulf is officially released, stable will refer to Beowulf and testing will refer to the next release in development, Chimaera (Debian Bullseye).
However, if your ASCII sources.list refers to the release codename ascii you will remain on ASCII until you change your sources.list. That means that you will have more control over when the upgrade happens. And if you are using beowulf in your sources.list you will move seamlessly to the new stable version of Beowulf when it is released.
To avoid the possibility of mixing two potentially incompatible repositories, Devuan recommends using release codenames in sources.list.
Source: https://devuan.org/os/releases
Good find!
I found this link more informative than reddit:
https://www.patreon.com/posts/31633933
Yes. Just haven't gotten around to it yet.
I think this is it:
And abolishing source distributions would stop global warming within months!
bitcoins are the real energy hogs.
If you use "testing" in your sources you will get Debian Bullseye and fubar your install. Always use the release name in your sources list. This is explained on the website. Look for "Codenames or suites?".
Please continue discussion at this existing thread:
HoaS . . . see the link on my first post in this thread that was rejected by the OP.
The ones that are actually harmful and not just imagination are listed here:
https://pkgmaster.devuan.org/bannedpackages.txt
If they are also listed here, let us know:
Maybe I'm just doing something stupid . . . <<<< this
~/.config/liferea/liferea.css
Is the file that's needed to change colors etc.
I thought I'd have a look at #10: Custom CSS for Article Rendering and the link is dead:
Not Found
The requested URL /liferea/blog/Liferea+Trick+#10:+Custom+CSS+for+Article+Rendering was not found on this server.
Apache Server at lzone.de Port 80
So, what happens? Can someone resubmit the job, or does it just sit for days until something mysterious fixes it?
Fix has been in limbo for 2 months:
https://lists.dyne.org/lurker/message/2 … 02.en.html
Those involved just had a discussion on irc. Hopefully will move forward soon, possibly by the end of the week.
Unfortunately, this is a recurring problem that is out of Devuan's control to correct at the source. No matter how many times it happens, no one who is able to fix it seems to be interested it tracking down the glitch.
Ian jackson has posted a response:
With FF now depending on it, that is unlikely.
plymouth is a banned package in Devuan:
https://pkgmaster.devuan.org/bannedpackages.txt
Why not reviewing a Devuan with Trinity desktop environment?
Because Devuan does not offer Trinity as an option. The possibility was discussed several years ago but went nowhere. The Devuan derivative http://exegnulinux.net uses Trinity.
With the 2.1 point release, openrc no longer requires an expert install. Even the graphical installer offers the option. Remember that openrc is still tied to sysvinit scripts:
This from https://dev1galaxy.org/search.php?actio … er_id=5727 titled "Solving Init Compatibility":
Openrc
Openrc is provided as an alternative service manager from the Devuan installer, which is already a step up from Debian. However, this is far from a replacement to sysvinit. In fact, it simply runs atop it. Sysvinit scripts are still used during initialization, and no openrc run scripts are provided as replacements for the various sysvinit scripts used in starting services. In recent versions of Openrc, it comes with its own init. This skips inittab and boots openrc directly, but since it still uses sysvinit scripts, it’s noticeably slower. Also, without providing getty scripts, the user won’t even reach the login prompt. Gentoo provides all the run scripts we could ever need, and so bringing them over is not an impossibility. Why bother using openrc run scripts and using openrc as an init and a service manager? The scripts are much easier to read, and process supervision would be handled much more cleanly. There’s also faster boot times and better overall performance, but your mileage may vary on those claims.
And spelling it wrong in places too: DeVaun
A note from Parrot OS:
we are not based on devuan yet, and the rolling branch is still based on debian testing
meanwhile we have an experimental lts branch that tracks devuan, and we plan to release a lts version of parrot (5.0) for both x86 and arm architectures, and keep it aside to the rolling edition that will remain the same as now (but amd64 only)
the eta is "when it's ready"
This point release includes all updates since the 2.0.0 release.
"Reputation systems" are just mob click-bait. Really beneath the quality of users that populate this forum.
That would best be discussed on #devuan-arm where the arm devs hang out.