Re: [yocto] Possible introspection failure in master
> On 18 Mar 2016, at 18:59, alexander.kana...@linux.intel.com wrote: > >> The gstreamer _git recipes have not been updated to include the >> gobject introspection patches which were applied to the 1.6.3 recipes. > > Yeah, I forgot about the git recipes, as they're totally hidden from > default builds. I'll get them fixed. Thanks - I’ll try and keep an eye open so I can have a look once the changes are available. > >> Try disabling gobject introspection via DISTRO or MACHINE features, ie: >> >> MACHINE_FEATURES_BACKFILL_CONSIDERED_append = " >> gobject-introspection-data" > > That is not going to help, I'm afraid. The recipes need further custom > fixing even when introspection is disabled. > > Alex -- Chris Tapp opensou...@keylevel.com www.keylevel.com You can tell you're getting older when your car insurance gets real cheap! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [matchbox-wm][PATCH] ewmh: Fix data type of a few XChangeProperty calls
XChangeProperty documentation: "If the specified format is 32, the
property data must be a long array."
Using int can lead to bogus data being used on platforms where long
actually is different from int.
Signed-off-by: Jussi Kukkonen
---
Yocto-specific reference: Sato does not really use the other cases
but _NET_SHOW_DESKTOP corruption lead to problems like [YOCTO #9284]
and [YOCTO #9026].
src/ewmh.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/src/ewmh.c b/src/ewmh.c
index 31ac969..a736037 100644
--- a/src/ewmh.c
+++ b/src/ewmh.c
@@ -136,7 +136,7 @@ ewmh_init(Wm *w)
void
ewmh_init_props(Wm *w)
{
- int num_desktops = 1;
+ long num_desktops = 1;
set_compliant(w);
set_supported(w);
@@ -455,15 +455,18 @@ ewmh_update_lists(Wm *w)
*/
if (w->config->super_modal)
{
+ long modals = w->n_modals_present;
+ long modal_blockers = w->n_modal_blocker_wins;
+
XChangeProperty(w->dpy, w->root,
w->atoms[_MB_NUM_MODAL_WINDOWS_PRESENT],
XA_CARDINAL, 32, PropModeReplace,
- (unsigned char *)&w->n_modals_present, 1);
+ (unsigned char *)&modals, 1);
XChangeProperty(w->dpy, w->root,
w->atoms[_MB_NUM_SYSTEM_MODAL_WINDOWS_PRESENT],
XA_CARDINAL, 32, PropModeReplace,
- (unsigned char *)&w->n_modal_blocker_wins, 1);
+ (unsigned char *)&modal_blockers, 1);
}
}
@@ -472,7 +475,7 @@ ewmh_update_desktop_hint(Wm *w)
{
/* Desktop showing hint */
- int val = (w->flags & DESKTOP_RAISED_FLAG) ? 1 : 0;
+ long val = (w->flags & DESKTOP_RAISED_FLAG) ? 1 : 0;
XChangeProperty(w->dpy, w->root, w->atoms[_NET_SHOW_DESKTOP],
XA_CARDINAL, 32, PropModeReplace,
--
2.7.0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Re: Qt5.6 new modules
Hi, 2016-03-17 17:16 GMT+01:00 idealsim : > Hi, i have started a build of the image this master Branch, like you said i > have an error on qtserialbus : > > WARNING: Failed to fetch URL > git://github.com/qtproject/qtserialbus.git;name=qtserialbus;branch=5.6;protocol=git, > attempting MIRRORS if available > ERROR: Fetcher failure: Unable to find revision > 6a16281aceedb713676e16c3074e6f7ea1e70b79 in branch 5.6 even from upstream > ERROR: Function failed: Fetcher failure for URL: > 'git://github.com/qtproject/qtserialbus.git;name=qtserialbus;branch=5.6;protocol=git'. > Unable to fetch URL from any source. > ERROR: Logfile of failure stored in: > /media/modjo/data1TO/yocto/seco/udoo-community-bsp/neoBuild/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/qtserialbus/5.5.99+5.6.0-rc+gitAUTOINC+6a16281ace-r0/temp/log.do_fetch.5862 > ERROR: Task 894 > (/media/modjo/data1TO/yocto/seco/udoo-community-bsp/sources/meta-qt5/recipes-qt/qt5/qtserialbus_git.bb, > do_fetch) failed with exit code '1' > > This is my qtserialbus_git.bb : > > require qt5.inc > require qt5-git.inc > > # There are no LGPLv3-only licensed files in this component. > # There are no GPLv2 licensed files in this component. > LICENSE = "GFDL-1.3 & BSD & (LGPL-2.1 & The-Qt-Company-Qt-LGPL-Exception-1.1 > | LGPL-3.0)" > LIC_FILES_CHKSUM = " \ > file://LICENSE.LGPLv3;md5=b8c75190712063cde04e1f41b6fdad98 \ > file://LICENSE.GPLv3;md5=40f9bf30e783ddc201497165dfb32afb \ > file://LICENSE.FDL;md5=6d9f2a9af4c8b8c3c769f6cc1b6aaf7e \ > file://LICENSE.GPLv2;md5=05832301944453ec79e40ba3c3cfceec \ > " > > DEPENDS += "qtbase qtserialport" > > SRCREV = "6a16281aceedb713676e16c3074e6f7ea1e70b79" The SRCREV is the git SHA1 of the repository qtserialbus. For the 5.6 Branch the latest one is: SRCREV = "92c979c6652d55c30ab9118d45db74d8da96fc3b" You can check the SHA1s here: https://github.com/qtproject/qtserialbus/commits/5.6 The MD5 Sums will be complained during configure step and bitbake wil tell you the right ones. Please check if the Licences do match Regards, Christian > > An idea is welcome ! > > Regards, > > Mickaël > > > > Le 16/03/2016 14:57, idealsim a écrit : > > Thanks for the tip. I will try it out and let you know ... > > Regards, > > Mickaël > > Le 16/03/2016 10:17, Christian Ege a écrit : > > Hi,, > > 2016-03-16 9:04 GMT+01:00 idealsim : > > Hi, we have build an image for udoo neo from meta-qt5 jansa/master-5.6 and > works fine (thanks to Christian Ege ). The problem is that I'm looking for > https://github.com/qtproject/qtquickcontrols2 and > https://github.com/qtproject/qtserialbus. My question is how we can add this > modules to our build ? I add this to our local.conf : > > "qtquickcontrols2 \ > qtserialbus \ > " > But this modules don't have buildable providers ! If someone can help to > said me how to proceed ... > > You can try to add a meta-qt5/recipes-qt/qt5/qtserialbus_git.bb and > take for example meta-qt5/recipes-qt/qt5/qtsensors_git.bb as reference > > require qt5.inc > require qt5-git.inc > # There are no LGPLv3-only licensed files in this component. > # There are no GPLv2 licensed files in this component. > LICENSE = "GFDL-1.3 & BSD & (LGPL-2.1 & > The-Qt-Company-Qt-LGPL-Exception-1.1 | LGPL-3.0)" > LIC_FILES_CHKSUM = " \ > file://LICENSE.LGPLv21;md5=58a180e1cf84c756c29f782b3a485c29 \ > file://LICENSE.LGPLv3;md5=b8c75190712063cde04e1f41b6fdad98 \ > file://LICENSE.GPLv3;md5=40f9bf30e783ddc201497165dfb32afb \ > file://LGPL_EXCEPTION.txt;md5=9625233da42f9e0ce9d63651a9d97654 \ > file://LICENSE.FDL;md5=6d9f2a9af4c8b8c3c769f6cc1b6aaf7e \ > file://LICENSE.GPLv2;md5=05832301944453ec79e40ba3c3cfceec \ > " > DEPENDS += "qtbase" > > SRCREV = "71a323e1f12df8d213a4052621027e223eb5a343" > > The configure step will bail out due to the fact that you have wrong > checksums but it will show you the right ones > > Best, > Christian > > > regards, > > Mickael > > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > > > > -- http://ch.ege.io/ -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [matchbox-panel-2][PATCH] showdesktop: Make sure active state is initialized
There are cases (in qemu at least) where set_active()
is never called on startup. Make sure we initialize the active
state so the icon gets loaded and the applet is not confused
about the current state.
Signed-off-by: Jussi Kukkonen
---
applets/showdesktop/showdesktop.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/applets/showdesktop/showdesktop.c
b/applets/showdesktop/showdesktop.c
index 61dd5c2..33c13e1 100644
--- a/applets/showdesktop/showdesktop.c
+++ b/applets/showdesktop/showdesktop.c
@@ -181,6 +181,12 @@ button_clicked_cb (GtkButton *button,
&xev);
}
+static void
+realize_cb (GtkWidget *button, ShowDesktopApplet *applet)
+{
+sync_applet (applet);
+}
+
G_MODULE_EXPORT GtkWidget *
mb_panel_applet_create (const char*id,
GtkOrientation orientation)
@@ -216,6 +222,10 @@ mb_panel_applet_create (const char*id,
"clicked",
G_CALLBACK (button_clicked_cb),
applet);
+g_signal_connect (button,
+ "realize",
+ G_CALLBACK (realize_cb),
+ applet);
g_object_weak_ref (G_OBJECT (button),
(GWeakNotify) show_desktop_applet_free,
--
2.7.0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] kernel: "devtool modify -x" issue
Hi Steve,
FYI the backports just got merged over the weekend.
Cheers,
Paul
On Tue, 15 Mar 2016 09:53:08 Paul Eggleton wrote:
> I hope we are talking a week or less, but I'm not able to give you a
> definitive answer - it depends on patch review and how busy we are dealing
> with issues on the master branch among other things.
>
> Cheers,
> Paul
>
> On Mon, 14 Mar 2016 13:49:40 Steve Rae wrote:
> > thanks much...
> > I am very new to this: does "not long though" mean 2-3 days or 2-3 weeks
> > or
> > ???
> >
> >
> > On Mon, Mar 14, 2016 at 1:47 PM, Paul Eggleton
> >
> > wrote:
> > > Hi Steve,
> > >
> > > I've just sent out the patches; beyond that it's a matter of the stable
> > > branch testing and integration process. I hope not long though.
> > >
> > > Cheers,
> > > Paul
> > >
> > > On Mon, 14 Mar 2016 11:51:08 Steve Rae wrote:
> > >> Paul -- please ETA for getting this into the "jethro" branch.
> > >> Thanks, Steve
> > >>
> > >> On Fri, Mar 11, 2016 at 10:11 AM, Steve Rae
>
> wrote:
> > >> > OK - this seems to build successfully - Thanks!
> > >> >
> > >> >>> although I still do see the line:
> > >> > Cloning into '/tmp/devtool6ZA4IK/workdir/source'...
> > >> >
> > >> > On Thu, Mar 10, 2016 at 7:07 PM, Paul Eggleton
> > >> >
> > >> > wrote:
> > >> >> On Fri, 11 Mar 2016 07:55:25 Paul Eggleton wrote:
> > >> >>> On Wed, 09 Mar 2016 10:12:30 Steve Rae wrote:
> > >> >>> > ( using jethro )
> > >> >>> >
> > >> >>> > I have a 'linux-yocto-custom' layer which builds successfully;
> > >> >>> > then
> > >> >>> > I
> > >
> > > run:
> > >> >>> > devtool modify -x linux-yocto-custom ../../poky-dev/kernel
> > >> >>> > >>
> > >> >>> > >> I see a line:
> > >> >>> > Cloning into '/tmp/devtoolfgiLXr/workdir/source'...
> > >> >>> >
> > >> >>> > Then I run:
> > >> >>> > devtool build linux-yocto-custom
> > >> >>> > >>
> > >> >>> > >> it reports the following:
> > >> >>> > Log data follows:
> > >> >>> > | DEBUG: Executing shell function do_kernel_configme
> > >> >>> > | NOTE: kernel configme
> > >> >>> > | [INFO] Configuring target/machine combo: "standard/bcmjava"
> > >> >>> > | [ERROR] frag
> > >> >>> >
> > >> >>> > /tmp/devtoolfgiLXr/workdir/source/.meta/cfg/scratch/obj/tmp/devto
> > >> >>> > ol
> > >> >>> > fgi
> > >> >>> > LXr/
> > >> >>> > wo rkdir/defconfig does not exist
> > >> >>> >
> > >> >>> > | [ERROR] No configuration fragments found, this typically is a
> > >> >>> >
> > >> >>> > misconfigured BSP.
> > >> >>> >
> > >> >>> > | Check that fragments (or defconfigs) are referenced by
> > >> >>> > | the
> > >> >>> > | board
> > >> >>> >
> > >> >>> > description.
> > >> >>> >
> > >> >>> > | config of "standard/bcmjava" failed
> > >> >>> > | WARNING: exit code 1 from a shell command.
> > >> >>> >
> > >> >>> > which is true, because "devtool modify -x" deletes the temp
> > >> >>> > directory
> > >> >>> > ("/tmp/devtoolfgiLXr") that it used to create this specified
> > >> >>> > workspace
> > >> >>>
> > >> >>> Hmm, it looks like the temporary path is leaking in somewhere. Is
> > >> >>> there
> > >> >>> an
> > >> >>> easy way I can reproduce this here so I can debug it?
> > >> >>
> > >> >> Actually I just realised, this task ought not to be running at all -
> > >> >> in
> > >> >> master we've disabled it under these circumsances. There's also one
> > >> >> other fix on master that you'd benefit from in jethro - I've put
> > >> >> them
> > >> >> both on this>>
> > >> >>
> > >> >> contrib branch:
> > >> >> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=paul
> > >> >> e/
> > >> >> jet
> > >> >> hro-fixes4>>
> > >> >>
> > >> >> If you could let me know how it works for you that would be great;
> > >> >> I'll
> > >> >> send it out soon.
> > >> >>
> > >> >> Cheers,
> > >> >> Paul
> > >> >>
> > >> >> --
> > >> >>
> > >> >> Paul Eggleton
> > >> >> Intel Open Source Technology Centre
> > >
> > > --
> > >
> > > Paul Eggleton
> > > Intel Open Source Technology Centre
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-selinux][PATCH 0/2] policy upgrade and cleanup
By default we build *_git refpolicy packages. The release packages have been lagging behind. The first patch replaces the 2.2014120 release with the latest (2.20151208). The second removes the old 2.20140311 release. Philip Tricca (2): refpolicy: Replace 2.2014120 with release 2.20151208. refpolicy: Remove 2.20140311 release. .../ftp-add-ftpd_t-to-mlsfilewrite.patch | 39 .../refpolicy-2.20140311/poky-fc-clock.patch | 22 -- .../poky-fc-corecommands.patch | 24 --- .../refpolicy-2.20140311/poky-fc-dmesg.patch | 20 -- .../refpolicy-2.20140311/poky-fc-fix-bind.patch| 30 --- .../poky-fc-fix-real-path_login.patch | 37 .../poky-fc-fix-real-path_resolv.conf.patch| 24 --- .../poky-fc-fix-real-path_shadow.patch | 34 --- .../poky-fc-fix-real-path_su.patch | 25 --- .../refpolicy-2.20140311/poky-fc-fstools.patch | 65 -- .../refpolicy-2.20140311/poky-fc-ftpwho-dir.patch | 27 --- .../refpolicy-2.20140311/poky-fc-iptables.patch| 24 --- .../refpolicy-2.20140311/poky-fc-mta.patch | 27 --- .../refpolicy-2.20140311/poky-fc-netutils.patch| 24 --- .../refpolicy-2.20140311/poky-fc-nscd.patch| 27 --- .../refpolicy-2.20140311/poky-fc-rpm.patch | 25 --- .../refpolicy-2.20140311/poky-fc-screen.patch | 27 --- .../refpolicy-2.20140311/poky-fc-ssh.patch | 24 --- .../refpolicy-2.20140311/poky-fc-su.patch | 23 --- .../refpolicy-2.20140311/poky-fc-subs_dist.patch | 29 --- .../refpolicy-2.20140311/poky-fc-sysnetwork.patch | 41 .../refpolicy-2.20140311/poky-fc-udevd.patch | 35 .../poky-fc-update-alternatives_hostname.patch | 23 --- .../poky-fc-update-alternatives_sysklogd.patch | 59 -- .../poky-fc-update-alternatives_sysvinit.patch | 53 - ...poky-policy-add-rules-for-bsdpty_device_t.patch | 121 --- ...ky-policy-add-rules-for-syslogd_t-symlink.patch | 30 --- .../poky-policy-add-rules-for-tmp-symlink.patch| 99 - ...ky-policy-add-rules-for-var-cache-symlink.patch | 34 --- ...licy-add-rules-for-var-log-symlink-apache.patch | 31 --- ...rules-for-var-log-symlink-audisp_remote_t.patch | 29 --- ...poky-policy-add-rules-for-var-log-symlink.patch | 145 - ...ky-policy-add-syslogd_t-to-trusted-object.patch | 31 --- ...-policy-allow-nfsd-to-exec-shell-commands.patch | 58 -- ...-policy-allow-setfiles_t-to-read-symlinks.patch | 29 --- .../poky-policy-allow-sysadm-to-run-rpcinfo.patch | 33 --- .../poky-policy-don-t-audit-tty_device_t.patch | 35 .../poky-policy-fix-dmesg-to-use-dev-kmsg.patch| 37 .../poky-policy-fix-new-SELINUXMNT-in-sys.patch| 229 - ...poky-policy-fix-nfsd_t-to-mount_nfsd_fs_t.patch | 65 -- ...olicy-fix-setfiles-statvfs-get-file-count.patch | 31 --- ...ky-policy-fix-seutils-manage-config-files.patch | 43 .../refpolicy-update-for_systemd.patch | 46 - .../ftp-add-ftpd_t-to-mlsfilewrite.patch | 39 .../refpolicy-2.20141203/poky-fc-clock.patch | 22 -- .../poky-fc-corecommands.patch | 24 --- .../refpolicy-2.20141203/poky-fc-dmesg.patch | 20 -- .../refpolicy-2.20141203/poky-fc-fix-bind.patch| 30 --- .../poky-fc-fix-real-path_login.patch | 37 .../poky-fc-fix-real-path_resolv.conf.patch| 24 --- .../poky-fc-fix-real-path_shadow.patch | 34 --- .../poky-fc-fix-real-path_su.patch | 25 --- .../refpolicy-2.20141203/poky-fc-fstools.patch | 70 --- .../refpolicy-2.20141203/poky-fc-ftpwho-dir.patch | 27 --- .../refpolicy-2.20141203/poky-fc-iptables.patch| 24 --- .../refpolicy-2.20141203/poky-fc-mta.patch | 27 --- .../refpolicy-2.20141203/poky-fc-netutils.patch| 24 --- .../refpolicy-2.20141203/poky-fc-nscd.patch| 27 --- .../refpolicy-2.20141203/poky-fc-rpm.patch | 25 --- .../refpolicy-2.20141203/poky-fc-screen.patch | 27 --- .../refpolicy-2.20141203/poky-fc-ssh.patch | 24 --- .../refpolicy-2.20141203/poky-fc-su.patch | 23 --- .../refpolicy-2.20141203/poky-fc-subs_dist.patch | 29 --- .../refpolicy-2.20141203/poky-fc-sysnetwork.patch | 46 - .../refpolicy-2.20141203/poky-fc-udevd.patch | 35 .../poky-fc-update-alternatives_hostname.patch | 23 --- .../poky-fc-update-alternatives_sysklogd.patch | 59 -- .../poky-fc-update-alternatives_sysvinit.patch | 53 - ...poky-policy-add-rules-for-bsdpty_device_t.patch | 121 --- ...ky-policy-add-rules-for-syslogd_t-symlink.patch | 30 --- .../poky-policy-add-rules-for-tmp-symlink.patch| 99 - ...ky-policy-add-rules-for-var-cache-symlink.patch | 34 --- ...licy-add-rules-for-var-log-symlink-apache.patch | 31 --- ...rules-for-var-log-symlink-audisp_remote_t.patc
[yocto] [meta-selinux][PATCH 2/2] refpolicy: Remove 2.20140311 release.
Signed-off-by: Philip Tricca --- .../ftp-add-ftpd_t-to-mlsfilewrite.patch | 39 .../refpolicy-2.20140311/poky-fc-clock.patch | 22 -- .../poky-fc-corecommands.patch | 24 --- .../refpolicy-2.20140311/poky-fc-dmesg.patch | 20 -- .../refpolicy-2.20140311/poky-fc-fix-bind.patch| 30 --- .../poky-fc-fix-real-path_login.patch | 37 .../poky-fc-fix-real-path_resolv.conf.patch| 24 --- .../poky-fc-fix-real-path_shadow.patch | 34 --- .../poky-fc-fix-real-path_su.patch | 25 --- .../refpolicy-2.20140311/poky-fc-fstools.patch | 65 -- .../refpolicy-2.20140311/poky-fc-ftpwho-dir.patch | 27 --- .../refpolicy-2.20140311/poky-fc-iptables.patch| 24 --- .../refpolicy-2.20140311/poky-fc-mta.patch | 27 --- .../refpolicy-2.20140311/poky-fc-netutils.patch| 24 --- .../refpolicy-2.20140311/poky-fc-nscd.patch| 27 --- .../refpolicy-2.20140311/poky-fc-rpm.patch | 25 --- .../refpolicy-2.20140311/poky-fc-screen.patch | 27 --- .../refpolicy-2.20140311/poky-fc-ssh.patch | 24 --- .../refpolicy-2.20140311/poky-fc-su.patch | 23 --- .../refpolicy-2.20140311/poky-fc-subs_dist.patch | 29 --- .../refpolicy-2.20140311/poky-fc-sysnetwork.patch | 41 .../refpolicy-2.20140311/poky-fc-udevd.patch | 35 .../poky-fc-update-alternatives_hostname.patch | 23 --- .../poky-fc-update-alternatives_sysklogd.patch | 59 -- .../poky-fc-update-alternatives_sysvinit.patch | 53 - ...poky-policy-add-rules-for-bsdpty_device_t.patch | 121 --- ...ky-policy-add-rules-for-syslogd_t-symlink.patch | 30 --- .../poky-policy-add-rules-for-tmp-symlink.patch| 99 - ...ky-policy-add-rules-for-var-cache-symlink.patch | 34 --- ...licy-add-rules-for-var-log-symlink-apache.patch | 31 --- ...rules-for-var-log-symlink-audisp_remote_t.patch | 29 --- ...poky-policy-add-rules-for-var-log-symlink.patch | 145 - ...ky-policy-add-syslogd_t-to-trusted-object.patch | 31 --- ...-policy-allow-nfsd-to-exec-shell-commands.patch | 58 -- ...-policy-allow-setfiles_t-to-read-symlinks.patch | 29 --- .../poky-policy-allow-sysadm-to-run-rpcinfo.patch | 33 --- .../poky-policy-don-t-audit-tty_device_t.patch | 35 .../poky-policy-fix-dmesg-to-use-dev-kmsg.patch| 37 .../poky-policy-fix-new-SELINUXMNT-in-sys.patch| 229 - ...poky-policy-fix-nfsd_t-to-mount_nfsd_fs_t.patch | 65 -- ...olicy-fix-setfiles-statvfs-get-file-count.patch | 31 --- ...ky-policy-fix-seutils-manage-config-files.patch | 43 .../refpolicy-update-for_systemd.patch | 46 - .../refpolicy/refpolicy-mcs_2.20140311.bb | 11 - .../refpolicy/refpolicy-minimum_2.20140311.bb | 48 - .../refpolicy/refpolicy-mls_2.20140311.bb | 10 - .../refpolicy/refpolicy-standard_2.20140311.bb | 8 - .../refpolicy/refpolicy-targeted_2.20140311.bb | 20 -- .../refpolicy/refpolicy_2.20140311.inc | 60 -- 49 files changed, 2071 deletions(-) delete mode 100644 recipes-security/refpolicy/refpolicy-2.20140311/ftp-add-ftpd_t-to-mlsfilewrite.patch delete mode 100644 recipes-security/refpolicy/refpolicy-2.20140311/poky-fc-clock.patch delete mode 100644 recipes-security/refpolicy/refpolicy-2.20140311/poky-fc-corecommands.patch delete mode 100644 recipes-security/refpolicy/refpolicy-2.20140311/poky-fc-dmesg.patch delete mode 100644 recipes-security/refpolicy/refpolicy-2.20140311/poky-fc-fix-bind.patch delete mode 100644 recipes-security/refpolicy/refpolicy-2.20140311/poky-fc-fix-real-path_login.patch delete mode 100644 recipes-security/refpolicy/refpolicy-2.20140311/poky-fc-fix-real-path_resolv.conf.patch delete mode 100644 recipes-security/refpolicy/refpolicy-2.20140311/poky-fc-fix-real-path_shadow.patch delete mode 100644 recipes-security/refpolicy/refpolicy-2.20140311/poky-fc-fix-real-path_su.patch delete mode 100644 recipes-security/refpolicy/refpolicy-2.20140311/poky-fc-fstools.patch delete mode 100644 recipes-security/refpolicy/refpolicy-2.20140311/poky-fc-ftpwho-dir.patch delete mode 100644 recipes-security/refpolicy/refpolicy-2.20140311/poky-fc-iptables.patch delete mode 100644 recipes-security/refpolicy/refpolicy-2.20140311/poky-fc-mta.patch delete mode 100644 recipes-security/refpolicy/refpolicy-2.20140311/poky-fc-netutils.patch delete mode 100644 recipes-security/refpolicy/refpolicy-2.20140311/poky-fc-nscd.patch delete mode 100644 recipes-security/refpolicy/refpolicy-2.20140311/poky-fc-rpm.patch delete mode 100644 recipes-security/refpolicy/refpolicy-2.20140311/poky-fc-screen.patch delete mode 100644 recipes-security/refpolicy/refpolicy-2.20140311/poky-fc-ssh.patch delete mode 100644 recipes-security/refpolicy/refpolicy-2.20140311/poky-fc-su.patch delete mode 100644 recipes-security/refpolicy
[yocto] what is your way to flash for target using own image?
Hi, I have always flash own compiled binary for to check some modification. this way, it was spending too much time. So, i really want to know the effective way. Please help and shares your wisdom. Thank you. Best Regards. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
