From: Giovanni Funchal on
Hi,

I've just noticed that the file command returns wrong mime for a file.
In fact, if a LaTeX file uses the command \bibligraphystyle somewhere
in the beginning, file will return mime "text/vnd.graphviz" instead of
"text/x-tex". I took a look at /usr/share/file/magic (on Lenny), and
it has something like :

0 regex/100 [\r\n\t\ ]*graph[\r\n\t\ ]*.*\\{ graphviz graph text
!:mime text/vnd.graphviz

This regular expression matches \biblioGRAPHystyle in the first
thousand characters or so. A good fix would be :

- 0 regex/100 [\r\n\t\ ]*graph[\r\n\t\ ]*.*\\{ graphviz graph text
+ 0 regex/100 (^|[\r\n\t\ ]+)graph[\r\n\t\ ]*.*\\{ graphviz graph text

Since in the dot file format[1], the keyword "graph" must be preceded
by a white space or be in the beginning of the file.

Anyone knows where I can report this?

-- Giovanni

[1] http://www.graphviz.org/doc/info/lang.html


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Γιώργος Πάλλας on
Giovanni Funchal wrote:
> Hi,
>
> I've just noticed that the file command returns wrong mime for a file.
> In fact, if a LaTeX file uses the command \bibligraphystyle somewhere
> in the beginning, file will return mime "text/vnd.graphviz" instead of
> "text/x-tex". I took a look at /usr/share/file/magic (on Lenny), and
> it has something like :
>
> 0 regex/100 [\r\n\t\ ]*graph[\r\n\t\ ]*.*\\{ graphviz graph text
> !:mime text/vnd.graphviz
>
> This regular expression matches \biblioGRAPHystyle in the first
> thousand characters or so. A good fix would be :
>
> - 0 regex/100 [\r\n\t\ ]*graph[\r\n\t\ ]*.*\\{ graphviz graph text
> + 0 regex/100 (^|[\r\n\t\ ]+)graph[\r\n\t\ ]*.*\\{ graphviz graph text
>
> Since in the dot file format[1], the keyword "graph" must be preceded
> by a white space or be in the beginning of the file.
>
> Anyone knows where I can report this?
>
> -- Giovanni
>
> [1] http://www.graphviz.org/doc/info/lang.html
>
>
>

I think this belongs to package 'file'...

From: Stephen Powell on
On Wed, 10 Feb 2010 06:02:02 -0500 (EST), Giovanni Funchal wrote:
>
> Hi,
>
> I've just noticed that the file command returns wrong mime for a file.
> In fact, if a LaTeX file uses the command \bibligraphystyle somewhere
> in the beginning, file will return mime "text/vnd.graphviz" instead of
> "text/x-tex". I took a look at /usr/share/file/magic (on Lenny), and
> it has something like :
>
> 0 regex/100 [\r\n\t\ ]*graph[\r\n\t\ ]*.*\\{ graphviz graph text
> !:mime text/vnd.graphviz
>
> This regular expression matches \biblioGRAPHystyle in the first
> thousand characters or so. A good fix would be :
>
> - 0 regex/100 [\r\n\t\ ]*graph[\r\n\t\ ]*.*\\{ graphviz graph text
> + 0 regex/100 (^|[\r\n\t\ ]+)graph[\r\n\t\ ]*.*\\{ graphviz graph text
>
> Since in the dot file format[1], the keyword "graph" must be preceded
> by a white space or be in the beginning of the file.
>
> Anyone knows where I can report this?
>
> [1] http://www.graphviz.org/doc/info/lang.html

According to the packages page on the Debian web site, /usr/share/file/magic
belongs to package libmagic1. I would suggest filing a bug report against
package libmagic1.


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Jon Dowland on
On Wed, Feb 10, 2010 at 01:30:11PM +0200, Γιώργος Πάλλας wrote:
> I think this belongs to package 'file'...

Yup, source package file is the best place. See
<http://www.debian.org/Bugs/Reporting> if you need info on
how to report bugs in Debian.



--
Jon Dowland
From: Andrei Popescu on
On Wed,10.Feb.10, 12:02:02, Giovanni Funchal wrote:
> Hi,
>
> I've just noticed that the file command returns wrong mime for a file.
> In fact, if a LaTeX file uses the command \bibligraphystyle somewhere
> in the beginning, file will return mime "text/vnd.graphviz" instead of
> "text/x-tex". I took a look at /usr/share/file/magic (on Lenny), and
> it has something like :

[snip]

> Anyone knows where I can report this?

You already have the answer, but here are two more ways:

$ dpkg -S /your/buggy/file

or even

$ reportbug /your/buggy/file

(reportbug uses dpkg -S AFAIK).

Regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic