AUR web interface

Tasklist

FS#37496 - Better error message for refusing split packages

Attached to Project: AUR web interface
Opened by Justin Dray (justin8) - Saturday, 26 October 2013, 04:45 GMT
Last edited by Lukas Fleischer (lfleischer) - Monday, 13 January 2014, 19:07 GMT
Task Type Feature Request
Category PKGBUILD Parser
Status Closed
Assigned To canyonknight (canyonknight)
Lukas Fleischer (lfleischer)
Architecture All
Severity Low
Priority Normal
Reported Version 2.2.1
Due in Version 2.3.1
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

When uploading a split package the error given is "Invalid name: only lowercase letters are allowed" The reason for refusal was that it is a split package.

Perhaps upon parsing that it is a split package, return a more relevant error.
This task depends upon

Closed by  Lukas Fleischer (lfleischer)
Monday, 13 January 2014, 19:07 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 2.3.1.
Comment by canyonknight (canyonknight) - Sunday, 27 October 2013, 15:10 GMT
I believe that the error message was made clearer with a prior commit [1]. I'll have to look into the cases where that less than clear error message is still appearing.

[1] https://projects.archlinux.org/aur.git/commit/?id=789245077d1ded7b2aaf4631bbca2a9267690739
Comment by x33a (x33a) - Sunday, 27 October 2013, 15:51 GMT
Here's the problematic PKGBUILD in question (not mine), if it helps you narrow down the problem:

https://gist.github.com/anonymous/7184087
Comment by Lukas Fleischer (lfleischer) - Saturday, 11 January 2014, 12:39 GMT
Patch submitted to the mailing list [1].

[1] https://mailman.archlinux.org/pipermail/aur-dev/2014-January/002613.html
Comment by Marty (vadmium) - Sunday, 12 January 2014, 03:07 GMT
I think the error message “Invalid name: only lowercase letters are allowed” could be improved as well:

Refer to the $pkgname variable: “name” on its own was too vague.

The AUR clearly also allows digits, and some other punctuation, which are not lowercase letters. So maybe explicitly say which characters are allowed.

Maybe also mention if Bash substitutions (or other complicated syntax) are not allowed. This seems to be the reason I got the message today, though I think it worked in the past. BTW I worked around this with “.AURINFO”.

Loading...