date:20201124

[yocto] M+ & H bugs with Milestone Movements WW47

2020-11-24 Thread Stephen Jolley

All,

YP M+ or high bugs which moved to a new milestone in WW47 are listed below: 


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


Medium+

  13338

SDK  build fails if image contains bash

randy.macl...@windriver.com

akus...@mvista.com

2.6.3

3.3 M1


 

  13566

Write tests for multiconfig files in layers and document

randy.macl...@windriver.com

mostthings...@gmail.com

3.2 M4

3.3 M1


 

  13722

Debugging With the GNU Project Debugger enhancements

randy.macl...@windriver.com

newco...@yoctoproject.org

3.2 M4

3.3 M1


 

  13822

Easy to have misleading warnings if env script is executed instead of sourced

randy.macl...@windriver.com

newco...@yoctoproject.org

3.2 M4

3.3 M1


 

  14040

recipetool: creating binary recipe from upstream git repo without explicit PV 
causes circular reference in SRC_URI

randy.macl...@windriver.com

mostthings...@gmail.com

3.2 M4

3.3 M1

Thanks, 

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com  

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#51549): https://lists.yoctoproject.org/g/yocto/message/51549
Mute This Topic: https://lists.yoctoproject.org/mt/78488518/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Enhancements/Bugs closed WW47!

2020-11-24 Thread Stephen Jolley

All,

The below were the owners of enhancements or bugs closed during the last
week!


Who

Count


richard.pur...@linuxfoundation.org

5


randy.macl...@windriver.com

4


mhalst...@linuxfoundation.org

1


r...@burtonini.com

1


Grand Total

11

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#51548): https://lists.yoctoproject.org/g/yocto/message/51548
Mute This Topic: https://lists.yoctoproject.org/mt/78488505/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Current high bug count owners for Yocto Project 3.3

2020-11-24 Thread Stephen Jolley

All,

Below is the list as of top 50 bug owners as of the end of WW47 of who have
open medium or higher bugs and enhancements against YP 3.3.   There are 111
possible work days left until the final release candidates for YP 3.3 needs
to be released. 


Who

Count


richard.pur...@linuxfoundation.org

36


r...@burtonini.com

24


david.re...@windriver.com

21


bruce.ashfi...@gmail.com

20


bluelightn...@bluelightning.org

19


jpewhac...@gmail.com

12


timothy.t.orl...@intel.com

12


sakib.sa...@windriver.com

11


mark.mor...@windriver.com

11


kai.k...@windriver.com

9


akuster...@gmail.com

9


trevor.gamb...@windriver.com

9


qi.c...@windriver.com

6


stacy.gaikov...@windriver.com

5


raj.k...@gmail.com

5


mingli...@windriver.com

4


yi.z...@windriver.com

4


idad...@gmail.com

4


randy.macl...@windriver.com

4


chee.yang@intel.com

3


hongxu@windriver.com

3


mostthings...@gmail.com

3


alejan...@enedino.org

3


jon.ma...@arm.com

2


matthew...@posteo.net

2


jeanmarie.lemeta...@gmail.com

2


saul.w...@windriver.com

2


ydir...@free.fr

2


mark.ha...@kernel.crashing.org

2


pokyli...@reliableembeddedsystems.com

2


jae...@xilinx.com

2


nicolas.deche...@linaro.org

2


f...@evolware.org

1


anuj.mit...@intel.com

1


aeh...@gmail.com

1


mhalst...@linuxfoundation.org

1


apoorvsan...@gmail.com

1


shac...@vdoo.com

1


matt.ranos...@konsulko.com

1


dl...@gmx.de

1


kai.ruh...@live.com

1


kexin@windriver.com

1


martin.ja...@gmail.com

1


liezhi.y...@windriver.com

1


joe.sla...@windriver.com

1


jpuhl...@mvista.com

1


kerg...@gmail.com

1


maxime.roussinbelan...@gmail.com

1


akus...@mvista.com

1


kamen...@cisco.com

1

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#51547): https://lists.yoctoproject.org/g/yocto/message/51547
Mute This Topic: https://lists.yoctoproject.org/mt/78488399/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2020-11-24 Thread Stephen Jolley

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and
how to create a bugzilla account at:

https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, 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 triage
team) are therefore going to start reporting out the currently 328
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "3.2", "3.3, "3.99" and "Future", the more pressing/urgent issues
being in "3.2" and then "3.3".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer
_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#51546): https://lists.yoctoproject.org/g/yocto/message/51546
Mute This Topic: https://lists.yoctoproject.org/mt/78488382/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Status WW47'20

2020-11-24 Thread Stephen Jolley

Current Dev Position: YP 3.3 M1 development

Next Deadline: 7th December 2020 YP 3.3 M1 build

 

Next Team Meetings:

*   Bug Triage meeting Thursday Nov. 26th at 7:30am PDT (

https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*   Monthly Project Meeting Tuesday Dec. 1st at 8am PDT (

https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
 )
*   Weekly Engineering Sync Tuesday Nov. 24th at 8am PDT (

https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
 )
*   Twitch -  See https://www.twitch.tv/theyoctojester

 

Key Status/Updates:

*   YP 3.1.4 will build later this week.
*   YP 3.3 development in master is continuing as patches are reviewed,
tested and merged.
*   We plan to backport the sphinx documentation transition back to our
LTS after 3.1.4 is built.
*   A small but important issue was identified related to build
reproducibility where the host umask was influencing the build output in
relatively minor ways. We plan to run a mixture of umasks on the autobuilder
infrastructure in future to avoid this source of reproducibility issues.
There are patches for the issues queued for master and will be backported in
due course.
*   Support for fedora33 has been resolved but required making
pseudo-native host specific and not 'uninative' due to differences in the
way pseudo builds depending on the presence of headers.
*   Hashserve "passthrough" support has merged allowing hashservers to
be chained together, thanks Joshua.
*   Intermittent autobuilder issues continue to occur. You can see the
list of failures we're continuing to see by searching for the "AB-INT" tag
in bugzilla:

https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT

*   Further autobuilder improvements have been submitted and accepted
into upstream buildbot (field history, triggered build summary stats and
work name display in build summary). As these are released and deployed,
they will make small but important improvements to the autobuilder
usability.

 

Ways to contribute:

*   There are bugs identified as possible for newcomers to the project:

https://wiki.yoctoproject.org/wiki/Newcomers
*   There are bugs that are currently unassigned for YP 3.3. See:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.3_Unassigned_Enhan
cements.2FBugs
*   We'd welcome new maintainers for recipes in OE-Core. Please see the
list at:

http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/main
tainers.inc and discuss with the existing maintainer, or ask on the OE-Core
mailing list. We will likely move a chunk of these to "Unassigned" soon to
help facilitate this.

 

YP 3.3 Milestone Dates:

*   YP 3.3 M1 build date 2020/12/07
*   YP 3.3 M1 Release date 2020/12/18
*   YP 3.3 M2 build date 2021/01/18
*   YP 3.3 M2 Release date 2021/01/29
*   YP 3.3 M3 build date 2021/03/01
*   YP 3.3 M3 Release date 2021/03/12
*   YP 3.3 M4 build date 2021/04/05
*   YP 3.3 M4 Release date 2021/04/30

 

Planned upcoming dot releases:

*   YP 3.1.4 build date 2020/11/2
*   YP 3.1.4 release date 2020/11/13
*   YP 3.2.1 build date 2020/11/16
*   YP 3.2.1 release date 2020/12/4
*   YP 3.1.5 build date 2021/01/11
*   YP 3.1.5 release date 2021/01/22
*   YP 3.2.2 build date 2021/02/08
*   YP 3.2.2 release date 2021/02/19
*   YP 3.1.6 build date 2021/02/22
*   YP 3.1.6 release date 2021/03/05
*   YP 3.1.7 build date 2021/03/22
*   YP 3.1.7 release date 2021/04/02

 

Tracking Metrics:

*   WDD 2532 (last week 2534) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1279 (last week 1275)
*   Patches in the Pending State: 497 (39%) [last week 497 (39%)]

 

The Yocto Project's technical governance is through its Technical Steering
Committee, more information is available at:

 
https://wiki.yoctoproject.org/wiki/TSC

 

The Status reports are now stored on the wiki at:

https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[If anyone has suggestions for other information you'd like to see on this
weekly status update, let us know!]

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:

Re: [yocto] How to add python application into the build. #python #toolchain

2020-11-24 Thread Nicolas Jeker

On Tue, 2020-11-24 at 04:33 -0800, vijayrakeshmunga...@gmail.com wrote:
> Hi, 

Hi Vijay

> I'm new to the Yocto Project, trying to include my python application
> into the build. Can anyone guide me how to write a bitbake recipe .bb
> file or any example recipe would be helpful. 

Reading and following the section about "Writing a New Recipe" in the
manual is probably a good starting point:

https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#new-recipe-writing-a-new-recipe

I usually look at related recipes that already exist (in your case some
other python recipe) and try to start with a minimal recipe and fix
build errors/missing dependencies/etc. iteratively.

> Thank & Regards,
> Vijay.
> 
> 
> 



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#51544): https://lists.yoctoproject.org/g/yocto/message/51544
Mute This Topic: https://lists.yoctoproject.org/mt/78475601/21656
Mute #python:https://lists.yoctoproject.org/g/yocto/mutehashtag/python
Mute #toolchain:https://lists.yoctoproject.org/g/yocto/mutehashtag/toolchain
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] How to add python application into the build. #python #toolchain

2020-11-24 Thread vijayrakeshmunganda

Hi,

I'm new to the Yocto Project, trying to include my python application into the 
build. Can anyone guide me how to write a bitbake recipe .bb file or any 
example recipe would be helpful.

Thank & Regards,
Vijay.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#51543): https://lists.yoctoproject.org/g/yocto/message/51543
Mute This Topic: https://lists.yoctoproject.org/mt/78475601/21656
Mute #python:https://lists.yoctoproject.org/g/yocto/mutehashtag/python
Mute #toolchain:https://lists.yoctoproject.org/g/yocto/mutehashtag/toolchain
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Yocto Project Outreachy interns

2020-11-24 Thread Dorinda

Thank you all,
I appreciate the opportunity given to me to intern with the Yocto Project.
I am excited about this internship and I look forward to working with you
on my project.

Sincerely,
Dorinda.

On Nov 24, 2020 08:47, "Nicolas Dechesne" 
wrote:

> Dear all,
>
> We are very excited to be part of the Outreachy program again for the
> December round this year, let me congratulate Ida and Dorinda for
> being accepted as interns for the next three months.
>
> I want to give a warm thank you to our mentors as well, Paul, Ross,
> Tim. Without mentors there isn't much we can do, so this is very much
> appreciated. A big thank you to Microsoft and Arm who are sponsoring
> the internships.
>
> Ida and Dorinda will engage on the following topics:
>
> == Enhance Yocto Project License Tracing
> The Yocto Project build system is typically used to build customised
> Linux images from source for embedded applications. Along with the
> image, a manifest of packages and their corresponding licenses is
> prepared, however the accuracy of the license information in the
> manifest is dependent on the accuracy of the metadata we have for each
> package (i.e. what is in the recipe file). As part of the build, we
> have an internal mapping from output files to source files which is
> currently used to prepare source packages to aid in debugging, however
> with the increasing presence of SPDX headers in source files it could
> also be used to allow tracing the license of sources used in building
> a package/image to help improve our metadata and future license
> manifests.
>
> == Add support for elfutils debug info server"
> The Yocto Project build system is typically used to build customised
> Linux images from source for embedded applications. debuginfod (part
> of elfutils 0.178 onwards) is a way to share debuginfo files, which
> provide debugging symbols for gdb to enable it to debug a running
> program on a target device. Users of the Yocto Project would benefit
> from integrating support for debuginfod such that binaries in an image
> produced by the Yocto Project build system could be debugged more
> easily.
>
> Ida and Dorinda, welcome into our open source community, you can count
> on everyone's support during your internship!
>
> cheers
> nico
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#51542): https://lists.yoctoproject.org/g/yocto/message/51542
Mute This Topic: https://lists.yoctoproject.org/mt/78473005/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][yocto-kernel-cache][master yocto-5.4][PATCH] qemuppc: configure the CONFIG_SCSI to '=y'

2020-11-24 Thread Xu, Yanfei

From: Yanfei Xu 

Changing CONFIG_SCSI from '=m' to '=y' to be consistent with its
direct dependency, which is 'CONFIG_SCSI_VIRTIO=y' in virtio.cfg.

Signed-off-by: Yanfei Xu 
---
 bsp/qemu-ppc32/qemu-ppc32.cfg | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bsp/qemu-ppc32/qemu-ppc32.cfg b/bsp/qemu-ppc32/qemu-ppc32.cfg
index 39a71e5d..ed7ec330 100644
--- a/bsp/qemu-ppc32/qemu-ppc32.cfg
+++ b/bsp/qemu-ppc32/qemu-ppc32.cfg
@@ -34,7 +34,7 @@ CONFIG_INPUT_ADBHID=y
 CONFIG_INPUT_KEYBOARD=y
 CONFIG_INPUT_MOUSE=y
 
-CONFIG_SCSI=m
+CONFIG_SCSI=y
 CONFIG_BLK_DEV_SD=m
 
 CONFIG_USB_MON=y
-- 
2.18.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9185): 
https://lists.yoctoproject.org/g/linux-yocto/message/9185
Mute This Topic: https://lists.yoctoproject.org/mt/78474086/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Python function caching question

2020-11-24 Thread Quentin Schulz

Hi Michael,

On Mon, Nov 23, 2020 at 04:49:30PM -0700, Michael Callahan wrote:
> I do not want do_compile to run again, it rebuilds the whole image.
> What is the best way to always run find_version?
> 

Use an anonymous python function that sets VERSION, e.g.:

python __anonymous() {
d.setVar('VERSION', find_version(d))
}

as anonymous python functions are always executed during parsing.

Then add the following to your recipe:
do_compile[vardepsexclude] += "VERSION"

VERSION will always be set appropriately every time the recipe is parsed
but do_compile will only be rerun when a change in the task has occurred
to the exception of the VERSION variable.

No idea if that works as I don't use those, but that's an hint. Anyway, you
probably want a behavior similar to DATETIME's.

Cheers,
Quentin

> On Sun, Nov 22, 2020 at 7:53 PM Khem Raj  wrote:
> >
> > On Sun, Nov 22, 2020 at 6:17 PM Michael Callahan
> >  wrote:
> > >
> > > I am having trouble with sstate caching of my os-release.bbappend and
> > > am stuck.  The simple example file looks like something below, where I
> > > am setting a variable from a computed python function.  What's the magic
> > > to make the find_version(d) always run but do_compile to only run if
> > > VERSION changes?  I basically want something like
> > > `find_version[nostamp]="1"` but that seems to only work for tasks.
> > >
> > > def find_version(d):
> > > import subprocess
> > > cmd = "git describe --long"
> > > return subprocess.check_output(cmd).rstrip().decode('utf-8')
> > >
> > > VERSION = "${@find_version(d)}"
> > > # do_compile uses $VERSION
> > >
> >
> > perhaps mark the task which is using this variable as nostamp.
> >
> > > 
> > >

> 
> 
> 


-- 
StreamUnlimited Engineering GmbH
High Tech Campus Vienna, Gutheil-Schoder-Gasse 10, 1100 Vienna, Austria
Fax: +43 1 667 20 02 4401
quentin.sch...@streamunlimited.com, www.streamunlimited.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#51541): https://lists.yoctoproject.org/g/yocto/message/51541
Mute This Topic: https://lists.yoctoproject.org/mt/78445317/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Yocto Project Outreachy interns

2020-11-24 Thread Meh Mbeh Ida Delphine

Thank you all so much for having us. I learned so much about embedded linux
and the Yocto Project in a very short while. I can't wait to start
working with you and on my project.


Cheers,
Ida.

On Tue, 24 Nov 2020, 8:47 am Nicolas Dechesne, 
wrote:

> Dear all,
>
> We are very excited to be part of the Outreachy program again for the
> December round this year, let me congratulate Ida and Dorinda for
> being accepted as interns for the next three months.
>
> I want to give a warm thank you to our mentors as well, Paul, Ross,
> Tim. Without mentors there isn't much we can do, so this is very much
> appreciated. A big thank you to Microsoft and Arm who are sponsoring
> the internships.
>
> Ida and Dorinda will engage on the following topics:
>
> == Enhance Yocto Project License Tracing
> The Yocto Project build system is typically used to build customised
> Linux images from source for embedded applications. Along with the
> image, a manifest of packages and their corresponding licenses is
> prepared, however the accuracy of the license information in the
> manifest is dependent on the accuracy of the metadata we have for each
> package (i.e. what is in the recipe file). As part of the build, we
> have an internal mapping from output files to source files which is
> currently used to prepare source packages to aid in debugging, however
> with the increasing presence of SPDX headers in source files it could
> also be used to allow tracing the license of sources used in building
> a package/image to help improve our metadata and future license
> manifests.
>
> == Add support for elfutils debug info server"
> The Yocto Project build system is typically used to build customised
> Linux images from source for embedded applications. debuginfod (part
> of elfutils 0.178 onwards) is a way to share debuginfo files, which
> provide debugging symbols for gdb to enable it to debug a running
> program on a target device. Users of the Yocto Project would benefit
> from integrating support for debuginfod such that binaries in an image
> produced by the Yocto Project build system could be debugged more
> easily.
>
> Ida and Dorinda, welcome into our open source community, you can count
> on everyone's support during your internship!
>
> cheers
> nico
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#51540): https://lists.yoctoproject.org/g/yocto/message/51540
Mute This Topic: https://lists.yoctoproject.org/mt/78473005/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Disable systemd-timesyncd.service in image

2020-11-24 Thread Damien LEFEVRE

Yes SYSTEMD_AUTO_ENABLE_${PN} doesn't apply to systemd recipe core services
as they are not installed as separate packages.

But I got it working now.

The default enable/disable service are defined in
https://github.com/systemd/systemd/blob/master/presets/90-systemd.preset

So
do_configure_append() {
sed -i -e "s/enable systemd-timesyncd.service/disable
systemd-timesyncd.service/g" ${S}/presets/90-systemd.preset
}

does the trick

Cheers,
-Damien

On Mon, Nov 23, 2020 at 10:42 PM Konrad Weihmann 
wrote:

> The service is deployed with standard systemd package, which doesn't
> have that set as far as I see it (no SYSTEMD_AUTO_ENABLE_${PN} in the
> latest recipe revision)
>
> I think, after browsing through the code of systemd - this "autostart"
> behavior comes from [1].
> So I would say you can disable it with a drop-in file at
> /etc/systemd/system/systemd-timesyncd.service.d/disable.conf
> [Install]
> WantedBy=
>
> which also would be charming in a way that it isn't that invasive in the
> build system
>
> [1]
>
> https://github.com/systemd/systemd/blob/5b639090d0b4a49d77ba58bebe180b2a6f8da322/units/systemd-timesyncd.service.in#L55
>
> haven't tested it though, but you might wanna give that a shot, if
> Aaron's approach doesn't work.
>
> On 23.11.20 21:21, Joel A Cohen wrote:
> > I think you need to set SYSTEMD_AUTO_ENABLE = “disable” (actually any
> > value other than “enable”) in your bbappend.
> >
> > (It looks like SYSTEMD_AUTO_ENABLE_${PN} is intended to work too, but I
> > can’t verify it at the moment and reading over systemd.bbclass I’m not
> > sure if it works or not)
> >
> > —Aaron
> >
> > On Mon, Nov 23, 2020 at 11:51 AM Damien LEFEVRE  > > wrote:
> >
> > Hi,
> >
> > I would like to have systemd-timesyncd.service as part of an image
> > but have it disabled by default.
> >
> > Right now it is enabled by default which causes some issues.
> >
> > I've tried systemd_%.bbappend
> >
> > do_install_append() {
> >  rm
> "$D/etc/systemd/system/dbus-org.freedesktop.timesync1.service"
> >  rm
> >
>  "$D/etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service"
> > }
> >
> > but those symlinks are not part of the package.
> >
> > I've tried this to remove the link during the package deployment
> > during do_rootfs
> > pkg_postinst_${PN}_append() {
> >  #!/bin/sh -e
> >  rm
> "$D/etc/systemd/system/dbus-org.freedesktop.timesync1.service"
> >  rm
> >
>  "$D/etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service"
> > }
> >
> > But at this stage the links still don't exist.
> >
> > Which package is actually responsible for enabling the default
> > services / creating the symlinks? How can we turn some of them off
> > while keeping them in the image?
> >
> > Thanks,
> > -Damien
> >
> >
> >
> >
> >
> > 
> >
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#51539): https://lists.yoctoproject.org/g/yocto/message/51539
Mute This Topic: https://lists.yoctoproject.org/mt/78461756/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] M+ & H bugs with Milestone Movements WW47

[yocto] Enhancements/Bugs closed WW47!

[yocto] Current high bug count owners for Yocto Project 3.3

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[yocto] Yocto Project Status WW47'20

Re: [yocto] How to add python application into the build. #python #toolchain

[yocto] How to add python application into the build. #python #toolchain

Re: [yocto] Yocto Project Outreachy interns

[linux-yocto][yocto-kernel-cache][master yocto-5.4][PATCH] qemuppc: configure the CONFIG_SCSI to '=y'

Re: [yocto] Python function caching question

Re: [yocto] Yocto Project Outreachy interns

Re: [yocto] Disable systemd-timesyncd.service in image

12 matches

Site Navigation

Mail list logo

Footer information