Opened 3 years ago
Closed 3 years ago
#64735 closed defect (fixed)
hugo install fails due to change in bash completion generation
Reported by: | jdwoody (Justin Woody) | Owned by: | cardi (calvin ardi) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | hugo |
Description
Per this issue in hugo:
https://github.com/gohugoio/hugo/issues/8862
The command hugo gen autocomplete was removed in favor of hugo completion [shell] in v0.92.2. The release notes for hugo confirm:
https://github.com/gohugoio/hugo/releases
As a result, the macports installation fails due to the old comman. This is a very simple fix in the Portfile:
https://github.com/macports/macports-ports/blob/master/www/hugo/Portfile#L42
Command to reproduce:
sudo port install hugo +bash_completion +extended
Relevant log snippet:
... :debug:build system -W /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_www_hugo/hugo/work/gopath/src/github.com/gohugoio/hugo: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_www_hugo/hugo/work/gopath/src/github.com/gohugoio/hugo/hugo gen autocomplete --completionfile=hugo.sh :info:build Error: unknown flag: --completionfile :info:build Usage: :info:build hugo gen [command] :info:build Available Commands: :info:build chromastyles Generate CSS stylesheet for the Chroma code highlighter :info:build doc Generate Markdown documentation for the Hugo CLI. :info:build man Generate man pages for the Hugo CLI :info:build Flags: ...
Please let me know if you need any further information
Change History (3)
comment:1 Changed 3 years ago by jmroot (Joshua Root)
Owner: | set to cardi |
---|---|
Status: | new → assigned |
comment:2 Changed 3 years ago by cardi (calvin ardi)
comment:3 Changed 3 years ago by cardi (calvin ardi)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
Thanks, Justin.
We're working on a fix for this now.