Document apt-get workaround #2
Conversation
README.md
Outdated
| `apt-get` invocations with `apt-get -o Acquire::Check-Valid-Until=false` | ||
| - If you want to use the latest versions of each software, you can replace | ||
| `http://snapshot.debian.org/archive/debian/20171007T213914Z/` in raspi3.yaml | ||
| with the URL of your favorite Debian mirror. Of course, this means that the |
There was a problem hiding this comment.
s,the URL of your favorite Debian mirror,http://deb.debian.org/debian, please. People who care about mirrors will know how to replace it.
|
Thanks for the PR!
Yeah, we should definitely recommend |
building the image fails otherwise (encoding issues, missing PATH, etc.); took invocation from https://unix.stackexchange.com/a/49057
|
I implemented your suggestion, thanks! As for the environment cleanup issue, I tried to explain how to do it, but with I'm running a build now to check that the proposed invocation works until the end; if it does work I'm fine with merging. |
README.md
Outdated
|
|
||
| ```shell | ||
| umask 022 | ||
| sudo env -i HOME="$HOME" LC_CTYPE="${LC_ALL:-${LC_CTYPE:-$LANG}}" PATH="$PATH" USER="$USER" \ |
There was a problem hiding this comment.
Do you know why $HOME and $USER are required? This strikes me as odd.
We should set LC_CTYPE=C.UTF-8.
There was a problem hiding this comment.
$HOME and $USER were probably not required, I just lost patience after $LT_CTYPE and $PATH so I searched for a solution online. Fixed.
|
I did your suggested change, thanks! The build seems to run, just checking now that it actually completes. |
|
Please let me know once you have a working image and I’ll merge. Thanks again! |
|
Image creation completed successfully, so for me this can be merged. Thanks for reviewing and for coding this. :)
…--
Antoine Amarilli
Sent from a mobile device, please excuse brevity and top-posting.
On October 25, 2017 12:15:23 PM GMT+02:00, Michael Stapelberg ***@***.***> wrote:
Please let me know once you have a working image and I’ll merge. Thanks
again!
|
Hi, this is as discussed in issue #1. I also documented the need to install the dependencies of vmdb2, if that's OK.
By the way, one other thing that could maybe be documented is the fact that building the image fails mysteriously ("cannot run apt-key") if the user running the build has another umask that 022 (see here). I don't know whether you think it's a relevant point to document, but it's the main problem I had to debug when building the image. What do you think?