Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#25760 - [libffi] uses obsolete 'force' option
Attached to Project:
Arch Linux
Opened by Garry Roseman (sitquietly) - Friday, 26 August 2011, 00:58 GMT
Last edited by Andrea Scarpino (BaSh) - Sunday, 28 August 2011, 23:10 GMT
Opened by Garry Roseman (sitquietly) - Friday, 26 August 2011, 00:58 GMT
Last edited by Andrea Scarpino (BaSh) - Sunday, 28 August 2011, 23:10 GMT
|
DetailsDescription: makepkg fails because PKGBUILD includes obsolete 'force' option
It appears that the option can just be removed without concern for epoch (?) in this case. I report such a minor problem because such errors in PKGBUILDs (also checksum errors are common) make me question if abs has the actual PKGBUILD that the packager used. How did the arch binary in the repositories get built if the distributed PKGBUILD has an obsolete option and doesn't work?? Additional info: * package version(s) libffi-3.0.10-1 * config and/or log files etc. Steps to reproduce: [BUILD]$ cp -a /var/abs/extra/libffi/ . [BUILD]$ cd libffi/ [libffi]$ makepkg --install --noconfirm --log; sync ==> ERROR: options array contains unknown option 'force' |
This task depends upon
http://projects.archlinux.org/svntogit/packages.git/tree/libffi/trunk/PKGBUILD