- Sep 01, 2022
-
-
Peter Korsgaard authored
Signed-off-by:
Peter Korsgaard <peter@korsgaard.com>
-
- Aug 31, 2022
-
-
Peter Korsgaard authored
Signed-off-by:
Peter Korsgaard <peter@korsgaard.com>
-
Peter Korsgaard authored
Signed-off-by:
Peter Korsgaard <peter@korsgaard.com> (cherry picked from commit 6c872197f412b011ceefc6fb5ebbb34f2fb00c15) [Peter: drop Makefile/Vagrantfile changes] Signed-off-by:
Peter Korsgaard <peter@korsgaard.com>
-
Marcus Hoffmann authored
This tests valdates that we can publish a message and read it back. Signed-off-by:
Marcus Hoffmann <marcus.hoffmann@othermo.de> Tested-by:
Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> [yann.morin.1998@free.fr: - don't manually start mosquitto, there's a startup script for that - don't pass custom timeout ] Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
Marcus Hoffmann authored
Fixes the following error on calling mqtt.publish(): File "/usr/lib/python3.10/site-packages/paho/mqtt/publish.py", line 222, in single multiple([msg], hostname, port, client_id, keepalive, will, auth, tls, File "/usr/lib/python3.10/site-packages/paho/mqtt/publish.py", line 126, in multiple if not isinstance(msgs, collections.Iterable): AttributeError: module 'collections' has no attribute 'Iterable' Backported from https://github.com/eclipse/paho.mqtt.python/pull/497/ This was deprecated in python 3.9 and stopped working in python 3.10 Signed-off-by:
Marcus Hoffmann <marcus.hoffmann@othermo.de> Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
Peter Korsgaard authored
This was naturally 2022.05.1, NOT 2021.05.1. Signed-off-by:
Peter Korsgaard <peter@korsgaard.com>
-
Peter Korsgaard authored
Signed-off-by:
Peter Korsgaard <peter@korsgaard.com>
-
Peter Korsgaard authored
Signed-off-by:
Peter Korsgaard <peter@korsgaard.com> (cherry picked from commit bf0d8c96599f3dc09d8fa7b706c3cf19294fd70e) [Peter: drop Makefile changes] Signed-off-by:
Peter Korsgaard <peter@korsgaard.com>
-
- Aug 30, 2022
-
-
Marcus Hoffmann authored
See: https://security-tracker.debian.org/tracker/CVE-2022-37434 Signed-off-by:
Marcus Hoffmann <marcus.hoffmann@othermo.de> Signed-off-by:
Arnout Vandecappelle <arnout@mind.be>
-
Marcus Hoffmann authored
gnu vendor is not found for zlib in CPE database [1]. zlib is the correct vendor [2]. [1] https://nvd.nist.gov/products/cpe/search/results?namingFormat=2.3&keyword=cpe:2.3:a:gnu:zlib [2] https://nvd.nist.gov/products/cpe/search/results?namingFormat=2.3&keyword=cpe:2.3:a:zlib:zlib Signed-off-by:
Marcus Hoffmann <marcus.hoffmann@othermo.de> Signed-off-by:
Arnout Vandecappelle <arnout@mind.be>
-
Romain Naour authored
There is currently no version of gdbserver for or1k. Until this is implemented we will prevent both the direct and indirect selection of gdbserver for or1k builds. In practice this means that 'cross gdb for the host' cannot be selected and that 'full debugger' must be automatically selected for the gdb target package. This partially reverts commit 991b7b99 which claimed that gdbserver for or1k was already supported before version 8.3. That is not true - the commit that adds gdbserver support for or1k [1] was only merged for version 12.1, which hasn't been integrated in Buildroot yet. Without that support, the build of gdbserver fails with /home/buildroot/autobuild/instance-1/output-1/host/opt/ext-toolchain/bin/../lib/gcc/or1k-buildroot-linux-musl/11.2.0/../../../../or1k-buildroot-linux-musl/bin/ld: server.o: in function `main': server.cc:(.text.startup+0x6dc): undefined reference to `initialize_low()' /home/buildroot/autobuild/instance-1/output-1/host/opt/ext-toolchain/bin/../lib/gcc/or1k-buildroot-linux-musl/11.2.0/../../../../or1k-buildroot-linux-musl/bin/ld: remote-utils.o: in function `prepare_resume_reply(char*, ptid_t, target_waitstatus*)': remote-utils.cc:(.text+0x28a8): undefined reference to `using_threads' /home/buildroot/autobuild/instance-1/output-1/host/opt/ext-toolchain/bin/../lib/gcc/or1k-buildroot-linux-musl/11.2.0/../../../../or1k-buildroot-linux-musl/bin/ld: remote-utils.cc:(.text+0x28b0): undefined reference to `using_threads' Fixes: http://autobuild.buildroot.net/results/b3c/b3c0df53d09d9facaf0c3c2bc4529f9fcf7737ee [1] https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=4933265c3f71b9134363d0c05f09542d5cc677f4 Signed-off-by:
Romain Naour <romain.naour@gmail.com> Cc: Stafford Horne <shorne@gmail.com> Signed-off-by:
Arnout Vandecappelle <arnout@mind.be>
-
Romain Naour authored
Commit [1] enabled glibc on or1k since it's now supported but it requires a toolchain with linux-headers >= 5.4. From [2]: "Here we define the minumum linux kernel version at 5.4.0, as that is the long term support version where 32-bit architectures start to support 64-bit time API's. The OpenRISC kernel had some bugs up until version 5.8 which caused issues with glibc fork/clone, they have been backported to 5.4 but not previous versions." Fixes: checking installed Linux kernel header files... 3.2.0 or later checking for kernel header at least 5.4.0... too old! configure: error: *** The available kernel headers are older than the requested https://gitlab.com/buildroot.org/toolchains-builder/-/jobs/2875256686 [1] 68d0aede [2] https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=0c3c62ca7d9ff3bdacdd13e636bc858101e3e288 Signed-off-by:
Romain Naour <romain.naour@gmail.com> Signed-off-by:
Arnout Vandecappelle <arnout@mind.be>
-
Fabrice Fontaine authored
openssl is an optional dependency since version 1.5.13 and https://github.com/memcached/memcached/commit/ee1cfe3bf9384d1a93545fc942e25bed6437d910 which must be handled through pkg-config to avoid static build failure Signed-off-by:
Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by:
Arnout Vandecappelle <arnout@mind.be>
-
Romain Naour authored
While building host-rust with a musl based toolchain without C++ compiler, the build fail since libunwind bundled in rust sources needs a C++ compiler. cargo:warning=i686-buildroot-linux-musl-gcc.br_real: error: [...]/host-rust-1.62.0/src/llvm-project/libunwind/src/Unwind-EHABI.cpp: C++ compiler not installed on this system Note: the issues can't be reproduced with a glibc based toolchain without C++ probaly due to extra steps required to support musl libc. We could add the C++ dependency direclty to host-rustc but it would requires adding the C++ reverse dependencies to all rust packages. Instread, we add the C++ dependency to BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS only when a musl toolchain is used. So we can still install a prebuilt rust compiler but without the rust standard library (rust-std). Usually we should not add toolchain dependencies in a _ARCH_SUPPORTS option but BR2_PACKAGE_HOST_RUSTC_TARGET_TIER... options contains already some BR2_TOOLCHAIN_USES_GLIBC or BR2_TOOLCHAIN_USES_MUSL. Fixes: http://autobuild.buildroot.org/results/636/636fb39c8f1b8c05e4ca451ac506cd63c7166d82 Signed-off-by:
Romain Naour <romain.naour@smile.fr> Reviewed-by:
Nicolas Tran <nicolas.tran@smile.fr> Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
Michael Nosthoff authored
fixes: - Fixed comparison of maps in Python. Signed-off-by:
Michael Nosthoff <buildroot@heine.tech> Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
- Aug 29, 2022
-
-
Yann E. MORIN authored
To report usable tracebacks, pyc files embed the path of the original py files, so that users can more easily try and debug the reported issue. We generate the pyc files by calling the python3-supplied compileall script, to scan the directory where python modules are installed. Since this is done on the build machine, we tell compileall.py to strip away the TARGET_DIR prefix, as that has no meaning at runtime. However, compileall.py forgets [0] to keep a leading / in the front of the paths, thus generating non-rooted paths., e.g.: /path/buildroot.ouput/targt/usr/lib/python3.10/argparse.py gets embedded as: usr/lib/python3.10/argparse.py This is a bit confusing but, as far as we could see, should be mostly be used for display purposes in tracebacks, and does not seem to impact actual functionality. We fix that by instructing compileall.py that the embedded paths should be rooted to / which generates proper paths in tracebacks. And alternate solution would be to swith gears, and tell compileall.py exactly the resulting runtime "base" directory, which replaces the stripping and prefixing; i.e. it's either: -s $(TARGET_DIR) -p / or -d /usr/lib/python$(PYTHON3_MAJOR_VERSION) We choose to keep the first solution, because that is semantically what we really want to do: to strip the leading build-time path, rather than to force anything. Note: the python test-suite was executed with both solutions (in a pyc-only setup), and the results were exactly the same; so in practice, -d or -s+-p yield the same results. Many thanks go to Vincent for reporting the issue and suggesting the solutions. [0] Not sure whether this is a bug or a feature... Reported-by:
Vincent Fazio <vfazio@xes-inc.com> Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr> Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
-
Yann E. MORIN authored
This reverts commit 0be1c3e9. The actual issue is more complex. The problem purportedly fixed was not caused by a missing libupsclient (it was present), but by a missing type definition for time_t (on a musl toolchain). Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
Fabrice Fontaine authored
Disable libupsclient to avoid the following build failure if libupsclient is installed on host: src/nut.c:40:2: error: #error "Unable to determine the UPS connection type." 40 | #error "Unable to determine the UPS connection type." | ^~~~~ src/nut.c:46:3: error: unknown type name 'collectd_upsconn_t' 46 | collectd_upsconn_t *conn; | ^~~~~~~~~~~~~~~~~~ libupsclient is an optional dependency of nut plugin since version 5.10.0 and https://github.com/collectd/collectd/commit/bc2d94024d0250211c1e498db1b43bb4525324da Fixes: - http://autobuild.buildroot.org/results/22b758097e8fb72c68e41329cbc7abc748d81ca6 Signed-off-by:
Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
Fabrice Fontaine authored
Fix CVE-2022-25484, CVE-2022-27416, CVE-2022-27418, CVE-2022-27939, CVE-2022-27940, CVE-2022-27941, CVE-2022-27942, CVE-2022-28487, CVE-2022-37047, CVE-2022-37048, CVE-2022-37049 https://github.com/appneta/tcpreplay/releases/tag/v4.4.2 Signed-off-by:
Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
- Aug 28, 2022
-
-
Fabrice Fontaine authored
This is a bug-fix release, fixing a $edit_headers bug on MacOS, along with a few other small bugs. It also tightens the $query_command parser to accept a single tab between fields, and changes $pager to accept a %s expando. https://gitlab.com/muttmua/mutt/-/blob/mutt-2-2-7-rel/ChangeLog Signed-off-by:
Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
Julien Olivain authored
The script "utils/check-package" checks that patch email prefix are not be numbered. See: https://git.buildroot.org/buildroot/tree/utils/checkpackagelib/lib_patch.py?h=2022.08-rc1#n42 The error message recommends to generate patches to be included in Buildroot with the command 'git format-patch -N'. The patch policy section in the Buildroot manual does mention that. This commit adds a note about that requirement. Signed-off-by:
Julien Olivain <ju.o@free.fr> Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
Fabrice Fontaine authored
Disable -Werror to avoid the following build failure: In file included from hash.c:7: xxhash.h:2667:5: error: #warning is a GCC extension [-Werror] 2667 | # warning "XXH3 is highly inefficient without ARM or Thumb-2." | ^~~~~~~ xxhash.h:2667:5: error: #warning "XXH3 is highly inefficient without ARM or Thumb-2." [-Werror=cpp] Fixes: - http://autobuild.buildroot.org/results/3124bae73c207f1a118e57e41e222ef464ccb297 Signed-off-by:
Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
Fabrice Fontaine authored
Fix CVE-2022-2257, CVE-2022-2264, CVE-2022-2284, CVE-2022-2285, CVE-2022-2286, CVE-2022-2287, CVE-2022-2288, CVE-2022-2289, CVE-2022-2304, CVE-2022-2343, CVE-2022-2344, CVE-2022-2345, CVE-2022-2522, CVE-2022-2571, CVE-2022-2580, CVE-2022-2581, CVE-2022-2598, CVE-2022-2816, CVE-2022-2817, CVE-2022-2819, CVE-2022-2845, CVE-2022-2849, CVE-2022-2862, CVE-2022-2874, CVE-2022-2889, CVE-2022-2923, CVE-2022-2946, CVE-2022-2980 CVE-2022-2982 Signed-off-by:
Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
Fabrice Fontaine authored
Fix the following build failure without threads raised since bump to version 1.17.1 in commit 3f121357 and https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgme.git;a=commit;h=f3177d3ee0a1d30e15f33ff226b5e4c96b7610db: run-wkdlookup.cpp: In function 'int main(int, char**)': run-wkdlookup.cpp:130:18: error: 'std::this_thread' has not been declared 130 | std::this_thread::sleep_for(std::chrono::milliseconds{250 * cnt}); | ^~~~~~~~~~~ Fixes: - http://autobuild.buildroot.org/results/2915f6105bae595274fabaa12de7cc53926d22d0 Signed-off-by:
Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
Fabrice Fontaine authored
cpe:2.3:a:minetest:minetest is a valid CPE identifier for this package: https://nvd.nist.gov/products/cpe/search/results?namingFormat=2.3&keyword=cpe%3A2.3%3Aa%3Aminetest%3Aminetest Signed-off-by:
Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
- Aug 27, 2022
-
-
Jesse Van Gavere authored
Add license hashes to the hash file and add the information into the makefile. Signed-off-by:
Jesse Van Gavere <jesseevg@gmail.com> [Arnout: use correct file names and hashes] Signed-off-by:
Arnout Vandecappelle <arnout@mind.be>
-
Jesse Van Gavere authored
Hash file with just the qt6base tarball hash Signed-off-by:
Jesse Van Gavere <jesseevg@gmail.com> Signed-off-by:
Arnout Vandecappelle <arnout@mind.be>
-
Fabrice Fontaine authored
libcamera needs gcc >= 8 since bump to 8a845ab078c3fe12ac4edd16c8cbac5b7ec03b98 in commit 64f67ede and https://git.libcamera.org/libcamera/libcamera.git/commit/?id=a7ab5ef1d2f9b05056db450e631a99a73382d589: ../output-1/build/libcamera-ba6435930f08e802cffc688d90f156a8959a0f86/meson.build:82:8: ERROR: Problem encountered: gcc version is too old, libcamera requires 8.0 or newer Fixes: - http://autobuild.buildroot.org/results/f8eba0e564d03b83fcda4085baec16a4857c7d25 Signed-off-by:
Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
Fabrice Fontaine authored
Fix typo added by commit 84d32e53: configure: error: invalid variable name: `ac_cv_path_krb5-config' Fixes: - http://autobuild.buildroot.org/results/5a0e5023c274223b5eb7623165395549e7f446bf Signed-off-by:
Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
Fabrice Fontaine authored
Fix the following build failure: In file included from libavcodec/ppc/audiodsp.c:31: libavcodec/ppc/audiodsp.c: In function 'scalarproduct_int16_altivec': ./libavutil/ppc/util_altivec.h:123:5: error: implicit declaration of function 'vec_vsx_ld'; did you mean 'vec_vslh'? [-Werror=implicit-function-declaration] 123 | vec_vsx_ld(offset, b) | ^~~~~~~~~~ Fixes: - http://autobuild.buildroot.org/results/b772d285f978ff9bc3b07872d009633c943f20b1 VSX is indeed an extension to AltiVec, so havinf VSX implies having AltiVec [0], so we can condition he altivec support on LE ,on VSX being available. To be noted, however, is that ffmpeg has a configre switch dedicated to VSX: --enable-vsx. We do not use it add support for that here, as we are just fixing the AltiVec support. Adding VSX configure flag is left as an excercise for a future feature addition. [0] https://en.wikipedia.org/wiki/AltiVec#VSX_(Vector_Scalar_Extension) Signed-off-by:
Fabrice Fontaine <fontaine.fabrice@gmail.com> [yann.morin.1998@free.fr: - add comment in .mk - exend commit log to explain VSX implies AltiVec ] Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
Adrian Perez de Castro authored
This update fixes a potential memory allocation issue. There is no associated advisory, though. Release notes: https://wpewebkit.org/release/libwpe-1.12.1.html https://wpewebkit.org/release/libwpe-1.12.2.html https://wpewebkit.org/release/libwpe-1.12.3.html Signed-off-by:
Adrian Perez de Castro <aperez@igalia.com> Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
Yann E. MORIN authored
Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
Fabrice Fontaine authored
tools needs C++ since the addition of the package in commit 27ad470d resulting in the following build failure: no -DHAVE_CONFIG_H -I. -I.. -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -I../include -I../master -Wall -DREV=`if test -s ../revision; then cat ../revision; else hg id -i .. 2>/dev/null || echo "unknown"; fi` -fno-strict-aliasing -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Ofast -g0 -c -o ethercat-Command.o `test -f 'Command.cpp' || echo './'`Command.cpp /bin/bash: line 1: no: command not found Fixes: - http://autobuild.buildroot.org/results/89d096006839f32a3d03786e69e51ec3c5ea70f6 Signed-off-by:
Fabrice Fontaine <fontaine.fabrice@gmail.com> [yann.morin.1998@free.fr: move it before package's options] Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
Fabrice Fontaine authored
Fix CVE-2022-2652: Depending on the way the format strings in the card label are crafted it's possible to leak kernel stack memory. There is also the possibility for DoS due to the v4l2loopback kernel module crashing when providing the card label on request (reproduce e.g. with many %s modifiers in a row). https://github.com/umlaeute/v4l2loopback/blob/v0.12.7/ChangeLog Signed-off-by:
Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
Fabrice Fontaine authored
cpe:2.3:o:v4l2loopback_project:v4l2loopback is a valid CPE identifier for this package: https://nvd.nist.gov/products/cpe/search/results?namingFormat=2.3&keyword=cpe%3A2.3%3Ao%3Av4l2loopback_project%3Av4l2loopback Signed-off-by:
Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
Fabrice Fontaine authored
Fix CVE-2021-46784: In Squid 3.x through 3.5.28, 4.x through 4.17, and 5.x before 5.6, due to improper buffer management, a Denial of Service can occur when processing long Gopher server responses. https://github.com/squid-cache/squid/security/advisories/GHSA-f5cp-6rh3-284w Signed-off-by:
Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
Fabrice Fontaine authored
Fix CVE-2021-46828: In libtirpc before 1.3.3rc1, remote attackers could exhaust the file descriptors of a process that uses libtirpc because idle TCP connections are mishandled. This can, in turn, lead to an svc_run infinite loop without accepting new connections. https://sourceforge.net/projects/libtirpc/files/libtirpc/1.3.3/Release-1.3.3.txt/download Signed-off-by:
Fabrice Fontaine <fontaine.fabrice@gmail.com> Reviewed-by:
Petr Vorel <petr.vorel@gmail.com> Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
Fabrice Fontaine authored
Fix typo: EDK2_LICENSE_FILE -> EDK2_LICENSE_FILES added by commit 1074a37e Signed-off-by:
Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
Fabrice Fontaine authored
Fix typo: EDK2_PLATFORMS_LICENSE_FILE -> EDK2_PLATFORMS_LICENSE_FILES added by commit 33aa59e7 Signed-off-by:
Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-
Fabrice Fontaine authored
Fix typo: MALI_DRIVER_LICENSE_FILE -> MALI_DRIVER_LICENSE_FILES added by commit f3ecd9ea Signed-off-by:
Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr>
-