Moxon commented on 2016-08-02 18:09

WoefulDerelict: I am humbled by your efforts to recreate the bug. I checked my makepkg.conf and BUILDDIR is the only variable which has been changed by me.

Even worse and probably embarassing for me: I cannot reproduce the error any more. I can only guess that it was some glitch in my system which went away either by rebooting or by updating the system - zynaddsubfx-git was just successfully compiled and installed on my machine.

Thank you for taking care of this piece of software in arch, it enables me to make music (which probably only I like) with a fine soft synthesizer.

WoefulDerelict commented on 2016-07-21 01:30

Moxon: That is, of course, your prerogative. Unfortunately I have been completely unable to reproduce the reported behaviour on a multitude of systems. The package builds fine in a clean test environment (https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot) as well as on test boxes with nothing more than a pacstrap of base and base-devel: even when building in /tmp on machines with as little as 1GB of RAM. Not even yaourt misbehaves and it also builds in /tmp.

If I parse the output you shared correctly your build isn't even managing to properly retrieve the sources. The fetch data is all off and it appears to be looking for the git repository is a very, very strange place '/var/cache/pacman/pkg/zynaddsubfx-git27501/zynaddsubfx-git/zynaddsubfx-git' This is definitely not the default location for package sources. If makepkg has a BUILDDIR of /tmp/makepkg the primary location it should be working with is '/tmp/makepkg/zynaddsubfx-git' along with the source, which by default is downloaded to the same directory the PKGBUILD resides in. If you have modified other variables in makepkg.conf like SRCDEST they could be responsible for altering the default behaviour and the root of your current issue. If there is not enough space to download the sources it could result in the errors you're experiencing.

If you compare the output you provided with the following output from a healthy build you should notice that the git repo has more data than is being reported/retrieved on your system which would explain why it does not appear to be a valid repository when git attempts to work with it: it's incomplete.

One thing of which I am certain at this point, having conducted thorough build testing on multiple machines, is that the issue is specific to your system, likely the result of deviating from the standard distribution configuration, not this package.

Moxon commented on 2016-07-20 18:43

Hm. I beg to differ. With 4.9GB on /tmp even zynaddsubfx should be able to compile. It is the only package which fails, all others from AUR work. Also the error occurs even before the compilation starts and does not hint towards a out of space error.

WoefulDerelict commented on 2016-07-18 18:41

Moxon: Unfortunately this problem exists not with any package or even in opting to use /tmp/makepkg as your BUILDDIR but between the keyboard and chair. If you had bothered to consult the documentation you would know that the default behaviour on Arch is that /tmp exists on tmpfs which is limited to half of the system memory (https://wiki.archlinux.org/index.php/Tmpfs). The build is failing because your system does not have enough space in tmpfs to house the build. This limitation is one of the key reasons /tmp/makepkg is not used by default and why yaourt attracts the most negative feedback of any AUR helper as it attempts to build in tmpfs by default. You can solve this problem by either building outside of tmpfs or by adjusting the maximum size of your tmpfs by following the procedure on the tmpfs page of the Arch Wiki.

Moxon commented on 2016-07-18 14:12

This might be a problem with not just this package, but:

If you set BUILDDIR in /etc/makepkg.conf to e.g. /tmp/makepkg, the build fails early with this error message: