Devuan revisited and its repository maze

What distrowatch calls Debuan 2.1 in its weekly is also listed as a “fixed” release.  Since when is anything based on Debian perceived as fixed unless it intentionally had its package management software released. Alternatively any live “image” is fixed unless you update its software.  Should someone clarify what such terms mean to Distrowatch?

See, we can even defend the honor of those we openly have disliked in the past.

Devuan’s, not debuan’s, repositories for its 2.xx series based on Debian Stretch, is Ascii.

Next edition which is called Beowulf is still under testing, pkgs for which can be found on

http://deb.devuan.org/devuan/dists/testing/
http://deb.devuan.org/devuan/dists/beowulf/

or

http://pkgmaster.devuan.org/devuan/dists/testing/
http://pkgmaster.devuan.org/devuan/dists/beowulf/

Are you confused about debian/antiX/MX/devuan/Refracta editions?

Debian 10 Buster became stable a few months ago, the rest of the systems had to follow but took their time.  This is done every two years and creates a wave of confusion, especially those on forked versions of Debian, like antiX, MX, devuan, refracta, etc.  Even more dangerous and confusing it is if you are using testing and although testing during debian stretch was buster it now becomes bullseye, while your antiX/MX/Devuan is testing alongside Buster still.

After antiX announced 19 (Marielle Franco) as its current stable branch, MS followed its mothership the week later (a few days ago), while Devuan/Refracta are still chasing Stretch (Debian 9), what they call Devuan 2 or ascii.

So here it is, to take the confusion away from numbers and names:

Debian         *   Debian       *  AntiX/MX   *  Devuan
the last good1 *   7   Wheezy   *    13       *  0  beta-testing
old old stable *   8   Jessie   *    15       *  1 jessie (old-stable)
old stable     *   9   Stretch  *    17       *  2 ascii (stable)
stable         *  10   Buster   *    19       *  3 beowulf(testing)
testing        *  11   Bullseye *    21       *  4 chimaera (next testing)
unstable       *       sid      *    sid      *       ceres

Devuan, EOL – trust, suspicion, and unanswered questions

First things first.  Those of us involved in this project had an internal debate from day one whether to cover Devuan development or not.  All but one person here, yours truly, argued that Devuan would never be able to overcome and change the psychopathology evident in Debian developer community and the inherent elitism against the common individual user.  If you are not directing the departmental budget of an IT enterprise nobody in that community would give a rat’s penny of what your problem may be.  Seeking help as a common user you must put up with tons of unsubstantiated arrogance, irony, and elitism.  This is also evident in the DNG list where devuan developers and their pre-split backroom buddies are larking, pretending they are Devian without the infrastructure of Debian.  It is like a life-raft’s  officers and buddies pretending to be the officers operating a supertanker.

Devuan testing new amprolla3 powered repository

If you like to test the new amprolla3 powered repository system here is a small list of optional /etc/apt/sources.list

deb https://pkgmaster.devuan.org/merged/ ascii main contrib non-free
deb https://pkgmaster.devuan.org/merged/ ascii-backports main contrib non-free
deb https://pkgmaster.devuan.org/merged/ ascii-proposed-updates main contrib non-free
deb https://pkgmaster.devuan.org/merged/ ascii-security main contrib non-free
deb https://pkgmaster.devuan.org/merged/ ascii-updates main contrib non-free
deb https://pkgmaster.devuan.org/devuan/ ascii-proposed main contrib non-free
deb https://pkgmaster.devuan.org/devuan/ ascii-proposed-security main contrib non-free
 

About Devuan repositories and the future

 

Gravimetric wrote: ↑I think experimental then goes into unstable, then into a normal repo, over a period of time.

fsmithred wrote: ↑

That’s the theory.

In theory, theory and practice are the same.
In practice, they are not.

 

That is probably how things may work in the distant future, but you can not apply debian logic to what is not yet formed as debian.
In theory, devuan is meant to be debian without systemd, and I believe that is what Jessie is, Debian Jessie without systemd and co-dependents, with substitutions.
Ascii is meant to be stretch w/o sysD, but I think it still needs some work.

If network manager gives you long network interface names return to eth0 & wlan0

Edit your /etc/default/grub change GRUB_CMDLINE_LINUX=”” to :

GRUB_CMDLINE_LINUX="net.ifnames=0"

If the biosdevname is installed you need to add :

GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"

$ sudo update-grub

WARNING about Devuan endeavors/enDevuanors

Please read this if not the release notes before you click upgrade.  Jessie, stable Devuan, has full care and attention of the Devuan team of developers.  Ascii (the name of an other minor planet) which is Devuan-testing, has had minor initial attention and screening.  It is very unstable and already has proven semi-problematic.  It is by far a mild revision of straight Debian-Stretch.  No warranties that things will not break or pull in systemd dependencies and dependants.  Ceres (a third minor planet in the name sequence), Devuan-Unstable, is not even Debian-buster (testing), it is a copy of the Debian-unstable/Sid repository.  There is no Devuan intervention in this repository at all.  It is beyond even the scope of the Devuan team to be testing it.