@Viktor, thanks for fixing the status and making it clear it was fixed in stonking!
The bot comment was maybe a bit confusing there and I will try to tweak the wording maybe, but as a rule if you don't have a bug line targetting the series where you want to land the fix (resolute here), which is often the case since targetting is an privileged action which requires group membership, you better mark the current task as "fix commited", if you close it as "fix released" the bug will drop from the sponsoring report. Being explicit in the description should be enough to make the bot happy and avoid confusion for the sponsor. That said I've sponsored the fix to resolute now so can keep the state for this one as it is. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2167039 Title: pam_lastlog2.so not linked against libpam: "undefined symbol: pam_syslog" when loaded by systemd-executor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2167039/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
