Dev1 Galaxy Forum / apt update tries to delete /lib/init & /lib/lsb

Re: apt update tries to delete /lib/init & /lib/lsb

dummy@example.com (stultumanto) — Wed, 06 Mar 2024 21:51:30 +0000

I've already run usrmerge. Doesn't the below mean that the original /lib/init is already gone? So apt would have actually been trying to delete /usr/lib/init.

$ realpath /lib/init
/usr/lib/init
$ realpath /lib/init/init-d-script
/usr/lib/init/init-d-script

Re: apt update tries to delete /lib/init & /lib/lsb

dummy@example.com (GlennW) — Tue, 05 Mar 2024 22:47:57 +0000

this may not be useful, but

quite some time ago I tried usrmerge... and as I had began to think as well, But I thought I was imagining things...

Not just /usr merge of /bin and /sbin, other things are broken as well.

At one point I "ln -s" the directories instead of using usrmerge and the system seemed to work ok.

I didn't stick with it, but the experiment was wonder-full.

Something was broken, possible only revealed when compiling (making and installing) a kernel or software.

Re: apt update tries to delete /lib/init & /lib/lsb

dummy@example.com (fsmithred) — Tue, 05 Mar 2024 11:33:18 +0000

I didn't think it was a usrmerge problem until I compared files in different versions of initscripts. They moved scripts from /lib/init to /usr/lib/init.

Is this upgrade trying to install the usrmerge package, or did you already have merged usr in your system?
Does /usr/lib/init contain the same scripts as /lib/init? If so, I think you could move /lib/init out of the way. (move rather than delete, in case you need to put it back.)

apt update tries to delete /lib/init & /lib/lsb

dummy@example.com (stultumanto) — Tue, 05 Mar 2024 03:35:52 +0000

I just ran an Excalibur upgrade and got these errors:

Preparing to unpack .../sysvinit-utils_3.08-7devuan1_amd64.deb ...
Unpacking sysvinit-utils (3.08-7devuan1) over (3.08-5devuan1) ...
dpkg: warning: unable to delete old directory '/lib/lsb/init-functions.d': Directory not empty
dpkg: warning: unable to delete old directory '/lib/lsb': Directory not empty
Setting up sysvinit-utils (3.08-7devuan1) ...
[...]
Preparing to unpack .../2-initscripts_3.08-7devuan1_all.deb ...
Unpacking initscripts (3.08-7devuan1) over (3.08-5devuan1) ...
dpkg: warning: unable to delete old directory '/lib/init': Directory not empty

I checked, and dozens of scripts in /etc/init.d still source the scripts in /lib/init. So it seems odd that an upgrade would try to delete it. Does anyone know what's going on here? Is this usrmerge related?