Dear America by Eric Bibb.

Alpine are packaging libudev-zero for use with busybox's mdev but there doesn't seem to be a Debian package for it.

EDIT: looking at the missing features though I think Devuan should go with systemd-udev plus the openembedded patches *dives for cover*

^ This might have worked for you now but there is an increasing chance of this technique breaking a stable system as testing moves ahead. There is a chance that method has already broken your system if it pulled in any critical packages from testing, such as glibc (libc6).

EDIT: which is why I suggested backporting. Twice.

True Genius by Ray Charles. Five hours and and forty-seven minutes of musical bliss.

Looks like it's a dbus service so it probably won't work unless you can hook it into that somehow with sysvinit (systemd listens to the bus automatically). But this is just a guess; I don't use Bluetooth.

Looks fine to me but you don't have to test for the exit status after starting the daemon — just use the conditional instead, like this:

start() {
	log_daemon_msg "Starting $DESC" "$prog"
	if start_daemon -p $PIDFILE /usr/bin/bluealsa $OPTIONS ; then
		log_end_msg 0
	else
		log_end_msg 1
	fi
}

Oh, and $Usage is referenced but not assigned but I think that's a typo :-)

There are packages in the repositories for a kernel and bootloader signed with Microsoft's own Secure Boot certificates. No need to create your own.

Note that testing isn't covered by the security team. IMO backporting was the better option.

The Poet by Bobby Womack. Incredible album, utter genius.

If a package is marked obsolete then it has already been removed from the repositories[1]. You should probably remove it yourself manually and switch to something current and supported. GRUB is nice, as is systemd-boot (although the latter is only UEFI capable).

[1] https://pkginfo.devuan.org/cgi-bin/poli … o&x=submit

EDIT:

Don't be fooled by the multiply-redundent grub.cfg generated by grub-mkconfig. A handwritten configuration can be *much* simpler. Here's one of mine that multi-boots Debian & OpenBSD along with an entry to boot a live ISO image stored on the hard drive:

https://raw.githubusercontent.com/Head- … r/grub.cfg

15 lines :-)

Please share the full configuration and also indicate which services were enabled (and how) to acheive this.

It's always best to provide the full, verbatim command output rather than a vague description.

There should be no problem using wpa_supplicant alone to associate with the access point. Disabling any other networking services that might conflict and configuring wpa_supplicant and dhclient correctly should work.

Create a file at /ect/apt/preferences.d/fix with this content:

Package: *
Pin: release n=chimaera-backports
Pin-Priority: 100

Then run apt update (as root) and check the pinning to see if it's fixed.

I would also recommend downgrading as many backports as possible, especially the QEMU packages. You'll have to use apt install package=version (replace package with the actual name of the package and replace version with the version number from chimaera) for each package. There's probably a quicker way to do that but I don't know of any.

And please remember to submit a bug report to Devuan about this. See https://www.chiark.greenend.org.uk/~sgtatham/bugs.html for a general guide to bug reporting; it might be good to include a link to this thread for background.

EDIT: in respect of pkgmaster.devuan.org, the advice to use the deb.devuan.org redirector is to avoid loading the specific mirror unduly (AFAIUI).

That's just how aptitude identifies the archive for the ~A search option.

I think we've found a problem.

The Debian bullseye-backports repository has a Release file that contains these lines:

NotAutomatic: yes
ButAutomaticUpgrades: yes

This confers a pin priority of 100 for all packages, which means they will not be installed unless explicitly targetted (either by version or with the --target option for apt) but any packages that are installed from backports will be kept updated from there.

But the Devuan chimaera-backports repository Release file does not have those lines.

Can we please see the output of

apt policy

^ That will show the pin priority assigned to all active repositories. If the backports repository is at 500 rather than 100 then it is pinned wrong and a bug report is called for.

Note that the pkgmaster.devuan.org repositories are no longer recommended; see https://www.devuan.org/os/packages for the canonical list of official sources.