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#10016 - arson URLPath returned by RPC calls is incorrect

Attached to Project: AUR web interface
Opened by Colin Shea (FriarFoaly) - Sunday, 30 March 2008, 03:21 GMT
Last edited by Callan Barrett (wizzomafizzo) - Monday, 09 June 2008, 20:29 GMT
Task Type Bug Report
Category Backend
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 1.5.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No


When calling AUR's RPC methods and looking up the URL to the .tar.gz for a package, it normally returns "/packages/$name/$name.tar.gz", but when I lookup arson, it returns "/packages/arson/arson-0.6.1-2.tar.gz" instead, which doesn't exist. "/packages/arson/arson.tar.gz" does though. It had been working before. This is the only package that I see that does return the version info in URLPath.
This task depends upon

Closed by  Callan Barrett (wizzomafizzo)
Monday, 09 June 2008, 20:29 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in testing, don't forget to resubmit your packages when it goes live.
Comment by Colin Shea (FriarFoaly) - Monday, 31 March 2008, 01:36 GMT
With louipc's advice, I uploaded arson v0.6.3 as "arson.tar.gz" instead of "arson-0.6.3-1.src.tar.gz" and the URLPath from calling RPC works now. You devs still need to fix AUR so that it really shouldn't matter what name I upload it under :)
Comment by Loui Chang (louipc) - Tuesday, 01 April 2008, 04:42 GMT
Allowing to upload as pkgname-version.src.tar.gz also supports makepkg --source so this definitely should be looked at.
Comment by Callan Barrett (wizzomafizzo) - Thursday, 05 June 2008, 15:50 GMT
Has this been fixed? I'm guessing it's just a problem with rpc.php since all tarballs get repackaged on upload.
Comment by Loui Chang (louipc) - Thursday, 05 June 2008, 18:35 GMT
No it's a problem with the upload.
RPC doesn't upload or write to the DB in any way. ;)