Bug#314187: lintian: incorrect warning about useless-call-to-update-menus

[<allomber@math.u-bordeaux.fr>]

On Wed, Jun 15, 2005 at 09:33:49AM +0100, Adam D. Barratt wrote:
> On Wednesday, June 15, 2005 6:22 AM, Wesley J. Landaker <wjl@icecavern.net>
> wrote:
> 
> > When I run lintian on one of my packages, it gives me warnings about
> > useless calls to update-menus.
> [...]
> > Well, the warning is kind of right, I don't have a menu file in
> > /usr/lib/menu. But, that is because in Debian Policy section 3.1, it
> > says they should go in /usr/share/menu, which is where it is:
> [...]
> > Is this some new check added to lintian on purpose? It contradicts
> > current Debian policy...
> 
> Section 3.1 of Debian Policy is "The package name". I'm assuming you mean
> section 3.1 of http://www.nl.debian.org/doc/packaging-manuals/menu.html/
> ("Debian Menu System"), which *isn't* policy.
> 
> That document appears to have last been updated three days ago. At the end
> of March, the text in question read
> 
>     Packages provided menu files should be in `/usr/lib/menu/'.
>      System-local menu files should be in `/etc/menu/'.  User-specific menu
>      files should be in `~/.menu/'
> 
> so, afaics, no this isn't "some new check added to lintian on purpose" and
> it *doesn't* contradict Policy. What's happened is that the menu maintainers
> have changed their recommendations as to where menu files should be placed.

This is correct.  What happens here is that debhelper was also updated to
put menu entries in /usr/share/menu.

Lintian should now support both locations, though use of /usr/lib/menu 
should trigger a warning since it is only for executable binaries
menufiles and there are none in Debian currently.

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here.