Closed a3nm closed 6 years ago
The ideal solution for this is tracked upstream at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763419 — any help with implementing it is very welcome.
Until then, you’ll either need to replace the snapshot URL with an archive URL (but then you might get different image contents, of course) or disable the check as you did.
I see, thanks for the pointer! As this probably won't be fixed soon, maybe it'd be worth it to point out the problem in README.md where you explain how to prepare the image? Or maybe add the workaround to disable the check to raspi3.yaml like you did for other upstream bugs?
In any case, thanks for the explanation, and thanks for this project!
I think adding the problem to the README is fair. Would you like to send a pull request for that?
When running
sudo ./vmdb2/vmdb2 --output raspi3.img raspi3.yaml --log raspi3.log
, image creation fails after installing the base system because apt-get complains about an expired release file:I was able to fix this by instructing apt-get to ignore the check with
-o Acquire::Check-Valid-Until=false
, but I'm not sure whether this is the best solution.