399583 – >=sys-apps/systemd-37-r3: pam_systemd installed into incorrect destination

Bug 399583 - >=sys-apps/systemd-37-r3: pam_systemd installed into incorrect destination

Summary: >=sys-apps/systemd-37-r3: pam_systemd installed into incorrect destination

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Core system (show other bugs)
Hardware:	All Linux

Importance:	Normal normal
Assignee:	Gentoo systemd Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2012-01-21 08:33 UTC by Benjamin Franzke
Modified:	2012-01-21 16:16 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Benjamin Franzke 2012-01-21 08:33:57 UTC

Since the migration to /usr/lib root-prefix for systemd the pam_systemd
module is incorrectly installed to /usr/lib as well.
Please pass --with-pamlibdir to configure in the systemd ebuilds.

btw: Other directories like the udevulesdir and dbusdirs are detected by
the configure script since it uses pkg-config there.
Not sure, but I think since thats automagic, the ebuild should pass those explicitly as well?


Reproducible: Always

Comment 1 Michał Górny archtester

2012-01-21 09:55:54 UTC

This is fixed already in -9999.

Comment 2 Michał Górny archtester

2012-01-21 16:16:45 UTC

Fixed in all current versions (with revision bumps).