Bug 628338

Summary:	sys-apps/systemd and LIBDIR_x86=lib SYMLINK_LIB=no
Product:	Gentoo Linux	Reporter:	Georgy Yakovlev <gyakovlev>
Component:	Current packages	Assignee:	Gentoo systemd Team <systemd>
Status:	RESOLVED INVALID
Severity:	normal	CC:	franz.trischberger, mgorny
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	emerge --info systemd, freshly boostrapped ~amd64 stage.

Description Georgy Yakovlev archtester

2017-08-19 22:22:37 UTC

Created attachment 489712 [details]
emerge --info systemd, freshly boostrapped ~amd64 stage.

sys-apps/systemd installs libraries and binaries into
/usr/lib/systemd and (since 334) /lib/systemd

I'm testing a ~arch default/linux/amd64/13.0/systemd profile with forced 
LIBDIR_x86=lib
SYMLINK_LIB=no

and maybe it should go to /lib64 /usr/lib64

I'm not sure if it's intended or should be fixed.


see https://bugs.gentoo.org/show_bug.cgi?id=506276

Comment 1 Michał Górny archtester

2017-08-19 22:48:40 UTC

Nope, it's the correct upstream location. Moving it elsewhere will break a lot of stuff.

Comment 2 Franz Trischberger 2019-10-17 06:09:48 UTC

You could have kept a symlink to lib64. The binary was reachable through /usr/lib64/systemd/systemd (/usr/lib was a symlink to /usr/lib64) and that was what I had in my grub.conf.
After the migration to 17.1 I had an unbootable system. Luckily I carry an old entry with openrc around...
This really caused me quite some headaches and even more hours to track down.

I hope we are now done with risky upgrades and just have to deal with normal updates...