[sf-lug] "bullseye" 11.5 minor update out this wknd, other .deb-based spins

[aaronco36]

Essentially fwd'ing this email originally (but so far unsuccessfully) 
sent to the BAD (Bay Area Debian) mailing-list


Quoting Saturday's 2022-09-10 announcement at [01]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Updated Debian 11: 11.5 released

September 10th, 2022

The Debian project is pleased to announce the fifth update of its stable
distribution Debian 11 (codename "bullseye"). This point release mainly
adds corrections for security issues, along with a few adjustments for
serious problems. Security advisories have already been published
separately and are referenced where available.

Please note that the point release does not constitute a new version of
Debian 11 but only updates some of the packages included. There is no need
to throw away old "bullseye" media. After installation, packages can be
upgraded to the current versions using an up-to-date Debian mirror.

Those who frequently install updates from security.debian.org won't have
to update many packages, and most such updates are included in the point
release.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Had to deal with a dual-boot Devuan GNU+Linux[02]/other-Linux "situation"
on a secondary machine throughout the time-of-announcement until now, so
didn't [yet] try to reach the actual Debian "bullseye" download mirrors,
e.g., for downloading a couple of variably purposed 11.5 ISO CD images, to
wit........
* debian-11.5.0-amd64-netinst.iso  <=== by far the most common download
* firmware-11.5.0-amd64-netinst.iso
* debian-11.5.0-amd64-i386-netinst.iso
* firmware-11.5.0-amd64-i386-netinst.iso
* other inevitable v11.5 .deb-based distros

Following this, and as the many of us using Debian testing/"bookworm" or
.deb distros _based upon_ testing/"bookworm" realize, one would reasonably
expect updates to the ISO CD images listed for multiple architectures at
[03] fairly shortly.

BTW, that "situation" with Devuan ultimately involved a recent signing key
issue some of you might recall which effectively prevented Devuan
"Chimaera"/Stable from updating at all.......
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
the signing key 'Devuan Repository (Amprolla3 on Nemesis)' is expired:
W: GPG error: http://deb.devuan.org/merged stable InRelease:
The following signatures were invalid:
EXPKEYSIG BB23C00C61FC752C Devuan Repository (Amprolla3 on Nemesis)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Turns out that last week's Devuan DNG mailing-list posting '[DNG] Key is
expired' [04] successfully offered a decisive fix for that issue, so big
kudos for Ludovic Belli?re and the other Devuan experts for rapidly
providing and publicizing the fix! :-)
Seems to this Devuan user that Devuan itself remains as strong as ever
despite the above hiccup and despite the innuendos of some of its
detractors, e.g., see the archived BAD mailing-list post from eight years
back in time entitled 'Here we go: devuan'[05] :-|

Over ten years ago, there was a Debian Stable-based distro spin called
CrunchBang Linux #! that effectively (IMHO) used Openbox as its default
WM.
#!'s maintainer discontinued this excellent .deb-based spin over 7 1/2
years ago, in an announcement apocalyptically entitled 'The end.'[06]
The remaining #! website[07] lists a pair of other .deb-based Openbox
spins that although are setup by default with SystemD-init, at the same
time on the positive side do a decent job (also IMHO) with Openbox WM on
top of the current "bullseye"....
* BunsenLabs Linux [08]
* Crunchbangplusplus a.k.a., both "CBPP" and "#!++" [09]

Sure, am keenly aware as ever of Rick's fine 'Debian 8 "Jessie" OpenRC
Conversion' article at [10], whereby "one hopes, [in] Debian 9 "Stretch",
Debian 10 "Buster", and later" that Rick's conversion to OpenRC steps will
similarly prove effective for BunsenLabs Linux, #!++, and other 11.5
.deb-based distros.
Therefore, have been isolating these default SystemD-init-dependent,
.deb-based distros in their own test virtual machines so that OpenRC/Runit
conversion steps won't eventually just end up borking any
production+productive installs via the latest Debian SystemD-entanglement
du jour.
Rick and/or anyone else want to take a stab at answering and/or better
yet, explaining the following....
===> Are Freedesktop.org's udisks2 and policykit system software still
among Debian's primary SystemD "entanglements"??

-A


====================================
REFERENCES
====================================
[01]https://www.debian.org/News/2022/2022091002
[02]https://www.devuan.org/
[03]https://cdimage.debian.org/cdimage/weekly-builds/
[04]https://lists.dyne.org/lurker/message/20220903.172703.1050aabb.en.html
[05]http://bad.debian.net/pipermail/bad/2014-November/003654.html
[06]https://crunchbang.org/forums/viewtopic.php?id=38916
[07]https://crunchbang.org/
[08]https://www.bunsenlabs.org/
[09]https://www.crunchbangplusplus.org/
[10]http://linuxmafia.com/kb/Debian/openrc-conversion.html
====================================