You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For something fundamental like PAM it seems we'd want to not mess around with older versions unless there was a reason-- although a quick review of the changes doesn't reveal a pressing need to upgrade either, so.... maybe we just don't want to break all the things? :)
Anyway wanted to ask to make sure it wasn't lost in flurry of PR's or something-- is there a reason to not move to 1.3.1?
The musl patch stack will need adjusting of course but otherwise....? :)
The text was updated successfully, but these errors were encountered:
Issue description
pam 1.3.1 released a while back (~11 months ago), see: https://github.com/linux-pam/linux-pam/releases/tag/v1.3.1
repology suggests it's generally adopted elsewhere: https://repology.org/metapackage/pam/information
For something fundamental like PAM it seems we'd want to not mess around with older versions unless there was a reason-- although a quick review of the changes doesn't reveal a pressing need to upgrade either, so.... maybe we just don't want to break all the things? :)
Anyway wanted to ask to make sure it wasn't lost in flurry of PR's or something-- is there a reason to not move to 1.3.1?
The musl patch stack will need adjusting of course but otherwise....? :)
The text was updated successfully, but these errors were encountered: