Package Details: hugo 0.18.1-1

Git Clone URL: (read-only)
Package Base: hugo
Description: Fast and Flexible Static Site Generator in Go — built from source.
Upstream URL:
Licenses: Apache
Conflicts: hugo-bin, hugo-src
Submitter: fusion809
Maintainer: fusion809
Last Packager: fusion809
Votes: 8
Popularity: 2.025120
First Submitted: 2016-11-04 00:38
Last Updated: 2017-01-12 18:23

Dependencies (4)

Required by (0)

Sources (1)

Latest Comments

alan1world commented on 2017-02-05 00:13

Redirects worked for me:
git config --global http. true

imp0 commented on 2017-02-04 22:06

Since the latest git update this package does not build anymore.
The problem is related to and is explained here:

A temporary workaround until fixes things is to allow redirects in your git config for, like this: git config --global http. true

Another improvement to this package would be to use the provided "govendor" rule in the hugo Makefile instead of manually installing it.

fusion809 commented on 2017-01-12 18:24

I pushed DeedleFake's fix.

Unia commented on 2017-01-12 17:46

I can confirm that DeedleFake's workaround works.

DeedleFake commented on 2017-01-11 15:48

I found a workaround. I'm not sure if you want to actually use it or not, but here's a patch for the PKGBUILD with my changes:

fusion809 commented on 2017-01-06 15:28

I followed your GitHub issue and will also follow this thread, so yeah I am paying attention to what happens there.

runical commented on 2017-01-06 15:08

Ah crap, seems I deleted my previous post. Anyway, the discussion has moved from github to Dicsuss (

@fusion809, I think it would be nice if you could drop in as well, as you know most about the PKGBUILD and why you did things in a certain way.

burij commented on 2017-01-06 12:36

Thx for help. I'm on hugo-bin-0.18.1-1 now.

runical commented on 2017-01-06 11:34

Or install hugo-bin for the time being. I'll file a bug report later today if no-one was quicker.

fusion809 commented on 2017-01-06 11:25

Well a temporary work-around (as opposed to a solution) for people with this build error is to install this pre-built binary package of mine

runical commented on 2017-01-06 11:19

Yup, when I build it myself in a clean chroot I get the same error. Seems to be something in the build process of the software itself and a quick search does not result in a bug report. Version 0.18 also fails to build, so I think there is a GO dependency missing or was updated.

fusion809 commented on 2017-01-06 11:15

Hmm... Not sure how to fix this error. I looked to see if you might be missing a go module/library that most of the rest of us hugo users already have but I can't find one that seems relevant to that error. Maybe try building again, might be a temporary issue with your network connection... If anyone has any ideas I'll be happy to hear them.

burij commented on 2017-01-06 08:44

I'm sorry. I posted the complet log on

runical commented on 2017-01-05 12:12

@burij: Mind running the build process with LANG=C in front of it so it produces english errors instead of german ones? My german isn't that good ;-)

burij commented on 2017-01-05 11:57

Can't update:

==> Beginne package()...
install: der Aufruf von stat für 'hugo' ist nicht möglich: Datei oder Verzeichnis nicht gefunden
==> FEHLER: Ein Fehler geschah in package().
Breche ab...
==> FEHLER:Makepkg konnte hugo nicht erstellen.
==> Erstellen von hugo neu starten?[j/N]
==> ------------------------------------
==> ==> FEHLER:Konnte nicht aktualisieren

fusion809 commented on 2016-11-09 12:55

Good question, fixed in my latest commit as I saw this issue I also tried building without that makedepend and it worked fine.

ogarcia commented on 2016-11-09 12:24

Why 'mercurial' as makedepend? You can make hugo without mercurial.

fusion809 commented on 2016-11-04 00:27

What request would I have to make? Merge request? As there's only merge, orphan and deletion requests available.

neitsab commented on 2016-11-03 19:32

Hi fusion809, I just wanted to let you know that I took over the former "hugo" package and requested its move to "hugo-bin" so as to follow package naming guidelines. As a consequence, the "hugo" namespace is yours to take ! Feel free to submit a request to have your package renamed (adjustments to the PKGBUILD and .SRCINFO will be necessary). Cheers!