AUR web interface

**This is the bug tracker for the AUR web interface.**

Use this tracker to report bugs or make feature requests regarding the behaviour or implementation of the AUR software.
Please read the Reporting Bug Guidelines before filing a new task.

- Please report bugs related to Arch Linux official packages here:
- Please report bugs for [community] packages here:
- For any packages in the AUR contact the maintainer or leave a comment on the package's detail page.

Source Code:

FS#62625 - AUR atom generation doesn't pass w3c validator

Attached to Project: AUR web interface
Opened by Swift Geek (swiftgeek) - Monday, 13 May 2019, 22:02 GMT
Last edited by Eli Schwartz (eschwartz) - Monday, 13 May 2019, 22:04 GMT
Task Type Bug Report
Category Backend
Status Unconfirmed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 4.7.0
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 1
Private No


Example atom feed for yay package:

W3C Validator:

Namely contains this error that prevents parsing the feed:
line 12, column 137: XML parsing error: <unknown>:12:137: not well-formed (invalid token)
... b1c3b38dc0b5bf07e1b0a62519b845ba497f20&h=yay'/>
This task depends upon

Comment by Eli Schwartz (eschwartz) - Monday, 13 May 2019, 22:12 GMT
This comes from cgit, not aurweb itself. In our configuration, this is producing content such as:

<link rel='alternate' type='text/html' href=''/>

And the href contents have an unescaped & in there, which is probably not very good news... the thing is, the only way to find a commit in the aurweb cgit interface is with the GIT_NAMESPACE branch. Upstream cgit seems to, usually, just print the commit id= there, without referencing branches. I believe this should be raised as a cgit bug.