Bug 9401

Summary: application/pgp-* are missing magic/globs
Product: shared-mime-info Reporter: Adam Schreiber <sadam>
Component: freedesktop.org.xmlAssignee: Jonathan Blandford <jrb>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: high CC: bugzilla, sadam, slomo
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: Adds magic to pgp types
pgp-mimetypes.patch

Description Adam Schreiber 2006-12-20 04:43:27 UTC 
The missing magic for application/pgp-encrypted, application/pgp-keys and
application/pgp-signature is causing conflicts with the mime info file installed
properly with seahorse.  This causes our integration with the file system to
break.  The solution is to copy our magic to freedesktop.org.xml.in.  I will
attach a patch.
Comment 1 Adam Schreiber 2006-12-20 04:44:16 UTC 
Created attachment 8175 [details] [review]
Adds magic to pgp types
Comment 2 Sebastian Dröge (slomo) 2006-12-20 04:50:15 UTC 
There's also application/pgp which is chosen for *.pgp files. This should
probably be removed in favor of application/pgp-encrypted as now both are
responsible for *.pgp.
Comment 3 Sebastian Dröge (slomo) 2006-12-20 08:35:13 UTC 
Created attachment 8179 [details] [review]
pgp-mimetypes.patch

This patch removes application/pgp and marks it as an alias of
application/pgp-encrypted. This makes the mimetype detection finally work on my
machine and seahorse via nautilus is also happy.
Comment 4 Adam Schreiber 2007-01-26 13:13:42 UTC 
Jonathan, Is there anything else that needs to be done for Sebastian's patch to be applied?
Comment 5 Bastien Nocera 2007-02-05 02:57:18 UTC 
2007-02-05  Bastien Nocera  <hadess@hadess.net>

        * freedesktop.org.xml.in: Patch from Adam Schreiber <sadam@clemson.edu>
        and Sebastian Dröge <slomo@ubuntu.com> to clean up PGP/GnuPG file
        types detection (Closes: #9401)

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.