FS#36378 - [devtools] commitpkg get wrong data if you have a PKGBUILD at ~
Attached to Project:
Arch Linux
Opened by Angel Velasquez (angvp) - Friday, 02 August 2013, 06:29 GMT
Last edited by Pierre Schmitz (Pierre) - Saturday, 02 November 2013, 22:11 GMT
Opened by Angel Velasquez (angvp) - Friday, 02 August 2013, 06:29 GMT
Last edited by Pierre Schmitz (Pierre) - Saturday, 02 November 2013, 22:11 GMT
|
Details
Description:
I've downloaded a PKGBUILD and kept at ~ .. copied to a dir and did the build, then later i forgot to erase that file from ~. What happened on my next build of another package I did the steps svn update bla bla.. and when I've tried to commit I got a file Error: svn file not found. The PKGBUILD that I had in ~ was subversion PKGBUILD and then the check at 215 was called and failed the process. Checking the line 195 of commitpkg is: . PKGBUILD If my bash noob skills are correct this can be fixed doing: ."`pwd`/PKGBUILD" Of course this shouldn't happen to all users, just devs or tus who are a mess like me and have PKGBUILD files everywhere #facepalm :). Steps to reproduce: 1.- Copy a PKGBUILD of X to your ~. note: must have several items at sources array 2.- Go and build a package Y and try to commit to the repos and then have fun seeing Error: foo not found |
This task depends upon
Is the correct thing to do. Source will honor the user PATH if it its a bare file name.