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#37424 - pam-1.1.8-1: pam.install not included in package
Attached to Project:
Arch Linux
Opened by Jussi Saarinen (jtts) - Sunday, 20 October 2013, 22:06 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 21 October 2013, 06:21 GMT
Opened by Jussi Saarinen (jtts) - Sunday, 20 October 2013, 22:06 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 21 October 2013, 06:21 GMT
|
DetailsDescription:
The pam package currently in core has a file "pam.install" in the git tree: https://projects.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/pam However, PKGBUILD-file doesn't contain an install-variable. If I have understood the workings of PKGBUILD correctly, the package built using this PKGBUILD won't contain the install script unless PKGBUILD-file contains an install-variable. Additional info: * package version(s) pam-1.1.8-1 * config and/or log files etc. Steps to reproduce: run 'abs core/pam' run 'makepkg --source' in pam's abs directory check whether the created source tarball contains the install script or not. |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Monday, 21 October 2013, 06:21 GMT
Reason for closing: Fixed
Additional comments about closing: removed from trunk
Monday, 21 October 2013, 06:21 GMT
Reason for closing: Fixed
Additional comments about closing: removed from trunk