Your message dated Sun, 14 Sep 2014 10:12:41 +0200
with message-id <[email protected]>
and subject line #726799: not a shared-mime-info [email protected]
has caused the Debian Bug report #726799,
regarding update-mime-database.real deletes files installed by other packages
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
726799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726799
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qgo
Version: 2.0~git-20130914-1
Severity: serious
User: [email protected]
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package deletes one of its
shipped files during upgrades.
debsums reports modification of the following files,
from the attached log (scroll to the bottom...):
0m50.7s ERROR: FAIL: debsums reports modifications inside the chroot:
debsums: missing file /usr/share/mime/text/x-sgf.xml (from qgo
package)
Cheers,
Andreas
qgo_2.0~git-20130914-1.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Hi,
first of all, the behaviour of update-mime-database is correct: it
deletes files in *generated* directories.
Yes, the various application, audio, text, subdirectories under
/usr/share/mime are business of update-mime-database, where it places
the XML mimetypes generated from the XML definitions in
/usr/share/mime/packages. It is exactly in this directory where
applications should install XML definitions of mime types to have them
registered in the XDG mime type system.
Installing stuff directly to e.g. /usr/share/mime/text is like
installing to, say, /var/cache (i.e., you shouldn't).
Furthermore, qgo is installing wrong things, and I will send the
proper explanation and fix to #749582.
This is not a bug in shared-mime-info, hence closing.
--
Pino Toscano
--- End Message ---
