reassign 726799 shared-mime-info
retitle 726799 update-mime-database.real deletes files installed by other 
packages
severity 726799 grave
seen 726799 shared-mime-info/1.0-1+b1
seen 726799 shared-mime-info/1.3-1
thanks

I got hit by this issue again myself, so well...

Tried a couple of downgrade-to-testing and back-to-sid, with no
disappearance appearing.  In the meantime, looks like current piuparts
runs are OK.  So what ?

On Fri, Dec 13, 2013 at 11:11:32PM +0100, Yann Dirson wrote:
> On Fri, Dec 13, 2013 at 01:58:31AM +0100, Andreas Beckmann wrote:
> > On 2013-12-03 22:30, Yann Dirson wrote:
> > > I'm wondering if that could not be caused by a bug in the mime
> > > trigger, that would have been fixed already.
> > 
> > That would be easier to test - what package is it?
> 
> I was thinking about the mime-support trigger, but that package has
> not been changed for 6 months, so the problem must be somewhere else.

I notice in the log sent in OP that *shared-mime-info* got upgraded at
the same time, when piuparts runs dist-upgrade.

Good news, there is a new version in sid, let's install it.  Bum.

So:

root@home:~# aptitude reinstall qgo
...
root@home:~# ls /usr/share/mime/text/x-sgf.xml
/usr/share/mime/text/x-sgf.xml
root@home:~# update-mime-database.real /usr/share/mime
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Unknown media type in type 'uri/mms'
Unknown media type in type 'uri/mmst'
Unknown media type in type 'uri/mmsu'
Unknown media type in type 'uri/pnm'
Unknown media type in type 'uri/rtspt'
Unknown media type in type 'uri/rtspu'
root@home:~# ls /usr/share/mime/text/x-sgf.xml
ls: cannot access /usr/share/mime/text/x-sgf.xml: No such file or directory

Culprit found - but piuparts seems to be based on very wrong assumptions...


Since the OP involves a version of this package that's nearly that of
wheezy, we may want to consider some stable update as well.


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

Reply via email to