Switch to AUTORELEASE for simplicity.
Use autotools build.
Remove upstream patch.
Minor cleanups for consistency between packages.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
Make sure filesystem is ready when volume becomes available.
Use 'write-once' as initial state for read-only volumes, only allow
writing to volumes in that state and transision to 'read-only' once
write has completed.
Also fix a typo which prevented 'list' command from working with LVM.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
libseccomp can't be built on ARC, so we must disable the option here as
well. A different fix was first proposed by @zxlhhyccc in #15377.
Fixes: #15313
Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
Bugs:
- Fix for invalid handler warning on Windows builds
- Fix config hash to trigger container recreation on IPC mode updates
- Fix conversion map for placement.max_replicas_per_node
- Remove extra scan suggestion on build
Signed-off-by: Javier Marcet <javier@marcet.info>
This enables tools again which has been disabled in commit
498506af9 ("libupnp: update to 1.14.5"). Disabling tools leads to the
header upnptools.h not being installed into /usr/include. But e.g. mpd-full
depends on this header.
Fixes: 498506af9 ("libupnp: update to 1.14.5")
Signed-off-by: Alexander Egorenkov <egorenar-dev@posteo.net>
Fixes: https://github.com/openwrt/packages/issues/15370
This is inspired from:
330bc94dcc/lang/python-greenlet/Makefile
The `PKG_USE_MIPS16:=0` is not taken into consideration when building
Python modules. That's because the sysconfig is used.
This is only an issue with greenlet (on MIPS) so far.
One option is to do `PKG_USE_MIPS16:=0` in the core Python package.
But, since we know that the `wlanslovenija` group has successfully used
greenlet on MIPS with this construct, we might as well adopt it until GCC10
becomes the main compiler.
As noted here:
https://github.com/openwrt/packages/issues/15370#issuecomment-817015484
GCC10 doesn't have this problem.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
Add patch fixing compilation without deprecated OpenSSL APIs.
Fix installation. This never worked as the section was misnamed.
Updated tool names.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
Removed two now pointless patches as they were added as options.
Switch to AUTORELEASE for simplicity.
Update MESON_ARGS.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
chacha20policy1305 is also an AEAD cipher, and hence does not
permit a hash algorithm.
Fixes issue #15397.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
Fixes two CVEs:
CVE-2021-28965: XML round-trip vulnerability in REXML
CVE-2021-28966: Path traversal in Tempfile on Windows
Signed-off-by: Luiz Angelo Daros de Luca <luizluca@gmail.com>
Features:
- Add profile filter to docker-compose config
- Add a depends_on condition to wait for successful service completion
Miscellaneous:
- Add image scan message on build
- Update warning message for --no-ansi to mention --ansi never as alternative
- Bump docker-py to 5.0.0
- Bump PyYAML to 5.4.1
- Bump python-dotenv to 0.17.0
Signed-off-by: Javier Marcet <javier@marcet.info>
This reverts commit b29e609701.
Adding DEPENDS+=@!arc will cause a circular dependency, because some
packages select libseccomp based on a build option.
Commit e29483d7e ("libseccomp: workaround a recursive dependency") added
a workaround that was not properly documented, so I'll explain here.
The problem arises when libseccomp is selected depending on some config
option:
define Pakcage/foo
DEPENDS=+FOO_SECCOMP:libseccomp
Even if the condition is correctly defined, excluding arc, such as:
define Package/foo/config
config FOO_SECCOMP
depends on !arc
the config generator will parse libseccomp's DEPENDS variable and
generate menuconfig statements like these:
config PACKAGE_foo
select PACKAGE_libseccomp if FOO_SECCOMP
depends on !FOO_SECCOMP || !arc
The last condition is always true because FOO_SECCOMP will always be
be false when arc is true. The config generator is not able to
simplify/optimize the condition.
The circular dependecy occurs because FOO_SECCOMP depends on
PACKAGE_foo, and the redundant, always true line will make PACKAGE_foo
depend on FOO_SECCOMP.
As a workaround, we can add the 'depends on !arc' line to
Package/libseccomp/config, outside of the DEPENDS variable, so that the
redundant depends line line does not get generated.
Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
Cc: Daniel Golle <daniel@makrotopia.org>
The package needs libseccomp, which does not currently support arc.
In order to avoid a circular dependency, we must avoid arc here as well.
Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
Fix log spam:
daemon.err netdata[2090]: PROCFILE: Cannot open file '/proc/sysvipc/shm'
This is caused by a non existant /proc/sysvipc/shm because of the
CONFIG_PROC_STRIPPED option that is enabled by default in the kernel
generic target config
Signed-off-by: Tiago Gaspar <tiagogaspar8@gmail.com>
Rosen Penev