AUR web interface

Tasklist

FS#15497 - Error: Missing build function in PKGBUILD.

Attached to Project: AUR web interface
Opened by jon (emphire) - Monday, 13 July 2009, 10:32 GMT
Last edited by Loui Chang (louipc) - Monday, 20 September 2010, 01:43 GMT
Task Type Bug Report
Category PKGBUILD Parser
Status Closed
Assigned To Loui Chang (louipc)
Architecture All
Severity Medium
Priority Normal
Reported Version 1.5.6.2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

I get the following error when trying to submit the attached PKGBUILD.

Submit
Missing build function in PKGBUILD.
This task depends upon

Closed by  Loui Chang (louipc)
Monday, 20 September 2010, 01:43 GMT
Reason for closing:  Fixed
Additional comments about closing:  1.7.0
Comment by Roman Kyrylych (Romashka) - Wednesday, 15 July 2009, 12:39 GMT
I guess this may be due to ${pkgname#lib32-}
Try to change it and see if it works.
Comment by jon (emphire) - Thursday, 23 July 2009, 01:23 GMT
Thanks. That got it working. Will variable mangling like that be supported again in the future?
Comment by Roman Kyrylych (Romashka) - Thursday, 23 July 2009, 12:45 GMT
not sure
Comment by Roman Kyrylych (Romashka) - Thursday, 23 July 2009, 12:46 GMT
@ Loui : doesn't AUR use bash for parsing PKGBUILDs now?
Comment by Loui Chang (louipc) - Thursday, 23 July 2009, 14:48 GMT
Nope it was determined that using bash would introduce a security hole.
PKGBUILDs are parsed by a PHP script.
Comment by Roman Kyrylych (Romashka) - Thursday, 23 July 2009, 15:08 GMT
Hm, I thought this was secure: http://projects.archlinux.org/?p=namcap.git;a=blob;f=parsepkgbuild since namcap uses it
but I've certainly missed recent AUR development during >year of inactivity.
Comment by Loui Chang (louipc) - Thursday, 23 July 2009, 15:31 GMT
Callan and Simo put together some tests and it is not secure.
Namcap is therefore not secure and should not be run on untrusted PKGBUILDs
Comment by Loui Chang (louipc) - Thursday, 23 July 2009, 15:34 GMT
You can try it out yourself. Put a 'malicious' test command in a PKGBUILD and run namcap on it.
The only way that you can ensure some kind of security is if you run the PKGBUILDs as a special
user that has no privileges to anything.
Comment by Xiong Chiamiov (Xiong_Chiamiov) - Friday, 06 November 2009, 00:23 GMT
Ah, just found this one on my own, and was going to file a bugreport when I saw it in here already. For me, it was a # in one of the source urls.
Comment by Laszlo Papp (djszapi) - Tuesday, 15 December 2009, 05:58 GMT
For this problem see this thread:  FS#17482 
Comment by Lukas Fleischer (lfleischer) - Thursday, 24 June 2010, 04:52 GMT
This will be due in version 1.7.0. There's a patch in the GIT repo that removes the build() function check [1].

[1] http://projects.archlinux.org/aur.git/commit/?id=f08fbbe80eba009c6f42411456479e328c92175b
Comment by Loui Chang (louipc) - Sunday, 04 July 2010, 07:15 GMT
Do not consider this fixed until the fixed is -released-. Thanks.
Comment by Aldrik (N30N) - Thursday, 26 August 2010, 10:03 GMT
I had this message for a valid PKGBUILD that only had a package function.

Loading...