Although it may not appeal so much to users to prefer 80x24 consoles,
the general trend is for screens to get bigger and the current output
has started to look a little cramped on a modern HD display.
Increasing from 17 to 20 is obviously arbitrary, but does give enough
space to cleanly display la
== Series Details ==
Series: base.bbclass: increase indent in get_layers_branch_rev() and
buildcfg_vars()
Revision: 1
URL : https://patchwork.openembedded.org/series/9677/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated resp
Although it may not appeal so much to users to prefer 80x24 consoles,
the general trend is for screens to get bigger and the current output
has started to look a little cramped on a modern HD display.
Increasing from 17 to 20 is obviously arbitrary, but does give enough
space to cleanly display la
Signed-off-by: Chen Qi
---
.../recipes-extended/sysstat/{sysstat_11.5.7.bb => sysstat_11.6.1.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-extended/sysstat/{sysstat_11.5.7.bb => sysstat_11.6.1.bb}
(53%)
diff --git a/meta/recipes-extended/sysstat/sysstat_11.5
Signed-off-by: Chen Qi
---
meta/recipes-extended/cups/{cups_2.2.4.bb => cups_2.2.6.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-extended/cups/{cups_2.2.4.bb => cups_2.2.6.bb} (40%)
diff --git a/meta/recipes-extended/cups/cups_2.2.4.bb
b/meta/recipes-extende
The following changes since commit b656fd9267b1f36d46ca20a1c0bcfaedbf7df438:
gcc: fix miscompilation on mips64 (2017-11-08 22:24:04 +)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib ChenQi/PU-20171109
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=C
test-arrayind1-Remove-hashbang-line.patch is dropped as it has
been merged in new version.
Signed-off-by: Chen Qi
---
.../test-arrayind1-Remove-hashbang-line.patch | 30 --
.../gawk/{gawk-4.1.4 => gawk}/run-ptest| 0
.../gawk/{gawk_4.1.4.bb => gawk_4.2.0.bb}
Signed-off-by: Chen Qi
---
meta/recipes-extended/sudo/{sudo_1.8.20p2.bb => sudo_1.8.21p2.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-extended/sudo/{sudo_1.8.20p2.bb => sudo_1.8.21p2.bb} (90%)
diff --git a/meta/recipes-extended/sudo/sudo_1.8.20p2.bb
b/meta/
Backport
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82445
Fixes [YOCTO 12297]
Signed-off-by: Khem Raj
---
meta/recipes-devtools/gcc/gcc-6.4.inc | 1 +
...5-suppress-32-bit-aligned-ldrd-strd-peeph.patch | 194 +
meta/recipes-devtools/gcc/gcc-7.2.inc
Rich Felker (9):
fix access by setjmp and longjmp to __hwcap on arm built as thumb2
for executing init array functions, use function type with prototype
fix read-after-free type error in pthread_detach
fix incorrect base name offset from nftw when pathname ends in slash(es)
Signed-off-by: Khem Raj
---
.../0001-Use-uintmax_t-for-handling-rlim_t.patch | 89 ++
meta/recipes-core/systemd/systemd_234.bb | 1 +
2 files changed, 90 insertions(+)
create mode 100644
meta/recipes-core/systemd/systemd/0001-Use-uintmax_t-for-handling-rlim_t.pa
Signed-off-by: Khem Raj
---
meta/recipes-devtools/go/go-1.9.inc| 3 +
.../go/go-1.9/default-buildmode-pie.patch | 18
.../go/go-1.9/set-external-linker.patch| 111 +
3 files changed, 132 insertions(+)
create mode 100644 meta/recipe
This makes it easy to override them in bbappends
Signed-off-by: Khem Raj
---
meta/recipes-devtools/binutils/binutils-2.29.inc | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-devtools/binutils/binutils-2.29.inc
b/meta/recipes-devtools/binutils/binutils-2.29.
If you have a recipe that uses overrides to conditionally extend
SRC_URI to add additional patches, then you will often need to update
those patches if you're making other changes to the source tree (for
example if you're upgrading the underlying source). Make this possible
with devtool by creating
upgrade musl past 1.1.18 release
fix armv5 codegen issue seen with gcc7 while compiling kernel
fix systemd for musl/64-bit
make binutils SRC_URI overridable
Fix go with PIE/musl
The following changes since commit 3717c76eb24217c14a22f72fdd8732923729dee8:
gcc: fix miscompilation on mips64 (2017-
If a file is going to be effectively removed from the destination by
devtool finish, we should report that rather than just reporting that
we're removing files from the workspace. This is a little tricky because
the way we actually operate when finishing is to:
(1) remove all original files (as re
* Only log one warning message instead of one per line
* Be a bit more verbose
* "if list" is more pythonic than "if len(list)"
Signed-off-by: Paul Eggleton
---
scripts/lib/devtool/upgrade.py | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/scripts/lib/devtool/upgrade.py
If the files that the devtool-source class is supposed to create in the
source tree aren't found in the temporary directory then we know that
the class hasn't worked properly - say that explicitly.
Signed-off-by: Paul Eggleton
---
scripts/lib/devtool/standard.py | 11 +++
1 file changed,
Give the user a little more insight into what's being done.
Signed-off-by: Paul Eggleton
---
scripts/lib/devtool/upgrade.py | 2 ++
1 file changed, 2 insertions(+)
diff --git a/scripts/lib/devtool/upgrade.py b/scripts/lib/devtool/upgrade.py
index 6d51958..e7d47b9 100644
--- a/scripts/lib/devtoo
If the directory where the source code extracts to changes (for
example, when upgrading iucode-tool from 1.5 to 2.1.1, the subdirectory
in the tarball changed from "iucode_tool-${PV}" to "iucode-tool-${PV}")
then handle this automatically. Also handle when it changes to match the
default S value (i
github archive URLs are not guaranteed to be stable [1] and thus we
should show a warning if a user specifies one to recipetool create (or
devtool add).
[1]
http://lists.openembedded.org/pipermail/openembedded-core/2017-September/142519.html
Signed-off-by: Paul Eggleton
---
scripts/lib/recipet
devtool upgrade did not properly handle setting SRC_URI checksums for
recipes that use named SRC_URI entries and also use those names in the
SRC_URI checksums. A further complication was where the name contained
an expression that changed with the version e.g. ${PV} (probably quite
rare, but the dn
I noticed that using bitbake-layers add-layer followed by a devtool
command resulted in bitbake re-parsing all of the recipes, which is
annoying. Upon closer inspection I could see that devtool was moving the
workspace layer path to the end of BBLAYERS if it happened to be
somewhere in the middle -
If you're not sure what changes devtool finish is going to make, or
you're not sure you're finished with your modifications, it is useful to
be able to see what devtool finish is going to do beforehand, so add
a -N/--dry-run option to make that possible.
(It's also very useful for debugging devtoo
This looks like some debug printing that was left in by accident.
Signed-off-by: Paul Eggleton
---
scripts/lib/recipetool/create_npm.py | 1 -
1 file changed, 1 deletion(-)
diff --git a/scripts/lib/recipetool/create_npm.py
b/scripts/lib/recipetool/create_npm.py
index ae53972..fb57e70 100644
--
If the git repository for a recipe in the workspace has uncommitted
changes in it then it's possible that the user has forgotten to commit
something, so check and exit if there are any. Provide a -f/--force
option to continue in the case where the uncommitted changes aren't
needed.
Separately, if
devtool finish will check if the destination layer is part of
bblayers.conf so that we avoid the user getting confused about the
recipe vanishing from their configuration if it isn't. devtool finish
also accepts a path underneath a layer so that you have a bit
more control over where it ends up. Ho
* Show a warning in devtool upgrade if the version is less than the
current version suggesting that the user may need to bump PE in the
recipe
* Show a warning in devtool add and devtool upgrade if the version looks
like a pre-release version suggesting using a version number that
won't mes
If S points to a subdirectory of the source rather than the "base" of
the source tree then we weren't handling the oe-local-files directory
properly - it got extracted to the base of the tree but devtool
update-recipe and devtool finish assumed it would be under S which would
be the subdirectory, t
If S points to a subdirectory of the source rather than the "base" of
the source tree then print that rather than the subdirectory path when
telling the user they need to remove the source tree, since that is the
directory that they will need to remove.
Signed-off-by: Paul Eggleton
---
scripts/l
After some reconsideration I think it's a bit annoying for users to be
forced to use an option to work with recipes where the file isn't in the
workspace, so let's just have these commands check the workspace first
for the recipe, and if it isn't there then load the cache and get it
that way.
Sign
When devtool upgrade is upgrading to a new version where the source is
fetched as an archive (e.g. a tarball), we create a single commit in the
git repository that is the upgrade from the old version to the new. We
do this by extracting the old source, committing it, deleting all files,
copying in
With versions of git older than 2.0, "git add" on a deleted file (i.e.
in this case a file that was removed between versions) will not add the
delete to be committed by default, with the result that the rebase of
patches on top of the new branch will fail. We need to use the -A
option in order to f
find_layerdir() should really return absolute paths, so make it do so.
This fixes devtool finish not deleting files it should do after devtool
upgrade if the specified path is relative, since the devtool finish code
was assuming that find_layerdir() was returning an absolute path.
Fixes [YOCTO #12
It appears that when fixing the signature unlocking in OE-Core commit
4e9a0be32fc30fb87d65da7cd1a4015c99533aff I swapped the parameters here
and did not test it within the eSDK (it does nothing outside of the
eSDK) resulting in a TypeError when devtool upgrade was used in the
eSDK. Swap the paramet
If a value was split over multiple lines (e.g. as SRC_URI usually is)
then we were inserting the value as one item in the lines list with
newlines between each line. There's nothing wrong with this if you're
writing the list out to a file, but if you want to generate a patch (as
patch_recipe_file()
We shouldn't be passing a relative path to the plugins if that's what's
been specified on the recipetool command line.
Signed-off-by: Paul Eggleton
---
scripts/lib/recipetool/create.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/lib/recipetool/create.py b/scri
Fix a number of bugs in devtool/recipetool and make the following
improvements:
* Conditional patch handling (e.g. musl-specific patches)
* Add dry-run option for devtool finish
* Automatically adjust S on upgrade if needed
* Make devtool upgrade output more useful
* Make devtool finish check
If the source tree happens to contain a kernel module as an example, a
test or under a "contrib" directory then we shouldn't be picking it up
and making the determination that the entire thing is a kernel module.
An example that triggered this is zstd, which ships a kernel module
under contrib/lin
Hey all,
So, per Ed's feedback on my first series, I went and spent some time
trying to figure out how to have wic know what the UUID would be when
updating the fstab. It turns out the easiest answer here is to have WIC
make the UUID. Per Otavio's concern last time, I also make sure that
the fil
First, allow for wic to be given a filesystem UUID to be used when
creating a filesystem. When not provided, wic will generate the UUID to
be used. Next, when --use-uuid is passed, we update the fstab to mount
things via UUID (and if not found, then use PARTUUID) as UUID is more
portable.
Signed
First, we support squashfs as root, so mention that. Second, the btrfs
rootfs creation function had a copy/paste of the previous function
comment, remove the irrelevant line.
Signed-off-by: Tom Rini
---
scripts/lib/wic/partition.py | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff
The SquashFS filesystem does not support UUIDs so make this combination
be an error.
Signed-off-by: Tom Rini
---
scripts/lib/wic/ksparser.py | 5 +
1 file changed, 5 insertions(+)
diff --git a/scripts/lib/wic/ksparser.py b/scripts/lib/wic/ksparser.py
index 7850e81d2f37..4fb6868531df 100644
Haris,
Thanks for your patience on this process. This version works well, now
I have the extra work of getting these kernel known to systemd-boot!
Acked-by below!
Sau!
On Tue, 2017-11-07 at 12:40 -0600, Haris Okanovic wrote:
> Some distros may want to provide alternate kernel "flavors" via fe
The issues here was that WORKDIR changes based on the multilib variant
and the WORKDIR is used in the RECIPE_SYSROOT path. We need to use the
same WORKDIR that everything else is using so reset it before we expand
RECIPE_SYSROOT.
Signed-off-by: Dan Dedrick
---
meta/classes/staging.bbclass | 1 +
On 11 October 2017 at 16:34, Alexander Kanavin <
alexander.kana...@linux.intel.com> wrote:
> Drop 0001-nls.m4-Take-it-from-gettext-0.15.patch as it's now
> upstreamed.
>
> Remove --disable-xevie option:
> https://github.com/GNOME/at-spi2-core/commit/
> 644096a28a47bdf5c6e0c34c9cd5b944df059925
My
Thanks for reminding me. :)
1/2 is queued but 2/2 was implicated in a number of systemd-related boot
failures on the autobuilder (
https://autobuilder.yocto.io/builders/nightly-qa-extras/builds/553).
I've not yet got around to looking at exactly what sanity test 5 and 7 do
to trigger this.
Ross
(ping) for this patch series.
On 10/16/2017 09:31 AM, Martin Kelly wrote:
The regex for acceptable systemd WantedBy/RequiredBy targets does not include
target.wants, so a line like this:
WantedBy=multi-user.target.wants
gets silently ignored, even though it works fine on a real system.
Signed
The only change from previous report is slightly newer oe-core and bitbake.
http://www.openembedded.org/wiki/Bitbake_World_Status
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='4'|Failed tasks
!!|Signatures
!!colspan='15'|Q
To run some x11 apps via Xwayland,I have both x11 and wayland in the distro
features on my Morty based TI-SDK.
I had to get mesa-gl included to provide the features of OpenGL that are
not provided by TI's SGX DDK for Xwayland to build.
With this change however, qtwayland is refusing to build becau
On Wed, Nov 8, 2017 at 2:17 PM, Otavio Salvador wrote:
> Upgrade to a new stable release and drop patches applied on upstream.
>
> For a full release notes, please see:
> https://mesa3d.org/relnotes/17.2.0.html
> https://mesa3d.org/relnotes/17.2.1.html
> https://mesa3d.org/relnotes/17.2.2.html
> h
On Wed, Nov 8, 2017 at 4:46 PM, akuster808 wrote:
>
>
> On 11/08/2017 03:04 AM, Nicolas Dechesne wrote:
>> From: Artur Mądrzak
>>
>> The WIC's 'part' can now give a name for GPT partition in WKS file.
>> It's similar to '--label', but is naming partintions instead file systems.
>> It's required b
On 11/08/2017 03:04 AM, Nicolas Dechesne wrote:
> From: Artur Mądrzak
>
> The WIC's 'part' can now give a name for GPT partition in WKS file.
> It's similar to '--label', but is naming partintions instead file systems.
> It's required by some bootloaders to partitions have specified names.
>
> B
On Wed, Nov 08, 2017 at 10:00:54AM -0500, Tom Rini wrote:
> On Wed, Nov 08, 2017 at 01:20:15PM +0200, Ed Bartosh wrote:
> > On Tue, Nov 07, 2017 at 09:54:57AM -0500, Tom Rini wrote:
> > > On Tue, Nov 07, 2017 at 10:11:35AM +0200, Ed Bartosh wrote:
> > > > On Mon, Nov 06, 2017 at 07:44:23AM -0500, T
On 11/8/17 9:09 AM, Mark Wielaard wrote:
> Hi Alex,
>
> On Wed, 2017-11-08 at 15:14 +0200, Alexander Kanavin wrote:
>> On 11/07/2017 11:17 PM, Neal Gompa wrote:
>>
Thanks, this is the offending commit:
https://github.com/rpm-software-management/rpm/commit/88989572fff1f31e0c4f972a689
On Wed, Nov 08, 2017 at 01:20:15PM +0200, Ed Bartosh wrote:
> On Tue, Nov 07, 2017 at 09:54:57AM -0500, Tom Rini wrote:
> > On Tue, Nov 07, 2017 at 10:11:35AM +0200, Ed Bartosh wrote:
> > > On Mon, Nov 06, 2017 at 07:44:23AM -0500, Tom Rini wrote:
> > > > On Mon, Nov 06, 2017 at 09:36:20AM -0200, O
On 11/08/2017 01:43 AM, Alistair Francis wrote:
I don't want to be the Glib maintainer unfortunately, I just had to
test something with Glib 2.53.4+ and I figured I would send the patch
once I got it working.
I just want to say that as a community project, Yocto is what you make
it. If no one
This includes following changes:
bf04291 WHENCE: Add new qed firmware
d8fc990 WHENCE: Add new radeon firmware
7245319 WHENCE: Fix syntax error for iwlwifi-8265-31.ucode entry
18d71a8 Revert "ath10k: QCA988X hw2.0: update firmware to 10.2.4.70.63-2"
4ebfab3 ath10k: QCA6174 hw3.0: update board-2.bin
Signed-off-by: Otavio Salvador
---
Changes in v7:
- new patch
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2: None
.../cmake/{cmake-native_3.9.3.bb => cmake-native_3.9.5.bb}| 0
meta/recipes-devtools/cmake/cmake.inc
Signed-off-by: Otavio Salvador
---
Changes in v7:
- upgrade to 2.4.88 release
Changes in v6: None
Changes in v5:
- new patch
Changes in v4: None
Changes in v3: None
Changes in v2: None
meta/recipes-graphics/drm/{libdrm_2.4.83.bb => libdrm_2.4.88.bb} | 4 ++--
1 file changed, 2 insertions(+)
Upgrade to a new stable release and drop patches applied on upstream.
For a full release notes, please see:
https://mesa3d.org/relnotes/17.2.0.html
https://mesa3d.org/relnotes/17.2.1.html
https://mesa3d.org/relnotes/17.2.2.html
https://mesa3d.org/relnotes/17.2.3.html
https://mesa3d.org/relnotes/17
Those are the patches we have queued here for master.
Changes in v7:
- fix commit log typo
- upgrade to 2.4.88 release
- new patch
Changes in v6:
- update to 17.2.4
Changes in v5:
- rebase on top of master
- new patch
Changes in v4:
- update to 17.2.2
Changes in v3:
- fix build for way
On 11/07/2017 11:17 PM, Neal Gompa wrote:
Thanks, this is the offending commit:
https://github.com/rpm-software-management/rpm/commit/88989572fff1f31e0c4f972a6895585e4742ef4b
Looks like they added sophisticated in-place processing/rewriting of the
actual binary (that is not possible to switch
On 11/07/2017 10:17 PM, Paul Eggleton wrote:
So there is a method to this madness, but it's less about your use case than
it is people making customisations that they are best advised to put somewhere
else - I'm trying to make the user think about where the changes should go
beforehand, because
On Wed, Nov 08, 2017 at 12:04:09PM +0100, Nicolas Dechesne wrote:
> From: Artur Mądrzak
>
> The WIC's 'part' can now give a name for GPT partition in WKS file.
> It's similar to '--label', but is naming partintions instead file systems.
> It's required by some bootloaders to partitions have speci
On Tue, Nov 07, 2017 at 09:54:57AM -0500, Tom Rini wrote:
> On Tue, Nov 07, 2017 at 10:11:35AM +0200, Ed Bartosh wrote:
> > On Mon, Nov 06, 2017 at 07:44:23AM -0500, Tom Rini wrote:
> > > On Mon, Nov 06, 2017 at 09:36:20AM -0200, Otavio Salvador wrote:
> > > > On Mon, Nov 6, 2017 at 8:08 AM, Ed Bar
From: Artur Mądrzak
The WIC's 'part' can now give a name for GPT partition in WKS file.
It's similar to '--label', but is naming partintions instead file systems.
It's required by some bootloaders to partitions have specified names.
Backport from master, without it WIC cannot be used on Qualcomm
+Armin.
On Tue, Nov 7, 2017 at 9:07 PM, Artur Mądrzak wrote:
> The WIC's 'part' can now give a name for GPT partition in WKS file.
> It's similar to '--label', but is naming partintions instead file systems.
> It's required by some bootloaders to partitions have specified names.
>
> Backport from
So that we can use this on aarch64 with HiKey board.
Signed-off-by: Peter Griffin
---
meta/recipes-core/initrdscripts/initramfs-live-install-efi_1.0.bb | 2 +-
meta/recipes-core/initrdscripts/initramfs-live-install_1.0.bb | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a
Does this work on poky-lsb? Previous upgrades were failing with that due
to the security flags being enabled.
Ross
On 8 November 2017 at 09:56, zhengrq wrote:
> 1) Upgrade kexec-tools from 2.0.14 to 2.0.15.
> 2) Remove patches that are included in 2.0.15.
>kexec-tools/0001-arm64-Disable-PI
70 matches
Mail list logo
