Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Preparing to unpack .../archives/usrmerge_35_all.deb ...
Unpacking usrmerge (35) ...
Setting up usrmerge (35) ...
cp: -r not specified; omitting directory '/lib/systemd/system'
FATAL ERROR:
cp --no-dereference --preserve=all --reflink=auto --sparse=always /lib/systemd/system /usr/lib/systemd/system~~tmp~usrmerge~~: rc=1
You can try correcting the errors reported and running again
/usr/lib/usrmerge/convert-usrmerge until it will complete without errors.
Do not install or update other Debian packages until the program
has been run successfully.
E: usrmerge failed.
dpkg: error processing package usrmerge (--configure):
installed usrmerge package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
usrmerge
E: Sub-process /usr/bin/dpkg returned an error code (1)
can anyone suggest something to try to fix the FATAL ERROR ?
Thanks
PS: this is a test system and I can restore a snapshot to start the upgrade over.
Last edited by robfantini on 2023-06-01 01:05, edited 2 times in total.
I use synaptic. Open it up and mouse to Status>Installed to display your systems installed packaged. Scroll down to and highlight the file init, a metapackage, and its -system-helpers. In the main menu Package>Lock Version = click the box.
These two packages will then show in Status>Pinned. From there on out if you 'upgrade all' it WILL upgrade those files, so don't do that. Use the category Installed(upgradable) and highlight all, right click and mark upgrade. Those two files are excluded from that list.
in addition, I think I remember upgrading into bookworm from earlier init 1.60 or so without issue. For a system that did not pass through version 1.63, use gdebi or any method to manually install before the upgrade. Then update the repositories, pin or Lock the version as described, and proceed.
I was able to solve the issue by installing usrmerge when the system was using bullseye. doing so the error issue was easier to spot then when doing an upgrade to bookworm
in our case this symlink [ which i needed to run special software designed for red hat installs ]
removing the symlink fixed the issue with usrmerge and allowed upgrade to bookwork to succeed . n addition we ended up with a /usr/lib/systemd/system as /lib is a symlink to usr/lib/
so I did not need to use apt-mark hold.
CwF thank you for the help. your advice gave me the clue of installing usrmerge at bullseye.
Last edited by robfantini on 2023-06-01 00:42, edited 1 time in total.