Vagrant package with relative path

Seems like the vagrant package expects the path to be relative to it's root= initialisation. Without a relative path it lead to some weird errors were it tried to copy the absolute path relative to it's root

The current setup is used in production and many other servers, e.g. the public instances: https://gitlab.com/fdroid/wiki/-/wikis/Buildserver/Public-buildserver-instances

The current state works fine in those place. My guess is that whatever problem you're seeing is due to your local setup.

@fdroid-anyone seems like you are right, my setup somehow works again without this patch

closed