[yocto] [PATCH][meta-selinux] net-tools: Rename net-tools bbappend with wildcard for minor version.
Signed-off-by: Philip Tricca
---
recipes-extended/net-tools/net-tools_1.%.bbappend | 11 +++
recipes-extended/net-tools/net-tools_1.60-25.bbappend | 11 ---
2 files changed, 11 insertions(+), 11 deletions(-)
create mode 100644 recipes-extended/net-tools/net-tools_1.%.bbappend
delete mode 100644 recipes-extended/net-tools/net-tools_1.60-25.bbappend
diff --git a/recipes-extended/net-tools/net-tools_1.%.bbappend
b/recipes-extended/net-tools/net-tools_1.%.bbappend
new file mode 100644
index 000..e99a5bc
--- /dev/null
+++ b/recipes-extended/net-tools/net-tools_1.%.bbappend
@@ -0,0 +1,11 @@
+PR .= ".2"
+
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+SRC_URI += "file://netstat-selinux-support.patch"
+
+inherit selinux
+
+DEPENDS += "${LIBSELINUX}"
+
+EXTRA_OEMAKE += "${@target_selinux(d, 'HAVE_SELINUX=1', 'HAVE_SELINUX=0')}"
diff --git a/recipes-extended/net-tools/net-tools_1.60-25.bbappend
b/recipes-extended/net-tools/net-tools_1.60-25.bbappend
deleted file mode 100644
index e99a5bc..000
--- a/recipes-extended/net-tools/net-tools_1.60-25.bbappend
+++ /dev/null
@@ -1,11 +0,0 @@
-PR .= ".2"
-
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-
-SRC_URI += "file://netstat-selinux-support.patch"
-
-inherit selinux
-
-DEPENDS += "${LIBSELINUX}"
-
-EXTRA_OEMAKE += "${@target_selinux(d, 'HAVE_SELINUX=1', 'HAVE_SELINUX=0')}"
--
2.1.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] dropbear is not working after including in IMAGE_FEATURES
Hi,
Now Dropbear feature is including in the image but it is getting failed to
start time while booting
error [3.164188] systemd[1]: Failed to start SSH Server.
Does can one help with this issue.
Thanks and Regards
vivek
On Thu, Sep 10, 2015 at 11:07 PM, Robert Berger <
gm...@reliableembeddedsystems.com> wrote:
> On 09/10/2015 05:17 PM, Vivek Per wrote:> Hi,
> > I have included IMAGE_FEATURES += "ssh-server-dropbear" in my
> > recipe image. and created the image.
>
> So you have something like:
>
> image-features-image.bb with something like this?
>
> -->
>
> IMAGE_INSTALL = "packagegroup-core-boot packagegroup-base-extended"
>
> IMAGE_FEATURES += "debug-tweaks splash x11-base ssh-server-dropbear \
>package-management x11-sato"
>
> inherit core-image
>
> <--
>
> > But after flashing the image i was not able to connect to target using
> > ssh from my host machine. but target to host is working fine. Can any
> > one tell me why it is not working. Is there any package need to add?
>
> check your IMAGE_FEATURES if it's really like you want it:
>
> bitbake -e image-features-image | grep ^IMAGE_FEATURES=
>
> I see something like this:
>
> IMAGE_FEATURES="debug-tweaks splash x11-base ssh-server-dropbear
> package-management x11-sato"
>
> You might want to check if dropbear made it into your image with
> something like this before flashing it:
>
> bitbake -g image-features-image && cat pn-depends.dot | grep -v -e
> '-native' | grep -v digraph | grep -v -e '-image' | awk '{print $1}' |
> sort | uniq
>
> This will give you a list and you should find something like:
>
> "dropbear"
>
>
> "packagegroup-core-ssh-dropbear"
>
> >
> >
> > Thanks and Regards
> >
> >
> > --
> >
>
> Regards,
>
> Robert..."Whereas Europeans generally pronouce my name the right way
> (Ni-klows Virt), Americans invariably mangle it into 'Nickle-less
> Worth'. This is to say that Europeans call me by name, but Americans
> call me by value." -- Niklaus Wirth
>
> My public pgp key is available,at:
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi] du giving non-integer result?
>From the feedback, it looks like I'm the only one seeing this issue.
That's okay, but I'll update this issue with new information in case
it's useful to others. Today I also had some other strangeness with the
"make sd card image" portion of a build, this time for cubietruck
(meta-sunxi):
ERROR: Error: The image creation script
'/z/tmp/build/tmp/work/cubietruck-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/create_image.sunxi-sdimg'
returned 1:
0+0 records in
0+0 records out
0 bytes (0 B) copied, 3.0606e-05 s, 0.0 kB/s
expr: non-integer argument
WARNING:
/z/tmp/build/tmp/work/cubietruck-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/create_image.sunxi-sdimg:1
exit 1 from
parted -s
/z/tmp/build/tmp/deploy/images/cubietruck/core-image-minimal-cubietruck-20150910182624.rootfs.sunxi-sdimg
unit KiB mkpart primary ext2 $(expr ${BOOT_SPACE_ALIGNED} \+ 2048)
$(expr ${BOOT_SPACE_ALIGNED} \+ 2048 \+ 10240.0)
Not only am I getting the floating point again, but it looks like
"BOOT_SPACE_ALIGNED" isn't getting expanded!
The frustrating part is that simply rerunning "bitbake
core-image-minimal" fixes the problem. The second time it completes
without error.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Peripheral hardware support
I'd like to include a RFID reader in a Yocto-based project. What is the best way to find devices that have driver support already or that provide open-source drivers suitable for inclusion? Is there a hardware support list for stuff like that somewhere? Thanks, Brad -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] kernel change detection for packages that depend on kernel version?
I'm running into an issue where the branch for my kernel received some new commits, changing what the kernel version string looks like. When I rebuilt my system (bitbake my-image) the kernel was rebuilt (I believe at some point I probably also ran bitbake virtual/kernel -c clean), however several OOT kernel module packages were not rebuilt (one of our modules, as well as lttng-modules). In addition, I have the kernel-devsrc package included in my TOOLCHAIN_TARGET_TASK, and running "... -c populate_sdk" seems to have built an SDK containing the old kernel source. Cleaning those recipes allowed them to rebuild properly, but it seems like rebuilding should have happened automatically... My image recipe looks like this (very abbreviated): inherit core-image IMAGE_INSTALL_append = " packagegroup-core-boot kernel-modules my-oot-module" IMAGE_FEATURES += "package-management" TOOLCHAIN_TARGET_TASK_append = " kernel-devsrc" This brings me to my questions: 1. How do recipes that depend on the kernel headers tell when they need to rebuild? Is there something wrong with my kernel recipe? (for reference, I'm using this one: https://github.com/kraj/meta-altera/blob/master/recipes-kernel/linux/linux-altera-ltsi-rt_3.10.bb) 2. Why didn't kernel-devsrc rebuild after the kernel changed? 3. How do I clean the populate_sdk output? Will do_clean clean the populate_sdk output as well? I know I can force it to rerun with "... -f -c populate_sdk" Thanks for your help, Ben -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] dropbear is not working after including in IMAGE_FEATURES
On 09/10/2015 05:17 PM, Vivek Per wrote:> Hi,
> I have included IMAGE_FEATURES += "ssh-server-dropbear" in my
> recipe image. and created the image.
So you have something like:
image-features-image.bb with something like this?
-->
IMAGE_INSTALL = "packagegroup-core-boot packagegroup-base-extended"
IMAGE_FEATURES += "debug-tweaks splash x11-base ssh-server-dropbear \
package-management x11-sato"
inherit core-image
<--
> But after flashing the image i was not able to connect to target using
> ssh from my host machine. but target to host is working fine. Can any
> one tell me why it is not working. Is there any package need to add?
check your IMAGE_FEATURES if it's really like you want it:
bitbake -e image-features-image | grep ^IMAGE_FEATURES=
I see something like this:
IMAGE_FEATURES="debug-tweaks splash x11-base ssh-server-dropbear
package-management x11-sato"
You might want to check if dropbear made it into your image with
something like this before flashing it:
bitbake -g image-features-image && cat pn-depends.dot | grep -v -e
'-native' | grep -v digraph | grep -v -e '-image' | awk '{print $1}' |
sort | uniq
This will give you a list and you should find something like:
"dropbear"
"packagegroup-core-ssh-dropbear"
>
>
> Thanks and Regards
>
>
> --
>
Regards,
Robert..."Whereas Europeans generally pronouce my name the right way
(Ni-klows Virt), Americans invariably mangle it into 'Nickle-less
Worth'. This is to say that Europeans call me by name, but Americans
call me by value." -- Niklaus Wirth
My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] dropbear is working after including in IMAGE_FEATURES
> On Sep 10, 2015, at 7:09 AM, Vivek Per wrote: > > Hi, > I have included IMAGE_FEATURES += "ssh-server-dropbear" in my recipe > image. and created the image. > But after flashing the image i was not able to connect to target from my host > machine. but target to host is working fine. Can any one tell me why it is > not working. Is there any package need to add? Make sure 1. ssh-server-dropbear ends up in the IMAGE_FEATUTES for sure and is no overwritten elsewhere ( bitbake -e | grep -e “^ IMAGE_FEATUTES”) If above is fine then It seems like that the service did not start on target. you can start the service manually and see if that works. -Khem -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] dropbear is not working after including in IMAGE_FEATURES
Hi, I have included IMAGE_FEATURES += "ssh-server-dropbear" in my recipe image. and created the image. But after flashing the image i was not able to connect to target using ssh from my host machine. but target to host is working fine. Can any one tell me why it is not working. Is there any package need to add? Thanks and Regards -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] dropbear is working after including in IMAGE_FEATURES
Hi, I have included IMAGE_FEATURES += "ssh-server-dropbear" in my recipe image. and created the image. But after flashing the image i was not able to connect to target from my host machine. but target to host is working fine. Can any one tell me why it is not working. Is there any package need to add? Thanks and Regards vivek -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
