Re: [yocto] [meta-security][PATCHv2] Upgrade scapy to 2.4.2
Scott,
On 1/19/19 3:16 AM, Scott Ellis wrote:
> Upstream MANIFEST.in removed doc and test directories
> so remove ptest.
>
> Signed-off-by: Scott Ellis
> ---
> recipes-security/scapy/files/run-ptest| 4
> recipes-security/scapy/python-scapy.inc | 11 +++
> recipes-security/scapy/python-scapy_2.4.0.bb | 6 --
> recipes-security/scapy/python-scapy_2.4.2.bb | 4
> recipes-security/scapy/python3-scapy_2.4.0.bb | 4
> recipes-security/scapy/python3-scapy_2.4.2.bb | 2 ++
> 6 files changed, 9 insertions(+), 22 deletions(-)
> delete mode 100755 recipes-security/scapy/files/run-ptest
> delete mode 100644 recipes-security/scapy/python-scapy_2.4.0.bb
> create mode 100644 recipes-security/scapy/python-scapy_2.4.2.bb
> delete mode 100644 recipes-security/scapy/python3-scapy_2.4.0.bb
> create mode 100644 recipes-security/scapy/python3-scapy_2.4.2.bb
Thank you for the update. The issue I have is the doc's and test got
removed from the pypi package via commit:
https://github.com/secdev/scapy/commit/8857c03bad798ba902b34c64282ef72483569c77
when they went to 2.4.2.
Any ideas on how to restore the ptests? I know 2.4.1 still has the
tests. I wonder how may folks run this ptest?
I am holding this update for now.
- armin
>
> diff --git a/recipes-security/scapy/files/run-ptest
> b/recipes-security/scapy/files/run-ptest
> deleted file mode 100755
> index 91b29f9..000
> --- a/recipes-security/scapy/files/run-ptest
> +++ /dev/null
> @@ -1,4 +0,0 @@
> -#!/bin/sh
> -UTscapy -t regression.uts -f text -l -C \
> --o @PTEST_PATH@/scapy_ptest_$(date +%Y%m%d-%H%M%S).log \
> -2>&1 | sed -e 's/^passed None/PASS:/' -e 's/^failed None/FAIL:/'
> diff --git a/recipes-security/scapy/python-scapy.inc
> b/recipes-security/scapy/python-scapy.inc
> index 5abe7db..95e5312 100644
> --- a/recipes-security/scapy/python-scapy.inc
> +++ b/recipes-security/scapy/python-scapy.inc
> @@ -5,15 +5,10 @@ LICENSE = "GPLv2"
>
> LIC_FILES_CHKSUM =
> "file://bin/scapy;beginline=9;endline=13;md5=1d5249872cc54cd4ca3d3879262d0c69"
>
> -SRC_URI[md5sum] = "d7d3c4294f5a718e234775d38dbeb7ec"
> -SRC_URI[sha256sum] =
> "452f714f5c2eac6fd0a6146b1dbddfc24dd5f4103f3ed76227995a488cfb2b73"
> +SRC_URI[md5sum] = "e6a03d8c924a6bbde1e86fc58bd2b9d6"
> +SRC_URI[sha256sum] =
> "1baa048936207ceb1a4281a0e1e3b4317667c754872a0bb4734c5213c468e86a"
>
> -inherit pypi ptest
> -
> -do_install_ptest() {
> -install -m 0644 ${S}/test/regression.uts ${D}${PTEST_PATH}
> -sed -i 's,@PTEST_PATH@,${PTEST_PATH},' ${D}${PTEST_PATH}/run-ptest
> -}
> +inherit pypi
>
> RDEPENDS_${PN} = "tcpdump ${PYTHON_PN}-compression ${PYTHON_PN}-netclient \
>${PYTHON_PN}-netserver ${PYTHON_PN}-pydoc
> ${PYTHON_PN}-pkgutil ${PYTHON_PN}-shell \
> diff --git a/recipes-security/scapy/python-scapy_2.4.0.bb
> b/recipes-security/scapy/python-scapy_2.4.0.bb
> deleted file mode 100644
> index 98db1fd..000
> --- a/recipes-security/scapy/python-scapy_2.4.0.bb
> +++ /dev/null
> @@ -1,6 +0,0 @@
> -inherit setuptools
> -require python-scapy.inc
> -
> -SRC_URI += "file://run-ptest"
> -
> -RDEPENDS_${PN} += "${PYTHON_PN}-subprocess"
> diff --git a/recipes-security/scapy/python-scapy_2.4.2.bb
> b/recipes-security/scapy/python-scapy_2.4.2.bb
> new file mode 100644
> index 000..ea8764a
> --- /dev/null
> +++ b/recipes-security/scapy/python-scapy_2.4.2.bb
> @@ -0,0 +1,4 @@
> +inherit setuptools
> +require python-scapy.inc
> +
> +RDEPENDS_${PN} += "${PYTHON_PN}-subprocess"
> diff --git a/recipes-security/scapy/python3-scapy_2.4.0.bb
> b/recipes-security/scapy/python3-scapy_2.4.0.bb
> deleted file mode 100644
> index 93ca7be..000
> --- a/recipes-security/scapy/python3-scapy_2.4.0.bb
> +++ /dev/null
> @@ -1,4 +0,0 @@
> -inherit setuptools3
> -require python-scapy.inc
> -
> -SRC_URI += "file://run-ptest"
> diff --git a/recipes-security/scapy/python3-scapy_2.4.2.bb
> b/recipes-security/scapy/python3-scapy_2.4.2.bb
> new file mode 100644
> index 000..34eb2a3
> --- /dev/null
> +++ b/recipes-security/scapy/python3-scapy_2.4.2.bb
> @@ -0,0 +1,2 @@
> +inherit setuptools3
> +require python-scapy.inc
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Proper Use of KERNEL_MODULE_AUTOLOAD variable
On Sun, Feb 3, 2019 at 12:51 AM Ulf Samuelsson wrote:
>
> Den 2019-02-03 kl. 04:16, skrev Ken Sloat:
> > On Sat, Feb 2, 2019 at 10:03 PM Bruce Ashfield
> > wrote:
> >>
> >> On 2019-02-02 9:59 p.m., Ken Sloat wrote:
> >>> Hello,
> >>>
> >>> I have an out of tree kernel module which I want autoloaded at startup
> >>> on my system. Looking at the Yocto project manual, I see that one way
> >>> I can do this is to add the module name to the KERNEL_MODULE_AUTOLOAD
> >>> variable within my custom module recipe.
> >>>
> >>> What I have found is that the module-split class is indeed generating
> >>> the "/etc/modules-load.d/mymodule.conf" file, however this file is not
> >>> actually being installed. To be more precise it is appearing in the
> >>> "package" directory (i.e.
> >>> tmp/work/**/mymodule/package/etc/modules-load.d/mymodule.conf) but not
> >>> within the "image" directory (nor in my final rootfs).
> >>>
> >>> Is there something I'm missing in the usage of KERNEL_MODULE_AUTOLOAD?
> >>> Is the intention for this variable I add extra steps to manually
> >>> install this file in my recipe? FYI I'm using Morty.
> >>
> >> Can you provide your recipe ? It would make suggestions easier. For
> >> example, my first question is: Is the module being installed to your
> >> image via IMAGE_INSTALL, or some other similar variable ?
> >>
> >> Bruce
> >>
> >>>
> >>> Thanks,
> >>> Ken Sloat
> >>>
> >>
> >
> > Hi Bruce,
> >
> > Thanks for your quick reply. Yes the module is being installed via
> > image_install. Module is installed but generated conf file is not. See
> > recipe below:
> >
> > require mymodule.inc
> >
> > inherit module kernel-module-split
> >
> > DEPENDS = "virtual/kernel"
> >
> > EXTRA_OEMAKE_append = " \
> > KERNELDIR=${STAGING_KERNEL_DIR} \
> > "
> >
> > MAKE_TARGETS = "module"
> >
> > MODULE_NAME = "mymodule"
> >
> > PKG_${PN} = "kernel-module-${MODULE_NAME}"
> >
> > module_do_install() {
> > install -d ${D}/lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME}
> > install -m 0644 ${MODULE_NAME}.ko \
> >
> > ${D}/lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME}/${MODULE_NAME}.ko
> > }
> >
> > FILES_${PN} = " \
> > /lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME} \
> > "
> >
> > KERNEL_MODULE_AUTOLOAD += "${MODULE_NAME}"
> >
>
> One would think that the file should be added automatically,
> but this might be required, - or a workaround...
>
> FILES_${PN} = " \
>/lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME} \
>${sysconfdir}/modules-load.d/${MODULE_NAME}.conf \
> "
>
>
> --
> Best Regards
> Ulf Samuelsson
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
Hi Ulf,
Yes it seems that this indeed allows it to end up in the final image.
Not sure why it doesn't work without as I see the kernel-module-split
class seems to have statements to do this automatically:
files = d.getVar('FILES_%s' % pkg, True)
files = "%s /etc/modules-load.d/%s.conf
/etc/modprobe.d/%s.conf" % (files, basename, basename)
d.setVar('FILES_%s' % pkg, files)
Maybe there's some type of name mismatch or something in my case?
Thanks,
Ken Sloat
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Set package DEB priority
Find the solution my own. I put PRIORITY := "required" in conf/local.conf to set all packages as "required" MZ Il 03/02/19 15:10, Mauro Ziliani ha scritto: > Hi all > > How can I set the priority of ad DEB by my recipes? > > I need to mark all packages as required. > > Now they are optional > > > Mauro > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Set package DEB priority
Hi all How can I set the priority of ad DEB by my recipes? I need to mark all packages as required. Now they are optional Mauro -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
