Bug#386320: Bug#386446: menu: Debug option of update-menus does not work

2006-09-11 Thread gregor herrmann
On Mon, 11 Sep 2006 19:06:57 +0200, Frank Küster wrote: > Bill Allombert <[EMAIL PROTECTED]> wrote: > > On Mon, Sep 11, 2006 at 01:42:51PM +0200, Frank Küster wrote: > >> P.S. I've recently filed a bug against jabref, demanding that it be > >> moved from Apps/Tools to Data managment. [..] > >> Are

Bug#386446: menu: Debug option of update-menus does not work

2006-09-11 Thread Bill Allombert
On Mon, Sep 11, 2006 at 01:42:51PM +0200, Frank Küster wrote: > Bill Allombert <[EMAIL PROTECTED]> wrote: > > Well, it does show the entries that are discarded because their package > is missing. But it I think it does not solve the other problem I > mentioned: JabRef doesn't get a menu entry, an

Bug#386446: menu: Debug option of update-menus does not work

2006-09-11 Thread Frank Küster
Bill Allombert <[EMAIL PROTECTED]> wrote: >> As I said, in a sid chroot this ends up in fluxbox' menu file, while on >> sarge with menu_2.1.30 it is missing in fluxbox' and WMaker's menu file. > > By any chance is there a file /etc/menu/jabref on that machine ? > that would explain the problem. Y

Bug#386320: Bug#386446: menu: Debug option of update-menus does not work

2006-09-11 Thread Frank Küster
Hi Gregor, Bill Allombert <[EMAIL PROTECTED]> wrote: > On Mon, Sep 11, 2006 at 01:42:51PM +0200, Frank Küster wrote: >> P.S. I've recently filed a bug against jabref, demanding that it be >> moved from Apps/Tools to Data managment. This has been fixed, but at >> the same time a lintian override

Bug#386446: menu: Debug option of update-menus does not work

2006-09-11 Thread Bill Allombert
On Mon, Sep 11, 2006 at 01:42:51PM +0200, Frank Küster wrote: > P.S. I've recently filed a bug against jabref, demanding that it be > moved from Apps/Tools to Data managment. This has been fixed, but at > the same time a lintian override has been added: > > jabref binary: menu-item-creates-new-

Bug#386446: menu: Debug option of update-menus does not work

2006-09-11 Thread Frank Küster
Bill Allombert <[EMAIL PROTECTED]> wrote: > On Thu, Sep 07, 2006 at 08:15:24PM +0200, Bill Allombert wrote: >> > What I would like from the debug option is information about menu files >> > that do not lead to creation of a menu entry, e.g. because the package >> > is not installed or there is an

Bug#386446: menu: Debug option of update-menus does not work

2006-09-07 Thread Bill Allombert
On Thu, Sep 07, 2006 at 08:15:24PM +0200, Bill Allombert wrote: > > What I would like from the debug option is information about menu files > > that do not lead to creation of a menu entry, e.g. because the package > > is not installed or there is an error in the file. > > Errors in the file are a

Bug#386446: menu: Debug option of update-menus does not work

2006-09-07 Thread Bill Allombert
On Thu, Sep 07, 2006 at 07:25:33PM +0200, Frank Küster wrote: > Package: menu > Version: 2.1.29, 2.1.24 > Severity: normal Hello Frank, > The output of "update-menus -v" and "update-menus -d" is identical. This is currently the case, yes. > According to the manual page, this is not intended. T

Bug#386446: menu: Debug option of update-menus does not work

2006-09-07 Thread Frank Küster
Package: menu Version: 2.1.29, 2.1.24 Severity: normal The output of "update-menus -v" and "update-menus -d" is identical. According to the manual page, this is not intended. What I would like from the debug option is information about menu files that do not lead to creation of a menu entry, e.g.