Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#15865 - {bugtracker} attached files should have a MIME type attached/sent

Attached to Project: Arch Linux
Opened by majiq (majiq) - Saturday, 08 August 2009, 23:47 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 15 March 2017, 14:17 GMT
Task Type Feature Request
Category Web Sites
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


Upon uploading a patch for an xml file, it seemed upon viewing it that the uploaded file had no content besides the header. Eventually the fact that the xml tags became interpreted was evident.

I don't know how difficult it is, but simply sending a MIME of text/plain before the file should make all xml items display properly. As long as only text is uploaded to the bugtracker, which I know it's not (screenshots). Possibly an extension sensitive function which defaults to text.

I think this is fairly important because some people just copy the patch info into a file or click on it from the bugtracker to read what is being changed, and then miss the items interpreted by the browser. In a large patch that affects multiple files, some people might not notice the fact that some xml information is missing. Lastly, it will fix future problems like on the task listed below, where the same file is uploaded multiple times.

Steps to reproduce:
Visit , and look at the supplied patch in the web browser. Then look at the source of the page and note the difference.
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 15 March 2017, 14:17 GMT
Reason for closing:  Deferred
Additional comments about closing:  Attachments are set to download by default now, so this is not an issue anymore.
Comment by Paul Mattal (paul) - Sunday, 06 December 2009, 20:55 GMT
What can we do about this?

It sounds like we'd have to hack flyspray for this, right? Should we try that, or file a similar request upstream?

Or is it something we can fix through server configuration or some other way?
Comment by majiq (majiq) - Monday, 07 December 2009, 19:34 GMT[]=attachments

It seems like a configuration option.
Comment by Paul Mattal (paul) - Tuesday, 05 January 2010, 05:49 GMT
Roman, do you have access to the flyspray config to do this, or do we need someone with root access? I don't think I have access.
Comment by Jakob Matthes (jakobm) - Sunday, 21 August 2011, 01:21 GMT
Is there any status update on this? Seems like a trivial fix
if server access/administration isn't too troublesome.
Comment by Greg (dolby) - Monday, 15 October 2012, 04:41 GMT
Is this still a problem? Its assigned to the wrong people.
Comment by majiq (majiq) - Monday, 15 October 2012, 06:44 GMT
Yes. If you visit task 15633 as noted in the description and look at the patch, you notice many -'s and +'s. Looking at the source, you can see they are part of a diff of an xml file so the tags are consequently interpreted.

This could be incorrectly assigned, but things change over three years. I assume it still could be a simple configuration option?