Merge ~andersson123/ubuntu/+source/shadow:ubuntu/noble-proposed into ubuntu/+source/shadow:ubuntu/noble-devel
Proposed by
Tim Andersson
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | d8203aead106b071fd6bde986b74f4ec53329c86 | ||||
Proposed branch: | ~andersson123/ubuntu/+source/shadow:ubuntu/noble-proposed | ||||
Merge into: | ubuntu/+source/shadow:ubuntu/noble-devel | ||||
Diff against target: |
32 lines (+9/-4) 2 files modified
debian/changelog (+9/-0) debian/login.pam (+0/-4) |
||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Steve Langasek (community) | Approve | ||
Lukas Märdian (community) | Needs Fixing | ||
git-ubuntu import | Pending | ||
Review via email:
|
Commit message
* Don't include pam_lastlog.so as optional (LP: #2060676)
- d/p/remove-
To post a comment you must log in.
Hi Tim! I left some inline comments below.
Overall, I'm not sure if the rationale is strong enough for this to be SRUed... As you mentioned in the bug report yourself, it's mostly a cosmetic issue, to avoid a warning log message. I'm not a SRU reviewer, but I'd suggest improving your [Impact] section, if you still want to get this landed.
IMO the risk & impact might be too high for just muting a log message. If you still want to go for it, I'd suggest getting the package into noble-proposed, but then adding the "block- proposed- noble" tag to the SRU bug. That way you could still do the full SRU verification, but keep the package update pending, until some other shadow SRU needs to be done and the two fixes could be deployed together as a bundle to noble-updates.
Another thought: When and why exactly did the pam_lastlog.so disappear? Might it be a better option to get that fixed instead? As that might actually affect users relying on the "last" command. Fixing that root cause (either by bringing back old pam_lastlog.so or some new lastlog2 binary), seems more valuable to me.