-
Notifications
You must be signed in to change notification settings - Fork 142
Provide an absolute path to a debootstrap tarball #424
Comments
Hm, I think what we need to do here is fix how the workspace path is handled. I never thought of using a relative path for that part. To keep things consistent, I think we should simultaneously make the workspace path relative to the manifest, like we do with a lot of other paths in the manifest. |
@andsens sorry for the delay. You are right - debootstrap finds tarball just fine while using a relative path for workspace in a manifest file. In my opinion, we should prefer a relative path instead of an absolute path. Our use case is as follows:
So:
Making workspace path relative to the manifest as you suggested looks great for me (consistency and no need for absolute paths). |
Other issue related to relative/absolute paths #368. |
@andsens I can try to prepare PR for this issue, but please give me some hints how you would like to get the workspace path relative to the manifest done. |
Oh, that's easy. Just use |
Hi,
while using
tarball: true
in manifest file bootstrap-vz returns a debootstrap errorE: Tarball must be given a complete path
. Debootstrap expects an absolute path to tarball while bootstrap-vz provides relative path.Bootstrap-vz should provide an absolute path to a debootstrap tarball.
Details:
As described in http://bootstrap-vz.readthedocs.io/en/master/manifests/index.html debootstrap can then be pointed at a tarball and use it instead of downloading packages from the internet.
Running bootstrap-vz with the manifest that contains
tarball: true
returns an error:Running debotstrap directly with given options returns an error "E: Tarball must be given a complete path". Link to debootstrap source code https://anonscm.debian.org/cgit/d-i/debootstrap.git/tree/debootstrap#n530
The text was updated successfully, but these errors were encountered: