Re: Bug#499269: dictionaries-common-dev: produces non Policy compliant maintainer scripts
On Wed, Sep 17, 2008 at 6:39 PM, Agustin Martin <agmartin@debian.org> wrote:
> reassign 499269 dictionaries-common
> retitle 499269 Should not use full paths in maintainer scripts
> thanks
>
> On Wed, Sep 17, 2008 at 03:04:00PM +0300, Martin-Éric Racine wrote:
>> Package: dictionaries-common-dev
>> Severity: important
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> As found while looking at the Lintian report for my dictionary packages:
>>
>> iestonian
>>
>> * W command-with-path-in-maintainer-script
>> o postrm:5 /usr/sbin/remove-default-ispell
>>
>> aspell-et
>>
>> * W command-with-path-in-maintainer-script
>> o postrm:6 /usr/sbin/update-dictcommon-aspell
>>
>> aspell-lv
>>
>> * W command-with-path-in-maintainer-script
>> o postrm:6 /usr/sbin/update-dictcommon-aspell
>>
>> irussian
>>
>> * W command-with-path-in-maintainer-script
>> o postrm:5 /usr/sbin/remove-default-ispell
>>
>> aspell-ru
>>
>> * W command-with-path-in-maintainer-script
>> o postrm:6 /usr/sbin/update-dictcommon-aspell
>>
>> All those Lintian warnings are the result of dictionaries-common-dev
>> generating maintainer scripts that are not Policy-compliant.
>>
>> As per Debian Policy:
>>
>> Commands that reside in standard system paths should not have
>> the full path prepended to them.
>
> Yes, I am aware of this, but this lintian check is recent (Early August),
> so I noticed its effects once lenny was frozen. dictionaries-common
> maintainer scripts suffer from the same problem, so I am reassigning this
> bug report to the basic package.
>
> Will be fixed once lenny is released.
I think that RM would have no problem allowing a freeze exception to
make dictionaries-common Policy-compliant, followed by a bin-NMU
trigger to rebuild all dictionaries.
Would the RM team please comment on this issue?
Cheers!
--
Martin-Éric Racine
http://q-funk.iki.fi
Reply to: