How to avoid usr-is-merged reconfiguration

[yvs222]

Hi everyone,

is there a way to disable "usr-is-merged' reconfiguration at 'apt upgrade ...' ?

Once broken it leads to
```
Preparing to unpack .../usr-is-merged_39_all.deb ...
Unpacking usr-is-merged (39) ...
Setting up usr-is-merged (39) ...
removed '/lib64'
/var/lib/dpkg/info/usr-is-merged.postinst: 16: rmdir: not found
dpkg: error processing package usr-is-merged (--configure):
installed usr-is-merged package post-installation script subprocess returned error exit status 127
Errors were encountered while processing:
usr-is-merged
E: Sub-process /usr/bin/dpkg returned an error code (1)
...
```

it takes some time to recover lib64 symlink every time after that

p.s. debian 'testing'

[sunrat]

Moved to Testing and Unstable subforum.

[fabien]

Hello,

what gives

Code: Select all

$> ls -l "$(command -v rmdir)"

?

[yvs222]

`command not found: ls`

what can be else if /lib64 already removed at this point?

[fabien]

what is the output of these commands? (using code tags please)

Code: Select all

$> apt list coreutils

Code: Select all

$> dpkg --verify coreutils

Code: Select all

$> find /usr/ -type f -name "ls"

Code: Select all

$> find /usr/ -type f -name "mkdir"

This one as root:

Code: Select all

#> apt-get check

[yvs222]

after deleting /lib64 by usr-is-merged: all commands (excluding those that loaded in memory) are broken because of shared libs are not accessible, i.e. system is broken (to restore its normal state I gotta load from rescue media, mount / and symlink /lib64 back to usr/lib64, after restoring /lib64 it works as usual).

all those commands and system work normally before usr-is-merged reconfiguration happens, after:
command not found: <put-here-any-command>

What caused reconfiguration of usr-is-merged in my case: broken package metadata (occasionally made once before at system transfer/update).
Question is how to disable 'usr-is-merged' reconfiguration (at 'apt upgrade' for example).

[fabien]

Question is how to disable 'usr-is-merged' reconfiguration (at 'apt upgrade' for example).

No, your question is typical of the XY problem.
Your problem appears to be caused by very specific conditions. Please answer the questions, otherwise, as you surely understand, it will not be possible to review it.

What is the output of these commands? (using code tags please)

Code: Select all

$> apt list libc6 usr-is-merged usrmerge

Code: Select all

$> dpkg-query -S /lib64

Code: Select all

$> dpkg --print-architecture

Code: Select all

$> dpkg --print-foreign-architectures

[CwF]

What caused reconfiguration of usr-is-merged in my case: broken package metadata (occasionally made once before at system transfer/update).
Question is how to disable 'usr-is-merged' reconfiguration (at 'apt upgrade' for example).

I'm not clear on the progression happening here?

What is the system status before this breakage? Debian 11.x, 12.x, fresh install ?

There is a way to run 'un-merged', late conversion to merged seems problematic if done >12.x if originally unmergerd.
Paint me a better picture, I need specifics.

[yvs222]

> I'm not clear on the progression happening here?
> What is the system status before this breakage? Debian 11.x, 12.x, fresh install ?

It was debian stable (12) that I've used for tests, then to get a couple new packages it was upgraded to 'testing'. Some package metadata was lost at upgrade (by removing to free some disk space for upgrade).
Now it's a current debian testing, it works okay if not to try 'apt upgrade' (because of usr-is-merged's reconfiguration deletes /lib64 symlink at that, a way how packages got dependency on usr-is-merged - no idea).
It's not critical to me, that installation is used for tests only.