Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#37436 - [pam] 1.1.8-1 Package is self-dependent
Attached to Project:
Arch Linux
Opened by Jussi Saarinen (jtts) - Monday, 21 October 2013, 16:49 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 23 October 2013, 16:44 GMT
Opened by Jussi Saarinen (jtts) - Monday, 21 October 2013, 16:49 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 23 October 2013, 16:44 GMT
|
DetailsDescription:
Currently, building pam is self-dependent, i.e. a previous version of pam needs to be installed in order to build it. This is because building pam_unix2 requires libpam.so, which is provided by Linux-PAM. Currently, the configuration-script for pam_unix2 only finds libpam.so that is already installed in the system, not the one that was built by makepkg when it built Linux-PAM just before building pam_unix2. Additional info: * package version(s) pam-1.1.8-1 * config and/or log files etc. Steps to reproduce: |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Wednesday, 23 October 2013, 16:44 GMT
Reason for closing: Fixed
Additional comments about closing: 1.1.8-2
Wednesday, 23 October 2013, 16:44 GMT
Reason for closing: Fixed
Additional comments about closing: 1.1.8-2
Comment by Dave Reisner (falconindy) -
Monday, 21 October 2013, 21:45 GMT
Does the attached patch to the PKGBUILD help?
Comment by Jussi Saarinen (jtts) -
Tuesday, 22 October 2013, 04:35 GMT
Package compiles OK. I'm not sure how to ascertain whether the right pam was used or not.
Comment by Jussi Saarinen (jtts) -
Tuesday, 22 October 2013, 04:38 GMT
I only run into this issue indirectly, since I recently adopted lib32-pam package in AUR. When I adapt your patch for lib32-pam, it compiles OK without a previously installed lib32-pam.
build-hermetic.patch
(0.6 KiB)