Package: jffnms Severity: serious Justification: 7.2 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
hi there, it was recently brought to my attention that the recommended method for using dbconfig-common in a package's config and postrm scripts was not policy compliant as hinted in the subject of this bugreport. the problem is that in both the config and the postrm you should test whether the files/programs in question exist before sourcing/executing them. more information is in a link below. NOTE that this is slightly different from the original posts about mass-bug filing in which only the postrm was mentioned, but the config file is too. so, even if you've fixed your package after i initially posted about this, you might want to take a second look to make sure. this mass bug-filing was announced 2006/08/19, though it seems there's a problem with the list archives for debian-devel. fortunately, i cc'd the dbconfig list: http://lists.alioth.debian.org/pipermail/dbconfig-common-devel/2006-August/000586.html and information for how you can fix your package: http://people.debian.org/~seanius/policy/dbconfig-common.html/ch-develguide.html#s-hooks fortunately, the fix is pretty simple, though i apologize for the inconvenience. feel free to ask if you have any questions. sean - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-amd64-k8 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFD7v1ynjLPm522B0RAl6pAJ4nm7WPz0xCZzNxqA3IspBfL9O9fQCfeIGH GxTzLrMEoK2oFWw7rtsk2UM= =nsNz -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
