On 8/19/06, sean finney <[EMAIL PROTECTED]> wrote:
it was recently brought to my attention that the documented method
for using the dbconfig-common hooks in a maintainer's postrm script
was non-compliant wrt policy 7.2. policy stipulates that packages
can not require use of programs from any non
Hi Sean,
2006/8/19, sean finney <[EMAIL PROTECTED]>:
unfortunately, the example packages used as guidelines didn't
make any checks to safeguard this, so i suspect most/all of
the packages using dbconfig-common do not either. since these
are rc-bugs, i don't think the lintian route is the corre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi sean,
On Sat, Aug 19, 2006 at 10:54:06AM -0400, sean finney wrote:
> unfortunately, the example packages used as guidelines didn't
> make any checks to safeguard this, so i suspect most/all of
> the packages using dbconfig-common do not either. si
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
sean finney wrote:
> hey d-d,
>
> it was recently brought to my attention that the documented method
> for using the dbconfig-common hooks in a maintainer's postrm script
> was non-compliant wrt policy 7.2. policy stipulates that packages
> can not r
hey d-d,
it was recently brought to my attention that the documented method
for using the dbconfig-common hooks in a maintainer's postrm script
was non-compliant wrt policy 7.2. policy stipulates that packages
can not require use of programs from any non-essential packages
in the postrm/purge pha
5 matches
Mail list logo