Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[pull] master from buildroot:master #361

Merged
merged 98 commits into from
Oct 29, 2024
Merged

Conversation

pull[bot]
Copy link

@pull pull bot commented Oct 29, 2024

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

jameshilliard and others added 30 commits October 27, 2024 19:13
Signed-off-by: James Hilliard <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: James Hilliard <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Release notes: https://sqlite.org/releaselog/3_47_0.html

Signed-off-by: Bernd Kuhls <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Switched _SITE to https.

Changelog: https://github.com/NLnetLabs/ldns/blob/1.8.4/Changelog

Signed-off-by: Bernd Kuhls <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Changelog: https://www.surina.net/soundtouch/README.html (section 5.)

Signed-off-by: Bernd Kuhls <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: Bernd Kuhls <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: Bernd Kuhls <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Drop no longer required python-cffi dependency.

Signed-off-by: James Hilliard <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: James Hilliard <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: Bernd Kuhls <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Migrate build opts to new format.

Signed-off-by: James Hilliard <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: James Hilliard <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: James Hilliard <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: James Hilliard <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Migrate from setuptools to hatch build backend.

Signed-off-by: James Hilliard <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: James Hilliard <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: James Hilliard <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
erthink and others added 28 commits October 28, 2024 15:47
This is bugfix release of stable libmdbx branch.

The most significant fixes since v0.12.10 (the previous version pinned to
buildroot):

 - Fixed the possibility of `SIGSEGV` inside the `coherence_check()` after
   changing the geometry by another process with an increase in the upper
   DB size above the previous in-process limit.

 - Fixed cursor(s) handling opened in parent transactions and closed before
   the completion of nested/child transactions. In such case, closed
   cursors were "resurrected", which led to a leak of memory allocated for
   such cursors.

 - Fixed a possibility of `SIGSEGV` when enabling logging of the
   `MDBX_LOG_TRACE` level in debug builds.

 - Correction of the missing `TXN_END_EOTDONE` in the case the start of
   a reading transaction fails. The mentioned bit-flag was missing in the
   transaction destruction/shutdown path on error its launch. Because of
   this, an attempt was made to destroy the cursors, which led to crash
   debug builds, since the corresponding array is intentionally filled
   with poison pointers.

 - Modification of `mdbx_close_by()` to return an error when trying to
   close the dbi descriptor of a table created and/or modified in a
   still-running transaction. Such premature closure of the descriptor is
   an incorrect use of the API and a violation of the contract/preconditions
   formulated in the description of `mdbx_close_dbi()`.

   However, instead of returning an error, an incorrect closure of the
   descriptor was performed, which could lead to the creation of a table
   with an empty name, leakage of database pages and/or corruption of a
   b-tree structure (wrong reference to the root of a table).

The complete ChangeLog:
    https://gitflic.ru/project/erthink/libmdbx/blob?file=ChangeLog.md

Signed-off-by: Леонид Юрьев (Leonid Yuriev) <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Building package/openssh 9.9p1 with musl failed during linking because
construct_utmp() was referenced due to "use construct_utmp to
construct btmp records" [1], but not built as utmp is disabled in the
Buildroot package. The fix comes from upstream and ensures the
construct_utmp function actually gets built when USE_BTMP is set [2].

[1] https://anongit.mindrot.org/openssh.git/commit/?id=671c440786a5a66216922f15d0007b60f1e6733f
[2] https://anongit.mindrot.org/openssh.git/commit/?id=76a618d2842c34c16cd21a4efc7230e2f459008d

Fixes:

  http://autobuild.buildroot.net/results/1e651724373f32e45d122d05fa3a10ac88fe29dc/

Signed-off-by: Fiona Klute (WIWA) <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
When compiling oath-toolkit with PSKC support, with:
BR2_PACKAGE_OATH_TOOLKIT=y
BR2_PACKAGE_OATH_TOOLKIT_PSKC=y

Build is failing on hosts without libxml2, with output:

    make[5]: Entering directory '/buildroot/instance-0/output-1/build/oath-toolkit-2.6.12/libpskc/schemas'
    create -noout \
	    --add "system" "urn:ietf:params:xml:ns:keyprov:pskc" \
		    "/buildroot/instance-0/output-1/build/oath-toolkit-2.6.12/libpskc/schemas/pskc-schema.xsd" \
	    --add "system" "http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xsd" \
		    "/buildroot/instance-0/output-1/build/oath-toolkit-2.6.12/libpskc/schemas/xmldsig-core-schema.xsd" \
	    --add "system" "http://www.w3.org/TR/2002/REC-xmlenc-core-20021210/xenc-schema.xsd" \
		    "/buildroot/instance-0/output-1/build/oath-toolkit-2.6.12/libpskc/schemas/xenc-schema.xsd" \
	    tmp
    /bin/sh: line 1: create: command not found
    make[5]: [Makefile:1267: catalog-pskc.xml] Error 127 (ignored)

The build needs the "xmlcatalog" command, provided the host-libxml2
package. The previous error log does not show the "xmlcatalog" because
it is not found by autoconf, then substituted by an empty string (we
only see its arguments).

This commit fixes the issue by adding this missing dependency.

Fixes:
https://autobuild.buildroot.org/results/d22b8d9ba1f8a948125b4f9713720d070e208799/

Signed-off-by: Julien Olivain <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
For change log since v2.3.6, see:
https://github.com/FluidSynth/fluidsynth/releases/tag/v2.3.7

Signed-off-by: Julien Olivain <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Fixes:
http://autobuild.buildroot.net/results/fb4/fb4a011f14e87d348a53695868bb5f3b69496fc8/

The build errors occured immediately after bumping ntp to 4.2.8p18 with
buildroot commit 49bd6bb.

Signed-off-by: Bernd Kuhls <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
When compiling jailhouse with BR2_PACKAGE_JAILHOUSE_HELPER_SCRIPTS=y,
build is failing with error:

    Traceback (most recent call last):
      File "/buildroot/output/build/jailhouse-e57d1eff6d55aeed5f977fe4e2acfb6ccbdd7560/setup.py", line 18, in <module>
        setup(name="pyjailhouse", version=version,
      File "/buildroot/output/host/lib/python3.12/site-packages/setuptools/__init__.py", line 108, in setup
        return distutils.core.setup(**attrs)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      ...
      File "/buildroot/output/host/lib/python3.12/sysconfig.py", line 549, in _init_posix
        _temp = __import__(name, globals(), locals(), ['build_time_vars'], 0)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ValueError: Empty module name

This is due to a missing dependency on the target python3 package.

Jailhouse Python scripts are using setuptools with host-python3 which
reads its sysconfig data from the target-python3. See:
https://gitlab.com/buildroot.org/buildroot/-/blob/2024.08.1/package/pkg-python.mk?ref_type=tags#L33

If the target python3 is not installed, this get expanded as an empty
string, leading to this "ValueError: Empty module name" error.

Pure Python packages which are using the python-package infrastructure
usually get this dependency automatically from:
https://gitlab.com/buildroot.org/buildroot/-/blob/2024.08.1/package/pkg-python.mk?ref_type=tags#L295

Here, the jailhouse package rather uses the generic-package
infrastructure, then installs the Python scripts (if enabled) with
dedicated macros. This is why the target python3 is needed.

This commit fixes the issue by adding this missing dependency.

Signed-off-by: Julien Olivain <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
This codifies style elements discussed on the mailing list, most
importantly PID file handling, and adds detailed considerations for
writing start scripts.

References:
https://lore.kernel.org/buildroot/[email protected]/
https://lore.kernel.org/buildroot/20240714223645.39adf8c6@windsurf/
https://lore.kernel.org/buildroot/[email protected]/

Signed-off-by: Fiona Klute (WIWA) <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Changelog:
https://git.kernel.org/pub/scm/libs/ell/ell.git/tree/ChangeLog?h=0.69

Needed for bump of iwd to 3.0.

Signed-off-by: Bernd Kuhls <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: James Hilliard <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Qemu 9.1 recently fixed the RISC-V virt target by adding the missing
default type for block devices [1].

But the qemu command line we use for RISC-V virt is slightly incorrect:

  -drive file=rootfs.ext2,format=raw,id=hd0 -device virtio-blk-device,drive=hd0

With Qemu 9.1, this command line now rejected since it conflict with
the new default bus:

  qemu-system-riscv64: -drive file=rootfs.ext2,format=raw,id=hd0: Drive 'hd0' is already in use because it has been automatically connected to another device (did you need 'if=none' in the drive options?)

Since we are currently still using Qemu 9.0, apply the suggested change by
adding 'if=none'.

Note: '-drive file=rootfs.ext2,format=raw,id=hd0' can be removed
in a followup patch after the qemu version bump 9.1 is merged.

[1] https://gitlab.com/qemu-project/qemu/-/commit/4406ba2b5efce6af64905f827ca244f699db8170

[Romain: rework the commit log]
Signed-off-by: Waldemar Brodkorb <[email protected]>
Signed-off-by: Romain Naour <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Qemu 9.1.0 removed support for NIOS2 emulation, so we can't
no longer test it when updating Qemu zo 9.1.0.
Furthermore it seems that NIOS2 architecture will be soon
deprecated in the toolchain support.

Signed-off-by: Waldemar Brodkorb <[email protected]>
Signed-off-by: Romain Naour <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
See here for changes:
https://wiki.qemu.org/ChangeLog/9.1

The support for the nios2 architecture got removed.

[Romain: Remove BR2_PACKAGE_QEMU_TARGET_NIOS2 from qemu.mk]
Signed-off-by: Waldemar Brodkorb <[email protected]>
Signed-off-by: Romain Naour <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Qemu 9.1 recently fixed the RISC-V virt target by adding the missing
default type for block devices [1].

We no longer need to specify virtio-blk-device on the qemu command line
since it's already the default.

[1] https://gitlab.com/qemu-project/qemu/-/commit/4406ba2b5efce6af64905f827ca244f699db8170

Signed-off-by: Romain Naour <[email protected]>
Cc: Waldemar Brodkorb <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
When bumping the Linux kernel version I inadvertently removed the pinned
linux-headers version from the defconfig which can break the build if
the default kernel version is not v6.10. Pin linux-headers to the
current am62ax-sk kernel version.

Signed-off-by: Bryan Brattlof <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
For details see:

https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/6.7.3/release-note.md

I have removed a couple of patches here, since they are included in this
version:

 - CVE-2024-39936  (qtbase)
 - QTBUG-125066 Configure fails in qttools if PrintSupport is disabled  (qttools)

Signed-off-by: Roy Kollen Svendsen <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
In Qt 6.8.0 this package will be replaced by Qt Graphs. But since it
was requested on the mailinglist we add it now. It will be replaced by
qt6graphs when Qt 6.8.0 is out.

Signed-off-by: Roy Kollen Svendsen <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Use the 'offset' property in genimage.cfg to align the boot partition on
1 MiB boundary. It is clearer than fixing the size of the previous
u-boot partition.

Suggested-by: Thomas Petazzoni <[email protected]>
Signed-off-by: Mattia Narducci <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: Jon Henrik Bjørnstad <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
Signed-off-by: James Hilliard <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>
This is minor release. According to
https://cmake.org/cmake/help/latest/release/3.30.html#updates:

3.30.1, 3.30.2

These versions made no changes to documented features or
interfaces. Some implementation updates were made to support ecosystem
changes and/or fix regressions.

Signed-off-by: Thomas Petazzoni <[email protected]>
@pull pull bot added the ⤵️ pull label Oct 29, 2024
@pull pull bot merged commit 1e9261d into ThomasDevoogdt:master Oct 29, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.