Summary: | sys-auth/pambase - rework gnome-keyring support | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexander Tsoy <alexander> |
Component: | Current packages | Assignee: | PAM Gentoo Team (OBSOLETE) <pam-bugs+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gnome, leho, poncho |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=516848 https://bugs.gentoo.org/show_bug.cgi?id=600216 https://bugs.gentoo.org/show_bug.cgi?id=662088 https://bugs.gentoo.org/show_bug.cgi?id=658646 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
pambase-20150213-gnome-keyring.patch
pambase-20150213-r1.ebuild.patch |
Description
Alexander Tsoy
2018-04-02 10:31:03 UTC
Created attachment 526314 [details, diff]
pambase-20150213-r1.ebuild.patch
Thanks for the investigation work. Who needs to approve what to get to the next step here? Would be nice to maybe have a masked ebuild in the tree or overlay for easier testing on a wider surface? I'm very supportive of this undertaking. Every few month there is a bug like: "pam change A,B and C break gnome-keyring" What if we make an another PAM config called, say, "xsession_session" and shove all gnome/systemd specific PAM configs there? This way, desktop manager maintainers don't have to think anything about specific polkit/consolekit/systemd/elogind setup a user have. [master fadc9f49e11f] sys-auth/pambase: Fix gnome-keyring (#652194 by Alexander Tsoy) 1 file changed, 106 insertions(+) create mode 100644 sys-auth/pambase/pambase-20150213-r2.ebuild (In reply to Pacho Ramos from comment #4) > 1 file changed, 106 insertions(+) It would be good to upload the patch also :) oh yes :S [master 669c574f742d] sys-auth/pambase: Commit forgotten patch 1 file changed, 48 insertions(+) create mode 100644 sys-auth/pambase/files/pambase-20150213-gnome-keyring.patch |