Release contains symlinks to non-existent targets

[leg100]

The latest stable release tarball for Linux, 64-bit, contains symlinks to target files that don't exist:

arachni-1.5.1-0.5.12/system/usr/etc/fonts/conf.d/10-scale-bitmap-fonts.conf -> /home/zapotek/arachni-build-dir/arachni/system/usr/share/fontconfig/conf.avail/10-scale-bitmap-fonts.conf
arachni-1.5.1-0.5.12/system/usr/etc/fonts/conf.d/65-nonlatin.conf -> /home/zapotek/arachni-build-dir/arachni/system/usr/share/fontconfig/conf.avail/65-nonlatin.conf
arachni-1.5.1-0.5.12/system/usr/etc/fonts/conf.d/51-local.conf -> /home/zapotek/arachni-build-dir/arachni/system/usr/share/fontconfig/conf.avail/51-local.conf
arachni-1.5.1-0.5.12/system/usr/etc/fonts/conf.d/20-unhint-small-vera.conf -> /home/zapotek/arachni-build-dir/arachni/system/usr/share/fontconfig/conf.avail/20-unhint-small-vera.conf
arachni-1.5.1-0.5.12/system/usr/etc/fonts/conf.d/50-user.conf -> /home/zapotek/arachni-build-dir/arachni/system/usr/share/fontconfig/conf.avail/50-user.conf
arachni-1.5.1-0.5.12/system/usr/etc/fonts/conf.d/60-latin.conf -> /home/zapotek/arachni-build-dir/arachni/system/usr/share/fontconfig/conf.avail/60-latin.conf
arachni-1.5.1-0.5.12/system/usr/etc/fonts/conf.d/80-delicious.conf -> /home/zapotek/arachni-build-dir/arachni/system/usr/share/fontconfig/conf.avail/80-delicious.conf
arachni-1.5.1-0.5.12/system/usr/etc/fonts/conf.d/69-unifont.conf -> /home/zapotek/arachni-build-dir/arachni/system/usr/share/fontconfig/conf.avail/69-unifont.conf
arachni-1.5.1-0.5.12/system/usr/etc/fonts/conf.d/45-latin.conf -> /home/zapotek/arachni-build-dir/arachni/system/usr/share/fontconfig/conf.avail/45-latin.conf
arachni-1.5.1-0.5.12/system/usr/etc/fonts/conf.d/40-nonlatin.conf -> /home/zapotek/arachni-build-dir/arachni/system/usr/share/fontconfig/conf.avail/40-nonlatin.conf
arachni-1.5.1-0.5.12/system/usr/etc/fonts/conf.d/90-synthetic.conf -> /home/zapotek/arachni-build-dir/arachni/system/usr/share/fontconfig/conf.avail/90-synthetic.conf
arachni-1.5.1-0.5.12/system/usr/etc/fonts/conf.d/65-fonts-persian.conf -> /home/zapotek/arachni-build-dir/arachni/system/usr/share/fontconfig/conf.avail/65-fonts-persian.conf
arachni-1.5.1-0.5.12/system/usr/etc/fonts/conf.d/30-metric-aliases.conf -> /home/zapotek/arachni-build-dir/arachni/system/usr/share/fontconfig/conf.avail/30-metric-aliases.conf
arachni-1.5.1-0.5.12/system/usr/etc/fonts/conf.d/49-sansserif.conf -> /home/zapotek/arachni-build-dir/arachni/system/usr/share/fontconfig/conf.avail/49-sansserif.conf
arachni-1.5.1-0.5.12/system/usr/etc/fonts/conf.d/30-urw-aliases.conf -> /home/zapotek/arachni-build-dir/arachni/system/usr/share/fontconfig/conf.avail/30-urw-aliases.conf
arachni-1.5.1-0.5.12/system/gems/gems/ffi-1.9.18/ext/ffi_c/libffi-x86_64-linux/include/ffitarget.h -> /home/zapotek/arachni-build-dir/arachni/system/gems/gems/ffi-1.9.18/ext/ffi_c/libffi/src/x86/ffitarget.h

This might seem harmless but I think I'm getting an error when extracting as part of the build of a Docker image:

tar: system/usr/lib: Directory renamed before its status could be extracted
tar: system/usr/etc/fonts/conf.d: Directory renamed before its status could be extracted
tar: system/usr/etc/fonts: Directory renamed before its status could be extracted
tar: system/usr/etc: Directory renamed before its status could be extracted
tar: system/usr: Directory renamed before its status could be extracted
tar: Exiting with failure status due to previous errors

Which is related to a bug with Docker but I think I could workaround it if it weren't for the errant symlinks above.

The same errant symlinks are in the nightly releases, too.

[Zapotek]

It does feel unclean to have it this way, but it does work fine when running in a proper env and I don't see how to improve the situation to be honest.
I'm a bit reluctant to mess with the packages since they've been working great in general.