Changelog:
=========
-BREAKING & SECURITY: The archive extraction functions now pass 3 security flags
(SECURE_NODOTDOT, SECURE_NOABSOLUTEPATHS and SECURE_SYMLINKS) to libarchive by
default, unless the current directory is the root.
-BREAKING: The ArchiveEntry properties atime, mtime, ctime, birthtime and size
now have the value None instead of 0 when they're unset.
-BREAKING: The ArchiveEntry.pathname property now attempts to decode bytes using
UTF-8. This breaks reading archives that contain file names which look like
UTF-8 but aren't, if such a thing exists. Proper support of encodings will
probably be added in the next version.
-Multiple entries from the same archive can now be kept in memory, however only
the current entry's content can be read.
-The filetype, linkpath, size, mode, redvmajor, redvminor, uid and gid
attributes of an archive entry can now be modified.
-The four time properties of archive entries now have setters, so for example
entry.set_mtime(0, 0) can be replaced by entry.mtime = 0.
-Archive entries have 4 new properties: perm, rdev, uname and gname.
-When adding files to an archive, a destination path can now be specified.
-The ArchiveRead class now has a bytes_read property.
-The ArchiveWrite class now has a bytes_written property.
-Python 3.6 is no longer tested.
-The documentation has been improved.
(From OE-Core rev: 9adbc075c5a2b396d991144596fd92ebe16d4154)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
v6.4.2
* fix#671 : NoReturn is not avaliable in painfully dead python 3.6
v6.4.1
* fix regression #669: restore get_version signature
* fix#668: harden the selftest for distribution extras
v6.4.0
* compatibility adjustments for setuptools >58
* only put minimal setuptools version into toml extra to warn people with old strict pins
* coorectly handle hg-git self-use
* better mercurial detection
* modernize packaging setup
* python 3.10 support
* better handling of setuptools install command deprecation
* consider pyproject.tomls when running as command
* use list in git describe command to avoid shell expansions while supporting both windows and posix
* add --strip-dev flag to python -m setuptools_scm to print the next guessed version cleanly
* ensure no-guess-dev will fail on bad tags instead of generating invalid versions
* ensure we use utc everywhere to avoid confusion
References:
https://github.com/pypa/setuptools_scm/issues/668https://github.com/pypa/setuptools_scm/issues/669https://github.com/pypa/setuptools_scm/issues/671
(From OE-Core rev: 3ac37c743470ab778bc47110660f3e1b37c534ba)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6.36.0 - 2022-01-19
* This release disallows using typing.Final with from_type() and register_type_strategy().
- Why? Because Final can only be used during class definition. We don’t generate class attributes.
- It also does not make sense as a runtime type on its own.
(From OE-Core rev: 5044bb45748887b01e857554976fe1eeb16921dd)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
ruby's makefiles are rebuilding several items on every invocation,
even if nothing changed, all of which are factored into libruby.so
and cause it to be relinked as well. This does not seem to affect plain
make invocation, but does cause races in make install:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14695
Rather than figure out how to use make properly and convince upstream
of it, let's just do serial installs and file a bug:
https://bugs.ruby-lang.org/issues/18506
(From OE-Core rev: 1dc5cdf683133d210658eba9a619b737ec95cfe3)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
0001-btrfs-tools-include-linux-const.h-to-fix-build-with-.patch
removed since it is included in 5.16
Add 0001-btrfs-progs-kerncompat-add-local-definition-for-alig.patch
to fix "undefined reference to `__ALIGN_KERNEL'".
Changelog:
=========
- rescue: new subcommand clear-uuid-tree to fix failed mount due to bad uuid
subvolume keys, caught by tree-checker
- fi du: skip inaccessible files
- prop: properly resolve to symlink targets
- send, receive: fix crash after parent subvolume lookup errors
- build:
fix build on 5.12+ kernels due to changes in linux/kernel.h
fix build on musl with old kernel headers
- other:
error handling fixes, cleanups, refactoring
extent tree v2 preparatory work
lots of RST documentation updates (last release with asciidoc sources),
https://btrfs.readthedocs.io
(From OE-Core rev: 420191dc951f04b36645ffae2d946b50150feab0)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Remove patch as upstream addressed the issue.
(From OE-Core rev: cf11425c460ee4ff6b7ac0221a21b13b2d2b7e1e)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
License-Update: copyright years
(From OE-Core rev: d6515a7f58d0405efea21e3be4158681ed9edbe6)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Backport patches to epiphany/gcr/g-i to address failures with new meson.
(From OE-Core rev: 2ab302edc33681f94b2cd85b564f6feebe154392)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This allows automated version updates when possible, and reduces friction in manual ones.
(From OE-Core rev: 54d4a767ab7beaa64cfc4c221317ea03b0b119ab)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
https://lore.kernel.org/all/c31dba4f-42a8-ba48-7df2-b56bf4699a4c@sigma-star.at/t/
Roughly half a year after the last release, this is a smaller, patch level
release that primarily consists of a hand full of fixes that have accumulated
since then.
This includes some fixes regarding the user space ports of mtd-tests using the
wrong page size, and most recently a fix regarding a missing jffs2 kernel header
in the last release tarball, causing build failures on some systems.
Changes from 2.1.3 to 2.1.4:
Features:
- ubiscan debugging and statistics utility
Fixes:
- Some mtd-tests erroneously using sub-pages instead of the full page size
- Buffer overrun in fectest
- Missing jffs2 kernel header in the last release, leading to build
failures on some systems.
(From OE-Core rev: e2102d25a1ca789d6cf90f68cece5a63c711c25c)
Signed-off-by: Denys Dmytriyenko <denis@denix.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
License-Update: year updated to 2022.
Changelog:
=========
Improvements
-----------
-Implemented --secontext=mismatch option to find mismatches in SELinux contexts.
-Implemented decoding of futex_waitv syscall introduced in Linux 5.16.
-Implemented decoding of BPF_LINK_GET_NEXT_ID and BPF_LINK_GET_FD_BY_ID bpf
syscall commands.
-Enhanced decoding of BPF_MAP_CREATE, BPF_PROG_TEST_RUN, and BPF_PROG_LOAD
bpf syscall commands.
-Enhanced decoding of BTRFS_IOC_FS_INFO ioctl command.
-Updated lists of AUDIT_*, BPF_*, BTRFS_*, DEVCONF_*, FAN_*, ETH_P_*,
IPV4_DEVCONF_*, KVM_*, NDA_*, SO_*, and V4L2_* constants.
-Updated lists of ioctl commands from Linux 5.16.
Bug fixes
---------
-Fixed build for older Android.
(From OE-Core rev: e213db717fa274db6dcab6f0b6b0728a87b8d803)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
License-Update: year updated to 2022.
Changelog:
=========
The NumPy 1.22.1 is maintenance release that fixes bugs discovered after
the 1.22.0 release. Notable fixes are:
Fix f2PY docstring problems
Fix reduction type problems
Fix various typing bugs.
The Python versions supported for this release are 3.8-3.10.
(From OE-Core rev: 7e42e8bbe4eb97316201640b43cafbbaf916e6e5)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6.35.0 - 2022-01-08¶
This release disallows using typing.ClassVar with from_type() and register_type_strategy().
Why? Because ClassVar can only be used during class definition. We don’t generate class attributes.
It also does not make sense as a runtime type on its own.
6.34.2 - 2022-01-05¶
This patch updates our vendored list of top-level domains, which is used by the provisional domains() strategy.
(From OE-Core rev: 836cec0b8096f157ae7051d34efbe637ff211617)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Commit 9985b17a30bb ("go: correctly set debug-prefix-map and build
directory") has changed CGO_LDFLAGS to the manually crafted version of
LDFLAGS to strip out DEBUG_PREFIX_MAP contents.
However this manually crafted version includes ${SECURITY_LDFLAGS}.
If security_flags.inc is not included, the variable is not defined, thus
CGO_LDFLAGS will include the '${SECURITY_LDFLAGS}' literally. When
building the recipe, the build would break with the follwing message:
aarch64-linaro-linux-gcc: error: ${SECURITY_LDFLAGS}: No such file or directory
So, instead of manually specifying variable contents, perform the
expected action: filter offending arguments out of LDFLAGS.
Cc: Alexander Kanavin <alex.kanavin@gmail.com>
(From OE-Core rev: e7d2d68679c1980d9e889d96c3eab49589f5b832)
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Turn on "link external modules statically" option
as otherwise ruby installer tries to do additional
building inside installed module directories in do_install
which fails horribly.
License-Update: additional MIT/BSD items
(From OE-Core rev: 4d4485442830bb52b152f0419f4ff9f1d581d46a)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
pthread has been merged into the main libc library
(and was never separate in musl), so separate linking
for it is no longer needed.
I ran the reproducing sequence on qemux86, qemux86_64 and same targets with musl,
and it went fine:
root@qemux86:~# python3
Python 3.10.0 (default, Oct 4 2021, 17:55:55) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import multiprocessing
>>> pool_sema = multiprocessing.BoundedSemaphore(value=1)
>>> pool_sema.acquire()
True
>>> pool_sema.release()
>>>
(From OE-Core rev: 2eabd3b611f4afa5eafa4490b6b0ef7578b742de)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Upstream dropped the now deprecated distutils:
18995d65 Remove distutils which are deprecated in python3.10 (RhBug:1950229)
Usage was replaced with sysconfig, which is in python3-core
[YOCTO #14610]
(From OE-Core rev: 93e9b006007ef1afc79c45b48fd92c9e384ff6cb)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
No longer depend on python3-distutils, current versions of setuptools
vendor as _distutils.
[YOCTO #14610]
(From OE-Core rev: 2b6735f648744c42484afec6edab6d5e130111e2)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
While building GCC it checks whether the include directory exists,
if it doesnt it throws an error and exits:
| The directory that should contain system headers does not exist:
| tmp/work/x86_64-nativesdk-pokysdk-linux/gcc-cross-canadian-riscv32/
11.2.0-r0/recipe-sysroot/usr/include/
| make[1]: *** [Makefile:3257: stmp-fixinc] Error 1
Even though for the baremetal toolchain not having this directory
does make sense.
We overcame this by removing the --with-sysroot=/not/exist argument
for baremetal toolchains (via TARGET_OS override), however, the
newlib toolchain does have headers and an includedir, hence by fixing
the baremetal toolchain we broke the newlib one since it uses the same
TARGET_OS as baremetal, causing for example (on newlib):
/sdk/sysroots/x86_64-pokysdk-linux/usr/lib/riscv32-poky-elf/gcc/
riscv32-poky-elf/11.2.0/include/stdint.h:9:16:
fatal error: stdint.h: No such file or directory
| # include_next <stdint.h>
^~~~~~~~~~
compilation terminated.
By creating a dummy includedir, and removing the previous fix we
allow GCC to be built the same way, unifying the cross compiler
for all targets.
After this fix both TCLIBC=baremetal and TCLIBC=newlib SDKs work
properly.
(From OE-Core rev: 08ff7c87efdf373f1874fcccd9a2a73fc0efef30)
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandro@enedino.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The "gcc: Fix compile of gcc plugins" patch had a typo making it a noop.
This was due to a rework to make it specific to the linux64.h header.
(From OE-Core rev: 5f0f00f0988c02d7fe0fa62edf3e4901ce9941a6)
Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The issue is reported upstream:
https://bugs.ruby-lang.org/issues/18456
Otherwise I do not feel that further investigation of rdoc's parser to find
out the source of non-determinism is worth the time.
(From OE-Core rev: 208021f7212a8a790c350ccca720695c5bcbb1ca)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When the tranisiton to perl-cross occured, the threading define
seems to have been missed. The perl tests for threading where
simply skipped, so there was no direct failures. This was verified
by running perl ptest before and after the change to see PASS vs SKIP
results of threaded related tests.
NOTE: Perl officially discourges the use of threads, so this
functionality maybe depercated in the future [0][1]
v2: adds the usethreads to native and nativesdk. This was tested by
builing postresql and rrdtool which use perl and automake.
[0] https://perldoc.perl.org/5.34.0-RC2/threads#WARNING
[1] https://perldoc.perl.org/perlpolicy#discouraged
(From OE-Core rev: b9fd7cd319a1d8f0ddf5ea60710b015e9afb588c)
Signed-off-by: Saul Wold <saul.wold@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Without this, compiling gcc plugins will fail with an error similar to:
[...]
fatal error: ./config/i386/linux64.h: No such file or directory
[...]
In Yocto, we set up compiling gcc-cross out of tree. Which in turn makes
the generated headers end up in B. The tm.h header will include
generated headers that are expected in plugin/include/config/*.
For example, the linux64.h header, when generating gcc-cross for x86-64,
will end up in tm.h header as:
include "./config/i386/linux64.h"
On the other hand, the make rule `install-plugin` in gcc/Makefile.in
will install the linux64.h assuming that it is generated in the sources
directory and because this is not the case in our setup, the Makefile
ends up installing it in plugin_includedir/`basename $$path` which ends
up installing the header in [..]plugin/include as opposed to
[..]plugin/include/config/i386 (as expected by the generator of tm.h).
The included patch modifies the Makefile rule to match the assumption of
gcc-cross being compiled out of tree.
(From OE-Core rev: 92167f8e02bb6fbbe1ee6a6678525a0ae27b00a5)
Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
