FS#62531 - [squid] upgrade and /etc/pam.d/squid

Attached to Project: Community Packages
Opened by Christophe Réquillart (crequill) - Thursday, 02 May 2019, 16:20 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 19 September 2019, 12:29 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Can you please change the PKGBUILD for squid to backup the config file /etc/pam.d/squid?
I am using an ldap authentication and every time I upgrade squid I lost it!

Additional info:
* package version: 4.6-1
* config and/or log files: /etc/pam.d/squid

Steps to reproduce:
Do a modification in /etc/pam.d/squid and upgrade squid
This task depends upon

Closed by  Sergej Pupykin (sergej)
Thursday, 19 September 2019, 12:29 GMT
Reason for closing:  Fixed
Comment by AMM (amish) - Thursday, 02 May 2019, 16:28 GMT
I would suggest that instead of adding it to backup() array. The file should be moved to /usr/lib/pam.d

From "man pam":
/usr/lib/pam.d
the Linux-PAM vendor configuration directory. Files in /etc/pam.d override files with the same name in this directory.
Comment by loqs (loqs) - Thursday, 02 May 2019, 16:58 GMT
 FS#61790  has not been resolved. Why move /etc/pam.d/squid to /usr/lib/pam.d/squid before a policy has been decided arch wide?
Comment by AMM (amish) - Friday, 03 May 2019, 05:36 GMT
Umm actually there is not much participation in that bug. And mostly only one person falconindy who has participated in discussion. And I have tried to address his arguments. Especially that there is no need to do a mass migration with news item.

Also moving squid pam file to /usr/lib/pam.d will not change anything for users who have not modified it and also help resolve this ticket and avoid merging of pacnew / pacsave file in future.

Loading...