Error in update

[bangorme]

I got the following errors when I updated codeblocks this morning:

  Updating   : codeblocks-13.12.svn.10026-1.el20.x86_64                                                                                                  3/22
Unknown media type in type 'chemical/x-alchemy'
Unknown media type in type 'chemical/x-cache'
Unknown media type in type 'chemical/x-cactvs-ascii'
Unknown media type in type 'chemical/x-cactvs-binary'
Unknown media type in type 'chemical/x-cactvs-table'
Unknown media type in type 'chemical/x-cdx'
Unknown media type in type 'chemical/x-cdxml'
Unknown media type in type 'chemical/x-chem3d'
Unknown media type in type 'chemical/x-cif'
Unknown media type in type 'chemical/x-cml'
Unknown media type in type 'chemical/x-daylight-smiles'
Unknown media type in type 'chemical/x-dmol'
Unknown media type in type 'chemical/x-gamess-input'
Unknown media type in type 'chemical/x-gamess-output'
Unknown media type in type 'chemical/x-gaussian-input'
Unknown media type in type 'chemical/x-gaussian-log'
Unknown media type in type 'chemical/x-genbank'
Unknown media type in type 'chemical/x-gulp'
Unknown media type in type 'chemical/x-hin'
Unknown media type in type 'chemical/x-inchi'
Unknown media type in type 'chemical/x-inchi-xml'
Unknown media type in type 'chemical/x-jcamp-dx'
Unknown media type in type 'chemical/x-macromodel-input'
Unknown media type in type 'chemical/x-mdl-molfile'
Unknown media type in type 'chemical/x-mdl-rdfile'
Unknown media type in type 'chemical/x-mdl-rxnfile'
Unknown media type in type 'chemical/x-mdl-sdfile'
Unknown media type in type 'chemical/x-mdl-tgf'
Unknown media type in type 'chemical/x-mmcif'
Unknown media type in type 'chemical/x-mol2'
Unknown media type in type 'chemical/x-mopac-graph'
Unknown media type in type 'chemical/x-mopac-input'
Unknown media type in type 'chemical/x-mopac-out'
Unknown media type in type 'chemical/x-msi-car'
Unknown media type in type 'chemical/x-msi-hessian'
Unknown media type in type 'chemical/x-msi-mdf'
Unknown media type in type 'chemical/x-msi-msi'
Unknown media type in type 'chemical/x-ncbi-asn1'
Unknown media type in type 'chemical/x-ncbi-asn1-binary'
Unknown media type in type 'chemical/x-ncbi-asn1-xml'
Unknown media type in type 'chemical/x-pdb'
Unknown media type in type 'chemical/x-shelx'
Unknown media type in type 'chemical/x-turbomole-basis'
Unknown media type in type 'chemical/x-turbomole-control'
Unknown media type in type 'chemical/x-turbomole-coord'
Unknown media type in type 'chemical/x-turbomole-grad'
Unknown media type in type 'chemical/x-turbomole-scfmo'
Unknown media type in type 'chemical/x-turbomole-vibrational'
Unknown media type in type 'chemical/x-vmd'
Unknown media type in type 'chemical/x-xyz'

[Jenna]

I guess you tried to update from my repo (you did not mention your OS etc.) on Fedora 20 64bit.
I did it yesterday without any issues.
The only problem is, that the shown (in codeblocks) svn-revision is "0", but that's just a cosmetical bug and will be fixed with the next update (of my repo).

[Jenna]

I guess you tried to update from my repo (you did not mention your OS etc.) on Fedora 20 64bit.
I did it yesterday without any issues.
The only problem is, that the shown (in codeblocks) svn-revision is "0", but that's just a cosmetical bug and will be fixed with the next update (of my repo).

Can you try it again with the latest update to svn r10029 (if you use my repo) ?

[bangorme]

I just did and got the exact same error message.  Sorry I didn't specify, but I am running Fedora 20, 64 bit.

[Jenna]

What happens if you manually run

Code

sudo update-mime-database -V /usr/share/mime

in a console ?
Do you have the "chemical-mime-data" package installed ?
If I install it and run the mentioned command or reinstall codeblocks I get the exact same messages as you.

We can send all output from "update-mime-database" to /dev/null and hide such messages, even if they do not come from our package.
I will not be able to upload any packages until at least monday or tuesday (if all wents good).

[bangorme]

Yes, updating in console using your command I get the same errors.  I'm not sure what I have installed for packages.  I just download the updates from your depository and install them as is.  I'm only posting these for developers of the software, since it doesn't effect the functionality.  Probably such messages should be shielded from users as they cause unnecessary anxiety.

[root@cpe-76-178-212-156 xxxx]# sudo update-mime-database -V /usr/share/mime
Updating MIME database in /usr/share/mime...

Unknown media type in type 'chemical/x-alchemy'
Unknown media type in type 'chemical/x-cache'
Unknown media type in type 'chemical/x-cactvs-ascii'
Unknown media type in type 'chemical/x-cactvs-binary'
Unknown media type in type 'chemical/x-cactvs-table'
Unknown media type in type 'chemical/x-cdx'
Unknown media type in type 'chemical/x-cdxml'
Unknown media type in type 'chemical/x-chem3d'
Unknown media type in type 'chemical/x-cif'
Unknown media type in type 'chemical/x-cml'
Unknown media type in type 'chemical/x-daylight-smiles'
Unknown media type in type 'chemical/x-dmol'
Unknown media type in type 'chemical/x-gamess-input'
Unknown media type in type 'chemical/x-gamess-output'
Unknown media type in type 'chemical/x-gaussian-input'
Unknown media type in type 'chemical/x-gaussian-log'
Unknown media type in type 'chemical/x-genbank'
Unknown media type in type 'chemical/x-gulp'
Unknown media type in type 'chemical/x-hin'
Unknown media type in type 'chemical/x-inchi'
Unknown media type in type 'chemical/x-inchi-xml'
Unknown media type in type 'chemical/x-jcamp-dx'
Unknown media type in type 'chemical/x-macromodel-input'
Unknown media type in type 'chemical/x-mdl-molfile'
Unknown media type in type 'chemical/x-mdl-rdfile'
Unknown media type in type 'chemical/x-mdl-rxnfile'
Unknown media type in type 'chemical/x-mdl-sdfile'
Unknown media type in type 'chemical/x-mdl-tgf'
Unknown media type in type 'chemical/x-mmcif'
Unknown media type in type 'chemical/x-mol2'
Unknown media type in type 'chemical/x-mopac-graph'
Unknown media type in type 'chemical/x-mopac-input'
Unknown media type in type 'chemical/x-mopac-out'
Unknown media type in type 'chemical/x-msi-car'
Unknown media type in type 'chemical/x-msi-hessian'
Unknown media type in type 'chemical/x-msi-mdf'
Unknown media type in type 'chemical/x-msi-msi'
Unknown media type in type 'chemical/x-ncbi-asn1'
Unknown media type in type 'chemical/x-ncbi-asn1-binary'
Unknown media type in type 'chemical/x-ncbi-asn1-xml'
Unknown media type in type 'chemical/x-pdb'
Unknown media type in type 'chemical/x-shelx'
Unknown media type in type 'chemical/x-turbomole-basis'
Unknown media type in type 'chemical/x-turbomole-control'
Unknown media type in type 'chemical/x-turbomole-coord'
Unknown media type in type 'chemical/x-turbomole-grad'
Unknown media type in type 'chemical/x-turbomole-scfmo'
Unknown media type in type 'chemical/x-turbomole-vibrational'
Unknown media type in type 'chemical/x-vmd'
Unknown media type in type 'chemical/x-xyz'
Wrote 1071 strings at 2c - 5e88

Wrote aliases at 5e88 - 664c

Wrote parents at 664c - 7d24

Wrote literal globs at 7d24 - 7e0c

Wrote suffix globs at 7e0c - 11f0c

Wrote full globs at 11f0c - 11f4c

Wrote magic at 11f4c - 1ec84

Wrote namespace list at 1ec84 - 1ee20

Wrote icons list at 1ee20 - 1ee24

Wrote generic icons list at 1ee24 - 1f858

Wrote types list at 1f858 - 20458

[root@cpe-76-178-212-156 xxxx]#

[Jenna]

I currently compile a new revision with a "fix" that hides all output from "update-mime-database" and always returns "0", so the scripts should run without that messages and without a possible break of the update/install process.

Should be uploaded to my server this evening.

Please give feedback if the error is gone (and of course if it stays).

By the way:
please use code tags, if you post long output-messages or code (the "#"-icon in the forum's editor).

[Jenna]

You might see the error-messages the next update  also, but (hopefully) the last time (at least with C::B).
I guess the old preuninstall-script runs before installing the update.

[bangorme]

This problem appears to have been resolved in your latest update.

Thanks.