> On May 18, 2016, at 10:38 PM, Robert Yang wrote:
>
>
>
> On 05/19/2016 01:28 PM, Khem Raj wrote:
>>
>>> On May 18, 2016, at 8:16 PM, Gary Thomas wrote:
>>>
>>> On 2016-05-18 22:07, Khem Raj wrote:
On Wed, May 18, 2016 at 2:03 AM, Robert Yang
wrote:
> * It doesn't build on
On 05/19/2016 01:28 PM, Khem Raj wrote:
On May 18, 2016, at 8:16 PM, Gary Thomas wrote:
On 2016-05-18 22:07, Khem Raj wrote:
On Wed, May 18, 2016 at 2:03 AM, Robert Yang wrote:
* It doesn't build on armv4:
{standard input}: Assembler messages:
{standard input}:52: Error: selected process
> On May 18, 2016, at 8:16 PM, Gary Thomas wrote:
>
> On 2016-05-18 22:07, Khem Raj wrote:
>> On Wed, May 18, 2016 at 2:03 AM, Robert Yang
>> wrote:
>>> * It doesn't build on armv4:
>>> {standard input}: Assembler messages:
>>> {standard input}:52: Error: selected processor does not support `b
On Thu, 2016-05-19 at 05:16 +0200, Gary Thomas wrote:
[...]
> Why do you think that changing the instruction set (to thumb2) would
> make the JIT work any better?
>
> If you tell me how, I'll test it on my i.MX6 (Cortex-A9) which is
> the platform that inspired the original bug report.
FWIW, I ra
On 2016-05-18 22:07, Khem Raj wrote:
On Wed, May 18, 2016 at 2:03 AM, Robert Yang wrote:
* It doesn't build on armv4:
{standard input}: Assembler messages:
{standard input}:52: Error: selected processor does not support `blx
llint_throw_stack_overflow_error' in ARM mode
{standard input}:126: E
On 05/19/2016 10:33 AM, Robert Yang wrote:
Hi Martin,
I found this patch in the bug:
http://git.openembedded.org/openembedded-core/commit/meta/lib/oe/sstatesig.py?id=336a7897e39b9e42dcfcba9e2520ea96b0c6a8d6
And this patch causes another inconsistent:
PACKAGE_CLASSES = "package_ipk"
1) Af
Hi Martin,
I found this patch in the bug:
http://git.openembedded.org/openembedded-core/commit/meta/lib/oe/sstatesig.py?id=336a7897e39b9e42dcfcba9e2520ea96b0c6a8d6
Too many PR bumps and rebuildings are caused by this patch. I'm
not very sure about what this patch tries to fix, it seems that
it
Use a common _log_check_common() function (based on the old
_log_check_warn() function) to implement the logic for both
_log_check_warn() and _log_check_error().
The main benefit of this is that now all error messages will be
reported again, not just the first one found. Additionally the output
wi
The reverted commit added a warning with the log line that triggered
the log check for error messages before the warning that states that
an error has been found in the log. However, the error line is output
by the call to bb.fatal() that follows immediately after the original
warning, which makes
This is a set of improvements to the log check code in
meta/lib/oe/rootfs.py. It started out with me wanting to reduce the
spam I got when there were many warnings in the log, and ended up with
quite a lot of refactoring. I also activated the fix to bug 7789 along
the way...
I have only tested thi
Before there were three different ways to exclude a line from being
searched for error messages in _log_check_error(). Now there is only
one: an array of regular expressions. This should make it easy to add
more excludes if nedded.
Signed-off-by: Peter Kjellerstedt
---
meta/lib/oe/rootfs.py | 25
For each warning found in the log, _log_check_warn() would output a
line stating that it had found a warning, then the actual warning and
finally an empty line. This is quite excessive when there are many
warnings in the log.
With this change the output is instead a line stating how many
warnings
The fact that this function was overridden in the RpmRootfs class
seems to have led to a number of misstakes when changes have been made
to the base function in the Rootfs class. E.g., this change will
properly solve ticket 7789, which was supposedly solved in 38871dc0,
but that change had no effec
In commit 0387d095 lines with "NOTE:" in them were excluded from the
log check for warnings. However, those lines were only there in the
first place since the regular expression that is used to find warning
messages explicitly included those lines...
Signed-off-by: Peter Kjellerstedt
---
meta/li
This will make _log_check_warn() exclude the same lines as
_log_check_error() does.
Signed-off-by: Peter Kjellerstedt
---
meta/lib/oe/rootfs.py | 19 +++
1 file changed, 15 insertions(+), 4 deletions(-)
diff --git a/meta/lib/oe/rootfs.py b/meta/lib/oe/rootfs.py
index 63ca22f..74
This hunk of patch went missing during the glibc upgrade to 2.24
and without it, uninative-tarball doesn't work properly. This adds
it back so we can spin a new version of uninative.
Signed-off-by: Richard Purdie
diff --git
a/meta/recipes-core/glibc/glibc/0003-nativesdk-glibc-Raise-the-size-of-
ACL's ptest has a handful of failure modes which can be triggered by
a restrictive or small system. First, the ptest requires that daemon
be in the bin group, which run-ptest attempts to do using gpasswd,
but gpasswd is part of shadow, and oe-core removes shadow when it
doesn't think shadow will be
On Wed, May 18, 2016 at 1:40 PM, Otavio Salvador
wrote:
> When the distribution has X11 and Wayland backends, we enable XWayland
> support and include XTerm as a test application for the XWayland
> backend.
>
> Signed-off-by: Otavio Salvador
As discussed on IRC, instead of XTerm - which is not i
The acl tests assume that umask is 022 (or similar) by default
for some of the permissions tests. The existing run-ptest script
also assumes availability of gpasswd, which we tend to remove by
default, and that the current filesystem supports ACLs. Fix
this by adding a line to the test script for t
There are few new failures most likely caused by glibc upgrade.
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!colspan='6'|Failed depencencies!!|Signatures
!!colspan='12'|QA !!Comment
|-
||
On Wed, May 18, 2016 at 2:03 AM, Robert Yang wrote:
> * It doesn't build on armv4:
> {standard input}: Assembler messages:
> {standard input}:52: Error: selected processor does not support `blx
> llint_throw_stack_overflow_error' in ARM mode
> {standard input}:126: Error: selected processor does
On 18 May 2016 at 20:39, Otavio Salvador
wrote:
> From the previous message it seems it won't work.
>
os.path.join has the "interesting" semantics that ("/foo", "/bar") produces
"/bar", whereas oe.path.join is basically just string joining so will
produce /foo/bar.
Ross
--
note: context of running "make export-sdk" in wind river linux, but
i have narrowed it down to pretty much the same question regarding
"bitbake -c populate-sdk". i hope.
what kernel header files are copied to the sysroot(?) when running
that command? pretty clearly, everything under include/u
On Tue, 2016-05-17 at 14:25 -0500, Edwin Plauchu wrote:
> From: Edwin Plauchu
>
> This patch avoids zip recipe fails to compile with compiler flags
> which elevate common string formatting issues into an error (-Wformat
> -Wformat-security -Werror=format-security).
In future please wrap the comm
On Wed, May 18, 2016 at 12:54 PM, Burton, Ross wrote:
>
> On 18 May 2016 at 15:14, Martin Jansa wrote:
>>
>> Use os.path.join instead of +
>
>
> I just went and edited the patch directly to do that, so no need to send it
> again.
>From the previous message it seems it won't work.
--
Otavio S
This fix was not sufficient and there has to be extra fix done to also
consider the case
when sysroot is created during image build time. I have updated it in
pull request here
http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/pu&id=642c6cf0b6a0371de476513162bd0cefa9c438b3
On T
On 18 May 2016 at 16:32, Martin Jansa wrote:
> Please ignore what I said, os.path.join won't work anyway, because
> libdir starts with slash so os.path.join would just return that part.
>
Luckily we have oe.path.join which doesn't have the os.path.join semantics,
so I changed the patch when merg
There are issues with a change made to RTLD_NEXT behaviour in glibc 2.24
and that change was also backported to older glibc versions in some distros
like Fedora 23. This adds a workaround whilst the pseudo maintainer fixes
various issues properly.
Signed-off-by: Richard Purdie
diff --git
a/meta
Instead of adding partial dependencies we list the PACKAGECONFIG
options that are required. Those are: X11 and Wayland.
The previous value were redudant with X11 PACKAGECONFIG option and as
it is a requirement, for XWayland, it can be removed to easy
maintenance.
Signed-off-by: Otavio Salvador
-
From: Tom Hochstein
Exit the program if an unrecognized command line option is found.
Signed-off-by: Tom Hochstein
Signed-off-by: Otavio Salvador
---
Changes in v8: None
Changes in v7:
- Rebase on top of 1.10 v2 + fixup
Changes in v6:
- Rebase on top of 1.10
Changes in v5:
- New patch.
Cha
Up to now, to make Xwayland to work it required several manual hacks
and it was difficult to make an image which had support for it out of
box.
This patchset intends to set the base for it. It enables weston-init
to be extended to support Xwayland launch when needed.
While working on it, some imp
When the DISTRO has X11 and Wayland support enabled, XWayland ought to
be enabled by default.
Signed-off-by: Otavio Salvador
---
Changes in v8:
- Split XWayland module in a package (Ross)
Changes in v7: None
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes
From: Tom Hochstein
weston-launch requires PAM for starting weston as a non-root user.
Since starting weston as root is a valid use case by itself, we check
the distro for 'pam' and build weston-launch with or without
non-root-user support.
Signed-off-by: Tom Hochstein
Signed-off-by: Otavio Sa
This improves the log shown in boot. Now it shows:
[ OK ] Started Weston Wayland Compositor
Signed-off-by: Otavio Salvador
---
Changes in v8: None
Changes in v7: None
Changes in v6:
- Fix typo on commit log (rborton)
Changes in v5: None
Changes in v4:
- New patch.
Changes in v3: None
Chan
When the distribution has X11 and Wayland backends, we enable XWayland
support and include XTerm as a test application for the XWayland
backend.
Signed-off-by: Otavio Salvador
---
Changes in v8:
- Install weston-xwayland package (Ross)
Changes in v7: None
Changes in v6:
- Add xterm
Changes in
From: Tom Hochstein
When weston is started as the first windowing system (i.e. not under X
nor under another Wayland server), it should be done with the command
weston-launch to set up proper privileged access to devices.
Signed-off-by: Tom Hochstein
Signed-off-by: Otavio Salvador
---
Chan
The weston-start script now supports loading modules so the Xwayland
support can be loaded optionally. Use this to load Weston accordingly.
Signed-off-by: Otavio Salvador
---
Changes in v8:
- Change order of patch (Ross)
Changes in v7:
- Rebase on top of 1.10 v2 + fixup
Changes in v6: None
Cha
To make weston-start more flexible we now support module loading. For
such modules, following functions can be used:
- add_weston_argument
- add_openvt_argument
Signed-off-by: Otavio Salvador
---
Changes in v8:
- Use ${datadir} for module path (Ross)
Changes in v7: None
Changes in v6: None
C
The Weston nested instance support is not implemented. This errors out
displaying an informative error message so someone insterested on it
may look at implement this later.
Signed-off-by: Otavio Salvador
---
Changes in v8: None
Changes in v7: None
Changes in v6: None
Changes in v5: None
Changes
The new 'weston-start' script redcues the code duplication for SysV
and SystemD based images.
Signed-off-by: Otavio Salvador
---
Changes in v8: None
Changes in v7: None
Changes in v6: None
Changes in v5: None
Changes in v4:
- Use --log= for weston call
Changes in v3:
- Fix log redirection
- Fix
The install -D allow for the parent directories to be created in a
single command line, reducing the code and number of fork during the
build.
Signed-off-by: Otavio Salvador
---
Changes in v8: None
Changes in v7: None
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes in v3: Non
This allow Weston to be build without the clients.
Signed-off-by: Otavio Salvador
---
Changes in v8: None
Changes in v7: None
Changes in v6: None
Changes in v5: None
Changes in v4:
- New patch.
Changes in v3: None
Changes in v2: None
meta/recipes-graphics/wayland/weston_1.10.0.bb | 7 +++
From: Patrick Ohly
Conversion to vmdk/vdi/qcow2 is also useful for other base images
types, not just for .hdddirect. This can be achieved by definining
them as conversion commands and relying on the conversion chaining
to convert arbitrary base images.
For this to work when the base image gets c
From: Patrick Ohly
If a certain image type can be created both by applying conversion
commands to a base type as well as via a specialized command (like a
fictious IMAGE_CMD_ext4.xz, or some dedicated task, as indicated by
IMAGE_TYPES_MASKED = ext4.xz), then pick the more specialized method
and s
From: Patrick Ohly
With the enhanced functionality, the term "compression" is no longer
accurate, because the mechanism also gets used for conversion
operations that do not actually compress data.
It is possible to remove this naming problem in a backward-compatible
manner by including COMPRESSI
From: Patrick Ohly
When a symlink does not get created, it is useful for debugging to log
what would have been created and why it was skipped.
Signed-off-by: Patrick Ohly
Signed-off-by: Ed Bartosh
Signed-off-by: Ed Bartosh
---
meta/classes/image.bbclass | 8 +---
1 file changed, 5 insert
From: Patrick Ohly
When using conversion chaining (for example example: .dsk.vdi.xz),
the imagetypes_getdepends() did not properly detect all compression
commands (thus skipping the corresponding COMPRESS_DEPENDS) and
the base type, leading to missing dependencies of the image's do_rootfs
task.
From: Patrick Ohly
When a derived distro adds a certain type, say zip, to
COMPRESSIONTYPES and later OE-core does the same, we end up with the
type being listed twice, and that would have undesired effects
(commands generated twice).
So to support such loosely coupled extension, we de-duplicated
Hi,
This patchset contains various improvements for the image creation functionality
made by Patchick Ohly during his work on bug #9076:
- fixed dependency calculation for conversion chaining
- converted vmdk/vdi/qcow2 image types into conversion commands
- renamed COMPRESSION variables to CONV
On 17 May 2016 at 17:36, Otavio Salvador wrote:
> +modules_dir=/usr/share/weston-start
>
Hard-coded paths in here (this, /run) - can these use symbols and get
replaced on do_install?
Ross
--
___
Openembedded-core mailing list
Openembedded-core@lists.
The --list-tests option assumes a terminal of 150 characters wide,
which is clearly wrong. The output for this command is messy and
hard to understand for lower widths. Every command should look
good in a 80 characters terminal.
Unfortunately, this can't be done at the moment. The bad naming of
te
On 17 May 2016 at 17:36, Otavio Salvador wrote:
> weston: Add Xwayland initialization support using weston-start
> weston-init: Error out if loading a nested instance
> weston-init: Add module support for the weston-start helper
>
Ordering here is wrong :)
Ross
--
___
On Wed, May 18, 2016 at 1:03 PM, Burton, Ross wrote:
>
> On 17 May 2016 at 17:36, Otavio Salvador wrote:
>>
>> When the DISTRO has X11 and Wayland support enabled, XWayland ought to
>> be enabled by default.
>
>
> Can this also split xwayland into a separate package so its still possible
> to bui
On 17 May 2016 at 17:36, Otavio Salvador wrote:
> When the DISTRO has X11 and Wayland support enabled, XWayland ought to
> be enabled by default.
>
Can this also split xwayland into a separate package so its still possible
to build a core-image-weston with the x11 DISTRO_FEATURE but without
pull
On 18 May 2016 at 15:14, Martin Jansa wrote:
> Use os.path.join instead of +
>
I just went and edited the patch directly to do that, so no need to send it
again.
Ross
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http
On Wed, May 18, 2016 at 05:26:16PM +0200, Herve Jourdain wrote:
> Hi Martin,
>
> Even though the line just below uses "+"? Or shall I modify both?
Ah that's where it came from. Sorry I haven't noticed that it was
already there.
Please ignore what I said, os.path.join won't work anyway, because
l
Hi Martin,
Even though the line just below uses "+"? Or shall I modify both?
Herve
-Original Message-
From: Martin Jansa [mailto:martin.ja...@gmail.com]
Sent: mercredi 18 mai 2016 16:15
To: Herve Jourdain
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [mesa][PATCH
On Wed, May 18, 2016 at 08:33:37PM +0800, Herve Jourdain wrote:
> When compiling mesa, if dri is disabled in PACKAGECONFIG, or if the list of
> DRI drivers is empty, it will cause populate_package to fail, because it
> can't find - rightfully - the directory for the DRI drivers.
> This patch chec
This option enables generation of .bmap file for the
result image using native bmaptool.
[YOCTO #9413]
Signed-off-by: Ed Bartosh
---
scripts/lib/wic/creator.py | 1 +
scripts/lib/wic/engine.py | 11 ---
scripts/lib/wic/imager/direct.py
Added bmaptool -> bmap-tools pair to the dictionary
executable -> recipe as bmaptool is going to be used by wic
to generate .bmap file.
[YOCTO #9413]
Signed-off-by: Ed Bartosh
---
scripts/lib/wic/utils/oe/misc.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/scripts/lib/
Hi,
just wanted to say that we are facing the same issue with PRServer and
live updates, looking forward to a possible solution.
Kind regards,
Sergey
On Wed, May 18, 2016 at 05:31:09PM +0800, Robert Yang wrote:
>
>
> On 05/18/2016 05:20 PM, Martin Jansa wrote:
> >On Wed, May 18, 2016 at 04:03:
Tested generation of .bmap file using wic --bmap command
line option.
Signed-off-by: Ed Bartosh
---
meta/lib/oeqa/selftest/wic.py | 8
1 file changed, 8 insertions(+)
diff --git a/meta/lib/oeqa/selftest/wic.py b/meta/lib/oeqa/selftest/wic.py
index a569fbf..895c6d6 100644
--- a/meta/lib
Included description of -m/--bmap option to the help page
produced by 'wic help create'.
[YOCTO #9413]
Signed-off-by: Ed Bartosh
---
scripts/lib/wic/help.py | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/scripts/lib/wic/help.py b/scripts/lib/wic/help.py
index 7dcc717..6
When compiling mesa, if dri is disabled in PACKAGECONFIG, or if the list of DRI
drivers is empty, it will cause populate_package to fail, because it can't find
- rightfully - the directory for the DRI drivers.
This patch checks that the directory indeed exists before trying to get a list
of the
When compiling mesa, if dri is disabled in PACKAGECONFIG, or if the list of DRI
drivers is empty, it will cause populate_package to fail, because it can't find
- rightfully - the directory for the DRI drivers.
This patch checks that the directory indeed exists before trying to get a list
of the
PAM environment vars must be ignored when UseLogin=yes
Signed-off-by: Jussi Kukkonen
---
.../openssh/openssh/CVE-2015-8325.patch| 39 ++
meta/recipes-connectivity/openssh/openssh_7.2p2.bb | 1 +
2 files changed, 40 insertions(+)
create mode 100644
meta/recipes-
Remove patches that are in the release.
Signed-off-by: Jussi Kukkonen
---
.../openssh/openssh/CVE-2016-1907_2.patch | 65
.../openssh/openssh/CVE-2016-1907_3.patch | 329 -
.../openssh/CVE-2016-1907_upstream_commit.patch| 33 ---
.../openssh/opens
The CVE fix should apply for at least Krogoth and Jethro as well.
The following changes since commit 7707cf6562e6a477ea953743a2d9aba682d90949:
sdk-manual: Fixed three broken links to sections within manual. (2016-05-17
21:35:00 +0100)
are available in the git repository at:
git://git.yocto
Hi Ross,
Yep, you’re right, sorry for that. V2 coming in a few.
Herve
From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: mercredi 18 mai 2016 13:28
To: Herve Jourdain
Cc: OE-core
Subject: Re: [OE-core] [mesa][PATCH 1/1] Fix mesa_populate_packages() when dri
is disabled
O
On 18 May 2016 at 10:45, Herve Jourdain wrote:
> +if os.path.isdir(dri_drivers_root):
>
You're checking files on the host here as dri_driver_root is ${libdir}/dri
and you failed to append PKGD (see the os.listdir call).
Ross
--
___
Openembedded-c
On Wed, May 18, 2016 at 05:31:09PM +0800, Robert Yang wrote:
>
>
> On 05/18/2016 05:20 PM, Martin Jansa wrote:
> > On Wed, May 18, 2016 at 04:03:58PM +0800, Robert Yang wrote:
> >> Hi Martin,
> >>
> >> On 05/18/2016 03:39 PM, Martin Jansa wrote:
> >>> See:
> >>> https://bugzilla.yoctoproject.org/
When compiling mesa, if dri is disabled in PACKAGECONFIG, or if the list of DRI
drivers is empty, it will cause populate_package to fail, because it can't find
- rightfully - the directory for the DRI drivers.
This patch checks that the directory indeed exists before trying to get a list
of the
* useradd/userdel functions will fail for recipes which override their target
prefix
(e.g. to /opt/foo), because it will try to use pseudo from
native-sysroot/opt/foo/bin/pseudo
Signed-off-by: Martin Jansa
---
meta/classes/useradd.bbclass | 4 ++--
1 file changed, 2 insertions(+), 2 deletion
When compiling mesa, if dri is disabled in PACKAGECONFIG, or if the list of DRI
drivers is empty, it will cause populate_package to fail, because it can't find
- rightfully - the directory for the DRI drivers.
This patch checks that the directory indeed exists before trying to get a list
of the
On 05/18/2016 05:20 PM, Martin Jansa wrote:
On Wed, May 18, 2016 at 04:03:58PM +0800, Robert Yang wrote:
Hi Martin,
On 05/18/2016 03:39 PM, Martin Jansa wrote:
See:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5970
Just using recipe checksum wont work, because the main reason for PR bu
On Wed, May 18, 2016 at 04:03:58PM +0800, Robert Yang wrote:
> Hi Martin,
>
> On 05/18/2016 03:39 PM, Martin Jansa wrote:
> > See:
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=5970
> >
> > Just using recipe checksum wont work, because the main reason for PR bumps
> > is to
> > automatica
* It doesn't build on armv4:
{standard input}: Assembler messages:
{standard input}:52: Error: selected processor does not support `blx
llint_throw_stack_overflow_error' in ARM mode
{standard input}:126: Error: selected processor does not support `bkpt #0' in
ARM mode
{standard input}:128: Error:
* V2
Rebase and resend.
// Robert
The following changes since commit 84b11bce72296d04a0e6bc9f18669284017c3704:
pkgconfig: Update AM_GLIB_GNU_GETTEXT macro (2016-05-17 17:26:05 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/webkitgt
Hi Joshua,
Thanks, I read packagefeed-stability.bbclass just now. If
we can change PRserver's checksum to consider RDEPENDS only
(or make it optional) I will run a testing on that script.
// Robert
On 05/18/2016 03:34 PM, Joshua G Lock wrote:
Hi Robert,
On Wed, 2016-05-18 at 14:09 +0800, Robe
Hi Martin,
On 05/18/2016 03:39 PM, Martin Jansa wrote:
See:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5970
Just using recipe checksum wont work, because the main reason for PR bumps is to
automatically upgrade the packages when one of the dependencies changes .so
version, which you won'
Building gcc-cross 4.9.3 with gcc 6 fails with the following error:
error: 'const char* libc_name_p(const char*, unsigned int)' redeclared inline
with 'gnu_inline' attribute
This is a backport of the upstream fix.
Signed-off-by: Ioan-Adrian Ratiu
---
meta/recipes-devtools/gcc/gcc-4.9.inc
It is required by python3's bitbake.
Signed-off-by: Robert Yang
---
meta/recipes-core/meta/buildtools-tarball.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-core/meta/buildtools-tarball.bb
b/meta/recipes-core/meta/buildtools-tarball.bb
index f45e781..34df531 100644
--- a/me
Signed-off-by: Robert Yang
---
meta/recipes-core/meta/buildtools-tarball.bb | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/meta/recipes-core/meta/buildtools-tarball.bb
b/meta/recipes-core/meta/buildtools-tarball.bb
index dd28b96..f45e781 100644
--- a/meta/recipes-
Need add python3-git to buildtools-tarball for the py3 build, and the
dependencies chain is:
python3-git -> python3-gitdb -> python3-smmap
Signed-off-by: Robert Yang
---
meta/recipes-devtools/python/python-smmap.inc | 19 +++
meta/recipes-devtools/python/python-smmap_0.9.0
It was added for testing, and not needed any more after:
4a8a74c62836a20610daf029d4cec0b3087758b2
Author: Robert Yang
Date: Mon Mar 21 02:25:50 2016 -0700
gpg_sign.py: get rid of pexpect
So remove it.
Signed-off-by: Robert Yang
---
meta/recipes-core/meta/buildtools-tarball.bb | 1 -
1 f
Need add python3-git to buildtools-tarball for the py3 build, and the
dependencies chain is:
python3-git -> python3-gitdb
Signed-off-by: Robert Yang
---
meta/recipes-devtools/python/python-gitdb.inc | 16
meta/recipes-devtools/python/python-gitdb_0.6.4.bb | 18 ++
Need add python3-git to buildtools-tarball for the py3 build.
Signed-off-by: Robert Yang
---
meta/recipes-devtools/python/python-git.inc | 21 +
meta/recipes-devtools/python/python-git_1.0.2.bb | 22 ++
meta/recipes-devtools/python/python3-git_1.0.2
Need add python3-git to buildtools-tarball for the py3 build, and the
dependencies chain is:
python3-git -> python3-gitdb -> python3-async
Signed-off-by: Robert Yang
---
meta/recipes-devtools/python/python-async.inc | 15 +++
meta/recipes-devtools/python/python-async_0.6.2.bb
See:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5970
Just using recipe checksum wont work, because the main reason for PR bumps
is to automatically upgrade the packages when one of the dependencies
changes .so version, which you won't detect from recipe checksum of the app
which is just usi
The following changes since commit 84b11bce72296d04a0e6bc9f18669284017c3704:
pkgconfig: Update AM_GLIB_GNU_GETTEXT macro (2016-05-17 17:26:05 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/btpy3
http://cgit.openembedded.org/cgit.cgi
Hi Robert,
On Wed, 2016-05-18 at 14:09 +0800, Robert Yang wrote:
> The PRServer bumps PR according to do_package's task hash, that
> causes it bumps *all* packages' PR when recipes like pseudo-native
> and rpm-native is changed. It is a very bad user experience when we
> run "smart/opkg upgrade" o
On 17 May 2016 at 23:24, Richard Purdie
wrote:
> On Tue, 2016-05-17 at 11:00 -0300, Otavio Salvador wrote:
>> On Tue, May 17, 2016 at 5:38 AM, Burton, Ross
>> wrote:
>> >
>> > On 17 May 2016 at 08:31, Jussi Kukkonen
>> > wrote:
>> > >
>> > > There's not much to work on as far as I can tell: 1.11
The PRServer bumps PR according to do_package's task hash, that
causes it bumps *all* packages' PR when recipes like pseudo-native
and rpm-native is changed. It is a very bad user experience when we
run "smart/opkg upgrade" on running target, for example, when we apply
a CVE patch to pseudo-native
93 matches
Mail list logo
