Arch Linux

symen

Member

Registered: 2014-10-13

Posts: 10

[SOLVED] VCS pkg doesn't build because of upstream bug: what to do?

I maintain a git package (gnome-mpv-git) that doesn't build anymore.
I think this is because of an upstream bug since the build fails at the ./configure step with a syntax error:

./configure: line 5982: syntax error near unexpected token `-O0'
./configure: line 5982: `	AX_APPEND_COMPILE_FLAGS(-O0 -g -fsanitize=address)'

I suppose it is OK to let the package as is. In the end this is the kind of problems one has to expect when using the absolute last revision of a package.
However if I know a working revision that isn't the most recent, but still more up to date than the current $pkgver, is it a good practice to temporarily fix it in the PKGBUILD (i.e. adding #commit=xxxx in the source URL) ? It messes with the expectation that the package will give you the last revision, but does it matter if the last revision doesn't even build ?

Last edited by symen (2015-08-28 07:57:37)

Xyne

Forum Fellow

Registered: 2008-08-03

Posts: 6,965

Website

Re: [SOLVED] VCS pkg doesn't build because of upstream bug: what to do?

Add commented lines to the PKGBUILD to enable users to easily build the last working revision but leave the PKGBUILD as-is to (attempt to) build the latest version.

Send an email to upstream to let them know that they goofed the last commit.

---

My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone

symen

Member

Registered: 2014-10-13

Posts: 10

Re: [SOLVED] VCS pkg doesn't build because of upstream bug: what to do?

That makes sense, I'll do that then.
Thanks !