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.40 release.
There are about 220 commits here, based on commits chosen from what were
used in the 4.19.46/47 stable releases -- plus some TCP
Yocto Project is excited to announce the preliminary agenda for the Yocto
Project DevDay NA 2019.
Agenda:
Keynote & Welcome
Package Feeds Deep-dive
Runqueue and Build Equivalency to New Yocto Project Releases
OEQA, QA Selftest, Runtime APIs, pTest
Containers/Multiconfig
Security Response
I'm not sure I follow. This collects everything into the worker's
"builddir/yocto-autobuilder-helper" path (I think; I'm new to buildbot).
My aim was to let the buildbot master the chance to SCM the configuration
files apart from the helper's behavior which should otherwise be consistent
whether
Hi Carsten,
Thanks for your help.
On Fri, 2 Aug 2019 at 20:42, Stelling2 Carsten <
carsten.stelli...@goerlitz.com> wrote:
> Hi Ryan,
>
>
>
> Regarding to timesyncd, have a look at
> https://wiki.archlinux.org/index.php/systemd-timesyncd, especially the
> section
>
> “Note: The service writes to
Add
FILES_${PN} += "/usr/local/bin"
in recipe. but it would be nicer if it was installed into /usr/bin by
qmake/make files itself
On Fri, Aug 2, 2019 at 11:59 AM Mauro Ziliani wrote:
>
> Hi all.
>
> This is my problem.
>
> I have my terminal.pro project (qmake5) with target "terminal".
>
> The
Hi Ryan,
Regarding to timesyncd, have a look at
https://wiki.archlinux.org/index.php/systemd-timesyncd, especially the section
“Note: The service writes to a local file /var/lib/systemd/timesync/clock with
every synchronization.
This location is hard-coded and cannot be changed. This may be
Hi all.
This is my problem.
I have my terminal.pro project (qmake5) with target "terminal".
The default destination folder for the binary is /usr/local/bin
With this setup I get installed-vs-shipped error.
Why?
--
___
yocto mailing list
On Sat, May 04, 2019 at 10:59:34AM -0700, Michael Halstead wrote:
> On 5/4/19 9:19 AM, Adrian Bunk wrote:
> > $ git pull
> > fatal: unable to access 'https://git.yoctoproject.org/git/poky/': server
> > certificate verification failed. CAfile: none CRLfile: none
> > $
> >
> >
> > Firefox says:
> >
>
> Is ./sources/poky/meta/recipes-core/systemd/systemd_234.bb the proper
> place to patch this service file?
You should really put this in a `.bbappend` instead and also that
`.bbappend` should be in your own meta-layer if possible. In case you want
to upgrade stuff in the future it makes
Hi Randy,
On 8/2/19, Randy MacLeod wrote:
> On 7/31/19 7:06 AM, JH wrote:
>> Hi,
>>
>> I searched recipes for supporting QUIC, but could not find it. Has
>> anyone tried to build and to use QUIC?
>>
>> Thank you.
>>
>> Kind regards,
>>
>> - JH
>>
>
> Hi,
>
> I presume that you mean QUIC (Quick
Hi,
I have a working system based on Sumo. The system boots with a read-only
rootfs, then applies are read-write overlay for /etc.
When I migrate to Warrior, systemd-resolved fails to start. If I mount the
same rootfs via NFS, it starts and works fine. systemd-timesyncd is also
failing, but I
Terrific, that works well, thanks Rudolf and ChenQi.
On 8/2/19, Rudolf J Streif wrote:
> Adding
>
> After=multi-user.target
>
> to the [Unit] section in your systemd service file should do what you want.
>
> :rjs
>
> On 8/1/19 4:08 AM, JH wrote:
>> The application requires network connection to
12 matches
Mail list logo
