this applies to software/seleniumrunner and testnodes

this was just not tested

the default bytes is just fine

also build with rawmidi enabled

Bring more structure to RU-specific code as a preparatory step for multiRU support:

- move RU-specific files under ru/<RU-type>/ . This mostly moves Lopcomm programs and configuration files there.
- move RU-specific instance code there as well. This also mostly moves Lopcomm specific services and promises there.
- bring more structure in naming. As buildout has global namespace use ru_<RU-type>_ prefix to avoid collision in names.

This should be a preparatory patch with practically no semantic change, but
preparing ground for further multiRU landing.

/cc @xavier_thompson, @Daetalus
/reviewed-by @jhuge, @lu.xu
/reviewed-on nexedi/slapos!1466

`render-templates -d` is used to remove all files that it previously
generated, so that it is easy to look around during development.

But, probably due to oversight, it was only *tdd files, that were
removed, with *fdd generated files still left in place.

-> Fix it.

The list of generated files, that is now additionally removed after this patch is:

        instance-fdd-enb-input-schema.json
        instance-fdd-gnb-input-schema.json
        instance-fdd-lopcomm-enb-input-schema.json
        instance-fdd-lopcomm-gnb-input-schema.json
        instance-fdd-lopcomm-ue-lte-input-schema.json
        instance-fdd-lopcomm-ue-nr-input-schema.json
        instance-fdd-ors-enb-input-schema.json
        instance-fdd-ors-gnb-input-schema.json
        instance-fdd-ors-ue-lte-input-schema.json
        instance-fdd-ors-ue-nr-input-schema.json
        instance-fdd-ue-lte-input-schema.json
        instance-fdd-ue-nr-input-schema.json
        software-fdd-lopcomm.cfg
        software-fdd-lopcomm.cfg.json
        software-fdd-ors.cfg
        software-fdd-ors.cfg.json
        software-fdd.cfg
        software-fdd.cfg.json
        test/testFDD-LOPCOMM.py
        test/testFDD-ORS.py
        test/testFDD.py

/cc @tomo, @xavier_thompson, @Daetalus
/reviewed-by @jhuge, @lu.xu
/reviewed-on !1463

For its operation slapos-render-config mimics jinja2 templates rendering
done for real in slapos. But to do so it currently duplicates the code
from slapos.recipe.template.

We can do the same by reusing slapos.recipe.template instead of
duplicating code from there.

-> Do it.

The output of generated gnb.cfg is the same before and after this patch.

/cc @xavier_thompson, @Daetalus
/reviewed-by @jhuge, @lu.xu, @tomo
/reviewed-on nexedi/slapos!1462

When I was first starting to look around inside ors-amarisoft software
release for me it was not clear off-hand what this program is for. It
should be more clear about what's the intent if there is explicit
comment.

/cc @xavier_thompson, @Daetalus
/reviewed-by @jhuge, @lu.xu, @tomo
/reviewed-on nexedi/slapos!1462

a6eaad9a (software/ors-amarisoft: add network_name parameter) updated
enb.jinja2.cfg and gnb.jinja2.cfg to require slap_configuration['configuration.com_addr']
and other parameters to be present, but did not updated
slapos-render-confg, which got broken as the result:

    (py3.venv) kirr@deca:~/src/wendelin/slapos/slapos/software/ors-amarisoft$ python slapos-render-config.py
    ...
    Traceback (most recent call last):
      File "/home/kirr/src/wendelin/slapos/slapos/software/ors-amarisoft/slapos-render-config.py", line 232, in <module>
        f.write(r._render().decode())
                ^^^^^^^^^^^
      File "/home/kirr/src/wendelin/slapos/slapos/software/ors-amarisoft/slapos-render-config.py", line 206, in _render
        return template_object.render(**self.context).encode(self.encoding)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      File "/home/kirr/src/wendelin/venv/py3.venv/lib/python3.11/site-packages/jinja2/environment.py", line 1301, in render
        self.environment.handle_exception()
      File "/home/kirr/src/wendelin/venv/py3.venv/lib/python3.11/site-packages/jinja2/environment.py", line 936, in handle_exception
        raise rewrite_traceback_stack(source=source)
      File "config/gnb.jinja2.cfg", line 62, in top-level template code
        com_addr: "{{ slap_configuration['configuration.com_addr'] }}:{{ slap_configuration['configuration.com_ws_port'] }}",
      ^^^^^^^^^^^^^^^^^^^^^^^^^
    jinja2.exceptions.UndefinedError: 'dict object' has no attribute 'configuration.com_addr'

-> Fix it.

/cc @xavier_thompson, @Daetalus
/reviewed-by @jhuge, @lu.xu, @tomo
/reviewed-on nexedi/slapos!1462

In multiRU we will need to be able to check multiple CPRI boards and multiple
SFP ports on them, not only SFP ports on CPRI board 0 that was implicitly used
until now.

-> As a preparatory step the SR to explicitly specify which CPRI resources are being verified.

This patch is necessary because in nexedi/slapos.toolbox!127
we adjust check_cpri_lock plugin to require CPRI device + SFP port to be
explicitly specified.

/cc @tomo, @xavier_thompson, @Daetalus
/reviewed-by @lu.xu, @jhuge
/reviewed-on nexedi/slapos!1461

In multiRU we will need to be able to check multiple radio units for RX saturation separately.

-> As a preparatory step adjust the SR to explicitly specify the list of RX antennas to be verified.

This patch is necessary because in slapos.toolbox!126
we adjust check_rx_saturated plugin to require list of RX channels to check to be
explicitly specified.

/cc @tomo, @xavier_thompson, @Daetalus
/reviewed-by @jhuge, @lu.xu
/reviewed-on !1459

In multiRU we will need to be able to check multiple devices and DMA channels,
not only /dev/sdr0@0 that was implicitly used until now.

-> As a preparatory step adjust the SR to explicitly specify which SDR resource is being verified.

This patch is necessary because in nexedi/slapos.toolbox!125
we adjust check_sdr_busy plugin to require SDR device/DMA channel to be
explicitly specified.

/cc @lu.xu, @tomo, @xavier_thompson, @Daetalus
/reviewed-by @jhuge
/reviewed-on nexedi/slapos!1458

also stop enabling pip user installation, this breaks slapos isolation too much

See merge request nexedi/slapos!1464

This reverts commit 6f167c36.

This causes issues that unexpectly slapos python processes use user
installed packages. This was to accomodate python extension prompting
user to install packages for them, but current version of the extension
no longer seem to do this.

See merge request nexedi/slapos!1460

Cover a case of not adding needless trailing / while accessing a backend from
top level of the URL.

As / are stripped while parsing the url, expose the situation that even if
url ends with a /, it won't be sent for top level access.

Here is the mapping of configured URL, path accessed on the CDN side and path
sent to the backend:

 * backend/index.html   frontend/     index.html
 * backend/index.html   frontend/a    index.html/a
 * backend/index.html   frontend/a/   index.html/a/
 * backend/index.html/  frontend/     index.html
 * backend/index.html/  frontend/a    index.html/a
 * backend/index.html/  frontend/a/   index.html/a/

During my recent work I needed to use path for generated interpreter in
several places and found the need to repeat
${buildout:bin-directory}/${python-interpreter:interpreter} both tiring
and error-prone, because the knowledge where executable is placed
is implicitly used and relied upon.

On the other hand:

- pygolang already provides ${gpython:exe} as reference to the place
  where gpython is installed (see e1d269b4)

- pygolang already uses :exe for interpreter generated to accompany
  pyprog (see 0ee52376 and e328aa49)

So python-interpreter not providing :exe is an oversight and the logical
fix is to start providing python-interpreter:exe as well.

-> Do it and convert */software.cfg throughout the tree, where
python-interpreter is found, to use it.

/cc @jerome, @Tyagov, @alain.takoudjou, @xavier_thompson, @levin.zimmermann
/reviewed-on nexedi/slapos!1456

The new ghostscript could not decrypt some password protected files. It turned out to be a bug in ghostscript but in the process of investigating I thought it might be related to missing libidn that is also used in PDF passwords, so I added it.

See merge request nexedi/slapos!1455

Fixes decryption of some password protected PDFs

INFO configure: WARNING: unrecognized options: --disable-threadsafe

without libidn, decrypting password protected PDFs does not fully work.