Bug#582395: modifying files from another package

2010-06-05 Thread Jens Peter Secher
On 4 June 2010 20:01, Steve Langasek vor...@debian.org wrote: I see the profile contained in the package is /usr/share/pam-configs/silent-ssh-single-sign-on, but in the prerm you're calling 'pam-auth-update --package --remove pam-ssh'.  The argument to pam-auth-update needs to be the name of

Bug#582395: modifying files from another package

2010-06-04 Thread Steve Langasek
Hi Jens Peter, I see the profile contained in the package is /usr/share/pam-configs/silent-ssh-single-sign-on, but in the prerm you're calling 'pam-auth-update --package --remove pam-ssh'. The argument to pam-auth-update needs to be the name of the profile: i.e., silent-ssh-single-sign-on.

Bug#582395: modifying files from another package

2010-05-24 Thread Jens Peter Secher
pam-ssh uses pam-auth-update (from libpam-runtime) in postinst and prerm, as advocated in http://lists.debian.org/debian-devel/2009/03/msg3.html, so I guess piuparts is flawed. Cheers, -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E

Bug#582395: modifying files from another package

2010-05-20 Thread Holger Levsen
Package: libpam-ssh Version: 1.92-13 Severity: serious User: debian...@lists.debian.org Usertags: piuparts piuparts.d.o Hi, during a test with piuparts I noticed your package modifies files from another package in /usr. This is so wrong, I'm not even bothered to look up the part of policy