You are not logged in.
I'm experiencing strange behavior with a PKGBUILD I've written:
https://aur.archlinux.org/packages/pipelinit-bin/
If I run the "./src/binnary-name-etc" I got the binary working as expected (it's a deno generated bin), but if I "install -Dm755 binary-name-etc "${pkgdir}/usr/bin/binary-name-etc"" I got a generic deno when I try to run it instead of the binary I have packaged.
No errors, hashes are right.
Never saw this before with other packages.
Someone that played with deno generated binaries in the past already saw something like this?
Here's more detailed information:
https://asciinema.org/a/f0QGg34NLGtJNCzIdbMj0yXhZ
Last edited by ayr-ton (2021-12-23 19:49:00)
Fork it all! Fork it all!
Offline
I have found the solution!
What was happening:
makepkg was stripping the binary so the destination binary was different from the source one.
The solution was adding the following to the PKGBUILD:
options = !strip
You can see the full diff here:
https://github.com/ayr-ton/PKGBUILDs/co … d3a4bb15da
The package is updated in AUR with the fix.
Fork it all! Fork it all!
Offline