From: Changqing Li
*preinst use "-f remove" to remove any links in the /etc/rcrunlevel.d
but this will make user cannot keep previous init script link
after upgrade
eg: user disable one service before upgrade, after upgrade, service
could be started since during preinst, all link have
These three patches are for support disable/enable function for update-rc.d
change in V2:
add some comments and fix commit message
change in V1:
* change of script update-rc.d is for support disable/enable of init script link
* update-rc.d.bbclass remove preinst to make disable/enable can work
On 2019-01-21 07:56, Zoran Stojsavljevic wrote:
Hello to all,
I have added to my local.conf the following lines in order to port
systemd service
in YOCTO (Thud release):
_/## Add systemd service
VIRTUAL-RUNTIME_init_manager = "systemd"
VIRTUAL-RUNTIME_dev_manager = "systemd"
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Zoran Stojsavljevic
Sent: Monday, January 21, 2019 7:56 AM
[...]
> While downloading initramfs on the target system, while bringing kernel up,
> the following
> happened (actual log):
> [ 0.00]
From: Changqing Li
Add support of enable/disable function, so that user can keep
previous config like disable one service even after upgrade package.
this patch need to work with oe-core patch
[update-rc.d.bbclass: remove preinst and remove -f for postinst]
[Yocto 12955]
Signed-off-by:
From: Changqing Li
Currently, yocto doc refer link http://www.tin.org/bin/man.cgi?
section=8=update-rc.d. as man page of update-rc.d, but lastest
debian udpate-rc.d have big difference with yocto, they need insserv
and all the initscripts support LSB comment header.
change to new link which is
Hello,
just to remind you that RRS continues to send these badly outdated,
misleading reports once a week to yocto@. Please switch them off
and/or take the new RRS into use (if the new RRS addresses the
problem).
Alex
On Mon, 21 Jan 2019 at 06:01, wrote:
>
> This mail was sent out by Recipe
Hi,
I have some build error problem.
Now, I have working on rocko release.
When I have built, I met this error message
build_src/tmp/work/aarch64-poky-linux/python3-pycairo/1.10.0-r2/temp/log.do_configure.81617
Log data follows:
| DEBUG:Executing shell function do_configure
| sh :1: bunzip2: not
Just FYI, I haven't forgot about this patch. I want to wait until the
dependent OE-core patch is at least in the master-next branch before I
apply this to the MinGW master-next branch. If you want to give me a
ping when the OE-core patch shows up in master-next, it would be very
helpful.
Thanks
Dear Yocto Experts,
I am seeing the below error when i am trying to integrate freescale
layers into my custom os?
srinishanmugam@ni-bln-07594:~/customBuild_test_rpi/customos/build_customosdistro_imx8$
bitbake -f -c clean custom-image-debug-imx8
WARNING: Host distribution "ubuntu-18.04" has not
Dear Yocto Experts,
I am trying to customize my vendor specific Yocto BSP's to my custom
OS. I am facing the below error, could you please do the needful or
provide me some pointers from your end for solving this issue
Error:
$ bitbake fsl-image-validation-imx
WARNING: Host distribution
Thanks a ton Ross, your inputs really worked :)
On Tue, Jan 15, 2019 at 11:34 AM Burton, Ross wrote:
>
> You'll have to not install either connman or network manager.
>
> Ross
>
> On Tue, 15 Jan 2019 at 05:18, srinivasan wrote:
> >
> > Dear Yocto experts,
> >
> > I am seeing the below error
Hi All,
For how many years yocto community officially support any Yocto release?
(This includes like bug fixes, CVE fixes, enhancements, etc etc)
For example, the latest release happened on 11/15/2018 (Yocto 2.6), so how
long this will be supported by community?
Sorry, if this information is
imx8mmevk
On Fri, Jan 18, 2019 at 12:20 PM Daiane Angolini wrote:
>
> On Fri, Jan 18, 2019 at 6:46 AM srinivasan wrote:
> >
> > Dear Yocto Experts,
> >
> > I am seeing the below error when i am trying to integrate freescale
> > layers into my custom os?
>
> Which imx8 MACHINE are you trying?
>
In yocto project ptest data are installed to
PTEST_PATH ?= "${libdir}/${BPN}/ptest". Here make DEFAULT_DIRECTORY
be able to be defined outside of c code (e.g. passed in by CFLAGS),
in case libdir isn't "/usr/lib", which will cause "No ptests found"
error when running "ptest-runner" command. We
Dear Yocto Experts Team,
I am seeing the below error after changing the package_classes from "rpm"
to "deb" as below, when I am trying to add freescale meta layers to my
custom yocto distribution
Could you please do the needful by providing some inputs in resolving the
below issue?
Logs:
Hallo Yocto,
Is it possible to use old versions of the recipe with newer yocto releases?
For example, I am currently trying to compile a 2015.01 version of the
U-boot recipe with the Yocto Sumo release, but unfortunately it throws a
compilation error that oe-runmake failed. Could anyone please
That's because we now prune what tools the recipes can see on the
host, and cc isn't on the list. Override cc to be ${BUILD_CC} and
this will work.
Ross
On Mon, 21 Jan 2019 at 16:14, Johannes Humpert
wrote:
>
> Hallo Yocto,
>
> Is it possible to use old versions of the recipe with newer yocto
this is the problem
dpkg-deb: error: package name has characters that aren't lowercase
alphanums or '-+.'
its possible that linux-imx is adding some string to PR which is not
honoring this convention usually introduced by setting EXTRAVERSION in
kernel toplevel makefile
On Mon, Jan 21, 2019 at
All,
The triage team meets weekly and does its best to handle the bugs reported into
the Bugzilla. The number of people attending that meeting has fallen, as have
the number of people available to help fix bugs. One of the things we hear
users report is they don't know how to help. We (the
Pushed, thx!,
http://git.yoctoproject.org/cgit/cgit.cgi/ptest-runner2/commit/?id=e1062f776eea60c50435c6b8ddf9714a31141aee
Feel free to update the recipe.
Cheers,
Anibal
On Sun, 20 Jan 2019 at 20:29, Li Zhou wrote:
> In yocto project ptest data are installed to
> PTEST_PATH ?=
> Hi All,
> For how many years yocto community officially support any Yocto
> release? (This includes like bug fixes, CVE fixes, enhancements, etc etc) For
> example, the latest release happened on 11/15/2018 (Yocto 2.6), so how long
> this will be supported by community?
> Sorry, if this
Hi all:
I am using the jethro (2.0.1) version of yocto.
I added a shared library (foo.so) to our native sdk build by putting
BBCLASSEXTEND = "nativesdk"
in the foo.bb recipe, then
TOOLCHAIN_HOST_TASK_append += " nativesdk-foo nativesdk-foo-dev "
in our rootfs image recipe.
This had
On 1/21/19 10:47 PM, Joshua Watt wrote:
Just FYI, I haven't forgot about this patch. I want to wait until the
dependent OE-core patch is at least in the master-next branch before I
apply this to the MinGW master-next branch. If you want to give me a
ping when the OE-core patch shows up in
Hello All,
This is the full report for 2.6.1 RC1:
https://wiki.yoctoproject.org/wiki/WW02_-_2019-01-09_-_Full_Test_Cycle_2.6.1_RC1
=== Summary
All planned tests were executed.
Total Test Executed - 3650
Passed Test - 3422
Failed Test - 210
Blocked Test - 12
From: Jeff Kirsher
This reverts commit 59361316afcb08569af21e1af83e89c7051c055a.
Due to problems found in additional testing, this causes an illegal
context switch in the RCU read-side critical section.
CC: Dave Jones
CC: Cong Wang
CC: Jan Jablonsky
Signed-off-by: Jeff Kirsher
On 1/18/19 9:20 AM, Paul Gortmaker wrote:
Bruce, Yocto kernel folks:
Here is the next 4.18.x stable update "extension" primarily created
for the Yocto project, continuing from the previous v4.18.24 release.
There are about 125 commits here, based on commits chosen from what
was used in the
Which kernel/bsp branch is this one for ? I'm about to push an
update to linux-yocto-dev today, so from the comment below, it
looks like we are already covered ?
Bruce
On 1/21/19 5:09 AM, zhe...@windriver.com wrote:
From: Jeff Kirsher
This reverts commit
On 1/21/19 8:55 AM, He Zhe wrote:
On 1/21/19 9:47 PM, Bruce Ashfield wrote:
Which kernel/bsp branch is this one for ? I'm about to push an
update to linux-yocto-dev today, so from the comment below, it
looks like we are already covered ?
This is for standard/base. It's from v5.0-rc3.
ok.
On 1/18/19 4:45 PM, Jon Mason wrote:
Last 2 config patches needed for the upcoming rename. The first one
allows for the current qemuarm to be renamed qemuarmv5, while keeping
the existing name for those who still want to access it that way for
legacy reasons. The second one adds defconfigs for
On 1/21/19 9:47 PM, Bruce Ashfield wrote:
> Which kernel/bsp branch is this one for ? I'm about to push an
> update to linux-yocto-dev today, so from the comment below, it
> looks like we are already covered ?
This is for standard/base. It's from v5.0-rc3.
Zhe
>
> Bruce
>
> On 1/21/19 5:09
31 matches
Mail list logo
