Bug#1023124: libsystemd-shared-251.so: cannot open shared object file

2022-10-31 Thread Luca Boccassi
Control: tags -1 -moreinfo
Control: close -1

On Sun, 30 Oct 2022 14:56:08 +0100 Salvo Tomaselli
 wrote:
> systemd-machine-id-setup: /usr/bin/systemd-machine-id-setup
> /bin/systemd-machine-id-setup
> /usr/share/man/man1/systemd-machine-id-setup.1.gz
> 
> 
> stat /usr/bin/systemd-machine-id-setup /bin/systemd-machine-id-setup
>  File: /usr/bin/systemd-machine-id-setup
>  Size: 18928   Blocks: 40 IO Block: 4096   regular
file
> Device: 259,5   Inode: 4201937 Links: 1
> Access: (0755/-rwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/   
root)
> Access: 2022-10-30 13:34:13.098418093 +0100
> Modify: 2022-08-14 20:06:18.0 +0200
> Change: 2022-08-22 15:25:56.730012624 +0200
> Birth: 2022-08-22 15:25:56.610011671 +0200
>  File: /bin/systemd-machine-id-setup
>  Size: 18928   Blocks: 40 IO Block: 4096   regular
file
> Device: 259,5   Inode: 8650854 Links: 1
> Access: (0755/-rwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/   
root)
> Access: 2022-10-30 13:38:20.0 +0100
> Modify: 2022-10-14 16:34:00.0 +0200
> Change: 2022-10-30 13:38:20.944385494 +0100
> Birth: 2022-10-30 13:38:20.816384357 +0100
> 
> 
> 
> It seems my system is in a weird status from some previous issues…
> Maybe originating  when apt told me to split /usr, then I had some
> issues and had to manually install a bunch of packages.

Yes, your system is in a bad state and needs to be fixed, and it has
nothing to do with the systemd packages or this update, so I'll close
this now.

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part


Bug#1023124: libsystemd-shared-251.so: cannot open shared object file

2022-10-30 Thread Salvo Tomaselli
systemd-machine-id-setup: /usr/bin/systemd-machine-id-setup
/bin/systemd-machine-id-setup
/usr/share/man/man1/systemd-machine-id-setup.1.gz


stat /usr/bin/systemd-machine-id-setup /bin/systemd-machine-id-setup
 File: /usr/bin/systemd-machine-id-setup
 Size: 18928   Blocks: 40 IO Block: 4096   regular file
Device: 259,5   Inode: 4201937 Links: 1
Access: (0755/-rwxr-xr-x)  Uid: (0/root)   Gid: (0/root)
Access: 2022-10-30 13:34:13.098418093 +0100
Modify: 2022-08-14 20:06:18.0 +0200
Change: 2022-08-22 15:25:56.730012624 +0200
Birth: 2022-08-22 15:25:56.610011671 +0200
 File: /bin/systemd-machine-id-setup
 Size: 18928   Blocks: 40 IO Block: 4096   regular file
Device: 259,5   Inode: 8650854 Links: 1
Access: (0755/-rwxr-xr-x)  Uid: (0/root)   Gid: (0/root)
Access: 2022-10-30 13:38:20.0 +0100
Modify: 2022-10-14 16:34:00.0 +0200
Change: 2022-10-30 13:38:20.944385494 +0100
Birth: 2022-10-30 13:38:20.816384357 +0100



It seems my system is in a weird status from some previous issues…
Maybe originating  when apt told me to split /usr, then I had some
issues and had to manually install a bunch of packages.

Il giorno dom 30 ott 2022 alle ore 13:52 Ansgar  ha scritto:
>
> On Sun, 2022-10-30 at 13:34 +0100, Salvo "LtWorf" Tomaselli wrote:
> > Preconfiguring packages ...
> > Setting up systemd (252~rc3-2) ...
> > systemd-machine-id-setup: error while loading shared libraries: 
> > libsystemd-shared-251.so: cannot open shared object file: No such file or 
> > directory
> > dpkg: error processing package systemd (--configure):
> >  installed systemd package post-installation script subprocess returned 
> > error exit status 127
> > Errors were encountered while processing:
> >  systemd
> > E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> The /bin/systemd-machine-id-setup shipped in the systemd 252~rc3-2
> package is linked against libsystemd-shared-252.so, not libsystemd-
> shared-251.so.
>
> Please check all paths given in the PATH used when calling dpkg/apt for
> systemd-machine-id-setup (e.g., by using `which -a systemd-machine-id-
> setup` with the correct PATH) and report their location and sha1 hash
> (sha1sum /bin/systemd-machine-id-setup ...).
>
> Please also report the output of `ls -ld /bin /usr/bin` and whether the
> system is merged-/usr already or not.
>
> Ansgar
>


-- 
Salvo Tomaselli

"Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di
senso, ragione ed intelletto intendesse che noi ne facessimo a meno."
-- Galileo Galilei

http://ltworf.github.io/ltworf/



Bug#1023124: libsystemd-shared-251.so: cannot open shared object file

2022-10-30 Thread Ansgar
On Sun, 2022-10-30 at 13:34 +0100, Salvo "LtWorf" Tomaselli wrote:
> Preconfiguring packages ...
> Setting up systemd (252~rc3-2) ...
> systemd-machine-id-setup: error while loading shared libraries: 
> libsystemd-shared-251.so: cannot open shared object file: No such file or 
> directory
> dpkg: error processing package systemd (--configure):
>  installed systemd package post-installation script subprocess returned error 
> exit status 127
> Errors were encountered while processing:
>  systemd
> E: Sub-process /usr/bin/dpkg returned an error code (1)

The /bin/systemd-machine-id-setup shipped in the systemd 252~rc3-2
package is linked against libsystemd-shared-252.so, not libsystemd-
shared-251.so.

Please check all paths given in the PATH used when calling dpkg/apt for
systemd-machine-id-setup (e.g., by using `which -a systemd-machine-id-
setup` with the correct PATH) and report their location and sha1 hash
(sha1sum /bin/systemd-machine-id-setup ...).

Please also report the output of `ls -ld /bin /usr/bin` and whether the
system is merged-/usr already or not.

Ansgar



Bug#1023124: libsystemd-shared-251.so: cannot open shared object file

2022-10-30 Thread Michael Biebl

Control: tags -1 + moreinfo

Am 30.10.22 um 13:34 schrieb Salvo "LtWorf" Tomaselli:


E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up systemd (252~rc3-2) ...
systemd-machine-id-setup: error while loading shared libraries: 
libsystemd-shared-251.so: cannot open shared object file: No such file or 
directory


..


merged-usr: no


Please attach the output of
whereis systemd-machine-id-setup



OpenPGP_signature
Description: OpenPGP digital signature