- Jul 28, 2022
-
-
Fabrice Fontaine authored
gdal needs json-c, not libjson, resulting in the following build failure since the addition of the package in commit 1e64fa29: configure: error: could not find json-c/json.h While at it, also drop unrecognized options: configure: WARNING: unrecognized options: --disable-gtk-doc, --disable-gtk-doc-html, --disable-doc, --disable-docs, --disable-documentation, --with-xmlto, --with-fop, --disable-dependency-tracking, --enable-ipv6, --disable-nls, --without-dods-root, --without-fme, --without-grass, --without-libgrass, --without-ingres, --without-jasper, --without-charls, --without-mdb, --without-mongocxx, --without-mrsid_lidar, --without-perl Fixes: - http://autobuild.buildroot.org/results/f977675125167806e844a176a4c8c8873557b709 Signed-off-by:
Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
-
Fabrice Fontaine authored
license hash is wrong since the addition of the package in commit 1e64fa29: ERROR: LICENSE.TXT has wrong sha256 hash: ERROR: expected: b82e6cca0b13f5db2f22ab667f22254fb1f4b135ea73d5bd6238ef89aff31f6c ERROR: got : fac0116e799ca4de79b076ee04863b5e2b69541ea3664b9bb108c81a5355f16a ERROR: Incomplete download, or man-in-the-middle (MITM) attack Fixes: - http://autobuild.buildroot.org/results/e443db6d7ff3ae867035d169853b880b5e13d181 Signed-off-by:
-
Marcin Niestroj authored
Second newline at the end of licence file was removed upstream, so update license file hash. [1] https://github.com/pytest-dev/pytest-asyncio/commit/4c7da65d6fcf9d725eccba28ad1ed2083524ee16 Signed-off-by:
Marcin Niestroj <m.niestroj@grinn-global.com> Signed-off-by:
-
Marcin Niestroj authored
There is just a starting year in licence file now (see [1]), but licence itself did not change. Also fixup the spacing in the hash file to match the "new" coding style. [1] https://github.com/pytest-dev/pytest/commit/ed24f29e6017183ea22f3136aa180a8e3280cf8a Signed-off-by:
-
Marcin Niestroj authored
Use the same TF-A as orangepi_zero_plus2 board. Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/2720001176 Signed-off-by:
-
Sen Hastings authored
sortGrid() has been rewritten to dynamically generate stylesheets with explicit grid-row properties to re-order the rows, instead of removing and reinserting the cells. Performance *should* now be comperable to sorttable.js. Signed-off-by:
Sen Hastings <sen@phobosdpl.com> Signed-off-by:
-
Sen Hastings authored
Like all good problems, disparate pieces work together to create a "synergistically" hairy mess. The sortGrid() overhaul highlighted a flaw in pkg-stats allowing for duplicate package class names across rows. As an example, boot/barebox/barebox.mk and boot/barebox/barebox/barebox.mk both get the classname ._barebox and so sortGrid() sticks them on the same line giving a table with a vestigal row sticking out of the right side like some kind of appendage. Also I neglected to add a "_" to the current version column's cells pkgname class so instead of "._pkgname" we had ".pkgname" and so the cells were not collected properly as part of the row. These issues explain the formatting weirdness. package classnames are now ".path_to_package_makefile" without suffix (.mk) (so ._boot_barebox_barebox and ._boot_barebox_barebox_barebox instead of ._barebox) in order to guarantee uniqueness. and what was *accidentally* class="centered current_version data .barebox" is now class="centered current_version data ._boot_barebox_barebox" just like *all* the other cells in the row. :p Signed-off-by:
-
Christian Stewart authored
nerdctl is a CLI for containerd (package docker-containerd) which is drop-in compatible with the Docker Daemon CLI. This allows using the lighter weight containerd daemon directly, instead of via the additional docker daemon. It also implements rootless mode. https://github.com/containerd/nerdctl Signed-off-by:
Christian Stewart <christian@paral.in> Signed-off-by:
-
- Jul 27, 2022
-
-
Yann E. MORIN authored
Add four new tests for systemd (rw and ro in each case): - use dbus-broker instead of the original dbus - use the original dbus, with dbus-broker installed The first two extend the existing IfUpDown test cases by just enabling dbus-broker; the second ones extend this further, by explicitly enabling the original dbus. For one of the tests, we overload the test_run() function to test that the dbus-broker daemon is indeed running as root. We need not replicate that check in the other dbus-broker-only test, and it does not make sense to test that in tests that have the original dbus enabled. Presence of the original dbus and dbus-broker on the same system is valid: the original dbus is used as the default system bus daemon. We do not test switching between the two at runtime, though as this is really too corner-case specific. We just test to ensure the original dbus system bus daemon is not impacted by the presence of dbus-broker. Note: the 'full' test-case enables all systemd options, and some of them do pull the original dbus package, so we can't use that to test the integration of dbus-broker; instead, we extend the ifupdown case, which does not enable the original dbus. The default external toolchain for cortex-A9 is the old ARM toolchain which has kernel headers 4.10 Since dbus-broker needs toolchain headers >= 4.17, it can't be selected with this toolchain. Switch the systemd tests to the Bootlin toolchains instead. We switch all of them to make things easier. Note that we will need to take care in the future that the headers version used in the bootlin toolchain doesn't get bigger than the kernel that is used. The kernel is currently 5.10, the headers in the bleeding edge bootlin toolchain are 5.4. Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr> Cc: Norbert Lange <nolange79@gmail.com> Signed-off-by:
Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
-
Yann E. MORIN authored
dbus-broker fits the bill as a message bus daemon, so only enable the original dbus if dbus-broker is not enabled. Signed-off-by:
-
Norbert Lange authored
dbus-broker is an alternate implementation of a dbus daemon. It can be used as a drop-in replacement for the system bus daemon, as well as the session bus daemon. dbus-broker is (basically, and as far as we're concerned in Buildroot) split in two components: - the actual message bus daemon, that relays messages across clients - a launcher, which is responsible for setting various aspects of the bus, like setting the policy et al. and opening the socket(s) the message bus daemon will have to listen on... The launcher can only be used in a systemd setup (it makes heavy use of systemd facilities), while the message bus is generic. However, the message bus daemon is useless without a launcher. There does not exist a non-systemd launcher, which makes dbus-broker actually a systemd-only package; this can be revisited when/if a non-systemd launcher appears. Note, however, that libdbus is not provided by dbus-broker. People who want to use dbus-broker as the bus daemon, and need libdbus, will have to enable both. If only original dbus is enabled, things stay as they are now. This is for the moment still the default, though we should change that once dbus-broker has proven to work. If only dbus-broker is enabled, it installs the necessary socket activation units and dbus configuration files. The daemon is not launched at boot time; instead it is socket-activated when a client connects to the bus the first time. If both original dbus and dbus-broker are enabled, we have a conflict with the configuration files, the socket activation file. Also, original dbus activates the daemon as a service in multi-user.target.wants, so it is not socket-activated and dbus-broker would never get the opportunity to start. Therefore, original dbus is updated to remove the conflicting files and the activation of dbus-daemon. Since dbus-broker installs some of the same file that original dbus removes, we have to add a dependency to make sure that the ones installed by dbus-broker aren't removed. If both are installed, it is still possible to revert back to using original dbus as system bus: - at build-time: by calling systemctl enable/disable from a post-build script (preferred), or by providing drop-in units or presets in an overlay (less preferred) or custom skeleton (as a last resort), - at runtime (on a RW filesystem): by calling systemctl enable/disable Note about the user: the path to the system bus socket is a so-called "well-known location": it is expected to be there, by spec. Moving it elsewhere is going to break existing programs. So, the user running the system bus daemon must be able to create that socket. As we may have two packages providing a system bus daemon, they have to be both able to create the socket, and thus must both be able to write in the directory containing the socket. And since they can be switched at runtime, they must be running as the same user. We can't just reference the original dbus user, so we duplicate the entry. What is important, is that the user be named 'dbus', as that's what we use in both cases. If both original dbus and dbus-broker are selected, the dbus user is included twice, but the specifications are identical so that's fine. mkusers will create the user only once. Finally, the licensing terms are pretty trivial for dbus-broker itself, but it makes use of third-party code that it inherits as git submodules (that are bundled in the release archive). Thus the licensing is a bit convoluted... The third-party codes claim to be licensed as "Apache-2.0 and LGP-2.1+" in their AUTHORS files, but at the same time claim "**Apache-2.0** OR **LGPL-2.1-or-later**" in their README files. The individual source files (that are used) do not seem to have any licensing header to clarify the situation. So we represent the situation with "Apache-2.0 and/or LGPL-2.1+". Signed-off-by:Norbert Lange <nolange79@gmail.com> [yann.morin.1998@free.fr: - don't select systemd; depend on it instead - only install config files and systemd units without original dbus - install a user to run the message bus as - fix licensing info - entirely reword and extend the commit log - add myself to DEVELOPERS as well ] Signed-off-by:
-
Thomas Petazzoni authored
The 'rtl8723ds' name, when queried from release-monitoring.org at https://release-monitoring.org/api/projects/?pattern=rtl8723ds returns one project, with one "stable_versions" array, which is empty. This was not expected by the pkg-stats code, causing an exception: Task exception was never retrieved future: <Task finished name='Task-764' coro=<check_package_latest_version_get() done, defined at /home/thomas/projets/buildroot/./support/scripts/pkg-stats:558> exception=IndexError('list index out of range')> Traceback (most recent call last): File "/home/thomas/projets/buildroot/./support/scripts/pkg-stats", line 566, in check_package_latest_version_get if await check_package_get_latest_version_by_guess(session, pkg): File "/home/thomas/projets/buildroot/./support/scripts/pkg-stats", line 544, in check_package_get_latest_version_by_guess projects[0]['stable_versions'][0], IndexError: list index out of range This commit therefore improves the checks done on the results received from release-monitoring.org to avoid this issue. Signed-off-by:
-
Sen Hastings authored
Pretty straightforward. Adds my name to copyright notice. Signed-off-by:
-
Sen Hastings authored
CSS classes are generated for each package name for sorting purposes, However some package names start with a number and this is not allowed. (see https://www.w3.org/TR/CSS2/syndata.html#value-def-identifier ) Fix is to prepend a character to every class name such as "_". so every ".package" is now "._package". Signed-off-by:
-
Sen Hastings authored
This fixes the .version-needs-update class being overridden by .correct class. Signed-off-by:
-
Paul Cercueil authored
Until now, when BR2_CCACHE=y, ccache support was built into the toolchain wrapper, and used regardless of whether the toolchain is using during the Buildroot build itself, or later as part of the SDK. However, having ccache support forcefully enabled in the SDK can really be surprising, and is certainly unexpected for a cross-compilation toolchain. This can be particularly surprising as the ccache cache directory may be hardcoded in the ccache binary to point to a folder that does not make sense on the SDK user's machine. So what this commit does is create a BR2_USE_CCACHE variable, which when set to 1 tells the toolchain wrapper to use ccache. Not defining the variable, or specifying any other value that 1 causes the toolchain wrapper to not use ccache. The main Buildroot Makefile is modified to export BR2_USE_CCACHE = 1 when ccache support is enabled, so that ccache is used during the Buildroot build. However, when someone will use the SDK outside of Buildroot, the toolchain wrapper will not use ccache. The BR2_USE_CCACHE variable is only conditionally enabled in the main Makefile (via ?=) so that it can be overridden in the environment if one wants to quickly test disabling ccache in a ccache-enabled Buildroot configuration. This is the scenario that was considered in commit 792f1278 ("toolchain-wrapper: support change of BR2_CCACHE"), which added the BR_NO_CCACHE variable. The BR_NO_CCACHE variable is no longer needed, and replaced by this BR2_USE_CCACHE variable. Signed-off-by:
Paul Cercueil <paul@crapouillou.net> [Thomas: almost entirely rework the implementation and commit log] Signed-off-by:
-
Thomas Petazzoni authored
Somewhere between binutils 2.35 and 2.37, some functionality was added in readelf to parse more DWARF information. Unfortunately, as reported in binutils bug 28981 ("https://sourceware.org/bugzilla/show_bug.cgi?id=28981" ), this feature causes a number of fairly scary warnings to be displayed when running readelf on binaries built with Clang, such as the pre-built rustc and rustdoc binaries part of the host-rust-bin package. It looks like this: readelf: /home/thomas/projets/buildroot/output/host/bin/rustc: Warning: Unrecognized form: 0x23 readelf: /home/thomas/projets/buildroot/output/host/bin/rustc: Warning: Bogus end-of-siblings marker detected at offset 2f in .debug_info section readelf: /home/thomas/projets/buildroot/output/host/bin/rustc: Warning: Unrecognized form: 0x22 readelf: /home/thomas/projets/buildroot/output/host/bin/rustc: Warning: Bogus end-of-siblings marker detected at offset 10b in .debug_info section readelf: /home/thomas/projets/buildroot/output/host/bin/rustc: Warning: Bogus end-of-siblings marker detected at offset 10c in .debug_info section readelf: /home/thomas/projets/buildroot/output/host/bin/rustc: Warning: Further warnings about bogus end-of-sibling markers suppressed readelf: /home/thomas/projets/buildroot/output/host/bin/rustc: Warning: Unrecognized form: 0x22 readelf: /home/thomas/projets/buildroot/output/host/bin/rustc: Warning: Unrecognized form: 0x22 readelf: /home/thomas/projets/buildroot/output/host/bin/rustc: Warning: Unrecognized form: 0x22 readelf: /home/thomas/projets/buildroot/output/host/bin/rustc: Warning: Unrecognized form: 0x23 readelf: /home/thomas/projets/buildroot/output/host/bin/rustc: Warning: Unrecognized form: 0x22 readelf: /home/thomas/projets/buildroot/output/host/bin/rustc: Warning: Unrecognized form: 0x23 readelf: /home/thomas/projets/buildroot/output/host/bin/rustc: Warning: Unrecognized form: 0x22 readelf: /home/thomas/projets/buildroot/output/host/bin/rustc: Warning: Unrecognized form: 0x22 readelf: /home/thomas/projets/buildroot/output/host/bin/rustc: Warning: Unrecognized form: 0x22 readelf: /home/thomas/projets/buildroot/output/host/bin/rustc: Warning: Unrecognized form: 0x23 readelf: /home/thomas/projets/buildroot/output/host/bin/rustc: Warning: Unrecognized form: 0x22 readelf: /home/thomas/projets/buildroot/output/host/bin/rustc: Warning: Unrecognized form: 0x23 readelf: /home/thomas/projets/buildroot/output/host/bin/rustc: Warning: Unrecognized form: 0x22 readelf: /home/thomas/projets/buildroot/output/host/bin/rustc: Warning: DIE at offset 0x1da refers to abbreviation number 5827 which does not exist These warnings are caused by the readelf calls done by the support/scripts/check-host-rpath script. The annoying thing is that once host-rust-bin has been installed in $(HOST_DIR), this warning appears after the installation of every single host package, because support/scripts/check-host-rpath rescans all binaries every time. To avoid showing those scary warnings, this commit sends the error output of readelf to /dev/null. Of course, it would be nicer to only filter out those warnings, but filtering the error output without merging the error output into the standard output is tricky, so let's keep things simple. If there is really an error, readelf will abort. Signed-off-by: -
Since systemd requires a relatively new kernel, we switched to a self-built 4.19.204 kernel. However, since then, the downloaded kernel used by the tests has been updated to 5.10, which is certainly recent enough to support systemd. Switch to this one. This reduces the test time significantly. Signed-off-by:
-
The --testcases option of run-tests says how many test cases to build in parallel. It automatically derives a jlevel from it by dividing the number of cores + 1 by the number of parallel testcases. However, this will typically result in a fractional number. Make doesn't like fractional numbers as argument to -j. Convert the number to integer (rounding down). * br2_jlevel is an int, as multiprocessing.cpu_count() is an int, so it will be always >=2 (cpu_count() raises an error if it can't determine the number of CPU, so it will always return at least 1); * args.testcases is an int, and is checked to be >=1 So br2_jlevel + args.testcases is guaranteed to always be bigger than or equal to args.testcases, and the division thus bigger than 1. Signed-off-by:
-
Quentin Barbe authored
This is useful to be able to customize the default env images in post build scripts. Signed-off-by:
Quentin Barbe <quentin@barbe.me> Signed-off-by:
-
Marcin Niestroj authored
We rely on config.toml to be created manually during first boot as setup stage. Even with an empty config.toml file, the gitlab-runner needs gitlab registration token to register to a gitlab server. Use the 14.5.1 release since 14.5.2 and 14.6.0 triggers a build error [1] due a patch for GO < 1.17. (helpers/patches/issue_28732/syscall.go:11:2: undefined: syscall.Issue28732Fix) Tested: https://gitlab.com/kubu93/buildroot/-/pipelines/442604876 [1] https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28766 Signed-off-by:
Romain Naour <romain.naour@smile.fr> Cc: Jérémy Rosen <jeremy.rosen@smile.fr> Signed-off-by:
-
TIAN Yuanhao authored
Given a .config with: FOO="1234" BAR="$(FOO)" and then: $(call KCONFIG_SET_OPT,FOO,azerty) would yield a .config with just: FOO="azerty" because \<FOO\> would match the assignment to BAR. Reported-by:TIAN Yuanhao <tianyuanhao3@163.com> Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by:
-
Yann E. MORIN authored
The first three lines of all systemd runtime tests are identical, and they already call into a common function. Therefore, move those lines into the common function as well. We need to pass an additional argument for the rootfs type. This changes the signature, which could create confustion with InitSystemBase.check_init() that has a different signature. Therefore, rename the function to check_systemd(). That also allows us to call self.check_init() directly instead of going through super(). Signed-off-by:
-
Yann E. MORIN authored
Signed-off-by:
-
Yann E. MORIN authored
Signed-off-by:
-
Yann E. MORIN authored
Signed-off-by:
-
Yann E. MORIN authored
Signed-off-by:
-
Yann E. MORIN authored
We currently have no internal and no external toolchain for csky. The website is down (no https:// available, and the http:// index page is 404). This commit removes the architecture entry; remnants will be dropped in followup changes. Signed-off-by:
-
Fabrice Fontaine authored
https://github.com/nmoinvaz/minizip is a symlink to https://github.com/zlib-ng/minizip-ng Signed-off-by:
-
Fabrice Fontaine authored
cpe:2.3:a:osgeo:gdal is a valid CPE identifier for this package: https://nvd.nist.gov/products/cpe/search/results?namingFormat=2.3&keyword=cpe%3A2.3%3Aa%3Aosgeo%3Agdal Signed-off-by:
-
Fabrice Fontaine authored
Disable example tools (enabled by default since bump to version 1.9.20 in commit 26ca7fec and https://github.com/jackaudio/jack2/commit/508d95a97e0cdfad2e8c7d6cdd478741fdba2c87 ) Signed-off-by:
-
Fabrice Fontaine authored
Add systemd optional dependency (enabled by default) Signed-off-by:
-
Fabrice Fontaine authored
Signed-off-by:
-
Fabrice Fontaine authored
Signed-off-by:
-
Fabrice Fontaine authored
Drop openssl dependency: "The OpenSSL provider was incompatible with OpenSSL 3.0. It has been removed" https://github.com/randombit/botan/blob/2.19.2/news.rst Signed-off-by:
-
Vincent Fazio authored
Include a patch to introduce the `install-nodoc` make target to avoid a dependency on host-python3 for manpage generation. Upstream: https://github.com/andikleen/mcelog/pull/109 Signed-off-by:
Vincent Fazio <vfazio@xes-inc.com> Signed-off-by:
-
Nicolas Tran authored
dust is an alternative of the command du from the Linux kernel, written in Rust. It aims to be more intuitive and visual in order to give the user a better view of his system's storage capacity. Signed-off-by:
Nicolas Tran <nicolas.tran@smile.fr> Signed-off-by:
-
Fabrice Fontaine authored
Update hash of gpl-2.0.txt (new line removed) https://github.com/OpenVPN/easy-rsa/releases/tag/v3.1.0 https://github.com/OpenVPN/easy-rsa/blob/v3.1.0/ChangeLog Signed-off-by:
-
Fabrice Fontaine authored
Switch to pcre2 as pcre is deprecated https://github.com/SpiderLabs/ModSecurity/releases/tag/v3.0.7 Signed-off-by:
-
Bernd Kuhls authored
Needed for upcoming version bump of transmission. Signed-off-by:
Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by:
-
