Bug 212437 - sys-auth/pambase-20080306.2 re-keyword request
|
Bug#:
212437
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: pam-bugs@gentoo.org
|
Reported By: flameeyes@gentoo.org
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: sys-auth/pambase-20080306.2 re-keyword request
|
|
Keywords: KEYWORDREQ
|
|
Status Whiteboard:
|
|
Opened: 2008-03-05 23:04 0000
|
Sorry to ask right after, but I was able to get around adding the support just
today. This new version adds support for pam_passwdc. Just try to change your
password with passwd (provided shadow was built with PAM support) and it should
show up an hint and provide an analysis of the password.
Thanks,
Diego
Sorry I've added now a dependency over sys-auth/pam_mktemp that requires a few
more arches to re-keyword pambase.
I have in my TODO list pam_capabilities (sys-libs/libcap-2), pam_blue and
pam_usb, so if you don't want to see it dropped again in the next weeks, you
might want to take a look to stable those already, too ;)
[I would have preferred waiting till pambase was complete, but sys-libs/pam had
a new release and didn't want to maintain twice the versions]
(In reply to comment #1)
> I have in my TODO list pam_capabilities (sys-libs/libcap-2), pam_blue and
> pam_usb, so if you don't want to see it dropped again in the next weeks, you
> might want to take a look to stable those already, too ;)
Flameeyes meant keywording, not stabilizing :) Talked to him on IRC
Please make the distfile available. Otherwise we can't do anything.
D'oh! I start to think I made a mistake in my script as I missed two pushes in
two days...
(that was a way to say it's pushed now btw)
Added back ~sparc again. Tested with USE=mktemp and re-login. (But permissions
on /tmp/.private are wrong, because the user can't write to it.)
It is correct that user can't write (or read for what matters) /tmp/.private,
/tmp/.private/$username is what you want.
(In reply to comment #7)
> It is correct that user can't write (or read for what matters) /tmp/.private,
> /tmp/.private/$username is what you want.
>
Actually, it works fine. I just made this comment before testing further.
keyworded ~arch for ppc64
I'll wait until you add those new deps so i can use.mask pam_blue and pam_usb
on ia64 at least.
Where's pam_capabilities?
>=libcap-2
As for the use mask, you can do that already if you want, but I suppose
package.use.mask is what you want.
The USE flags will be:
caps - pam_capabilities
usb - pam_usb
bluetooth - pam_blue
Keyworded on ~alpha. Note that bluetooth is use-masked on Alpha already, so
nothing done there. Current ~alpha versions of pam_usb (0.3.2) and pam_mktemp
(1.0.3) work fine.