From Newsgroup: comp.os.linux.misc

Just the latest upgrade for my Deb-derived distro (MX) and
suddenly getting evil evil messages about how the latest
kernel is missing dependencies and WON'T upgrade.

"
dpkg: error processing package linux-image-liquorix-amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-headers-liquorix-amd64:
linux-headers-liquorix-amd64 depends on
linux-headers-7.1.5-2-liquorix-amd64 (= 7.1-7~mx23ahs); however:
Package linux-headers-7.1.5-2-liquorix-amd64 is not configured yet.
dpkg: error processing package linux-headers-liquorix-amd64 (--configure):
dependency problems - leaving unconfigured
"

Never seen this with MX before. Waited a couple of
days to see if a fix was simply "late" - but no.
MX usually "Just Works".

Tried the usual junk-removal stuff. No good.
"--fix-missing", no good.

Now, fortunately, MX has a good 'custom ISO creator'
utility and I'd done a full image just maybe three
weeks ago. If I *must* I can make a thumb containing
that ... which WILL install. But that's kinda MAJOR.
Can copy my desktop and a few other things somewhere
and copy them back later. Then re-try the updates.

But that SUCKS SUCKS SUCKS !

"Dependency problems" ? Why not NAME it ???
Guess you're just "supposed to know" ...

Any advice here before I have to do The Nasty ???

Had a similar intractable update issue with Manjaro
a year ago - broken and would not be fixed. Had to
just HOSE it. Updates, esp "security" updates, are
very important these days - too many out to Get Us.

Plus, my MX is still WORKING. However the FUTURE
is unclear. NEED a 'future'.

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On Mon, 3 Aug 2026 23:05:35 -0400, c186282 wrote:

Just the latest upgrade for my Deb-derived distro (MX) and suddenly
getting evil evil messages about how the latest kernel is missing dependencies and WON'T upgrade.

How's that ahs going for you? I uodated today and 6.12.100 is doing fine.
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On 2026-08-04, c186282 <c186282@nnada.net> wrote:

Just the latest upgrade for my Deb-derived distro (MX) and
suddenly getting evil evil messages about how the latest
kernel is missing dependencies and WON'T upgrade.

This is similar to another thread I started here. IMHO
upgrades are the scariest part of Linux. I always take
full backups of everything first with a script like this:

#!/bin/bash
# Back up cjglap2 - version 2025-08-27
# This script must be run as root!
if [ "$(id -u)" -ne 0 ];
then
echo This script must be run as root!
exit
fi
# Copy the root partition.
dd if=/dev/sda1 | gzip >/mnt/backup/cjglap2/sda1.img.gz
# Copy various directories.
rsync -av --delete /etc /mnt/backup/cjglap2 rsync -av --delete /usr /mnt/backup/cjglap2 rsync -av --exclude='/home/cjg/.cache/' --delete /home /mnt/backup/cjglap2 rsync -av --delete /var/spool/slrnpull /mnt/backup/cjglap2

Then, even if the worst happens, I can wipe the disk and start over.
Having /home in its own partition makes things a lot easier.
--
/~\ Charlie Gibbs | In this world there are
\ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
X I'm really at ac.dekanfrus | 1. Those who can extrapolate
/ \ if you read it the right way. | from incomplete data.
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On Tue, 04 Aug 2026 18:18:23 GMT, Charlie Gibbs wrote:

# Copy the root partition.
dd if=/dev/sda1 | gzip >/mnt/backup/cjglap2/sda1.img.gz

Doing a dd on a volume that is currently mounted may not give
completely reliable results.

# Copy various directories.
rsync -av --delete /etc /mnt/backup/cjglap2 rsync -av --delete /usr /mnt/backup/cjglap2 rsync -av --exclude='/home/cjg/.cache/' --delete /home /mnt/backup/cjglap2 rsync -av --delete /var/spool/slrnpull /mnt/backup/cjglap2

rCL-arCY does not include rCL-ArCY or rCL-XrCY, which I like to include these days, just in case.
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On Tue, 04 Aug 2026 18:18:23 GMT, Charlie Gibbs wrote:

This is similar to another thread I started here. IMHO upgrades are the scariest part of Linux. I always take full backups of everything first
with a script like this:

I hit that this morning. I'd been playing with CircuitPython on an old Playground Express board using VS Code and the CircuitPython v2 extension.
All was good. I updated the Leap machine and got the latest Code, 1.131.
The extension crashed and burned on takeoff. I reverted Code to 1.130,
still no joy. I jumped a few but 1.127 works as expected.

The other part is 1.127 uses Electron 42.2, 1.130 and 1.131 use 42.7. That makes me suspicious. Before the Trixie update Code started to crash on the
Pi 5. It turned out the kernel optimizations for the Pi 5 were the problem
and reverting to the Pi 4 kernel solved it.

Too damn many moving parts! At least it helped me to decide on MicroPython instead of CircuitPython. CP has some advantages but the extension author
lost interest about 10 months ago so I'm not waiting for a VS Code fix. I assume it still works with Thonny, the default IDE in the Raspberry Pi OS. Adafruit used to recommend Mu but that's dead now too.
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On 8/4/26 02:29, rbowman wrote:

On Mon, 3 Aug 2026 23:05:35 -0400, c186282 wrote:

Just the latest upgrade for my Deb-derived distro (MX) and suddenly
getting evil evil messages about how the latest kernel is missing
dependencies and WON'T upgrade.

How's that ahs going for you? I uodated today and 6.12.100 is doing fine.

Six ??? Mine is into the sevens.

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On Wed, 5 Aug 2026 00:43:06 -0400, c186282 wrote:

On 8/4/26 02:29, rbowman wrote:

On Mon, 3 Aug 2026 23:05:35 -0400, c186282 wrote:

Just the latest upgrade for my Deb-derived distro (MX) and suddenly
getting evil evil messages about how the latest kernel is missing
dependencies and WON'T upgrade.

How's that ahs going for you? I uodated today and 6.12.100 is doing
fine.

Six ??? Mine is into the sevens.

https://mxlinux.org/download-links/

"rCoXfce

MX-25.2_Xfce_x64, standard Debian 6.12 64 bit kernel and hardware support
from Debian Stable. Suitable if your PC is a few years old. MX-25.2_Xfce_ahs_x64, an rCLAdvanced Hardware SupportrCY release for very recent hardware, with 7.07 kernel and newer graphics drivers and
firmware."

https://mxlinux.org/blog/new-advanced-hardware-support-repo-ahs-for-short/

"This new repo section is a little bit of an experiment. If you are
perfectly happy with the stable repos and graphics stack, there is no real reason to add the ahs repo to your sources."

You pays yer money and you makes your choice. I don't have any very new hardware to worry about.
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On 8/4/26 14:18, Charlie Gibbs wrote:

On 2026-08-04, c186282 <c186282@nnada.net> wrote:

Just the latest upgrade for my Deb-derived distro (MX) and
suddenly getting evil evil messages about how the latest
kernel is missing dependencies and WON'T upgrade.

This is similar to another thread I started here. IMHO
upgrades are the scariest part of Linux. I always take
full backups of everything first with a script like this:

I kinda agree at this point. Had to throw away
a couple of previously good Manjaro installs
due to hosed upgrades - and DID put in the
effort to save them. NO good. Once it's
fucked then it's FUCKED.

As said, MX does have a good "Live-Install"
app. Just a few weeks ago I made one of
those custom ISOs. If I *have* to I'll do
a complete re-install using that and THEN
retry the upgrades. Have already copied-out
my /home and /Desktop and a few other things
so I can 99.9% recover everything.

Anyway, these days now, the "missing"
dependencies are NOT gonna appear.
Sucks !!! The entire update system is
now CONFUSED - more enemy than help.

#!/bin/bash
# Back up cjglap2 - version 2025-08-27
# This script must be run as root!
if [ "$(id -u)" -ne 0 ];
then
echo This script must be run as root!
exit
fi
# Coy the root partition.
dd if=/dev/sda1 | gzip >/mnt/backup/cjglap2/sda1.img.gz
# Copy various directories.
rsync -av --delete /etc /mnt/backup/cjglap2 rsync -av --delete /usr /mnt/backup/cjglap2 rsync -av --exclude='/home/cjg/.cache/' --delete /home /mnt/backup/cjglap2 rsync -av --delete /var/spool/slrnpull /mnt/backup/cjglap2

Then, even if the worst happens, I can wipe the disk and start over.
Having /home in its own partition makes things a lot easier.

THINK I'm gonna have to wipe.

ULTRA-sucky !

Deb/MX is usually PERFECT ... but now,
well, obviously ..... it's all fucked up
at some low/obscure level that only
gurus on speed could possibly solve
with 48 hours of obsessive tweaks.

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On 2026-08-05, Lawrence D?Oliveiro <ldo@nz.invalid> wrote:

On Tue, 04 Aug 2026 18:18:23 GMT, Charlie Gibbs wrote:

# Copy the root partition.
dd if=/dev/sda1 | gzip >/mnt/backup/cjglap2/sda1.img.gz

Doing a dd on a volume that is currently mounted may not give
completely reliable results.

# Copy various directories.
rsync -av --delete /etc /mnt/backup/cjglap2 >> rsync -av --delete /usr /mnt/backup/cjglap2 >> rsync -av --exclude='/home/cjg/.cache/' --delete /home /mnt/backup/cjglap2 >> rsync -av --delete /var/spool/slrnpull /mnt/backup/cjglap2

???-a??? does not include ???-A??? or ???-X???, which I like to include these days, just in case.

also --numeric-ids

The machine you are backing up to may have different "system" ids (<1000)
and cause problems when copying back - depending on how one does it.


--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On 8/6/26 17:16, Jim Jackson wrote:

On 2026-08-05, Lawrence D?Oliveiro <ldo@nz.invalid> wrote:

On Tue, 04 Aug 2026 18:18:23 GMT, Charlie Gibbs wrote:

# Copy the root partition.
dd if=/dev/sda1 | gzip >/mnt/backup/cjglap2/sda1.img.gz

Doing a dd on a volume that is currently mounted may not give
completely reliable results.

# Copy various directories.
rsync -av --delete /etc /mnt/backup/cjglap2 >>> rsync -av --delete /usr /mnt/backup/cjglap2 >>> rsync -av --exclude='/home/cjg/.cache/' --delete /home /mnt/backup/cjglap2 >>> rsync -av --delete /var/spool/slrnpull /mnt/backup/cjglap2 >>

???-a??? does not include ???-A??? or ???-X???, which I like to include these
days, just in case.

also --numeric-ids

The machine you are backing up to may have different "system" ids (<1000)
and cause problems when copying back - depending on how one does it.

SO many complicating factors these days ! Remember
when Linux updates "Just Worked" ???

MY case, kinda lucky. MX has a good "custom live ISO"
utility and I did the full thing about three weeks ago.
I *can* restore my lap to it's previous condition and
then do the updates again. MIGHT work.

Nasty overkill though.

Have had intractable update issues with Manjaro - had
to hose a couple of boxes. However Deb derivs are
usually pretty solid this way. Is this no longer true ?

If not ... shit ... some of the BSDs aren't TOO bad now.

Rsync is a great util ... an option for almost ANY
particular need. Used it extensively for custom
company backups for a long time. However it just
saves the FILES - not the real SETUP, including
the boot-up partitions. For that, for a real and
complete re-install, it's either dd or a 'sparse'
variant. The MX util is a 'sparse variant'. Store,
make ISO, install ISO.

Kinda tried to write an rsync for Winders - minus
the client/server shit. Got sort of along with it
but it got TOO deep and time-consuming.

Gonna make the stick tomorrow. If my prob does not
resolve in a few days, then ...

Already copied all the shit in my home and Desktop
so I can copy them back.

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On Fri, 7 Aug 2026 01:53:15 -0400, c186282 wrote:

SO many complicating factors these days ! Remember when Linux updates
"Just Worked" ???

MY case, kinda lucky. MX has a good "custom live ISO" utility and I
did the full thing about three weeks ago.
I *can* restore my lap to it's previous condition and then do the
updates again. MIGHT work.

Strangely, my updates generally 'just work'. The only complete failure was EndeavourOS (Arch). A Mint update had problems with dkms and the funky Broadcom chip but it reverted to the existing kernel with no problem. Even Fedora has went smoothly despite it's very frequent updates. Also I
usually upgrade to the beta release when it's available. It updates and eventually morphs into the release version. I haven't seen a 45 beta yet.

I just updated MX 25.2. It's a VM so it was a little slow as dkms rebuilt quite a few modules for the new 6.12.101 kernel. I did not elect for the advanced hardware support kernel as you did. Oh yeah, the VM is kvm/QEMU.
I purged any memory of VirtualBox including the RPMFusion repos.

Leap 16 has also been well behaved. I won't update it today since one of
the programs it wants to update is code. I'd manually reverted that to
1.127 because of an extension problem. When I'm through playing with CircuitPython I'll let it go.
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On 2026-08-07, c186282 <c186282@nnada.net> wrote:

On 8/6/26 17:16, Jim Jackson wrote:

On 2026-08-05, Lawrence D?Oliveiro <ldo@nz.invalid> wrote:

On Tue, 04 Aug 2026 18:18:23 GMT, Charlie Gibbs wrote:

# Copy the root partition.
dd if=/dev/sda1 | gzip >/mnt/backup/cjglap2/sda1.img.gz

Doing a dd on a volume that is currently mounted may not give
completely reliable results.

# Copy various directories.
rsync -av --delete /etc /mnt/backup/cjglap2 >>>> rsync -av --delete /usr /mnt/backup/cjglap2 >>>> rsync -av --exclude='/home/cjg/.cache/' --delete /home /mnt/backup/cjglap2 >>>> rsync -av --delete /var/spool/slrnpull /mnt/backup/cjglap2 >>>

???-a??? does not include ???-A??? or ???-X???, which I like to include these
days, just in case.

also --numeric-ids

The machine you are backing up to may have different "system" ids (<1000)
and cause problems when copying back - depending on how one does it.

SO many complicating factors these days ! Remember
when Linux updates "Just Worked" ???

Sorry this isn't about updates, but about backups.

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On 8/7/26 15:50, Jim Jackson wrote:

On 2026-08-07, c186282 <c186282@nnada.net> wrote:

On 8/6/26 17:16, Jim Jackson wrote:

On 2026-08-05, Lawrence D?Oliveiro <ldo@nz.invalid> wrote:

On Tue, 04 Aug 2026 18:18:23 GMT, Charlie Gibbs wrote:

# Copy the root partition.
dd if=/dev/sda1 | gzip >/mnt/backup/cjglap2/sda1.img.gz

Doing a dd on a volume that is currently mounted may not give
completely reliable results.

# Copy various directories.
rsync -av --delete /etc /mnt/backup/cjglap2
rsync -av --delete /usr /mnt/backup/cjglap2
rsync -av --exclude='/home/cjg/.cache/' --delete /home /mnt/backup/cjglap2
rsync -av --delete /var/spool/slrnpull /mnt/backup/cjglap2

???-a??? does not include ???-A??? or ???-X???, which I like to include these
days, just in case.

also --numeric-ids

The machine you are backing up to may have different "system" ids (<1000) >>> and cause problems when copying back - depending on how one does it.

SO many complicating factors these days ! Remember
when Linux updates "Just Worked" ???

Sorry this isn't about updates, but about backups.

Note "upgrade" in the thread title.

I've writ many custom backup apps - and thus DO
heavily rec getting rsync involved.

--- Synchronet 3.22a-Linux NewsLink 1.2