See merge request !151

On slower hosts it takes a bit more time to boot the ISO some times, which
results with not receiving the ESC key to disable the graphic screen, and so
not working installation.

The general idea is to provide a machine connected to re6st, registered as
computer in SlapOS Master and with thorwable user to work on it.

Starting from default installation some uneeded packages are removed, and
few expected ones are added in order to have common set of packages and use
scenarios across all installations.

It's not possible on Ubuntu/Focal

The goal is to use the newest re6st-node package that correctly enables
the re6stnet service. re6st-node package has been fixed with
nexedi/re6stnet@5bdb32e6
and 6972e11f

See merge request nexedi/slapos.package!148

Packer can be run on slow machines, give them time to do the job.

Only shacache assures stable URLs for reproducible builds.

This is a fixup of 5e69756c

fixup of nexedi/slapos.package@f04d923d

This reverts commit 6e5b4d76 and commit 055ffef4.

After nexedi/slapos.buildout@0abf873d we don't have compiled wheels anymore

With previous version of setuptools (33.1.1), we have errors when downloading the latest version:

While:
  Bootstrapping.
  Getting distribution for 'setuptools==44.1.1'.
Error: https://files.pythonhosted.org/packages/b2/40/4e00501c204b457f10fe410da0c97537214b2265247bc9a5bc6edd55b9e4/setuptools-44.1.1.zip#sha256=c67aa55db532a0dadc4d2e20ba9961cbd3ccc84d544e9029699822542b5a476b hostname 'files.pythonhosted.org' doesn't match 'r.ssl.fastly.net'

See merge request !146

Having base playbook for Rapid.Space VPS servers is a good way to automate
common tasks on such servers.

Additional role rapid-space-vps-base is added for furhter extensions.

Unfortunately a lot of various approaches is needed:

 * ini_file for oneline manipulation
 * blockinfile for adding a section
 * lineinfile for uncommenting

Note: it was discovered, that some specific parts are just missing in
vifib-server, so add them there.

See merge request !143

See merge request !144

patsubst adds whitespaces preventing the correct file, perl
and chrpath to be used. For archlinux package file command fails
because of this.

33.1.0 fails to find zc.buildout

This replaces a long pipeline that only failed if the last pipe
command fails. But on Arch, we got the following error:

  xargs: file: terminated by signal 31

and the build continued, pretending it was successful whereas the
package was unusable.

This is similar to bash's pipefail.

Note that 'chrpath -k' exit code is ignored
because it is expected to return 2.

Fedora distribution refuses shebang with unknown python version:
ERROR: ambiguous python shebang in /opt/slapos/tmp-networkcached/bin/networkcache-download: #!/usr/bin/python. Change it to python3 (or python2) explicitly.
ERROR: ambiguous python shebang in /opt/slapos/tmp-networkcached/bin/networkcache-upload: #!/usr/bin/python. Change it to python3 (or python2) explicitly.
ERROR: ambiguous python shebang in /opt/slapos/tmp-networkcached/bin/buildout: #!/usr/bin/python. Change it to python3 (or python2) explicitly.
ERROR: ambiguous python shebang in /opt/slapos/tmp-networkcached/bin/generate-signature-key: #!/usr/bin/python. Change it to python3 (or python2) explicitly.

Using python2.7 explicitely will make the shebang /usr/bin/python2.7

This is needed specially for kernel after 4.16 (especially 4.19, kernel
version of Debian 10) because much more objects are counted in this
max_size limit.

See interesting discussion here: https://lore.kernel.org/patchwork/patch/1245043/

Also stop using deprecated TarFile.add's exclude parameter.

Shipping binaries in /usr/sbin fails because /usr/sbin is a symlink
to /usr/bin. Similarly, /lib is a symlink to /usr/lib.

https://wiki.archlinux.org/index.php/Frequently_asked_questions#Does_Arch_follow_the_Linux_Foundation's_Filesystem_Hierarchy_Standard_(FHS)?