Consider freeze exception for pam-devperm (RC fix ++)
I just had a look at pam-devperm, to see if I could fix the RC issue
reported against it. In the process I discovered that a new upstream
release was made in 2003, and decided it was worth a try to use this
newer version fixing a few minor issues with C pointer handling and
casting. The upstream changes are minimal.
New upstream version did not solve the crash bug reported in #492348,
but I was able to track down the issue and fix it. Looking at the
remaining two bugs, it became obvious to me that the gdm issue was the
one fixed with the patch in #492353, so I believed it was a good idea
to apply that patch to solve severity important bug #472360.
The Debian maintainer did not touched the package since 2003, and do
not reply to emails, so I decided it was time to orphan the package,
and did this too with my upload to unstable. This is the changelog.
I recommend allowing this new package to propagate into testing to
solve the RC issue. This upload should solve all BTS reports against
pam-devperm. Please consider an freeze exception to get it into
Lenny, when its resting period is over in unstable and no new issues
are reported against it.
pam-devperm (1.6-1) unstable; urgency=low
* QA upload.
* Orphan package, set Debian QA Group <firstname.lastname@example.org> as
the maintainer. The current maintainer is no longer active.
* New upstream version.
- Drop patch to add -fPIC in configure, as this is done in
src/Makefile.am in the new upstream version.
* Move local changes to debian/patches and use quilt to apply them.
* New patch segf-usermsg.diff to avoid crashing when no function
pointer is available to pass messages back to the application
* New patch reverse-restore.diff to restore permissions in the
reverse order of the one used to set permissions, to avoid
surprises with symlinked devices (Closes: #472360, #492353).
Patch from Christoph Pleger.
* Changed standards-version from 3.5.10 to 3.8.0.
-- Petter Reinholdtsen <email@example.com> Sun, 3 Aug 2008 12:00:19 +0200