Thomas Petazzoni [Wed, 17 Dec 2025 22:25:38 +0000 (23:25 +0100)]
package/cppcms: change upstream to Github, bump to 2.0.1
cppcms.com now points to a Github page at
https://github.com/artyom-beilis/cppcms which has a 2.0.1 version, so
let's use that. The number of differences to 2.0.0.beta2 is very
small:
$ git log --online v2.0.0.beta2..v2.0.1 b872972 (tag: v2.0.1, origin/master, origin/HEAD, master) Version to 2.0.1 a1914f7 (tag: v2.0.0) Replaced system category with one from predating C++11 (v1.2) because std::system_category does not translate WSAGetLastError results c4febcc Merge pull request #104 from dreaming-augustin/upstream 922cd49 Python 3.12 compatibility: wrap regex in r''. a11e9d4 Merge branch 'cpp11' 3000bc6 (origin/1.2_updates) Merge pull request #99 from dreaming-augustin/master 44e24c7 [#89] cppcms_error fix typo + consistent messages a6d5575 (origin/cpp11) Added backtrace to system error b3aef3b Fixed missing include for stripped down build 463a9a6 Removed IPV6 due to travis limitations f8163c6 Merges from cpp11 31d4fe7 Added verbose log on failure 90bc996 Added Linux to build matrix - so I have fallback if normal build environment fails f78ee39 Added Readme for github a737d5d Merged python3 compatibility from master 0c67544 Support of python 2.7 and python 3 0d121a7 Python3 compatibility 2fc7e38 Python3 compatibility d745869 python3 fix for tmp_cc
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Julien Olivain <ju.o@free.fr>
Indeed, ICU now requires C++17, and while cppcms.mk has some logic to
get C++ flags using icu-config, the -std=c++17 gets ultimately
overridden by the built-in -std=c++11 flag encoded in cppcms
CMakeLists.txt.
To fix this, we have submitted a patch upstream that ensures the
CMAKE_CXX_FLAGS passed on the command line take precedence over the
built-in flags defined in cppcms CMakeLists.txt.
Thomas Petazzoni [Thu, 25 Dec 2025 21:32:57 +0000 (22:32 +0100)]
package/freerdp: fix build with CMake >= 4
freerdp upstream is now at 3.x, far far ahead of what we're using in
Buildroot at the moment. So to fix the CMake >= 4 build, we add a very
simple non-upstreamable patch (upstream 3.x has a much higher CMake
minimum version already).
Thomas Petazzoni [Fri, 26 Dec 2025 17:12:06 +0000 (18:12 +0100)]
package/gli: add patch to fix CMake 4 build
Fixes:
CMake Error at CMakeLists.txt:1 (cmake_minimum_required):
Compatibility with CMake < 3.5 has been removed from CMake.
Update the VERSION argument <min> value. Or, use the <min>...<max> syntax
to tell CMake that the project requires at least <min> but has been updated
to work with policies introduced by <max> or earlier.
Or, add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to try configuring anyway.
Thomas Petazzoni [Wed, 17 Dec 2025 22:33:16 +0000 (23:33 +0100)]
package/cppdb: fix compatibility with CMake 4
Fixes:
CMake Error at CMakeLists.txt:1 (cmake_minimum_required):
Compatibility with CMake < 3.5 has been removed from CMake.
Update the VERSION argument <min> value. Or, use the <min>...<max> syntax
to tell CMake that the project requires at least <min> but has been updated
to work with policies introduced by <max> or earlier.
Or, add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to try configuring anyway.
We didn't submit the patch upstream, because contrary to cppcms, cppdb
seems completely dead. Last commit is from 2012 at
https://sourceforge.net/p/cppcms/code/HEAD/tree/cppdb/.
There are no known autobuilder failures for this issue.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Julien Olivain <ju.o@free.fr>
Maxime Leroy [Mon, 22 Dec 2025 21:56:33 +0000 (22:56 +0100)]
package/libecoli: bump version to 0.10.1
This new version is required to compile grout v0.14.2.
See the release note of the new versions:
https://github.com/rjarry/libecoli/releases/tag/v0.10.1
https://github.com/rjarry/libecoli/releases/tag/v0.10.0
https://github.com/rjarry/libecoli/releases/tag/v0.9.1
Signed-off-by: Maxime Leroy <maxime@leroys.fr> Signed-off-by: Julien Olivain <ju.o@free.fr>
CMake Error at cmake/Embed.cmake:3 (find_program):
Could not find XXD using the following names: xxd
Call Stack (most recent call first):
src/stdlib/CMakeLists.txt:1 (include)
There are no autobuilder failures for this issue at this point, but
the following defconfig exhibits the issue (of course on a host where
xxd is not installed system-wide):
Switched _SITE to github, the previous URL redirects to github.com.
Removed patches which are included in this release.
License file was renamed and updated:
https://github.com/resiprocate/resiprocate/commits/resiprocate-1.13.2/LICENSE.md
Switch build system to cmake, removed apps-specific option:
- sipdial is built if OpenSSL is enabled:
https://github.com/resiprocate/resiprocate/blob/resiprocate-1.13.2/apps/CMakeLists.txt#L6
- clicktocall build is broken
AddressTranslator.cxx: In member function 'void clicktocall::AddressTranslator::
addTranslation(const resip::Data&, const resip::Data&)':
AddressTranslator.cxx:55:16: error: assignment of read-only variable 'flags'
55 | flags |= std::regex_constants::nosubs;
Bernd Kuhls [Sun, 7 Dec 2025 14:42:33 +0000 (15:42 +0100)]
package/{libtorrent, rtorrent}: bump version to 0.15.3
Removed patches which are included in this release.
Switched SITE to github according to http://rtorrent.net/
Both packages need to be bumped together due to version check for
libtorrent by rtorrent:
https://github.com/rakshasa/rtorrent/commit/6f8c1246dc013d1d5c39ecd66373346ac42fe746
https://github.com/OGRECave/ogre/blob/v14.4.1/Docs/13-Notes.md
"The versioning scheme changed with this release. This is the successor
to Ogre 1.12 and the porting efforts are comparable with porting from
1.11 to 1.12."
Thomas Petazzoni [Tue, 23 Dec 2025 18:10:10 +0000 (19:10 +0100)]
package/vim: refactor install target logic
Instead of calling $(MAKE) multiple times, let's call it once, with
all installation targets needed. We introduce a VIM_INSTALL_TARGETS
variable to collect the list of make install targets that need to be
invoked.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Julien Olivain <ju.o@free.fr>
Thomas Petazzoni [Tue, 23 Dec 2025 18:10:08 +0000 (19:10 +0100)]
package/vim: fix reinstallation
While not very common, it is nice when package re-installation
works. Unfortunately the "installlinks" target of vim installs links
with "ln -s", causing a package reinstallation to fail with:
cd /home/thomas/buildroot/br/output-all/target/usr/bin; ln -s vim ex
cd /home/thomas/buildroot/br/output-all/target/usr/bin; ln -s vim view
cd /home/thomas/buildroot/br/output-all/target/usr/bin; ln -s vim rvim
cd /home/thomas/buildroot/br/output-all/target/usr/bin; ln -s vim rview
cd /home/thomas/buildroot/br/output-all/target/usr/bin; ln -s vim vimdiff
ln: failed to create symbolic link 'ex': File exists
ln: failed to create symbolic link 'view': File exists
make[2]: *** [Makefile:2749: /home/thomas/buildroot/br/output-all/target/usr/bin/ex] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [Makefile:2752: /home/thomas/buildroot/br/output-all/target/usr/bin/view] Error 1
ln: failed to create symbolic link 'rvim': File exists
ln: failed to create symbolic link 'rview': File exists
To fix this, we remove the target links before proceeding with the
installation.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Julien Olivain <ju.o@free.fr>
Maxime Leroy [Mon, 15 Dec 2025 11:43:00 +0000 (12:43 +0100)]
package/grout: bump to 0.14.2 version
See the release note of the new versions:
https://github.com/DPDK/grout/releases/tag/v0.14.0
https://github.com/DPDK/grout/releases/tag/v0.14.1
https://github.com/DPDK/grout/releases/tag/v0.14.2
Since v0.14.0, Grout uses the libmnl [1], the dependency are updated in
consequence. Grout also requires VRF support in the kernel, as it creates
a VRF on the Linux side to allow TCP/UDP termination by Linux
applications in different L3 domains. [2]
A few changes in the license files and an actual (sub)-license update:
* django/contrib/gis/measure.py -> formatting change
* django/contrib/admin/static/admin/img -> svg files got uupdated and
the new ones are licensed under CC-BY-4.0; separate LICENSE file got
removed, License is now mentioned in the readme
* django/utils/archive.py -> File got updated, license (which is only
the header) did not change.
Remove the comment about django site having an inconvenient download
URL. We download pretty much all python package from pypi.org, so doing
that for django shouldn't need a separate comment.
Signed-off-by: Marcus Hoffmann <buildroot@bubu1.eu> Signed-off-by: Julien Olivain <ju.o@free.fr>
Marcus Hoffmann [Mon, 22 Dec 2025 14:54:26 +0000 (15:54 +0100)]
package/python-django: security bump to 5.2.9
Fixes:
* CVE-2025-13372: Potential SQL injection in FilteredRelation column aliases on PostgreSQL
* CVE-2025-64460: Potential denial-of-service vulnerability in XML Deserializer
Full release notes: https://docs.djangoproject.com/en/6.0/releases/5.2.9/
Signed-off-by: Marcus Hoffmann <buildroot@bubu1.eu> Signed-off-by: Julien Olivain <ju.o@free.fr>
Joachim Wiberg [Mon, 15 Dec 2025 23:11:37 +0000 (00:11 +0100)]
package/watchdogd: bump to version 4.1
Changes:
- Add watchdogctl list-clients command to display currently subscribed
clients to the process supervisor. Outputs to stdout in either table
format (default) with colored headers, or JSON format with -j/--json
- New global -j, --json option for machine-readable output, currently
supported by list-clients and status commands
- New API: wdog_clients() returns array of wdog_client_t structs for
programmatic access to subscribed clients. See API documentation at
https://codedocs.xyz/troglobit/watchdogd/wdog_8h.html
- Enhance watchdogctl status command to display formatted output by
default, with device information, capabilities, and reset history in
a human-readable table format. Use -j/--json for JSON output
Fixes:
- Generic scripts running more than 1 second would fail with false
"critical error" reports and cause unwanted system reboots due
to uninitialized exit status variable
- watchdogctl reload with tempmon crashes watchdogd
- Issue causing unwanted reboot when watchdogctl reload was called
while a generic monitor script was running
- Fix memory leak in generic monitor with optional script path, would
be triggered on watchdogctl reload
The first of the fixes means we can now drop the backported patch.
Also, the test mode has been dropped from public use, hence it being
removed as well in this commit.
Signed-off-by: Joachim Wiberg <troglobit@gmail.com> Signed-off-by: Julien Olivain <ju.o@free.fr>
Downloading the source tarball is broken since at least Oct 30th, 2024
as reported by the buildroot autobuilders:
https://autobuild.buildroot.net/?reason=libmbus-0.8.0&step=50&start=50
Switching to the github helper provides the correct source code but the
tarball downloaded has a different hash. A quick search did not provide
alternative download locations for the original tarball
libmbus-0.8.0.tar.gz.
To solve the broken build we do not only switch _SITE to github but also
bump the package to 0.9.0 and add autoreconf which needs two directories
being created in _POST_PATCH_HOOKS. One missing directory was already
reported upstream: https://github.com/rscada/libmbus/issues/179
Release notes of this bugfix release:
https://udpcast.linux.lu/mailman3/hyperkitty/list/udpcast@udpcast.linux.lu/thread/JTGZCUMSXYLVT73TIRJJICBX7AWIE4CA/
Switched _SITE and Config.in homepage URL to https.
Bernd Kuhls [Wed, 17 Dec 2025 18:48:22 +0000 (19:48 +0100)]
package/libselinux: host-python3 needs SSL support
Buildroot commit 285097051d4a7dd821f01d15c705867f7e26c635 bumped
python-pip to version 25.3, causing build errors when host-python3 was
built without SSL support:
WARNING: pip is configured with locations that require TLS/SSL,
however the ssl module in Python is not available.
[...]
Could not fetch URL https://pypi.org/simple/setuptools/:
There was a problem confirming the ssl certificate:
HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded
with url: /simple/setuptools/ (Caused by SSLError("Can't connect to
HTTPS URL because the SSL module is not available.")) - skipping
ERROR: Could not find a version that satisfies the requirement setuptools>=40.8.0 (from versions: none)
Reverting the python-pip bump reveals the true cause of the build error
by showing these messages:
WARNING: pip is configured with locations that require TLS/SSL,
however the ssl module in Python is not available.
[...]
DEPRECATION: Building 'selinux' using the legacy setup.py bdist_wheel
mechanism, which will be removed in a future version. pip 25.3 will
enforce this behaviour change. A possible replacement is to use the
standardized build interface by setting the `--use-pep517` option,
(possibly combined with `--no-build-isolation`), or adding a
`pyproject.toml` file to the source tree of 'selinux'.
Discussion can be found at https://github.com/pypa/pip/issues/6334
Selecting BR2_PACKAGE_HOST_PYTHON3_SSL fixes the problem.
Criu, the only other buildroot package using host-python-pip as
dependency, already selects BR2_PACKAGE_HOST_PYTHON3_SSL.
projects / 0xmirror / buildroot.git / log