package shared-mime-info reopen 277991 quit >Everything seems fine with the version 0.16
>[EMAIL PROTECTED]:~$ gnomevfs-ls /var/cache/fonts/tfm/jknappen/tc/ >. (Directory, x-directory/normal) size 112 mode >1777 >.. (Directory, x-directory/normal) size 96 mode 1777 >tcrm1000.tfm (Regular, application/x-font-tex-tfm) size >1436 mode 0644 >tcrm1200.tfm (Regular, application/x-font-tex-tfm) size >1444 mode 0644 > >Please re-open this bug if you're still seeing this problem Thank you for testing, though the issue is not fixed. The problem was that a tar.gz could be detected as a tex font not the opposite. Mea culpa for the fast and too short bug report. I did not ship the tar.gz (way too big) though i paste the relevant part of the file in my report When the site works (dynamic ip :( you can reach my copy on http://prahal.darktech.org/debianbugs/GTK2-AluminumAlloy-Volcanic.tar.gz >From my first report: the start of the tar.gz 0: 037 213 010 000 021 117 005 100 000 003 354 134 011 074 124 373 AluminumAlloy-Volcanic/[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@^@ in ascii to compare i put an extract from a random tex font: /usr/share/texmf/fonts/tfm/public/misc/manfnt.tfm 0: 001 023 000 022 000 000 000 177 000 065 000 020 000 005 000 011 [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@^ then the rationale i was able to make from the "file" too "database" (file myfile.tar.gz was detected as tar.gz when nautilus via shared mime info data - obviously using the "magic" detection not the extension - detected it as a tex font). I also focused on the tex font pattern. /usr/share/misc/file/magic line 9730 # There is no way to detect TeX Font Metric (*.tfm) files without # breaking them apart and reading the data. The following patterns # match most *.tfm files generated by METAFONT or afm2tfm. 2 string \000\021 TeX font metric data >33 string >\0 (%s) 2 string \000\022 TeX font metric data >33 string >\0 (%s) /usr/share/mime/packages/freedesktop.org.xml line 3138 <magic priority="50"> <match value="\000\021" type="string" offset="2"/> <match value="\000\022" type="string" offset="2"/> </magic> tar.gz 0: 037 213 010 000 021 ^^^^^^^ tex font: 0: 001 023 000 022 ^^^^^^^ so i guessed that shared-mime-info count from -1 :( the issue could have remained unnoticed by most as if the offset is wrong for all pattern shared mime info will fail back to extension matching. The issue still exists with 0.16-3. I really hope i am wrong as changing the offset now that the freeze happened would mean any of the thousands of patterns may have unknown bugs. Better ship the broken tested version for sarge ... Regards Alban -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
