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#59474 - packer package is called packer-io
Attached to Project:
Community Packages
Opened by Dmytro (alkersan) - Saturday, 28 July 2018, 11:48 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 28 July 2018, 14:54 GMT
Opened by Dmytro (alkersan) - Saturday, 28 July 2018, 11:48 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 28 July 2018, 14:54 GMT
|
DetailsDescription:
Shouldn't the packer-io package be called just packer? The same concern for a single binary inside it /usr/bin/packer-io: should it be just /usr/bin/packer? This is how Hashicorp calls and distributes this package. Additional info: * package version(s) 1.2.5 * config and/or log files etc. Steps to reproduce: |
This task depends upon
Closed by Doug Newgard (Scimmia)
Saturday, 28 July 2018, 14:54 GMT
Reason for closing: Not a bug
Additional comments about closing: This is to avoid conflicts
Saturday, 28 July 2018, 14:54 GMT
Reason for closing: Not a bug
Additional comments about closing: This is to avoid conflicts