Django 4.0.x is no longer supported since April 2023.
Upgrade to the latest 4.x LTS release.
Fixes CVEs:
CVE-2024-24680: Potential denial-of-service in intcomma template filter
CVE-2023-43665: Denial-of-service possibility in django.utils.text.Truncator
CVE-2023-41164: Potential denial of service vulnerability in django.utils.encoding.uri_to_iri()
CVE-2023-36053: Potential regular expression denial of service vulnerability in EmailValidator/URLValidator
CVE-2023-31047: Potential bypass of validation when uploading multiple files using one form field
Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The "update" in commit 2af7d3f63e added a SRCREV rather than updating
SRCREV_xfstests. Change the recipe to actually use SRCREV so that it is
compatible with future AUH updates.
Also replace "/usr" with "${prefix}".
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
On start the usbgx service configures the usb gadget. However if
one stops the service nothing is done, a subsequent start then
tries to configure the gadget again and fails. `systemctl restart`
is implemented by doing a stop followed by a start and thus is
also affected.
Doing a start/stop/start results with the following reported in
status:
| systemd[1]: Starting Load USB gadget schemas...
| gadget-start[801]: usbg_create_gadget() duplicate gadget name
| gadget-start[801]:
| gadget-start[801]: Error on import gadget
| gadget-start[801]: Error: USBG_ERROR_EXIST : Already exist
| gadget-start[812]: ls: write error: Device or resource busy
The run-postinsts service does execute a restart for each package
which uses the systemd class which creates a race condition that the
usbgx service is already started when run-postinsts restarts usbgx
and creates the above error output.
Fix that by unconfiguring the usb gadget on stop.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The changes include:
- Change to use meson buildsystem.
- Fix build issues in OE.
- Move patches from files to plymouth subdirectory.
- Make themes build/installation optional, since a user might not want
all themes to be installed to rootfs, now he can set PLYMOUTH_THEMES
to chose the themes.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Add a recipe for the pyyaml-include package that extends PyYAML to include
YAML files within YAML files. Add a ptest to run the unit tests and include
the tests as part of the package lists in meta-python
Signed-off-by: Derek Straka <derek@asterius.io>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Resolves an issue where python3 package generation was failing to configure.
-- Cannot probe for Python/Numpy support (because we are cross-compiling OpenCV)
-- If you want to enable Python/Numpy support, set the following variables:
-- PYTHON2_INCLUDE_PATH
-- PYTHON2_LIBRARIES (optional on Unix-like systems)
-- PYTHON2_NUMPY_INCLUDE_DIRS
-- PYTHON3_INCLUDE_PATH
-- PYTHON3_LIBRARIES (optional on Unix-like systems)
-- PYTHON3_NUMPY_INCLUDE_DIRS
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Introduce cosmetic fixes to recipe file content based on oe-stylize.py
suggestions.
Signed-off-by: Niko Mauno <niko.mauno@vaisala.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The repositorys LICENSE file contains BSD-3-Clause license text, so
update the relevant recipe information field to match.
Signed-off-by: Niko Mauno <niko.mauno@vaisala.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Inheriting setuptools3 implies the inherit of python3native, so drop
the latter inherit as redundant.
Signed-off-by: Niko Mauno <niko.mauno@vaisala.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Update the HOMEPAGE value so that the URL points to the original
repository instead of a fork. By doing this we fix the mismatch
between HOMEPAGE and SRC_URI.
Signed-off-by: Niko Mauno <niko.mauno@vaisala.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Newer versions of the GNU assembler (observed with binutils 2.41) will
complain about the ".arch i386" in files assembled with "as --64",
with the message "Error: 64bit mode not supported on 'i386'".
Fix by moving ".arch i386" below the relevant ".code32" directive, so
that the assembler is no longer expecting 64-bit instructions to be used
by the time that the ".arch i386" directive is encountered.
Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
"openssl rsa" works with RSA keys only. Use "openssl pkey" instead which
is a frontend that picks the right operation automatically and works
with RSA keys, eliptic curve keys and also DSA keys.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
ModuleNotFoundError: No module named 'json'
ModuleNotFoundError: No module named 'logging'
ModuleNotFoundError: No module named 'dataclasses'
ModuleNotFoundError: No module named 'zipfile'
Signed-off-by: alperak <alperyasinak1@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Radically simplified static file serving for Python web apps
With a couple of lines of config WhiteNoise allows your web app
to serve its own static files, making it a self-contained unit
that can be deployed anywhere without relying on nginx, Amazon S3
or any other external service.
https://whitenoise.readthedocs.io/en/latest/
Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
A minimal low-level HTTP client.
This recipe is currently provided without trio support, as the author
has no use for it and it would require to add a new python3-trio recipe.
This recipe uses pypi as source:
https://pypi.org/project/httpcore
Signed-off-by: Richard Leitner <dev@g0hl1n.net>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
High level compatibility layer for multiple asynchronous event loop
implementations.
This recipe is currently provided without trio support, as the author
has no use for it and it would require to add a new python3-trio recipe.
This recipe uses pypi as source:
https://pypi.org/project/anyio
Signed-off-by: Richard Leitner <dev@g0hl1n.net>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Changes 1.26.0:
Brad House (14):
update release notes format
update format slightly
RELEASE-NOTES -> RELEASE-NOTES.md
test: fix outdated license headers
no reason to include sys/random.h all the time (#684)
Do not sanity check RR Name vs Question (#685)
autotools: fix building for 32bit windows due to stdcall symbol mangling (#689)
man ares_fds(3): mark as deprecated and add explanation (#691)
fix doxygen typo
Autotools allow make to override CFLAGS/CPPFLAGS/CXXFLAGS (#695)
Event Subsystem: No longer require integrators to have their own (#696)
adig: Differentiate between internal and server error
Release prep for c-ares 1.26.0 (#698)
clusterfuzz: enforce maximum DNS packet size due to long parser time
Erik Lax (1):
Added flags to are_dns_parse to force RAW packet parsing (#693)
Gregor Jasny (1):
cmake: improve some include related code (#680)
Changes 1.25.0:
Brad House (22):
fix test building with symbol hiding
ci: add test case for building with hidden symbol visibility
ci: disable static for symbol hiding tests
getrandom() may require sys/random.h on some systems
fix support with older google test versions
CI: Add Alpine Linux and old Ubuntu (#667)
Fix bad stub for ares__iface_ips_enumerate()
ahost should use ares_getaddrinfo() these days (#669)
Connection failure should increment server failure count first
sonarcloud: const
clang-format
ares_strsplit() rewrite as wrapper around ares__buf_split()
clang-format
Autotools warning fixes (#671)
Old MacOS SDKs require you include sys/socket.h before net/if.h (#673)
docs: host -> ip
Autotools: rework to simplify and fix recent issues (#674)
set winver consistently across build systems
autotools: update logic for building tests to provide more feedback
OSSFuzz: it assumes autotools builds a static library by default, which means the old autotools must have done that even though there were comments saying it wasn't. Disable static by default on Windows however since it can't build both simultaneously.
tests: replace google DNS with CloudFlare for reverse lookups as google's servers stopped responding properly
1.25.0 release prep (#676)
Gregor Jasny (1):
Fix minor warnings and documentation typos (#666)
Martin Chang (1):
Use SOCK_DNS extension on socket on OpenBSD (#659)
Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Some users would like to be able to share library code between multiple
applications without embedding a static copy.
Signed-off-by: William A. Kennington III <wak@google.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This makes it possible to avoid building components which are not used
in the native or runtime tooling. Most users of nanopb just want to
build `nanopb-generator-native` and `nanopb-runtime` and not the other
two combinations as they are building software for their target
leveraging nanopb.
Signed-off-by: William A. Kennington III <wak@google.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Uses the new nanopb_PYTHON_INSTDIR_OVERRIDE to drop the previous patch.
Maintains compatability with 0.4.7 and older by adding symlinks to the
old header paths.
Signed-off-by: William A. Kennington III <wak@google.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Having useradd class inherited for the -native recipe makes no sense and
emit this kind of warning during reproducibility test:
stdio: WARNING: QA Issue: mariadb-native: native/nativesdk class is not inherited last, this can result in unexpected behaviour. Classes inherited after native/nativesdk: useradd-staticids.bbclass [native-last]
So, move the useradd inherit and associated variables to the target side
of the recipe.
Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Upstream provides a pyproject.toml which declares a flit_core.buildapi build backend for PEP-517 packaging instead of setuptools. Also, RDEPENDS updated according to it.
Removed CLEANBROKEN because it is not necessary.
Changelog:
Version 3.0.1
Fix slow multipart parsing for large parts potentially enabling DoS attacks. CWE-407
Version 3.0.0
Remove previously deprecated code.
Deprecate the __version__ attribute. Use feature detection, or importlib.metadata.version("werkzeug"), instead.
generate_password_hash uses scrypt by default.
Add the "werkzeug.profiler" item to the WSGI environ dictionary passed to ProfilerMiddleware’s filename_format function. It contains the elapsed and time values for the profiled request.
Explicitly marked the PathConverter as non path isolating.
Version 2.3.8
Fix slow multipart parsing for large parts potentially enabling DoS attacks. CWE-407
Version 2.3.7
Use flit_core instead of setuptools as build backend.
Fix parsing of multipart bodies.
Adjust index of last newline in data start.
Parsing ints from header values strips spacing first.
Fix empty file streaming when testing.
Clearer error message when URL rule does not start with slash.
Accept q value can be a float without a decimal part.
Signed-off-by: alperak <alperyasinak1@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
In reproducible test, useradd config comes from static files:
meta-networking/files/static-{passwd,group}-meta-networking
Those files were not coherent :
* an unused "rasvd" was defined (a typo for "radvd")
* passwd referenced a unexisting group id.
This patch aligns static files to the USERADD_PARAM recipe value.
This will fix the errors seen during reproducibility tests:
stdio: ERROR: radvd-2.19-r0 do_prepare_recipe_sysroot: radvd: useradd command did not succeed.
stdio: ERROR: radvd-2.19-r0 do_prepare_recipe_sysroot: ExecutionError('/home/pokybuild/yocto-worker/reproducible-meta-oe/build/build/build-st-meta-networking/build-st/reproducibleA/tmp/work/core2-64-poky-linux/radvd/2.19/temp/run.useradd_sysroot.1178426', 1, None, None)
stdio: ERROR: Logfile of failure stored in: /home/pokybuild/yocto-worker/reproducible-meta-oe/build/build/build-st-meta-networking/build-st/reproducibleA/tmp/work/core2-64-poky-linux/radvd/2.19/temp/log.do_prepare_recipe_sysroot.1178426
stdio: ERROR: Task (/home/pokybuild/yocto-worker/reproducible-meta-oe/build/meta-openembedded/meta-networking/recipes-daemons/radvd/radvd_2.19.bb:do_prepare_recipe_sysroot) failed with exit code '1'
Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
* sometimes make install was failing with:
cp: cannot stat 'group.list': No such file or directory
and bunch of non-fatal messages:
mv: failed to preserve ownership for 'group.list': Invalid argument
* this was when tools/mkgroupfile did
mv -f "$new_groups" "$groupfile"
overwritting the group.list file while install-sh was already
copying it to output
* in the end easily reproducible by
1) removing tests/*/group.list before each make install
2) adding some sleep in mkgroupfile before the mv call
Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
* I'm trying to fix random build failure from world builds:
tests-install sometimes fails as shown bellow:
cp: cannot stat 'group.list': No such file or directory
...
mv: failed to preserve ownership for 'group.list': Invalid argument
whole log:
2023.10.29: http://errors.yoctoproject.org/Errors/Details/752403/
2024.01.14 http://errors.yoctoproject.org/Errors/Details/752404/
* Interestingly I finally triggered this error for first time in my
local build (when rebuilding it after reverting this upgrade -
which might be just coincidence), here is the log:
While looking at this a bit more, I've noticed that install-sh in:
# install-sh script in the project is outdated
# we use the one from the latest libtool to solve installation issues
# It looks like the upstream is not interested in having it fixed :(
# https://www.spinics.net/lists/fstests/msg16981.html
do_configure:prepend() {
cp ${STAGING_DIR_NATIVE}${datadir}/libtool/build-aux/install-sh ${B}
}
is copied only to ${B}, but Makefile still has "cp include/install-sh ."
which was removed in proposed change for upstream:
https://www.spinics.net/lists/fstests/msg16899.html
but here it isn't, so shouldn't we copy it to ${B}/include to make
sure that make won't use the old version?
So I've tried to add:
cp ${STAGING_DIR_NATIVE}${datadir}/libtool/build-aux/install-sh ${B}/include
in do_configure:prepend and then I've triggered the build failure again
this time with 2024.01.14 version as well by running:
for i in `seq -w 1 100`; do bitbake -c cleansstate xfstests; bitbake -k xfstests 2>&1 | tee log.xfstests.$i; done
so the issue isn't fixed in the 2024.01.14 version, but maybe it's
a bug introduced by our install-sh?
It was rejected by upstream in:
https://www.spinics.net/lists/fstests/msg16928.html
This install-sh has been used for performance reason, I'd like keep it
if possible. Would you please describe the failures you hit in
cross-compilation env? It'd be great if we could fix the env issue.
Also the important error isn't:
"mv: failed to preserve ownership for 'group.list': Invalid argument"
because that's shown in all the builds:
xfstests $ grep -c "mv: failed to preserve ownership for 'group.list': Invalid argument" */temp/log.do_install*
2023.10.29-broken/temp/log.do_install:14
2023.10.29-broken/temp/log.do_install.1094046:14
2023.10.29-fixed-after-broken/temp/log.do_install:14
2023.10.29-fixed-after-broken/temp/log.do_install.1094046:14
2023.10.29-fixed-after-broken/temp/log.do_install.1120923:14
2023.10.29/temp/log.do_install:14
2023.10.29/temp/log.do_install.1094046:14
2024.01.14-ok/temp/log.do_install:14
2024.01.14-ok/temp/log.do_install.1186155:14
but the "cp: cannot stat 'group.list': No such file or directory" which is shown only in the ones which in the end failed:
xfstests $ grep cp */temp/log.do_install*
2023.10.29-broken/temp/log.do_install:cp: cannot stat 'group.list': No such file or directory
2023.10.29-broken/temp/log.do_install.1094046:cp: cannot stat 'group.list': No such file or directory
2023.10.29-fixed-after-broken/temp/log.do_install.1094046:cp: cannot stat 'group.list': No such file or directory
2023.10.29/temp/log.do_install:cp: cannot stat 'group.list': No such file or directory
2023.10.29/temp/log.do_install.1094046:cp: cannot stat 'group.list': No such file or directory
So I guess we should just drop this install-sh hack from do_configure completely
as cross-compilation seems to be fixed upstream already in:
https://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git/commit/?id=5d20084fefaf09e86be26d7c71bd1c7ac2a2b35c
xfstests/2024.01.14-ok/git $ git log --oneline include/install-sh
fa993e51 include/: spdx license conversion
da7916f7 build: Use the original install-sh file from SGI
xfstests/2024.01.14-ok/git $ git log --oneline install-sh
5d20084f build: allow cros-compilation on chromeOS
e3ca126a xfstests: respect DESTDIR when installing
fa6a7868 xfsqa: more sh to bash conversions
491d467f Add GPL license plate to SGI's files.
d259454b Update copyright annotations and license boilerplates to correspond with SGI Legals preferences. Merge of master-melb:xfs-cmds:24329a by kenmcd.
3ef12e38 Update copyright dates (again)
bc4eb461 Undoes mod: xfs-cmds:slinx:120772a Undo xfs-cmds:slinx:120772a, inadvertently whacked a previous mod.
8ce73f86 Update copyright dates
db6944ec need a copy of this here too.
* buildhistory doesn't show any difference, so all the
files are installed in the same location as before
Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
* QA Issue: /usr/xfstests/src/soak_duration.awk contained in package xfstests requires /usr/bin/awk, but no providers found in RDEPENDS:xfstests? [file-rdeps]
this script which was added with upgrade to 2024.01.14
causes the file-rdeps QA, but awk is used in various
tests files even in older version:
grep -R awk xfstests/2023.10.29/image/usr/xfstests/tests/xfs/ | wc -l
77
e.g.:
xfstests/2023.10.29/image/usr/xfstests/tests/xfs/716: awk '{print $3}')
Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
