Boost upgrade hit Snapcast hard again: the process needs to be updated!
This patch is a patchset from badaix/snapcast@develop.
It is based on the following upstream commits:
badaix/snapcast@901b79a213 ("Build failure with boost 1.88.0 #1367")
badaix/snapcast@ffb086b4b3 ("Define BOOST_PROCESS_VERSION=1 globally")
badaix/snapcast@c37a76a4ab ("Add missing includes")
badaix/snapcast@571f6a8f69 ("Include process v1 headers for Boost version >= v1.88.0")
Refs: 3585ddfc44 ("boost: Updates package to version 1.88.0")
Signed-off-by: Szabolcs Hubai <szab.hu@gmail.com>
After revisiting the PR, it didn't even compile because of commit
c50de920a2 ("boost: Updates package to version 1.87.0").
Signed-off-by: Szabolcs Hubai <szab.hu@gmail.com>
Snapcast [1] is a multiroom client-server audio player, where all
clients are time synchronized with the server to play perfectly synced
audio.
It's not a standalone player, but an extension that turns your existing
audio player into a Sonos-like multiroom solution.
Audio is captured by the server and routed to the connected clients.
Several players can feed audio to the server in parallel and clients can
be grouped to play the same audio stream.
One of the most generic ways to use Snapcast is in conjunction with the
music player daemon (MPD) [2] or Mopidy [3].
The inclusion starts with version 0.28.0 because of OpenSSL dependency
issues of version 0.29.0. Newer versions (e.g. 0.32.3, see [4])
with optional OpenSSL support, will be incorporated with flavours,
like "-mini" and "-full" in the upcoming PRs.
More about this topic please check the inclusion PR at [5]!
[1]: https://github.com/badaix/snapcast
[2]: http://www.musicpd.org/
[3]: https://www.mopidy.com/
[4]: https://github.com/badaix/snapcast/blob/develop/changelog.md
[5]: https://github.com/openwrt/packages/pull/23956#discussion_r2330463363Fixes: #23924
Suggested-by: Tianling Shen <cnsztl@immortalwrt.org>
Suggested-by: George Sapkin <george@sapk.in>
Signed-off-by: Szabolcs Hubai <szab.hu@gmail.com>
This commit adds a valid git patch header for each patch, so that
additional information can be stored. This is in this case and 'CVE:' tag.
This can be used by CVE scanner to find out if the patch fixes a CVE.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
This patch fixes the following compilation build error for gcc14:
tftpd_pcre.c:109:37: error: passing argument 1 of 'pcre2_substring_list_free_8' from incompatible p
109 | pcre2_substring_list_free((const PCRE2_UCHAR **)substrlist);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| |
| const PCRE2_UCHAR8 ** {aka const unsigned char **}
In file included from tftpd_pcre.h:24,
from tftpd_pcre.c:35:
I have also submitted the change to the upstream project:
https://github.com/madmartin/atftp/pull/2
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
This patch fixes the following compilation build warning:
logger.c:117:47: warning: format '%li' expects argument of type 'long int', but argument 7 has type
117 | fprintf(log_fp, "%s %s %s[%d.%li]: %s\n", time_buf, hostname,
| ~~^
| |
| long int
118 | log_ident, getpid(), pthread_self(), message);
| ~~~~~~~~~~~~~~
| |
| pthread_t {aka struct __pthread *}
logger.c:124:47: warning: format '%li' expects argument of type 'long int', but argument 7 has type
124 | fprintf(stderr, "%s %s %s[%d.%li]: %s\n", time_buf, hostname,
| ~~^
| |
| long int
125 | log_ident, getpid(), pthread_self(), message);
| ~~~~~~~~~~~~~~
| |
| pthread_t {aka struct __pthread *}
I have also submitted the change to the upstream project:
https://github.com/madmartin/atftp/pull/2
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
The logic in e57cc9898a was flawed causing
gperftools-runtime to fail to get detected when building resulting in:
...
ninja: Entering directory `/scratch/union/build_dir/target-x86_64_glibc/snort3-3.9.1.0'
ninja: error: '/scratch/union/staging_dir/target-x86_64_glibc/usr/lib/libtcmalloc.so', needed by 'src/snort', missing and no known rule to make it
make[2]: *** [Makefile:161: /scratch/union/build_dir/target-x86_64_glibc/snort3-3.9.1.0/.built] Error 1
It was missed due testing in build root that already had gperftools-runtime
built only discovered when building from a clean build root.
This commit fixes this flaw.
Test:
cat <<EOF > .config
CONFIG_TARGET_x86=y
CONFIG_TARGET_x86_64=y
CONFIG_TARGET_x86_64_DEVICE_generic=y
CONFIG_PACKAGE_snort3=y
EOF
make defconfig
grep gperftools-run .config
CONFIG_PACKAGE_gperftools-runtime=y
cat <<EOF > .config
CONFIG_TARGET_qoriq=y
CONFIG_TARGET_qoriq_generic=y
CONFIG_TARGET_qoriq_generic_DEVICE_watchguard_firebox-m300=y
CONFIG_PACKAGE_snort3=y
EOF
make defconfig
grep gperftools-run .config
Signed-off-by: John Audia <therealgraysky@proton.me>
Adjust the variant definition so that DEFAULT_VARIANT is only applied
to the full variant.
Set the title of the full variant to 'full' for menuconfig.
Signed-off-by: Hannu Nyman <hannu.nyman@iki.fi>
The initial EPS is stored on the modem side. When establishing a connection,
it must therefore be deleted if no EPS has been configured. This is because
the system does not know whether one was configured previously.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
The pppd supports the option to configure the name of the network interface
at startup using the ifname option.
The pppd can overwrite the name of the network interface at startup using
the 'ifname' configuration option. If this option is not specified, the new
network interface is created according to the following scheme:
ppp<number>, e.g. ppp0, ppp1 and so on. This can therefore change with
every start if the number has been already assigned to another ppp connection.
In order to always get the same interface name with the modemmanger proto via
ppp, it is created according to the new scheme by setting the 'ifname':
ppp-<uci network interface name>, e.g. ppp-wwan.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
To prevent the keepalived service from starting if there is no valid
configuration yet, the new option enabled is added. This must be set to
true for keepalived to start.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
Only add the first two pieces of information to the configuration file if
there is a valid '/etc/config/keepalived'.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
Before keepalived version '2.3.0' the compilation was not reproducable
because the compile date and other information has been added to the binary.
Starting with version '2.3.0', there is a new compilation option
'--enable-reproducible-build' that makes the binary reproducible.
The data that prevented this has been moved to a separate file,
'/etc/keepalived/keepalived.config-opts'.
This commit enables the reproducable build.
[1] 30d2f75978
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
Bugfixes:
* Fixed infinite loop triggered by OCSP URL parsing errors (thx to Richard Könning for reporting).
* Fixed OPENSSL_NO_OCSP build issues (thx to Dmitry Mostovoy for reporting).
* Fixed default curve selection in FIPS mode with OpenSSL 3.4+.
* Fixed tests with modern Python versions.
* Fixed tests with multiple OpenSSL versions installed.
Features:
* Added provider URI support for "cert" and "key" options.
* Added new "CAstore" service-level option (OpenSSL 3.0+).
* Added "provider" (OpenSSL 3.0+), "providerParameter" (OpenSSL 3.5+), and "setEnv" global options.
* Key file/URI path added to passphrase prompt on Unix.
* PKCS#11 provider installed on Windows.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
Bugfixes:
* Fixed a stapling cache deallocation crash.
* Fixed "redirect" with protocol negotiation.
Features:
* "protocolHost" support for "socks" protocol clients.
* More detailed logs in OpenSSL 3.0 or later.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
Bugfixes
* Fixed a memory leak while reloading stunnel.conf sections with
"client=yes" and "delay=no".
* Fixed TIMEOUTocsp with values greater than 4.
* Fix the IPv6 test on a non-IPv6 machine.
Features
* HELO replaced with EHLO in the post-STARTTLS SMTP protocol negotiation
* OCSP stapling fetches moved away from server threads.
* improved client-side session resumption.
* Added support for the mimalloc allocator.
* Check for protocolHost moved to configuration file processing for the
client-side CONNECT protocol.
* Clarified some confusing OpenSSL's certificate verification error messages.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
The '/etc/init.d/acme start' crontab migration
should also delete the existing
'/etc/init.d/acme start' line.
Otherwise, on every sysupgrade that carries
forward existing configurations, a new
'0 0 * * * /etc/init.d/acme renew' line is
added to the crontab.
Furthermore, do not add an 'acme renew' crontab
line if it already exists.
Signed-off-by: Satadru Pramanik, DO, MPH, MEng <satadru@gmail.com>
Bump to latest release and removed upstreamed patch.
Resulting libs give a fully functional snort3 which was built against
this new version.
Build system: x86/64
Build-tested: x86/64-glibc
Run-tested: x86/64-glibc (Intel N150 based box)
Signed-off-by: John Audia <therealgraysky@proton.me>
IPv6 via PPPoE often receives a prefix, not an address. In that case
mwan3_get_src_ip would not find an address and fall back to ::. However
in case of multiple IPv6 upstreams, this no longer means a ping (such as
done by uptime check) succeeds, for there are multiple addresses.
With this, mwan3 can effectively load-balance/fail-over on a PPPoE IPv6
prefix and a secondary (LTE) acquired /64 without immediately disabling
the IPv6 prefix interface as soon as the secondary IPv6 interface comes
up.
I think this change is also a fix to #26690
but I'm not 100% sure of that.
Signed-off-by: Fabian Groffen <grobian@bitzolder.nl>
`pq' yields with GNU sed:
sed: -e expression #1, char 15: extra characters after command
so, make q a separate command instead.
busybox accepts this too, and still returns only the first match (q
quits processing)
Signed-off-by: Fabian Groffen <grobian@bitzolder.nl>
The tiny version disables tailscale by default for small package size.
OpenWrt also has the tailscale package as an alternative. We prefer
to keep the base version has the same build tags with the upstream
releases for compatibility.
Signed-off-by: Van Waholtz <brvphoenix@gmail.com>
3.3.9 release includes the following security fix of default gems:
- CVE-2025-24294: Possible Denial of Service in resolv gem
And the following fixes for build issues:
- GCC 15.1
- Visual Studio 2022 Version 17.14
3.3.7 and 3.3.8 are routine update that includes minor bug fixes.
Signed-off-by: Luiz Angelo Daros de Luca <luizluca@gmail.com>
libtorrent only links to boost headers since boost 1.69.
Remove boost-system from the dependencies and add boost as build
dependency.
Signed-off-by: Tianling Shen <cnsztl@immortalwrt.org>
- Use GitHub for sources URL
- Remove autoreconf fixup (it works out-of-the-box)
- Remove squid-mod-cachemgr package since cachemgr.cgi was removed upstream
- Rename ac_cv_epoll_works to squid_cv_epoll_works to follow upstream
- Don't customize target CFLAGS and LDFLAGS (they work as is)
- Remove nettle configure patch - upstream handles it correctly now
- Remove dummy comment in config menu
Signed-off-by: Aleksey Vasilenko <aleksey.vasilenko@gmail.com>
