[NOT SOLVED] packer keeps running out of room while building

medicineman25 · 2017-09-22 21:19:18

Hey y'all

I'm trying to install unity-editor and it's huge. I was warned that the build was incredibly large, from the Unity3D ArchWiki:

"Warning: The Unity package is huge. For a successful installation you'll need about 8GiB of free space for the package building, and another 3.5GiB for it to install."

I have rebuilt this system to increase my root partition to 46GB (I won't even go into why that was necessary, since there is no reasonable way to move partitions with parted. It makes me want to vomit out my eye-sockets and I have nothing nice to say about that)

I've edited /etc/makepkg.conf

BUILDDIR=/home/access/makepkg

But it still failed...

output from # df -h

Filesystem      Size  Used Avail Use% Mounted on
dev             3.9G     0  3.9G   0% /dev
run             3.9G  708K  3.9G   1% /run
/dev/sda2        46G  2.1G   42G   5% /
tmpfs           3.9G     0  3.9G   0% /dev/shm
tmpfs           3.9G     0  3.9G   0% /sys/fs/cgroup
tmpfs           3.9G  3.9G     0 100% /tmp
/dev/sda1       181M   45M  123M  27% /boot
/dev/sda3        19G   82M   18G   1% /var
/dev/sda4       394G  7.5G  366G   3% /home
tmpfs           799M     0  799M   0% /run/user/1000

output from # du -h / --max-depth=1

4.0K	/opt
16K	/lost+found
25M	/tmp
6.7M	/etc
4.0K	/mnt
0	/sys
708K	/run
360M	/var
12K	/srv
44M	/boot
24K	/root
7.5G	/home
du: cannot access '/proc/10855/task/10855/fd/4': No such file or directory
du: cannot access '/proc/10855/task/10855/fdinfo/4': No such file or directory
du: cannot access '/proc/10855/fd/3': No such file or directory
du: cannot access '/proc/10855/fdinfo/3': No such file or directory
0	/proc
2.1G	/usr
0	/dev
9.9G	/

Clearly /tmp is still being filled up, however it isn't mounted as a separate partition so I have no idea how to increase it's size.

So I edited /etc/pacman.conf

CacheDir    = /var/cache/pacman/pkg/

And I am yet to attempt another build. It takes an hour to download the ball so I don't really want to waste my time unless I at least have half an idea as to what is going on here.

Is there anything else I'm missing here? I've tried building this package numerous times (before and after a complete system rebuild) and I've run out of ideas.

Thanks in advance
Medicineman25

Last edited by medicineman25 (2017-09-22 23:50:03)

Trilby · 2017-09-22 21:28:33

I don't use packer, but the man page has this:

Packages are built in the TMPDIR path. If the TMPDIR variable is not set then the default path is /tmp

So try setting TMPDIR, or better yet just take aur helpers out of the equation and use makepkg directly.

Also, there is absolutely no reason you should be redownloading the source tarball every attempt, just don't delete the tarball inbetween attempts - makepkg will not try to download it again.

Slithery · 2017-09-22 21:33:19

Does packer respect the makepkg.conf BUILDDIR variable? Looking at the script I'm not sure if it does.

If it's building in /tmp then that's why you're running out of room as /tmp is a tmpfs limited to half the size of your RAM.
https://wiki.archlinux.org/index.php/Tmpfs

Try building using makepkg and see if the problem persists.

Also why are you re-downloading the source every time if it takes so long? Just download it once and copy it into your build folder before building.

medicineman25 · 2017-09-22 21:35:46

where did you find that in the manual? I haven't been able to find any documentation on packer usage and man packer just gives the standard options.

Do I just set that in pacman.conf?

I'll keep all that in mind, thanks.

EDIT: You guys are right. Don't even bother answering the above question. I am beyond frustrated with the AUR ecosystem. Using makepkg directly from here on out.

Last edited by medicineman25 (2017-09-22 21:40:27)

Trilby · 2017-09-22 22:05:07

Packer is in no way integral to the "AUR ecosystem". The official method of building AUR packages has always been and remains makepkg.

Packer is one of countlessly many AUR helpers. It may be one of the decent ones, but it is still just an add-on convenience tool.

For future reference TMPDIR is just an environment variable. You can set it anywhere that it would be inherited. For one-off use, you can do:

TMPDIR=/home/myuser/somepath packer ...

medicineman25 · 2017-09-22 23:30:23

Re-opened.

Turns out it's able to be set in /usr/bin/packer

# set tmpfile stuff, clean tmpdir
tmpdir="${TMPDIR:-/home/access/packer}/packertmp-$UID"

But the build still goes to /tmp/packer. Which then promptly runs out of space.

I tried to download the pkgbuild from the AUR and run makepkg, but it exits with read errors and

unable to source /home/access/packer/PKGBUILD

There are no tarballs for this... seems to download a script.

What am I supposed to do now?

EDIT: nevermind... I got lazy but packer has been marked out of date anyway so back to scraping my eyes out.

Last edited by medicineman25 (2017-09-22 23:50:58)

drcouzelis · 2017-09-23 02:42:52

What...? Your post is very confusing!

Here is the AUR tarball for "unity-editor", as found on the AUR page for the package: https://aur.archlinux.org/cgit/aur.git/ … tor.tar.gz

Extract it. Enter the newly created "unity-editor" directory. Run "makepkg". All done!

Does that work for you?

Last edited by drcouzelis (2017-09-23 02:44:19)

Arch Linux

#1 2017-09-22 21:19:18

[NOT SOLVED] packer keeps running out of room while building

#2 2017-09-22 21:28:33

Re: [NOT SOLVED] packer keeps running out of room while building

#3 2017-09-22 21:33:19

Re: [NOT SOLVED] packer keeps running out of room while building

#4 2017-09-22 21:35:46

Re: [NOT SOLVED] packer keeps running out of room while building

#5 2017-09-22 22:05:07

Re: [NOT SOLVED] packer keeps running out of room while building

#6 2017-09-22 23:30:23

Re: [NOT SOLVED] packer keeps running out of room while building

#7 2017-09-23 02:42:52

Re: [NOT SOLVED] packer keeps running out of room while building

Board footer