If you see on https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-python/pypam/pypam-0.5.0-r6.ebuild both homepage  and SRC_URI  are actually broken.
I've placed a working link for SRC_URI on https://github.com/scardracs/PyPAM/releases/download/0.5.0/pypam-0.5.0.tar.gz but, as I'm not a maintainer anymore, IMO is better to place it somewhere.
Does not exist a pypi counterparts.
If upstream is gone, we should think about removing this package from Gentoo.
The only reverse dependency is gnome-extra/cinnamon. Could we somehow avoid this dependency in that package?
(In reply to Mike Gilbert from comment #2)
> Possible replacement:
Yes, I saw it too but actually does not provide any test suite like the original one.
About rev-deps it is used by app-emulation/xen-tools too (I thought it was used by fprintd but actually I was wrong as it uses only pam_wrapper)
(In reply to Marco Scardovi (scardracs) from comment #3)
> About rev-deps it is used by app-emulation/xen-tools too
Hmm, it seems to be in DEPEND in xen-tools. That seems quite strange: why would it need to use PAM during build time? I would guess this is a mistake and it belongs in RDEPEND instead.
(In reply to Mike Gilbert from comment #4)
> (In reply to Marco Scardovi (scardracs) from comment #3)
> > About rev-deps it is used by app-emulation/xen-tools too
> Hmm, it seems to be in DEPEND in xen-tools. That seems quite strange: why
> would it need to use PAM during build time? I would guess this is a mistake
> and it belongs in RDEPEND instead.
It appears strange to me too
python-pam seems like this should be the way to go, considering they're working on a drop-in PyPAM replacement. Plus, it's using ctypes bindings instead of platform native bindings, which seems more desirable(?) for a python package.
If there were concerns about unit tests, presumably the tests that were added to the PyPAM fork could be submitted to python-pam without too much additional work?
From Cinnamon's perspective, it doesn't matter, as it natively supports both PyPAM and python-pam
The bug has been referenced in the following commit(s):
Author: Mike Gilbert <firstname.lastname@example.org>
AuthorDate: 2021-07-19 21:04:31 +0000
Commit: Mike Gilbert <email@example.com>
CommitDate: 2021-07-19 21:06:15 +0000
dev-python/pypam: add distfiles.gentoo.org to SRC_URI
Prevents fetch failures for people with broken GENTOO_MIRRORS.
Signed-off-by: Mike Gilbert <firstname.lastname@example.org>
dev-python/pypam/pypam-0.5.0-r6.ebuild | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
I found that exist a pypi version too if you prefer https://pypi.org/project/python-pam
(In reply to Marco Scardovi (scardracs) from comment #8)
> I found that exist a pypi version too if you prefer
That is https://github.com/FirefighterBlu3/python-pam
Probably preferable to use PyPI over GH as a mirror, but same comments on code still apply. Looks like they haven't tagged a release since 2018. So at the very least we'd want a new tag (or snapshot our own) if we wanted PyPAM compatibility (provided it's actually functional as a drop-in replacement).
@floppym seems they have actually added a test suite too https://github.com/FirefighterBlu3/python-pam/tree/master/tests so you should be able to replace it with newer version and drop PyPAM finally.
It looks like the python-pam dev is (slowly) prepping for a 2.0.0 release.
However, it looks like it has been refactored a few times, so it no longer has any API compatibility with PyPAM. This is not a problem for Cinnamon.
I dug into xen-tools a bit. Looking at all of the source files:
I wasn't seeing any reference to a python file importing "pam" or "PAM". So maybe the dependency on dev-python/pypam is incorrect? Though it does appear to be using the transitive dependency on sys-libs/pam for the C headers.