Mime problem in chemical-mime-data

Bug #217335 reported by Matthias Klumpp
2
Affects Status Importance Assigned to Milestone
chemical-mime-data (Debian)
Confirmed
Unknown
chemical-mime-data (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: chemical-mime-data

A lot of package postinst scripts display the following error
messages:

Unknown media type in type 'chemical/x-alchemy'
Unknown media type in type 'chemical/x-cache'
[many more...]

because they execute this command:

  update-mime-database /usr/share/mime

I believe that chemical-mime-data is responsible for this.

This is annoying because it pollutes my terminal when I upgrade
packages.

Revision history for this message
Daniel Leidert (dleidert-deactivatedaccount) wrote :

Read my comment in the Debian BTS.

If you don't know or understand what c-m-d does/is, then please remove it instead to send a pretty senseless bug report!

Changed in chemical-mime-data:
status: Unknown → Confirmed
Revision history for this message
Matthias Mailänder (mailaender) wrote :

If a removal script of a package runs "update-mime-data /usr/share/mime" and you have chemical-mime-data installed, you can't completely remove the package, see Bug #290621

Revision history for this message
Daniel Leidert (dleidert-deactivatedaccount) wrote :

This is wrong! These are warnings and do not lead to a failing update-mime-database.

Revision history for this message
Daniel Leidert (dleidert-deactivatedaccount) wrote :

The problem in Bug #290621 is, that output by update-mime-database is given to debconf and this leads to an "unknown command" error by debconf. It is currently discussed.

Revision history for this message
A. Denton (aquina) wrote :

I don't want to file a new bug report so I'm gonna post here what I have.

Executing "/usr/lib/kde4/bin/kbuildsycoca4 --noincremental" puts out some warnings...

kbuildsycoca4 running...
kbuildsycoca4(16860) KBuildMimeTypeFactory::createEntry: Missing <comment> field in "/usr/share/mime/text/x-boo.xml"
kbuildsycoca4(16860) KBuildMimeTypeFactory::createEntry: Missing <comment> field in "/usr/share/mime/text/x-ksysv-log.xml"
kbuildsycoca4(16860) KBuildMimeTypeFactory::createEntry: Missing <comment> field in "/usr/share/mime/text/x-nemerle.xml"
kbuildsycoca4(16860) KBuildMimeTypeFactory::createEntry: Missing <comment> field in "/usr/share/mime/text/x-msil.xml"
kbuildsycoca4(16860) KBuildMimeTypeFactory::createEntry: Missing <comment> field in "/usr/share/mime/text/x-js.xml"
kbuildsycoca4(16860) KBuildMimeTypeFactory::createEntry: Missing <comment> field in "/usr/share/mime/text/x-vb.xml"

etc.

I think someone should have a look at that.

Revision history for this message
Egon Willighagen (egonw) wrote : Re: [Bug 217335] Re: Mime problem in chemical-mime-data

Dear Aquina,

On Thu, Aug 27, 2009 at 5:50 AM, Aquina<email address hidden> wrote:
> I don't want to file a new bug report so I'm gonna post here what I
> have.
>
> Executing "/usr/lib/kde4/bin/kbuildsycoca4 --noincremental" puts out
> some warnings...
>
> kbuildsycoca4 running...
> kbuildsycoca4(16860) KBuildMimeTypeFactory::createEntry: Missing <comment> field in  "/usr/share/mime/text/x-boo.xml"
> kbuildsycoca4(16860) KBuildMimeTypeFactory::createEntry: Missing <comment> field in  "/usr/share/mime/text/x-ksysv-log.xml"
> kbuildsycoca4(16860) KBuildMimeTypeFactory::createEntry: Missing <comment> field in  "/usr/share/mime/text/x-nemerle.xml"
> kbuildsycoca4(16860) KBuildMimeTypeFactory::createEntry: Missing <comment> field in  "/usr/share/mime/text/x-msil.xml"
> kbuildsycoca4(16860) KBuildMimeTypeFactory::createEntry: Missing <comment> field in  "/usr/share/mime/text/x-js.xml"
> kbuildsycoca4(16860) KBuildMimeTypeFactory::createEntry: Missing <comment> field in  "/usr/share/mime/text/x-vb.xml"

These are not chemical mime types, which start with chemical/.

Please do file a new bug report, as it does not apply to the
chemical-mime package.

Kind regards,

Egon

--
Post-doc @ Uppsala University
http://chem-bla-ics.blogspot.com/

Revision history for this message
A. Denton (aquina) wrote :

Yes, I know. I realize! Nevertheless it's realted and I won't open a new bug report just for some warnings. The problem lies in "/usr/share/mime", I posted it in here and hope someone will handle that (autor, motu, etc.).

- Aquina

Revision history for this message
Matthias Klumpp (ximion) wrote :

Daniel Leidert wrote on 2008-04-16:
>> If you don't know or understand what c-m-d does/is, then please remove it instead to send a pretty senseless bug report! <<
Ehm... I have not commited the bug for Debian, and I know what chemical-mime-data does. I will try to commit a patch for this soon.

Revision history for this message
Matthias Klumpp (ximion) wrote :

This can only be fixed if chemical/ registered with IANA... So the bug report is invalid, sorry I've not looked at the Debian bug. (I better had...)

Changed in chemical-mime-data (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.