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#11909 - makepkg using bsdtar instead of jar
Attached to Project:
Arch Linux
Opened by Erwin Van de Velde (evdvelde) - Tuesday, 28 October 2008, 09:07 GMT
Last edited by Allan McRae (Allan) - Tuesday, 28 October 2008, 10:10 GMT
Opened by Erwin Van de Velde (evdvelde) - Tuesday, 28 October 2008, 09:07 GMT
Last edited by Allan McRae (Allan) - Tuesday, 28 October 2008, 10:10 GMT
|
DetailsDescription:
When building cgoban3 form AUR, I get following error: ==> Extracting Sources... -> bsdtar -x -f cgoban.jar Additional info: * package version(s) pacman 3.2.1-1 Steps to reproduce: e.g. Build cgoban3 from AUR |
This task depends upon
jar can - of course - extract .jar files correctly
1) the cgoban3 package is wrong as it should tell makepkg that the jar file does not need extracted
2) In cases where bsdtar fails two things should happen
- a bug report to the bsdtar developers
- use the noextract option in your PKGBUILD followed by manual extraction using jar (or unzip).
Using jar for .jar files in makepkg would add a dependency on a JDK package which will never happen.