Despite what GitHub states in their documentation, the runners feature a
different core count. Automatically set the build thread-count by the
amount of available CPU cores.

Link: https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources



Signed-off-by: David Bauer <mail@david-bauer.net>

It makes sense to run CI build-tests in case the CI itself is altered.

Signed-off-by: David Bauer <mail@david-bauer.net>

(cherry picked from commit b313a631)

Add ssh-client to enable deployment of the build output from CI.

While Podman automatically populates /etc/passwd and /etc/group with
matching entries for the mapped host user, such a feature is missing
from Docker. Install libnss-unknown, which will return passwd entries of
the form "uid-1000" for all unknown UIDs, to avoid warnings and other
weird behaviour that may occur when running as an unnamed user.

`-o` must be passed to useradd now to allow non-unique user entries, as
with libnss-unknown, every UID is considered occupied.

To make the container behave the same regardless of the UIDs used
outside of the container, choose a UID that is unlikely to be used by
the user mounting their build directory the container. 100 should not
conflict with common defaults on Linux (min UID 1000) or MacOS X
(min UID 500). Conveniently, there is already a group "users" at GID
100, so creating a new group can be avoided.

Initialize the /gluon volume with the contents of /etc/skel.

[Matthias Schiffer: extend commit message]

Instead of poorly parsing Makefiles using grep, use OpenWrt's processed
package info files. This fixes handling of DEPENDS fields spanning
multiple lines and adds support for source packages building multiple
binary packages.

Closes #2814

The build process fails without that.

Co-authored-by: Tom Herbers <mail@tomherbers.de>

* add missing libelf-dev dependency (to build x86-64)
* remove subversion dependency
* add rsync dependency
* add ecdsautils to docs

- [Release notes](https://github.com/editorconfig-checker/editorconfig-checker/releases)
- [Commits](https://github.com/editorconfig-checker/editorconfig-checker/compare/2.6.0...2.7.0

)

Signed-off-by: Jan-Niklas Burfeind <git@aiyionpri.me>

Co-authored-by: Jan-Niklas Burfeind <git@aiyionpri.me>
version bump to 2.6.0
aligned indentation

Signed-off-by: Stefan Weil <sw@weilnetz.de>

to match the editorconfig

awk code in contrib/sign.sh and contrib/sigtest.sh
reformatted as gawk does

`apt-get clean` clears out the local repository of retrieved package files.
It removes everything but the lock file from /var/cache/apt/archives/ and
/var/cache/apt/archives/partial/.

Co-authored-by: Vieno Hakkerinen <vieno@chemnitz.freifunk.net>

This updates the site.conf based on docs/site-example/site.conf for v2022.1

Updates the image to have a newer build environment, which is required
for some of the maintainer scripts.

Increases the image size from 414 to 545 MB.

to prevent word splitting and globbing

Starting from OpenSSH 9.0p, scp started to use sftp in favor of the
scp protocol by default. As dropbear in OpenWrt currently does not
support sftp by default, we now use the fallback cli switch "-O"
to use the scp protocol for scp.

Do not fail the new check that good_signatures ≤ #pubkeys.

The scripts directory contains most of our build system, so changing it
should trigger a build of all targets.

- Use printf instead of echo for better portability
- Print whole path without reordering components
- Deduplicate code

Iterating over all the package directories in the OpenWrt feed takes a
while, even though it doesn't contain any upgrade scripts. Skip the
whole directory.

0.7.1 complains about unescaped backslashes in double quotes (which are
intepreted by printf in the two affected places). While the warning was
retired with shellcheck 0.7.2, it seems like a good idea to fix it
anyways.

Using `make container` or, if you don't have automake/gmake on your host
system, `./scripts/container.sh` will build an image for the current
branch your are on and drop you into a shell running inside a container
using that image.

From there all tooling required to work on Gluon is available.

Supports both podman (preferred) and docker.

This has become possible with OpenWrt 21.02 and while the Dockerfile
already received that updated, we forgot to update the CI and the
documentation.

Has gone unused for a while now and if it is needed again it can be
retrieved from the history.

v2: In contrast to the last patches, this is now built on top of ssh
    only, without using e.g. 9pfs. Furthermore it works also with
    arbitary remote hosts on any target/architecture. Also the
    scripts were renamed and moved to /scripts.

The aim of this commit is to allow fast rebuild cycles during the
development of gluon packages.

Currently the following workflow can be used:

	# start a local qemu instance
	scripts/run_qemu.sh output/images/factory/[...].img

	# do your changes in the file you want to patch
	vi package/gluon-ebtables/files/etc/init.d/gluon-ebtables

	# rebuild and update the package
	scripts/push_pkg.sh package/gluon-ebtables/

	# test your changes
	...

	# do more changes
	...

	# rebuild and update the package
	scripts/push_pkg.sh package/gluon-ebtables/

	# test your changes
	...

	(and so on...)

Implementation details:
- Currently this is based on ssh/scp.
- Opkg is used to install/update the packages in the remote machine.

Benefits:
- This works with compiled and non-compiled packages.
- This works with native OpenWrt and Gluon packages.
- This even performs the check_site.lua checks as they are integrated
  as post_install scripts into the openwrt package.
- It works for all architectures/targets.

The kernel build requires rsync.