Bug#562702: python-pam: Debian differences not clearly separated from upstream source

[Sebastian Ramacher <sramacher@debian.org>]

Hi Bastian

On 2022-12-03 11:21:01 +0100, Bastian Germann wrote:
> Control: severity -1 serious
> X-Debbugs-Cc: doko@debian.org
> 
> On Sun, 27 Dec 2009 17:28:04 +1100 Ben Finney <ben+debian@benfinney.id.au> wrote:
> > However, the ‘python-pam_0.4.2.orig.tar.gz’ does not match the actual
> > file at <URL:http://www.pangalactic.org/PyPAM/PyPAM-0.4.2.tar.gz>,
> > with many significant changes.
> > 
> > These changes should be separated from the pristine upstream source
> > (in a ‘python-pam_0.4.2-nn.diff.gz’, if using the Debian source format
> > 1.0) and the ‘python-pam_0.4.2.orig.tar.gz’ should match the tarball
> > available from upstream.
> > 
> > The provenance of these changes should also be recorded in the Debian
> > copyright file for the package.
> 
> The upstream source is no longer available. There is a fork including py3 support available at
> https://github.com/openEuler-BaseService/PyPAM.
> 
> We should switch to that as upstream or drop this package entirely.
> I am copying Matthias as he worked on the package mostly since it was abandoned.
> For now, make this serious, to keep this out of bookworm in favour of pam-python.

This will have no effect. python-pam is a key package and so won't be
removed automatically from bookworm because of this bug.

Also:

$ dak rm -Rn -s testing python-pam
Will remove the following packages from testing:

python-pam |   0.4.2-16 | source
python3-pam |   0.4.2-16 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x

Maintainer: Debian QA Group <packages@qa.debian.org>

------------------- Reason -------------------

----------------------------------------------

Checking reverse dependencies...
# Broken Build-Depends:
pam-python: python3-pam

Dependency problem found.


This seems like it would be easy enough to fix.

Cheers
-- 
Sebastian Ramacher