Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | d/libpam-{modules,runtime}.post{inst,rm}: Use `set -e` instead of `/bin/sh -e` | Gioele Barabucci | 2025-02-13 | 1 | -1/+3 |
| | | | | | | | Policy recommends to use `set -e` to ensure that scripts always have `-e` enabled, even when they are run as `sh foo.postinst`. Fixes: lintian: *: maintainer-script-without-set-e | ||||
* | libpam-runtime.postrm: /var/lib/pam may not exist on purge | Sam Hartman | 2021-09-15 | 1 | -1/+1 |
| | | | | | | | In practice, I get a directory does not exist when I run dpkg --force-remove-essential --force-depends --purge libpam-runtime I'm guessing that somehow /var/lib/pam is getting removed both in the remove and purge stage. That's okay, so ignore it. | ||||
* | libpam-runtime.postrm: Remove session-noninteractive files on purge, Closes: ↵ | Josh Triplett | 2021-09-15 | 1 | -2/+4 |
| | | | | #978601 | ||||
* | set apporpriate values for the debconf question, by storing a list of known | Steve Langasek | 2019-01-03 | 1 | -1/+1 |
| | | | | configs in /var/lib/pam/seen | ||||
* | and also remove the /var/lib/pam directory itself | Steve Langasek | 2019-01-03 | 1 | -0/+1 |
| | |||||
* | in the unlikely event of purging libpam-runtime, take care of /var/lib/pam as | Steve Langasek | 2019-01-03 | 1 | -0/+2 |
| | | | | | well | ||||
* | remove other code related to the woody->sarge upgrade | Steve Langasek | 2019-01-03 | 1 | -8/+0 |
| | |||||
* | fix-up commit for grafting svn history onto git history | Steve Langasek | 2019-01-02 | 1 | -0/+16 |