|
Re: How to PROVIDE boost-python
Quentin Schulz
Hi Emily,
On Wed, Mar 18, 2020 at 10:16:23AM -0500, Emily wrote: Hi Laurent -You can create a patch for it. You can use devtool modify <your-recipe> and create the patch from there, you have access to the sources with that. devtool build <your-recipe> to check it builds okay. I realize this is not a long-term solution, as I'll need to update thatI don't think there is a need for BBMASK, you should be able to set PREFERRED_VERSION_boost = "1.63.0" in local.conf or your machine configuration file. ERROR: boost-1.63.0-r1 do_package: QA Issue: boost: Files/directories wereIf all of this is really temporary you can install it in some package, or even create a new package for it. (PACKAGES =+ "boost-numpy", FILES_${PN}-numpy = "/usr/lib/libboost_numpy.so.1.63.0"). No more ideas tbh. I would try to patch "your" SW first and see if it brings you somewhere, but that's what I would do, each their own way. Quentin
|
|
|
|
Re: How to PROVIDE boost-python
Emily
Hi Laurent - Unfortunately I don't have full control over the repo that's using boost_python-mt so I'm not sure I can switch it right now. I realize this is not a long-term solution, as I'll need to update that code (and my OS) to python3 soon, but for now I've just copied the boost recipe from this commit to my own layer, and added a BBMASK to the openembedded-core's boost recipe. This seems to work, except I get a QA error from the commit I'm using for the boost recipe now: ERROR: boost-1.63.0-r1 do_package: QA Issue: boost: Files/directories were installed but not shipped in any package: /usr/lib/libboost_numpy.so.1.63.0 Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install. boost: 1 installed and not shipped files. [installed-vs-shipped] ERROR: boost-1.63.0-r1 do_package: Fatal QA errors found, failing task. ERROR: boost-1.63.0-r1 do_package: Function failed: do_package I found a log that mentions this exact error, and also mentions a patch that fixes it - I've tried and thus far failed to find that patch. I'm not sure if this will actually work, but I thought I'd check and see if anyone had any ideas. Thanks, Emily
On Tue, Mar 17, 2020 at 5:24 PM Laurent Gauthier <laurent.gauthier@...> wrote: Also as Quentin suggested it might be needed to remove the "-mt"
|
|
|
|
Re: What are the key factors for yocto build speed?
Mike Looijmans
On 18-03-2020 15:49, Adrian Bunk via Lists.Yoctoproject.Org wrote:
On Wed, Mar 18, 2020 at 10:12:26AM -0400, Jean-Marie Lemetayer wrote:Seems a bit excessive to buy hardware just to handle a particular corner case. Most of OE/Yocto code is plain C, not even C++....Depends on what you are building. My rig only has 8GB but doesn't run into memory issues during big GUI builds. The only thing that made it swap was the populate_sdk task that created a 1.1GB fiel and needed 20GB of RAM to compress that. Took a few minutes more due to swapping. I submitted a patch today to fix that in OE. Your mileage may vary. But RAM is easy to add. On Wed, Mar 18, 2020 at 05:52:37AM -0700, Oliver Westermann wrote:Of course he's on a tight budget. He wouldn't need to ask for advice otherwise......I would buy 128 GB RAM to not run into problems due to lack of RAM, Most consumer boards support up to 64GB RAM. Pushing to 128 may suddenly double the price of the mobo as well. I'd go for 32 (as 2x16GB) and do an easy upgrade to 64 when there's trouble. Even with 4x16GB that's not a bad investment, if it turns out to be a bottleneck 16GB modules will be easy to sell (contrary to smaller modules).
|
|
|
|
Re: What are the key factors for yocto build speed?
Adrian Bunk
On Wed, Mar 18, 2020 at 10:12:26AM -0400, Jean-Marie Lemetayer wrote:
...Depends on what you are building. Building non-trivial C++ code (e.g. webkitgtk) with 24 cores but only 32 GB RAM will not work, for such code you need more than 2 GB/core. On Wed, Mar 18, 2020 at 05:52:37AM -0700, Oliver Westermann wrote: ...I would buy 128 GB RAM to not run into problems due to lack of RAM, and Linux will also automatically use unused RAM as disk cache. As long as you aren't running out of RAM or disk space all that matters is CPU speed, Ryzen 9 3950X with 128 GB RAM would be my choice unless you are on a tight budget. cu Adrian
|
|
|
|
Re: What are the key factors for yocto build speed?
Mike Looijmans
On 18-03-2020 15:09, Mike Looijmans via Lists.Yoctoproject.Org wrote:
Big ryzen is a good choice. Sorry - wrong number. My rig does not have a 1900, but an "AMD Ryzen 7 1700".
|
|
|
|
Re: What are the key factors for yocto build speed?
Alexander Kanavin
I have to say that AMD aggressively pursuing core count increase on consumer level CPUs is awesome news for the YP. Previously, you had to buy some hugely overpriced Xeons or similar to be able to work efficiently, or rely on CI doing builds for you which makes interactive development complicated. Alex
On Wed, 18 Mar 2020 at 15:12, Jean-Marie Lemetayer <jean-marie.lemetayer@...> wrote: Hi,
|
|
|
|
Re: What are the key factors for yocto build speed?
Hi,
toggle quoted messageShow quoted text
In my company we have tested some "big Ryzen" configurations to speed up Yocto builds. The conclusion of these tests is that the build time is almost only related to the CPU score: https://www.cpubenchmark.net/high_end_cpus.html The speed (overclock) and size of the RAM does not influence the build time, neither the the use of a SATA SSD or a NVME. For example one of our build servers is using: - AMD Ryzen 9 3900X - ASUS PRIME X570-P - 32Go DDR4 3200 MHZ CL14 - 500Go SSD It is a really good price / build time ratio configuration. Best regards, Jean-Marie
On Mar 18, 2020, at 2:29 PM, Paul Barker pbarker@... wrote:
On Wed, 18 Mar 2020 at 13:01, Mikko Rapeli <mikko.rapeli@...> wrote:What Mikko said is excellent advice.
|
|
|
|
Re: What are the key factors for yocto build speed?
Mike Looijmans
Big ryzen is a good choice.
toggle quoted messageShow quoted text
My home rig is a Ryzen 1900, with only 8GB RAM. It's way faster at OE yocto builds than the i7 at work that has 32GB RAM installed. My 8GB rig does not use swap space while building huge images (like satellite receivers and full-blown XFCE desktops). For the CPU, the more cores the better. OE loves cores. Real cores are better than SMT cores (a.k.a. hyperthreading), and AMD's SMT has more effect than Intel's. Harddisk speed has very little impact on your build time. It helps with the "setscene" parts, but doesn't affect actual compile time at all. I recall someone did a build from RAM disks only on a rig, and it was only about 1 minute faster on a one hour build compared to rotating disks. SSD or NVMe doesn't make much difference. If you have budget to spend, spend it on RAM and CPU but not on disks. I'd go for a reasonable NVMe disk, mostly for storing and booting the OS itself. If you plan to share sstate-cache and downloads from this machine to other clients, I'd even suggest a plain big (4TB or so) rotating disk for storing that kind of stuff. Again, don't spend your budget on disks. Disks are way easier to add later than any other component.
On 18-03-2020 13:52, Oliver Westermann via Lists.Yoctoproject.Org wrote:
Hey, --
Mike Looijmans
|
|
|
|
Re: What are the key factors for yocto build speed?
On Wed, 18 Mar 2020 at 13:01, Mikko Rapeli <mikko.rapeli@...> wrote:
What Mikko said is excellent advice. I'd recommend NVMe drives if you can. My build machine has two large M.2 NVMe drives, one is used for the working directory and the other for sstate, downloads and source checkouts to make the best use of the available bandwidth. I find that XFS is a better fit than ext4 when you've got fast drives and highly parallel I/O workloads. Make sure you spread your RAM across the different memory channels on your motherboard as this increases memory bandwidth - this usually means either filling your RAM slots or half-filling them with RAM in every 2nd slot but you'll need to check the motherboard manual to confirm the channel layout. Let me know if you need a detailed review of your proposed setup. Thanks, Paul
|
|
|
|
Re: What are the key factors for yocto build speed?
Mikko Rapeli
On Wed, Mar 18, 2020 at 05:52:37AM -0700, Oliver Westermann wrote:
Hey,Drop all virtualization and go for Linux on bare metal. Then make sure there is enough(tm) physical RAM for each CPU thread. For a "big Ryzen" the 64G of RAM sounds too little. I'd go higher there, but it all depends what kind of project is being compiled. I would also setup CPU, RAM, disk IO and network IO monitoring on the build machines and review and monitor the build times and results when the project evolves. There are times when most CPUs will be idling and there will be times when IO to disk is happening even when RAM is available. Linux kernel can be tuned to avoid disk IO if RAM is still available for example. Hope this helps, -Mikko
|
|
|
|
What are the key factors for yocto build speed?
Oliver Westermann
Hey,
We're currently using a VM on Windows and it's a lot slower than the native linux build (which is expected). We're looking into getting a dedicated build server for our team (basically a self-build tower PC). Any suggestions what to put in that build to get the most out of it? Currently we're looking at a big Ryzen, 64G of RAM and one or multiple SSDs on a "consumer grade" board like the X570. Suggestions, hints and links welcome :)
|
|
|
|
Armando Hernandez
Hello,
I created an eSDK and I am installing it on a docker image I created. Using the devtool I added/created a recipe for a simple HelloWorld application (such application is located in github, but I guess this is not relevant). My recipe inherits from cmake. My CMakeLists.txt file contains a "add_custom_command" block where I am specifying a COMMAND to be called. When running devtool build <recipe-name> I get errors letting me know that the file (i.e. the command) is not found. The command in question can be found my means of a soft link located under /usr/bin/ - I can run the command inside my docker container without issues. Actually, if I build the application using cmake in my docker container it will build without any issues. It is only when I try to use devtool, that the problem arises. I found this question and have already tried the solution there offered, but it has not solved my problem. So basically I added to my recipe: OECMAKE_FIND_ROOT_PATH_MODE_PROGRAM = "BOTH"with no success. I also added message() calls to my CMakeLists.txt trying to find out more about this issue, but those message() calls are ignored by devtool (they are not printed). I double checked that running cmake by myself prints such message() calls. I built my eSDK using yocto Thud v2.6.2. Any hints on how to debug this cmake problem or does anybody know why is the desired command not found when running devtool build? Thanks in advance! Armando
|
|
|
|
Re: Issue while adding the support for TLS1.3 in existing krogoth yocto
#yocto
#apt
#raspberrypi
amaya jindal
Hi All while I tried to add Openssh 7.8p1 recipe in krogoth yocto, to add support for openssl 1.1.1b. Every thing compiled successfully but now I am getting issue when I tried to. test that on board, its getting restarted every time. Please suggest Sent from my Huawei phone
-------- Original message -------- From: amaya jindal <amayajindal786@...> Date: Wed, 19 Feb 2020, 1:09 pm To: Mikko.Rapeli@... Cc: alex.kanavin@..., yocto@... Subject: Re: [yocto] Issue while adding the support for TLS1.3 in existing krogoth yocto #yocto #yocto #yocto #yocto #apt #raspberrypi #yocto
|
|
|
|
Amrun Nisha.R
Hi,
I want to add a feature auto login using sysvinit as init function in yocto. So I have created a new layer named "meta-autologin" and added in the bitbake layers. Now I have updated the local.conf with the following IMAGE_INSTALL_append = " autologin"
IMAGE_INSTALL_append = " linux-firmware dhcpcd dhcp-client dhcp-server iptables wpa-supplicant "
CORE_IMAGE_EXTRA_INSTALL_append ="openssh dhcpcd dhcp-client"
And I have added the meta-autologin in the bblayer.conf BBLAYERS = " \
${BSPDIR}/sources/poky/meta \
${BSPDIR}/sources/poky/meta-poky \
${BSPDIR}/sources/poky/meta-autologin \
\
${BSPDIR}/sources/meta-openembedded/meta-oe \
${BSPDIR}/sources/meta-openembedded/meta-multimedia \
\
${BSPDIR}/sources/meta-freescale \
${BSPDIR}/sources/meta-freescale-3rdparty \
${BSPDIR}/sources/meta-freescale-distro \
"
For init function, I have the fsl-wayland.conf file in \sources\meta-freescale-distro\conf\distro\fsl-wayland.conf as # FSL Distro for Wayland with XWayland.
require conf/distro/include/fsl-base.inc
DISTRO = "fsl-xwayland"
DISTRO_NAME = "FSL Wayland with XWayland"
# Remove conflicting backends
DISTRO_FEATURES_remove = "directfb"
DISTRO_FEATURES_append = " x11 wayland pam systemd"
#VIRTUAL-RUNTIME_init_manager = "systemd"
VIRTUAL-RUNTIME_init_manager = "busybox"
VIRTUAL-RUNTIME_initscripts = "initscripts"
VIRTUAL-RUNTIME_keymaps = "keymaps"
DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit"
For sysinit function, I have updated the inc file in \meta-fsl-bsp-release\imx\meta-sdk\conf\distro\include\fsl-imx-preferred-env.inc as # Use systemd as default init manager
VIRTUAL-RUNTIME_init_manager = "sysvinit"
#VIRTUAL-RUNTIME_dev_manager = "busybox-mdev"
#VIRTUAL-RUNTIME_login_manager = "busybox"
PREFERRED_PROVIDER_udev = "systemd"
PREFERRED_PROVIDER_udev-utils = "systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED = "systemd"
VIRTUAL-RUNTIME_initscripts = "initscripts"
IMX_DEFAULT_DISTRO_FEATURES += " sysvinit"
But I m getting error when the core-image-base_do_rootfs due to could not invoke dnf command and giving error as transaction failed . I have attached the error log file. Can someone resolve this issue? :(
|
|
|
|
[meta-security][PATCH 7/7] buck-security: move to recipes-scanners
Signed-off-by: Armin Kuster <akuster808@...>
--- .../buck-security/buck-security_0.7.bb | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename {recipes-security => recipes-scanners}/buck-security/buck-security_0.7.bb (100%) diff --git a/recipes-security/buck-security/buck-security_0.7.bb b/recipes-scanners/buck-security/buck-security_0.7.bb similarity index 100% rename from recipes-security/buck-security/buck-security_0.7.bb rename to recipes-scanners/buck-security/buck-security_0.7.bb -- 2.17.1
|
|
|
|
[meta-security][PATCH 6/7] checksecurity: move to recipes-scanners
Signed-off-by: Armin Kuster <akuster808@...>
--- .../checksecurity/checksecurity_2.0.15.bb | 0 .../files/check-setuid-use-more-portable-find-args.patch | 0 .../checksecurity/files/setuid-log-folder.patch | 0 3 files changed, 0 insertions(+), 0 deletions(-) rename {recipes-security => recipes-scanners}/checksecurity/checksecurity_2.0.15.bb (100%) rename {recipes-security => recipes-scanners}/checksecurity/files/check-setuid-use-more-portable-find-args.patch (100%) rename {recipes-security => recipes-scanners}/checksecurity/files/setuid-log-folder.patch (100%) diff --git a/recipes-security/checksecurity/checksecurity_2.0.15.bb b/recipes-scanners/checksecurity/checksecurity_2.0.15.bb similarity index 100% rename from recipes-security/checksecurity/checksecurity_2.0.15.bb rename to recipes-scanners/checksecurity/checksecurity_2.0.15.bb diff --git a/recipes-security/checksecurity/files/check-setuid-use-more-portable-find-args.patch b/recipes-scanners/checksecurity/files/check-setuid-use-more-portable-find-args.patch similarity index 100% rename from recipes-security/checksecurity/files/check-setuid-use-more-portable-find-args.patch rename to recipes-scanners/checksecurity/files/check-setuid-use-more-portable-find-args.patch diff --git a/recipes-security/checksecurity/files/setuid-log-folder.patch b/recipes-scanners/checksecurity/files/setuid-log-folder.patch similarity index 100% rename from recipes-security/checksecurity/files/setuid-log-folder.patch rename to recipes-scanners/checksecurity/files/setuid-log-folder.patch -- 2.17.1
|
|
|
|
[meta-security][PATCH 5/7] checksec: move to recipe-scanners
Signed-off-by: Armin Kuster <akuster808@...>
--- {recipes-security => recipes-scanners}/checksec/checksec_2.1.0.bb | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename {recipes-security => recipes-scanners}/checksec/checksec_2.1.0.bb (100%) diff --git a/recipes-security/checksec/checksec_2.1.0.bb b/recipes-scanners/checksec/checksec_2.1.0.bb similarity index 100% rename from recipes-security/checksec/checksec_2.1.0.bb rename to recipes-scanners/checksec/checksec_2.1.0.bb -- 2.17.1
|
|
|
|
[meta-security][PATCH 4/7] clamav: move to recipes-scanners
Signed-off-by: Armin Kuster <akuster808@...>
--- {recipes-security => recipes-scanners}/clamav/clamav_0.101.5.bb | 0 .../clamav/files/clamav-freshclam.service | 0 .../clamav/files/clamav-milter.conf.sample | 0 .../clamav/files/clamav.service | 0 {recipes-security => recipes-scanners}/clamav/files/clamd.conf | 0 .../clamav/files/freshclam-native.conf | 0 .../clamav/files/freshclam.conf | 0 .../clamav/files/tmpfiles.clamav | 0 .../clamav/files/volatiles.03_clamav | 0 9 files changed, 0 insertions(+), 0 deletions(-) rename {recipes-security => recipes-scanners}/clamav/clamav_0.101.5.bb (100%) rename {recipes-security => recipes-scanners}/clamav/files/clamav-freshclam.service (100%) rename {recipes-security => recipes-scanners}/clamav/files/clamav-milter.conf.sample (100%) rename {recipes-security => recipes-scanners}/clamav/files/clamav.service (100%) rename {recipes-security => recipes-scanners}/clamav/files/clamd.conf (100%) rename {recipes-security => recipes-scanners}/clamav/files/freshclam-native.conf (100%) rename {recipes-security => recipes-scanners}/clamav/files/freshclam.conf (100%) rename {recipes-security => recipes-scanners}/clamav/files/tmpfiles.clamav (100%) rename {recipes-security => recipes-scanners}/clamav/files/volatiles.03_clamav (100%) diff --git a/recipes-security/clamav/clamav_0.101.5.bb b/recipes-scanners/clamav/clamav_0.101.5.bb similarity index 100% rename from recipes-security/clamav/clamav_0.101.5.bb rename to recipes-scanners/clamav/clamav_0.101.5.bb diff --git a/recipes-security/clamav/files/clamav-freshclam.service b/recipes-scanners/clamav/files/clamav-freshclam.service similarity index 100% rename from recipes-security/clamav/files/clamav-freshclam.service rename to recipes-scanners/clamav/files/clamav-freshclam.service diff --git a/recipes-security/clamav/files/clamav-milter.conf.sample b/recipes-scanners/clamav/files/clamav-milter.conf.sample similarity index 100% rename from recipes-security/clamav/files/clamav-milter.conf.sample rename to recipes-scanners/clamav/files/clamav-milter.conf.sample diff --git a/recipes-security/clamav/files/clamav.service b/recipes-scanners/clamav/files/clamav.service similarity index 100% rename from recipes-security/clamav/files/clamav.service rename to recipes-scanners/clamav/files/clamav.service diff --git a/recipes-security/clamav/files/clamd.conf b/recipes-scanners/clamav/files/clamd.conf similarity index 100% rename from recipes-security/clamav/files/clamd.conf rename to recipes-scanners/clamav/files/clamd.conf diff --git a/recipes-security/clamav/files/freshclam-native.conf b/recipes-scanners/clamav/files/freshclam-native.conf similarity index 100% rename from recipes-security/clamav/files/freshclam-native.conf rename to recipes-scanners/clamav/files/freshclam-native.conf diff --git a/recipes-security/clamav/files/freshclam.conf b/recipes-scanners/clamav/files/freshclam.conf similarity index 100% rename from recipes-security/clamav/files/freshclam.conf rename to recipes-scanners/clamav/files/freshclam.conf diff --git a/recipes-security/clamav/files/tmpfiles.clamav b/recipes-scanners/clamav/files/tmpfiles.clamav similarity index 100% rename from recipes-security/clamav/files/tmpfiles.clamav rename to recipes-scanners/clamav/files/tmpfiles.clamav diff --git a/recipes-security/clamav/files/volatiles.03_clamav b/recipes-scanners/clamav/files/volatiles.03_clamav similarity index 100% rename from recipes-security/clamav/files/volatiles.03_clamav rename to recipes-scanners/clamav/files/volatiles.03_clamav -- 2.17.1
|
|
|
|
[meta-security][PATCH 3/7] chkrootkit: add rootkit recipe
Signed-off-by: Armin Kuster <akuster808@...>
--- recipes-scanners/rootkits/chkrootkit_0.53.bb | 48 ++++++++++++++++++++ 1 file changed, 48 insertions(+) create mode 100644 recipes-scanners/rootkits/chkrootkit_0.53.bb diff --git a/recipes-scanners/rootkits/chkrootkit_0.53.bb b/recipes-scanners/rootkits/chkrootkit_0.53.bb new file mode 100644 index 0000000..4536be3 --- /dev/null +++ b/recipes-scanners/rootkits/chkrootkit_0.53.bb @@ -0,0 +1,48 @@ +DESCRIPTION = "rootkit detector" +SUMMARY = "locally checks for signs of a rootkit" +HOMEPAGE = "http://www.chkrootkit.org/" +SECTION = "security" +LICENSE = "BSD-2-Clause" +LIC_FILES_CHKSUM = "file://COPYRIGHT;md5=fdbe53788f7081c63387d8087273f5ff" + +SRC_URI = "ftp://ftp.pangeia.com.br/pub/seg/pac/${BPN}.tar.gz" +SRC_URI[sha256sum] = "7262dae33b338976828b5d156b70d159e0043c0db43ada8dee66c97387cf45b5" + + +inherit autotools-brokensep + +TARGET_CC_ARCH += "${LDFLAGS}" + +do_configure () { + sed -i 's/@strip.*$//' ${S}/Makefile +} + +do_compile () { + make CC="${CC}" LDFLAGS="${LDFLAGS}" sense + gzip -9vkf ACKNOWLEDGMENTS + gzip -9vkf README +} + +do_install () { + install -d ${D}/${libdir}/${PN} + install -d ${D}/${sbindir} + install -d ${D}/${docdir}/${PN} + + install -m 644 ${B}/chkdirs ${D}/${libdir}/${PN} + install -m 644 ${B}/chklastlog ${D}/${libdir}/${PN} + install -m 644 ${B}/chkproc ${D}/${libdir}/${PN} + install -m 644 ${B}/chkutmp ${D}/${libdir}/${PN} + install -m 644 ${B}/chkwtmp ${D}/${libdir}/${PN} + install -m 644 ${B}/ifpromisc ${D}/${libdir}/${PN} + install -m 644 ${B}/strings-static ${D}/${libdir}/${PN} + + install -m 755 ${B}/chklastlog ${D}/${sbindir} + install -m 755 ${B}/chkrootkit ${D}/${sbindir} + install -m 755 ${B}/chkwtmp ${D}/${sbindir} + + install -m 644 ${B}/ACKNOWLEDGMENTS.gz ${D}/${docdir}/${PN} + install -m 644 ${B}/README.chklastlog ${D}/${docdir}/${PN} + install -m 644 ${B}/README.chkwtmp ${D}/${docdir}/${PN} + install -m 644 ${B}/README.gz ${D}/${docdir}/${PN} + install -m 644 ${B}/COPYRIGHT ${D}/${docdir}/${PN} +} -- 2.17.1
|
|
|
|
[meta-security][PATCH 2/7] fail2ban: change hardcoded sysklogd to VIRTUAL-RUNTIME_base-utils-syslog
Signed-off-by: Armin Kuster <akuster808@...>
--- recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb b/recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb index 8673c10..e737f50 100644 --- a/recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb +++ b/recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb @@ -46,6 +46,6 @@ INITSCRIPT_PARAMS = "defaults 25" INSANE_SKIP_${PN}_append = "already-stripped" -RDEPENDS_${PN} = "sysklogd iptables sqlite3 python3-core python3-pyinotify python3-logging python3-fcntl" -RDEPENDS_${PN} += " python3-json " +RDEPENDS_${PN} = "${VIRTUAL-RUNTIME_base-utils-syslog} iptables sqlite3 python3-core python3-pyinotify" +RDEPENDS_${PN} += " python3-logging python3-fcntl python3-json" RDEPENDS_${PN}-ptest = "python3-core python3-io python3-modules python3-fail2ban" -- 2.17.1
|
|
|