Bug#462648: update-menu: example menufiles giving syntax errors

2008-02-07 Thread Bill Allombert
On Wed, Feb 06, 2008 at 04:43:06PM -0800, Nick Daly wrote:
 Followup-For: Bug #462648
 Package: menu
 Version: 2.1.37
 
 *** Please type your report below this line ***
 More ways update-menus doesn't work:
 Update-menus no longer understands custom (any?) menufiles.
 
 To reproduce:
 Make a custom menu file (such as the lyx menufile from the 
 /usr/share/menu directory):
 ?package(lyx):
   needs=X11 section=Applications/Office \
   title=LyX Document Processor command=lyx \
   icon=/usr/share/icons/hicolor/32x32/apps/lyx.xpm\
   hints=Word processors
 
 After making the file executable (chmod 755) so it produces output, and 

You should not make it executable since it is not a shell script or
a program.

Cheers,
-- 
Bill. [EMAIL PROTECTED]

Imagine a large red swirl here. 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#462648: update-menu: example menufiles giving syntax errors

2008-02-06 Thread Nick Daly
Followup-For: Bug #462648
Package: menu
Version: 2.1.37

*** Please type your report below this line ***
More ways update-menus doesn't work:
Update-menus no longer understands custom (any?) menufiles.

To reproduce:
Make a custom menu file (such as the lyx menufile from the 
/usr/share/menu directory):
?package(lyx):
  needs=X11 section=Applications/Office \
  title=LyX Document Processor command=lyx \
  icon=/usr/share/icons/hicolor/32x32/apps/lyx.xpm\
  hints=Word processors

After making the file executable (chmod 755) so it produces output, and 
then running update-menus results in the following output:
/home/nick/.menu/lyx: line 1: syntax error near unexpected token `lyx'
/home/nick/.menu/lyx: line 1: `?package(lyx):'
Execution of /home/nick/.menu/lyx generated no output or returned an 
error.

update-menus results in the same syntax error for all menufiles with 
that syntax...  Has the syntax of update-menus changed without being 
documented?

Due to the fact that it fails with a syntax error for every menufile 
presented, it is thus impossible to add any custom menu entries to the 
standard Debian menu.

While this could be a separate bug, I have a feeling that it's related 
to the bug I'm currently filing it under, and that it's simply another 
expression of the same underlying problem.

If any further information is needed (I could be a bit too out of it to 
have included all necessary information), feel free to ask.  All 
menufiles in ~/.menu are of UTF-8 encoding, if that makes any 
difference (en-US locale).

Even making any of the menufiles in /usr/share/menu executable results 
in that file suffering from the same syntax error, unexpected token 
near the package name...  I don't understand how the Debian menu on my 
system is created at this point...  I only stumbled upon this problem because I
recently switched from Gnome to fluxbox, and then openbox when I found that the
fluxbox menu didn't work.  Running update-menus in openbox makes the menu
appear perfectly fine.

Thanks so much,
Nick Daly

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages menu depends on:
ii  libc6   2.7-6GNU C Library: Shared libraries
ii  libgcc1 1:4.3-20080116-1 GCC support library
ii  libstdc++6  4.3-20080116-1   The GNU Standard C++ Library v3

menu recommends no packages.

-- no debconf information


  

Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]