Community Packages

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!
Tasklist

FS#64769 - [go-bindata-assetfs] Package not running

Attached to Project: Community Packages
Opened by Artificial Intelligence Shielding (aishield) - Sunday, 08 December 2019, 04:02 GMT
Last edited by Christian Rebischke (Shibumi) - Saturday, 11 January 2020, 13:11 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Christian Rebischke (Shibumi)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

This package seems to be broken for me.

When I try to execute go-bindata-assetfs I get the following output:

/usr/bin/go-bindata-assetfs: line 1: syntax error near unexpected token `newline'
/usr/bin/go-bindata-assetfs: line 1: `!<arch>'

If I install the package from git using go get it works fine.

Running file on the installed binary outputs

/usr/bin/go-bindata-assetfs: current ar archive
This task depends upon

Closed by  Christian Rebischke (Shibumi)
Saturday, 11 January 2020, 13:11 GMT
Reason for closing:  Fixed
Additional comments about closing:  go-bindata-assetfs 1.0.0.-2
Comment by Martin Dimitrov (Martian) - Thursday, 02 January 2020, 12:00 GMT
I can confirm this. It's the same for me :

go-bindata-assetfs -prefix ui/dist ui/dist
/usr/bin/go-bindata-assetfs: line 1: syntax error near unexpected token `newline'
/usr/bin/go-bindata-assetfs: line 1: `!<arch>'
Comment by Christian Rebischke (Shibumi) - Saturday, 11 January 2020, 12:17 GMT
Hi,
sorry for the delay.
Can you provide a small example code I can test with?

I guess this is also the root for the problems with the current vault release. Very interesting.
Comment by Christian Rebischke (Shibumi) - Saturday, 11 January 2020, 13:11 GMT
Hi thanks a lot for reporting this, this might solve other bugs too.

Should be fixed with 1.0.0-2.

Loading...