On Tue, 2023-02-07 at 15:12 +0100, Alexis Lothoré via
lists.yoctoproject.org wrote:
> Hello,
> this minor patch series bring minor fixes into send-qa-email to ease
> development/debugging in it:
> - fetching current build test results works well in CI builds because we are
> sure that the build r
On Tue, 2023-02-07 at 15:52 +0100, Alexis Lothoré wrote:
> Hello Richard,
>
> On 2/7/23 15:42, Richard Purdie wrote:
> > On Tue, 2023-02-07 at 15:12 +0100, Alexis Lothoré via
> > lists.yoctoproject.org wrote:
> > > I assumed that no tool is currently trying to parse
On Thu, 2023-02-09 at 00:05 -0800, alexander.roda...@brose.com wrote:
> Hello,
>
> i am trying to install the PostgreSQL and the development package
> (postgresql-server-dev) as part of the SDK.
>
> I added via bbappend BBCLASSEXTED_append = "nativesdk" to the
> postgresql_12.9.bb.
>
> I can b
On Thu, 2023-02-09 at 23:16 -0800, alexander.roda...@brose.com wrote:
> I integrated the changes of the commit you posted, however i still
> have the same error message coming up. Do i need to make changes in
> the recipe to make the intercept work?
No, it should have changed PATH in the recipe a
On Mon, 2023-02-20 at 09:12 +, Chaplin, Kris via
lists.yoctoproject.org wrote:
> Hello,
>
> I'm working with our team to test supported development OS for our
> AMD/Xilinx PetaLinux distribution built on top of Langdale. The official
> supported Linux distributions are Ubuntu, Fedora, AlmaLi
On Mon, 2023-02-20 at 13:09 +, Chaplin, Kris via
lists.yoctoproject.org wrote:
> Thanks Alex,
>
> > Note that the list of supported host distros is set only for the poky
> > reference distro with a weak assignment, and not for oe-core or yocto
> > as a whole. If you do your own tests, and they
Hi,
On Thu, 2023-02-23 at 02:27 -0800, Tamis wrote:
> I know that this might be an old thread but we seem to deal the exact
> same issue in our yocto builds, that's why I am writing here.
> Recently we switched from sumo yocto branch to dunfel.
> Now some recipes with nothing special in it, just c
I saw you're still having problems even with the latest pseudo
revisions. I'll make some comments below.
On Thu, 2023-02-23 at 02:27 -0800, Tamis wrote:
> Install error:
>
> + install -m 0644
> WORKDIR/lib32-las/M-WBS0.1-r0/git/lasiflib/include/lasif_l
On Mon, 2023-03-13 at 15:51 +0100, Alexis Lothoré via
lists.yoctoproject.org wrote:
> From: Alexis Lothoré
>
> This series fixes regression report generation on "next" branches, as raised
> in
> [1].
>
> The first five patches are preparatory updates for the real fix, being either
> refactoring
On Fri, 2023-03-24 at 10:00 +0100, Alexis Lothoré via
lists.yoctoproject.org wrote:
> From: Alexis Lothoré
>
> When available, expose tesresult-regressions-report.txt on non-release web
> page,
> as it is done for many other artifacts currently
>
> Signed-off-by: Alexis Lothoré
> ---
> script
A build flagged for QA (yocto-4.2.rc1) was completed on the autobuilder and is
available at:
https://autobuilder.yocto.io/pub/releases/yocto-4.2.rc1
Build hash information:
bitbake: 46e1ea2e9a203992bb4de48ea21a8e736419ada2
meta-agl: 09135164a21a216c6e3e75d7decce896b92962f0
meta-arm: 3b4a
riginal Message-
> > From: qa-build-notificat...@lists.yoctoproject.org > notificat...@lists.yoctoproject.org> On Behalf Of Richard Purdie
> > Sent: Thursday, April 6, 2023 3:57 PM
> > To:
> > Cc: qa-build-notification
> > Subject: [qa-build-notification] QA no
Hi,
Whilst we had a green QA report and were thinking rc2 would release, we
did get a user report of problems with graphics on qemu and sato was
inoperable (bug 15100).
Sadly our QA automation doesn't catch an issue like this and it mustn't
have shown on real hardware.
Due to the nature of the b
On Thu, 2023-05-04 at 16:40 +0200, Nicolas Dechesne wrote:
> After five years, I have decided to resign from my position as the
> Yocto Project Community Manager. I joined the OpenEmbedded community
> around 2008. I have fond memories of my early days, and still
> remember some of my first interact
On Fri, 2019-11-22 at 09:59 -0800, akuster808 wrote:
>
>
> On 11/22/19 9:03 AM, rpj...@crashcourse.ca wrote:
> > On Fri, 22 Nov 2019, Robert P. J. Day wrote:
> >
> >
> > /// end /
> >
> > i have absolutely no idea what to think of this, and am open to
> > suggestions. does an
On Tue, 2019-12-03 at 07:15 +, Jain, Sangeeta wrote:
> This is the full report for 3.0.1 RC3:
> https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
>
> === Summary
> No high milestone defects.
> No new defects are found in this
On Tue, 2019-12-03 at 17:07 +, Ross Burton wrote:
> On 03/12/2019 15:15, Richard Purdie wrote:
> > On Tue, 2019-12-03 at 07:15 +, Jain, Sangeeta wrote:
> > > This is the full report for 3.0.1 RC3:
> > > https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testre
On Wed, 2019-12-11 at 10:39 -0500, Trevor Woerner wrote:
> On Wed 2019-12-11 @ 11:06:44 AM, Nicolas Dechesne wrote:
> > > +python do_check_build_type() {
> > > +_buildtype = d.getVar('MESA_BUILD_TYPE')
> > > +if _buildtype not in ['release', 'debug']:
> > > +
On Wed, 2019-12-18 at 03:32 +, Jain, Sangeeta wrote:
> Hello all,
>
> This is the full report for 3.1_M1.rc8:
> https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
>
>
> === Summary
> No high milestone defects.
> No new defect
On Wed, 2019-12-18 at 07:38 -0800, akuster808 wrote:
>
> On 12/18/19 2:46 AM, Richard Purdie wrote:
> > On Wed, 2019-12-18 at 03:32 +, Jain, Sangeeta wrote:
> > > Hello all,
> > >
> > > This is the full report for 3.1_M1.rc8:
> > >
On Thu, 2019-12-19 at 02:37 -0800, angeal1...@gmail.com wrote:
> Hi everyone,
>
> Recently, I tried to use the SSTATE_MIRRORS variable to get back
> sstate cache from a build machine shared amongst developers.
> When I tried with the simple FILE fetcher, it worked great and
> resumed the work wher
On Tue, 2020-01-07 at 12:55 +0100, Richard Leitner wrote:
> Hi Scott, Richard,
> I'm experiencing weird git submodule behaviour on poky master since
> commit 7e7b066085 ("YP 3.1 Docs: Updated Manual revision tables.")
>
> Was this intended?
No, it wasn't. Scott is unavailable right now so I've re
On Sun, 2020-01-12 at 08:01 +, André Draszik wrote:
> On a related note,
>
> It appears groups.io is generating a new Message-Id header:
>
> Message-Id: <15e914a621406cc1.15...@lists.yoctoproject.org>
> X-Orig-Message-Id: <
> f868f741ae07674cb99e2b0c4ea6f7621ca16474.ca...@andred.net>
>
> Is
On Tue, 2020-01-14 at 15:50 +0200, Nikolay Merinov via
Lists.Yoctoproject.Org wrote:
> Our company interested in updating an old Yocto releases (especially
> the Morty release) to use the OpenSSL version 1.1.1.
>
> Can Yocto Project integrate all necessary changes if Inango prepares
> all required
On Wed, 2020-01-15 at 06:50 +, Mittal, Anuj wrote:
> Can this be merged in zeus/warrior too please?
I've merged to zeus but this code isn't in warrior at all...
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#47966): https://l
On Thu, 2020-01-16 at 20:07 +, Paul Barker wrote:
> Hey folks,
>
> I've started looking through patchtest & patchtest-oe in detail and
> spotted that all the scripts, support code and test cases are
> licensed
> under GPLv2. Is that ok given that we plan to copy this into
> openembedded-core (
On Fri, 2020-01-17 at 14:16 +, Ross Burton wrote:
> Python 2 ceased being maintained on the 1st January 2020. We've
> already
> removed all users of it from oe-core so the final step is to move the
> recipe and supporting classes to meta-python2.
>
> The following are removed in this commit:
python2 is now EOL. To keep this old version of mc going, delete the python2
scripts to avoid the dependency.
Signed-off-by: Richard Purdie
---
recipes-extended/mc/mc_4.7.5.2.bb | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/recipes-extended/mc/mc_4.7.5.2.bb
b
Later versions of shared-mime-info need itstool which is GPLv3. Add an old
version of shared-mime-info to allow gplv3 free builds to suceed.
Use python to set PREFERRED_VERSION based on INCOMPATIBLE_LICENSE to
control this.
Signed-off-by: Richard Purdie
---
conf/layer.conf
On Fri, 2020-01-17 at 13:28 -0800, Khem Raj wrote:
> On Fri, Jan 17, 2020 at 12:15 PM Andreas Müller <
> schnitzelt...@gmail.com> wrote:
> > On Fri, Jan 17, 2020 at 7:35 PM Khem Raj
> > wrote:
> > > On 1/17/20 6:16 AM, Ross Burton wrote:
> > > > Python 2 ceased being maintained on the 1st January
On Mon, 2020-01-20 at 14:31 +0100, Stefan Agner wrote:
> Hi list, hi Ross,
>
> We still carry this downstream, any chance to get them still merged
> in
> psplash?
>
> If it is really considered unmaintained, then we probably should drop
> the psplash recipe altogether?
I've just merged them, sor
On Mon, 2020-01-20 at 22:48 +0100, Stefan Agner wrote:
> On 2020-01-20 17:14, Richard Purdie wrote:
> > On Mon, 2020-01-20 at 14:31 +0100, Stefan Agner wrote:
> > > Hi list, hi Ross,
> > >
> > > We still carry this downstream, any chance to get them still
On Mon, 2020-01-20 at 23:00 +0100, Stefan Agner wrote:
> From: Stefan Agner
>
> This adds optional systemd support. When enabled, an utility called
> psplash-systemd is built. This tool will connect to systemd using the
> system bus to obtain progress information and communicate that to
> psplash
On Tue, 2020-01-21 at 11:07 +0100, Stefan Agner wrote:
> From: Stefan Agner
>
> This adds optional systemd support. When enabled, an utility called
> psplash-systemd is built. This tool will connect to systemd using the
> system bus to obtain progress information and communicate that to
> psplash
On Wed, 2020-01-22 at 13:55 +, Rasmus Villemoes wrote:
> I have a do_configure() python function which is essentially
>
> python do_configure() {
> import fileinput
> with open("foo.txt", "w") as out:
> for line in
> fileinput.input(files=d.getVar("FOO_INPUT").split()):
>
On Wed, 2020-01-22 at 15:46 +, Rasmus Villemoes wrote:
> On 22/01/2020 15.35, Richard Purdie wrote:
> > Bitbake can only detect direct references to variables. The code
> > above only runs at configure time, not at parse time so its not
> > really surprising that bitbak
On Wed, 2020-01-22 at 16:39 +, Rasmus Villemoes wrote:
> On 22/01/2020 16.50, Richard Purdie wrote:
> > On Wed, 2020-01-22 at 15:46 +, Rasmus Villemoes wrote:
> > > On 22/01/2020 15.35, Richard Purdie wrote:
> > > > Bitbake can only detect direct references
With recipe specific sysroot, these settings do nothing. Drop
the obsolete code.
Signed-off-by: Richard Purdie
---
meta/classes/cross.bbclass | 1 -
meta/classes/crosssdk.bbclass | 1 -
meta/classes/native.bbclass| 1 -
meta/classes/nativesdk.bbclass | 1 -
4 files changed, 4 deletions
Fixes:
WARNING: l3afpad-0.8.18.1.11+gitAUTOINC+3cdccdc950-r0 do_package_qa: QA Issue:
package contains desktop file with key 'MimeType' but does not inhert mime-xdg:
l3afpad path
'XXX/packages-split/l3afpad/usr/share/applications/l3afpad.desktop' [mime-xdg]
Signed-of
out a bit (more
cleanup can follow).
Signed-off-by: Richard Purdie
---
meta/classes/base.bbclass | 4 ++--
meta/classes/features_check.bbclass| 3 +++
meta/lib/oeqa/selftest/cases/distrodata.py | 7 +++
3 files changed, 8 insertions(+), 6 deletions(-)
diff --git a
: Richard Purdie
---
meta-poky/conf/local.conf.sample | 1 -
meta-yocto-bsp/README.hardware| 142 --
meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf | 36 -
.../linux/linux-yocto-dev.bbappend| 2 -
.../linux/linux-yocto_4.19.bbappend
Hi,
On Thu, 2020-01-30 at 13:32 +0200, Alexandru N. Onea wrote:
> Let's consider the following example in a bb file:
>
> X = "1"
> A := "X is '${X}' and Y is '${Y}'"
> B = "X is '${X}' and Y is '${Y}'"
> X = "2"
> Y = "3"
>
> According to the bitbake user manual, section 3.1.7 [1], the expected
On Thu, 2020-01-30 at 16:19 -0800, akuster wrote:
> Signed-off-by: Armin Kuster
> ---
> config.py | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/config.py b/config.py
> index 7dbd5e7..b210275 100644
> --- a/config.py
> +++ b/config.py
> @@ -51,7 +51,6 @@ trigger_bu
I'm sorry to have to pass on the sad news that Scott Rifenbark, our
tech writer for the project passed away on Wednesday after a battle
with cancer.
I remember interviewing Scott over 10 years ago when forming a team at
Intel to work on what became the Yocto Project, he was with it from the
start.
On Sat, 2020-02-08 at 13:48 -0500, rpj...@crashcourse.ca wrote:
> On Sat, 8 Feb 2020, rpj...@crashcourse.ca wrote:
> ... snip ...
> > which seems odd as there don't appear to be any other recipes that
> > provide pkgconfig, and AIUI, the default provider for any recipe is
> > the recipe with *exact
On Sat, 2020-02-08 at 13:31 -0500, rpj...@crashcourse.ca wrote:
> (part of the nitpickiness of some of these questions stems from
> that, in my updated courseware, i want to use actual examples out of,
> say, the openembedded layer, and not just contrived examples
> involving
> packages like "foo
On Sat, 2020-02-08 at 13:31 -0500, rpj...@crashcourse.ca wrote:
> (part of the nitpickiness of some of these questions stems from
> that, in my updated courseware, i want to use actual examples out of,
> say, the openembedded layer, and not just contrived examples
> involving
> packages like "foo
On Tue, 2020-02-11 at 05:32 -0500, rpj...@crashcourse.ca wrote:
> second, i think we all agree that it is rarely necessary to use
> "PROVIDES +=", although i did run across one case in
> recipes-core/glibc/glibc.inc:
>
> PROVIDES = "virtual/libc"
> PROVIDES += "virtual/libintl virtual/libico
On Fri, 2020-02-14 at 12:08 -0500, Randy MacLeod wrote:
> Hi,
>
> There are many tests run for master-next and reported here:
> https://autobuilder.yocto.io/pub/non-release/
> such as:
>
> https://autobuilder.yocto.io/pub/non-release/20200214-4/testresults/testresult-report.txt
>
> It would
On Fri, 2020-02-14 at 17:14 +, Richard Purdie via
Lists.Yoctoproject.Org wrote:
> On Fri, 2020-02-14 at 12:08 -0500, Randy MacLeod wrote:
> > Hi,
> >
> > There are many tests run for master-next and reported here:
> > https://autobuilder.yocto.io/p
On Sat, 2020-02-15 at 11:41 +0100, Alexander Kanavin wrote:
> Something is wrong, as master and master-next are missing here?
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/
There is something wrong with the http caching on the git server. The
branches are there, they're just not appearing immed
On Mon, 2020-02-17 at 04:27 -0800, philip.le...@domino-uk.com wrote:
> Something using the built-in cache mirror in Yocto–there are a few
> ways it can do this, as it’s essentially a file share somewhere.
> https://pelux.io/2017/06/19/How-to-create-a-shared-sstate-dir.html
> for an example shows h
On Tue, 2020-02-18 at 17:44 +0100, Alexander Kanavin wrote:
> On Tue, 18 Feb 2020 at 17:10, wrote:
> > With the git infrastructure issue updated, we now have centos8
> > workers added to the autobuilder.
> >
>
> What are the current plans for centos 7?
Project members are keen to see support f
On Tue, 2020-02-18 at 11:26 -0500, Patrick Doyle wrote:
> Does anybody have any tips or tricks for how I might debug the
> (cross-canadian) gdb built by Yocto's SDK?
>
> I need to add some printf's to the gdb code to help track down why
> something isn't working, but none of my traditional
> get-r
On Wed, 2020-02-19 at 14:41 -0800, akuster808 wrote:
>
> On 2/18/20 11:33 PM, Jain, Sangeeta wrote:
> > Hi All,
> >
> > This is the full report for yocto-3.0.2.rc2:
> > https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
> >
> > === Summary
On Thu, 2020-02-20 at 07:46 +, Jain, Sangeeta wrote:
> Planned upcoming dot releases:
> YP 2.7.3 built and in QA
>
> I didn’t see any notification for this build. Am I missing something?
No, its due to be built but isn't built yet!
I think that was meant to say 3.0.2, sorry about any confu
On Thu, 2020-02-20 at 11:26 +, Paul Barker wrote:
> In my new CI setup I'm using an sstate mirror which seems to have
> some
> occasional download issues. This results in the setscene task
> failing.
> For example:
>
> ERROR: qt3d-5.13.2+gitAUTOINC+93361f1a59-r0
> do_package_write_ipk_setscene
On Thu, 2020-02-20 at 11:59 +, Paul Barker wrote:
> I'm now looking into this...
>
> In sstate_checkhashes() we mark sstate as available if
> fetcher.checkstatus() succeeds. Then at a later point
> sstate_setscene() calls sstate_installpkg() calls pstaging_fetch()
> calls fetcher.download() to
I discussed this quickly in bug triage today with Armin. We agreed
that:
* The openssh bug is minor and doesn't affect release
* Anuj resolved one of the bugs as being execution error so again it
doesn't affect release
* The bash issue does affect release
We're proposing we build and release an r
On Fri, 2020-02-21 at 10:03 +0200, Adrian Bunk wrote:
> On Thu, Feb 20, 2020 at 10:44:24PM +0000, Richard Purdie wrote:
> > ...
> > This would also include the bitbake memory optimisation during
> > parsing
> > which merged.
> > ...
>
> I would consider th
On Fri, 2020-02-21 at 17:26 +, Tummalapalli, Vineela wrote:
> [Vineela]: So we will have 3.0.2.rc3 as the release candidate and not
> 3.0.2.rc2 as we see issues with that. Am I correct?
> If so, in terms of release process I just have to redo the things
> like staging 3.0.2.rc3 and do the relea
On Fri, 2020-02-21 at 18:10 -0500, bruce.ashfi...@gmail.com wrote:
> From: Bruce Ashfield
>
> Updating the SRCREVs for the h/w references to v5.4.20, which includes
> the binutils fix for perf.
>
> Signed-off-by: Bruce Ashfield
> ---
> .../recipes-kernel/linux/linux-yocto_5.4.bbappend
On Mon, 2020-02-24 at 08:15 -0800, bill.k...@azuresummit.com wrote:
> Hello! I am currently using Yocto with default Poky distro. A
> customer would like a CentOS-based filesystem, and I am wondering if
> this is possible using Yocto?
>
> My initial thought is to imitate
> https://github.com/me
On Fri, 2020-02-28 at 22:51 +, Sean McKay wrote:
> This is probably a fairly short question (I hope):
> I’m working on a branch based on zeus. I found a bug in the way that
> one of our recipes was handling something during do_configure (which
> caused an error to pop up in a do_compile task).
Its posted at:
https://www.yoctoproject.org/yocto-project-long-term-support-announced/
but I'll copy it below since this is an important announcement
"""
To fulfill the evolving requirements of its members and users, the
Yocto Project announced a new plan to extend support for selected
releases. T
On Wed, 2020-03-04 at 14:00 +0100, Alexander Kanavin wrote:
> On Tue, 3 Mar 2020 at 16:59, wrote:
> > coreutils ptest blocked on libmodule-build-perl reproducibility
> > issue
> >
>
> I sent a patch for this.
Thanks!
Just FYI I think there may also be a couple of other packages coreutils
pulls
On Fri, 2020-03-06 at 22:53 +0100, Alexander Kanavin wrote:
> On Wed, 4 Mar 2020 at 23:42, Richard Purdie <
> richard.pur...@linuxfoundation.org> wrote:
> > Just FYI I think there may also be a couple of other packages
> > coreutils
> > pulls in and they may al
On Sat, 2020-03-07 at 16:58 +, Richard Purdie wrote:
> On Fri, 2020-03-06 at 22:53 +0100, Alexander Kanavin wrote:
> > On Wed, 4 Mar 2020 at 23:42, Richard Purdie <
> > richard.pur...@linuxfoundation.org> wrote:
> > > Just FYI I think there may also
On Tue, 2020-03-10 at 11:33 +, mikko.rap...@bmw.de wrote:
> On Fri, Feb 28, 2020 at 11:25:59PM +0000, Richard Purdie wrote:
> > On Fri, 2020-02-28 at 22:51 +, Sean McKay wrote:
> > > This is probably a fairly short question (I hope):
> > > I’m working on a bran
On Thu, 2020-03-12 at 14:55 +0100, Matthias Schoepfer via
Lists.Yoctoproject.Org wrote:
> We have noticed the following issue: We keep the versions of out
> software by means of tags on the git repositories, i.e. during the
> build, somethings like git describe --tags gets called. In yocto,
> ou
On Thu, 2020-03-19 at 08:05 +, Mikko Rapeli wrote:
> Once this is done, IO still happens when anything calls sync() and
> fsync() and worst offenders are package management tools. In yocto
> builds, package manager actions to flush to disk are always useless
> since rootfs images are going to b
On Thu, 2020-03-19 at 11:43 +, mikko.rap...@bmw.de wrote:
> On Thu, Mar 19, 2020 at 11:04:26AM +0000, Richard Purdie wrote:
> > Recipe parsing should hit 100% CPU, its one of the few places we
> > can do
> > that.
>
> I'm not fully aware what bitbake doe
On Thu, 2020-03-19 at 17:29 +0100, Yann Dirson wrote:
>
>
> Le jeu. 19 mars 2020 à 17:07, Mike Looijmans a
> écrit :
> > On 19-03-2020 12:04, Richard Purdie via Lists.Yoctoproject.Org wrote:
> > >> , fetch, configure, package and rootfs tasks.
> > >
On Thu, 2020-03-19 at 19:21 +0200, Adrian Bunk wrote:
> On Thu, Mar 19, 2020 at 05:07:17PM +0100, Mike Looijmans wrote:
> > ...
> > With both parallelization options
> > to "16", I might end up with 16 compile tasks running 16 compile
> > threads
> > each, i.e. 256 running processes.
> > ...
>
> T
On Mon, 2020-04-06 at 22:53 +, Poky Build User wrote:
> A build flagged for QA (yocto-3.1.rc1) was completed on the
> autobuilder and is available at:
>
>
> https://autobuilder.yocto.io/pub/releases/yocto-3.1.rc1
I haven't see any "started QA" email about this yet.
We have had some issu
s some issues.
>
> I will now start the QA on
> https://autobuilder.yocto.io/pub/releases/yocto-3.1.rc2/
>
> Thanks,
> Sangeeta
>
>
> > -Original Message-
> > From: yocto@lists.yoctoproject.org
> > On Behalf
> > Of Richard Purdie
>
On Wed, 2020-04-08 at 04:01 +, pokybu...@localhost.yoctoproject.org
wrote:
> A build flagged for QA (yocto-3.1.rc2) was completed on the
> autobuilder and is available at:
>
>
> https://autobuilder.yocto.io/pub/releases/yocto-3.1.rc2
>
>
> Build hash information:
>
> bitbake: 4618da20
On Thu, 2020-04-09 at 09:54 +0800, mohamad.noor.alim.hus...@intel.com wrote:
> From: Mohamad Noor Alim Hussin
>
> Using meta-intel with core-image-sato-(sdk)-ptest
> results in a hddimg size of more than 4 GB. Remove
> that image type from testing.
>
> hddimg is not built by default in dunfell s
Hi Sangeeta/Vineela,
On Sat, 2020-04-11 at 07:26 +, Jain, Sangeeta wrote:
> This is the full report for yocto-3.1.rc2:
> https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
>
> === Summary
> No high milestone defects.
> No new
On Wed, 2020-04-15 at 16:05 -0700, akuster wrote:
>
>
> On 4/15/20 3:25 PM, Paul Eggleton wrote:
> > Release notes draft attached, including a dedication to Scott
> > (wasn't sure where to put that so I've just left it at the top) and
> > contributors list. Let me know if you notice anything
> >
On Wed, 2020-04-22 at 14:43 -1000, Steve Sakoman wrote:
> We were mistakenly doing a force push if the branch was in either
> BUILD_HISTORY_FORKPUSH or BUILD_HISTORY_DIRECTPUSH.
>
> Now we force push for branches in BUILD_HISTORY_FORKPUSH, regular push
> for branches in BUILD_HISTORY_DIRECTPUSH, a
On Sat, 2020-04-25 at 17:30 +0900, Hao Qian wrote:
> However, if I change files' name into wildcard in SRC_URI like:
> ===
> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> SRC_URI += "file://*"
> ===
[...]
> Could any
On Sun, 2020-04-26 at 08:24 +0900, Hao Qian wrote:
> Hi, Richard
>
> Thanks for replying.
>
> Yes, it makes sense why patches not be applied by using wildcard.
>
> Just for confirmation, it looks like more than one person made it to
> use wildcard for patching as below:
> https://stackoverflow.c
The newly added dependency on python3-dbusmock in OE-Core is GPLv3
and would fail to work with this layer. Remove it in the config
for enabling the layer.
Signed-off-by: Richard Purdie
---
conf/distro/include/disable-gplv3.inc | 1 +
1 file changed, 1 insertion(+)
diff --git a/conf/distro
ilder config used for this
testing this layer.
Signed-off-by: Richard Purdie
---
conf/distro/include/disable-gplv3.inc | 2 ++
1 file changed, 2 insertions(+)
create mode 100644 conf/distro/include/disable-gplv3.inc
diff --git a/conf/distro/include/disable-gplv3.inc
b/conf/distro/include/disable-
ilder config currently used for
testing meta-gplv2.
Signed-off-by: Richard Purdie
---
conf/distro/include/disable-gplv3.inc | 2 ++
1 file changed, 2 insertions(+)
create mode 100644 conf/distro/include/disable-gplv3.inc
diff --git a/conf/distro/include/disable-gplv3.inc
b/conf/distro/include/di
The newly added dependency on python3-dbusmock in OE-Core is GPLv3
and would fail to work with this layer. Remove it in the config
for enabling the layer.
Signed-off-by: Richard Purdie
---
conf/distro/include/disable-gplv3.inc | 1 +
1 file changed, 1 insertion(+)
diff --git a/conf/distro
Signed-off-by: Richard Purdie
---
README | 5 +
1 file changed, 5 insertions(+)
diff --git a/README b/README
index 4558a99..6a61331 100644
--- a/README
+++ b/README
@@ -27,3 +27,8 @@ intended target branch of the Git repository.
Git repository: http://git.yoctoproject.org/cgit.cgi
On Tue, 2020-05-05 at 12:01 +0100, Richard Purdie via
lists.yoctoproject.org wrote:
> Signed-off-by: Richard Purdie
> ---
> README | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/README b/README
> index 4558a99..6a61331 100644
> --- a/README
> ++
On Mon, 2020-05-04 at 16:28 -0400, Robert P. J. Day wrote:
> i bring this up because i've run across occasional examples of that
> in the code base -- here's
> meta-gnome/recipes-connectivity/libnma/libnma_1.8.28.bb:
>
> EXTRA_OEMESON_mipsarchn32_append = " -Dvapi=false"
>
> is that deliberat
On Mon, 2020-03-23 at 11:53 -0400, Matthew wrote:
> Fixes [YOCTO #13319]
>
> Signed-off-by: Mingde (Matthew) Zeng
> ---
> libtaku/inotify/inotify-diag.c| 2 ++
> libtaku/inotify/inotify-diag.h| 2 ++
> libtaku/inotify/inotify-kernel.c | 2 ++
> libtaku/inotify/inotify-kernel.h | 2 ++
>
Hi Bill,
On Wed, 2020-05-27 at 12:31 +, Mills, William wrote:
> In a script, how would I download all the files in this dir:
>
> https://autobuilder.yocto.io/pub/releases/yocto-2.7.4.rc2/machines/beaglebone-yocto/
>
> I see no global md5sum (or sha256sum etc) file in the tree anywhere.
>
>
On Thu, 2020-05-28 at 00:28 -0400, William Mills via lists.yoctoproject.org
wrote:
>
> On 5/27/20 6:42 PM, Michael Halstead wrote:
> > I've rebuilt the fancyindex module and enabled it. The full filenames
> > are displayed now. The module is disabled automatically when new
> > versions of EPEL ar
On Wed, 2020-06-03 at 11:06 +0200, Alexander Kanavin wrote:
> I'm not sure if this is distro specific. _PYTHON_SYSCONFIGDATA_NAME
> is set from python3native.bbclass so that native python can pick up
> target configuration, and if the target configuration is not there
> (it comes with target python
On Wed, 2020-06-17 at 20:12 +, Vineela wrote:
> From: Vineela Tummalapalli
>
>
> ---
> scripts/publish-artefacts | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/publish-artefacts b/scripts/publish-artefacts
> index 6ed922a..3ef7206 100755
> --- a/script
On Fri, 2020-06-26 at 14:19 -0400, Robert P. J. Day wrote:
> background: trying to get ruby and a number of ruby gems migrated
> from "morty" to "zeus", and nothing but grief trying to
> compile/install ruby gems.
>
> plan A: start with standard YP layers all checked out to "zeus",
> and
> add
On Sun, 2020-07-05 at 15:24 -0400, Robert P. J. Day wrote:
> Quoting Ross Burton :
>
> > On Sun, 5 Jul 2020 at 11:50, Robert P. J. Day wrote:
> > >however, one can also generate a standard SDK with the generic
> > > (image-independent):
> > >
> > >$ bitbake meta-toolchain
> > >
> > > wh
On Sun, 2020-07-19 at 23:05 -0700, Amrun Nisha.R wrote:
> I want to create a offline build using yocto.
>
> I have sources and downloads packages directory in which i can able to create
> a successful bitbake. I have transferred those files to another system and
> tried to build them in offline
On Mon, 2020-07-20 at 07:18 -0700, Amrun Nisha.R wrote:
> For gnu-config-native-20150728, I have copied the git2 folder from
> older build folder to new build folder. It is fixed now.
>
> But I'm getting do_fetch error for the ncurses and ncurses_native. I
> have attached the log file for both pac
On Mon, 2020-07-20 at 15:06 +, Monsees, Steven C (US) wrote:
>
> I am fairly new to the Yocto SDK build process, and am looking to
> create an extensible SDK for one of our platforms.
>
> I am currently working with Rocko 2.4.1, in conjunction with
> uninative release 1.9…
>
> My current
301 - 400 of 732 matches
Mail list logo
