This can happen if running unpack task produces unrelated files and directories
(e.g. if recipe_qa or other tasks run); in this case it's better to stop, rather
than allow devtool to continue and error out much later with a message that has
nothing to do with where the problem originated.
The idea
With newly added recipe_qa task, the function needs to filter out its output as
well.
The issue wouldn't appear in selftest because it's triggered by buildhistory and
selftest disables that.
Signed-off-by: Alexander Kanavin
---
scripts/lib/scriptutils.py | 2 +-
1 file changed, 1 insertion(+),
On Tue, 1 Aug 2023 at 22:48, Tim Orling wrote:
> I did the meta-perl/meta-python run on Sunday 30th and noticed the same much
> higher preponderance of devtool errors.
> I did a run of the recipes in oe-core that I maintain on 25th July and it had
> less devtool errors (3 of my recipes passed,
>
On Mon, 31 Jul 2023 at 19:00, Luca Boccassi wrote:
>
> On Mon, 31 Jul 2023 at 18:37, Alexander Kanavin
> wrote:
> >
> > A better option: fix the libpam recipe to say:
> >
> > ANY_OF_DISTRO_FEATURES = "pam systemd"
> > instead of current
> > REQUIRED_DISTRO_FEATURES = "pam"
> >
> >
> > This shou
On Wed, 2 Aug 2023 at 10:30, Yu, Mingli wrote:
> Did a simple check against core-image-full-cmdline with qemuppc64 just
> now and it can boot successfully with the default 256M memory.
>
> But it failed to boot with my customized image as the attached
> messages(/var/log/messages). If not change t
On Mon, Jul 31, 2023 at 2:33 PM Richard Purdie
wrote:
>
> I did look at the bug and it sounds like if you clean a recipe, builds
> of other recipes which depend upon it then fail?
Well not just in this case specifically, it is reproducible when doing
a clean build.
But this is the easiest most co
The one liner tests using `[ ] && action` need to have || true after the action,
otherwise the line returns false and the recipie fails.
Signed-off-by: Joel Stanley
---
meta/classes-recipe/kernel.bbclass | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/classes-recipe/
On Mon, Jun 19, 2023 at 4:55 AM Steve Sakoman wrote:
> Please review this set of changes for kirkstone and have comments back by
> end of day Tuesday.
>
> Passed a-full on autobuilder:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/5481
>
> The following changes since commi
On Thu, Jun 22, 2023 at 5:31 PM Steve Sakoman wrote:
> Please review this set of changes for dunfell and have comments back by
> end of day Monday.
>
> Passed a-full on autobuilder:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/5493
>
> The following changes since commit
>
On Wed, 2 Aug 2023 at 13:47, Joel Stanley wrote:
> The one liner tests using `[ ] && action` need to have || true after the
> action,
> otherwise the line returns false and the recipie fails.
>
> Signed-off-by: Joel Stanley
> ---
> meta/classes-recipe/kernel.bbclass | 4 ++--
> 1 file changed,
From: Emil Ekmečić
If accepted, this patch should merge with the corresponding BitBake
patch titled "fetch2: add Google Cloud Platform (GCP) fetcher".
Signed-off-by: Emil Ekmečić
---
meta/classes-global/sanity.bbclass | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/c
On Wed, 2 Aug 2023 at 12:45, Frédéric Martinsons
wrote:
>
>
>
> On Wed, 2 Aug 2023 at 13:47, Joel Stanley wrote:
>>
>> The one liner tests using `[ ] && action` need to have || true after the
>> action,
>> otherwise the line returns false and the recipie fails.
>>
>> Signed-off-by: Joel Stanley
From: Frederic Martinsons
It supersed the --offline flag and guarantee that Cargo.lock
file will not be modified during the build.
Signed-off-by: Frederic Martinsons
---
meta/classes-recipe/cargo.bbclass | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/meta/classes-rec
From: Frederic Martinsons
This patch series force the usage of --frozen instead of --offline during cargo
build.
This has the advantage to be sure that Cargo.lock file will not be modified.
Moreover, raise a clear error when Cargo.lock is not present.
For this to work, we must modify ourself the
From: Frederic Martinsons
Now we use --frozen, Cargo.lock cannot be modified by cargo build.
These patched git dependencies requires that the git url is removed
from Cargo.lock.
Fixes #15104
Signed-off-by: Frederic Martinsons
---
meta/classes-recipe/cargo_common.bbclass | 41 +
From: Frederic Martinsons
we now have more rust/cargo recipes and test that covers
various use cases.
Signed-off-by: Frederic Martinsons
---
meta/conf/distro/include/maintainers.inc | 1 -
meta/lib/oeqa/runtime/cases/rust.py | 12 --
.../packagegroup-core-tools-testapps
Hi,
On Wed, Aug 02, 2023 at 01:15:34PM +, Joel Stanley wrote:
> On Wed, 2 Aug 2023 at 12:45, Frédéric Martinsons
> wrote:
> >
> >
> >
> > On Wed, 2 Aug 2023 at 13:47, Joel Stanley wrote:
> >>
> >> The one liner tests using `[ ] && action` need to have || true after the
> >> action,
> >> oth
From: Emil Ekmečić
If accepted, this patch should merge with the corresponding BitBake
patch titled "fetch2: add Google Cloud Platform (GCP) fetcher".
Signed-off-by: Emil Ekmečić
---
meta/classes-global/sanity.bbclass | 3 ++-
meta/classes/own-mirrors.bbclass | 1 +
2 files changed, 3 insert
On Wed, Aug 2, 2023 at 9:15 AM Joel Stanley wrote:
>
> On Wed, 2 Aug 2023 at 12:45, Frédéric Martinsons
> wrote:
> >
> >
> >
> > On Wed, 2 Aug 2023 at 13:47, Joel Stanley wrote:
> >>
> >> The one liner tests using `[ ] && action` need to have || true after the
> >> action,
> >> otherwise the li
Hello,
This causes
sstatetests.SStateHashSameSigs3.test_sstate_sametune_samesigs to fail:
https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/5572/steps/14/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/5538/steps/14/logs/stdio
https://autobuilder.yocto
From: Alexis Lothoré
Add a STATUS_STRINGS dictionnary matching raw statuses to custom strings.
Whenever a regression must be reported, raw status is searched in the
custom statuses dict (key search is case insensitive). If no custom string
is found, raw status is kept and used in regression repor
From: Alexis Lothoré
Whenever a test result is present in base test result but absent from
target test results, we have an entry in regression report looking like the
following one:
ptestresult.apr.testfile: PASSED -> None
The "None" status may be a bit confusing, so replace it with a custo
From: Alexis Lothoré
Hello,
this very small series intend to eliminate confusion about regressions
reported by resulttool whenever a test result is present in "base test
result" but absent from "target test result". This scenario leads to many
"XXX -> None" lines. The series allows to define cust
include conf/bblock.conf. This file is generated by the bblock tool. It
locks some package tasks by fixing their signatures. See bblock -h for
more details
Signed-off-by: Julien Stephan
---
meta/conf/bitbake.conf | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/conf/bitbake.conf b/meta/c
adding a new command in cooker to compute and get task signatures
this commit also add the associated command and event needed to get the
signatures using tinfoil
Signed-off-by: Julien Stephan
---
bitbake/lib/bb/command.py | 6 ++
bitbake/lib/bb/cooker.py | 16
bitbake/li
as of now, SIGGEN_LOCKEDSIGS_TASKSIG_CHECK can take 2 values: "warn" and
"error", displaying respectively a warning or a fatal error message
only when a task is locked and the task signature is different from
the locked one.
The "info" level is introduced to add a "note" message to remind the
user
bblock script allows to lock/unlock recipes to latest task signatures.
The idea is to prevent some recipes to be rebuilt during development.
For example when working on rust recipe, one may not want rust-native to be
rebuilt.
This tool can be used, with proper environment set up, using the followi
it implements various combination of locking single/multiple recipe(s)/task(s)
it also tests that locked sig are architecture dependant
Signed-off-by: Julien Stephan
---
meta/lib/oeqa/selftest/cases/bblock.py | 146 +
1 file changed, 146 insertions(+)
create mode 100644
Hi all,
This is v4 for bblock script.
Improvement from v3:
* Add self test
* Add a new "info" level for SIGGEN_LOCKEDSIGS_TASKSIG_CHECK: this allows to
display a Note when recipe contains locked task(s)
Limitations:
* Silently does nothing if given task doesn't exist
* Silently does nothing wh
Le dim. 30 juil. 2023 à 00:44, Alexandre Belloni
a écrit :
>
> Hello,
>
> On 27/07/2023 15:56:09+0200, Julien Stephan wrote:
> > Hi all,
> >
> > This is v3 from bblock script.
> >
>
> This doesn't apply cleanly on master, can you rebase?
>
> Thanks!
Hi Alexandre,
done, just pushed v4 here:
https
On Wed, Aug 02, 2023 at 04:24:29PM +0200, Julien Stephan wrote:
> adding a new command in cooker to compute and get task signatures
>
> this commit also add the associated command and event needed to get the
> signatures using tinfoil
>
> Signed-off-by: Julien Stephan
> ---
> bitbake/lib/bb/comma
Le mer. 2 août 2023, 15:16, a écrit :
> From: Frederic Martinsons
>
> This patch series force the usage of --frozen instead of --offline during
> cargo build.
> This has the advantage to be sure that Cargo.lock file will not be
> modified.
> Moreover, raise a clear error when Cargo.lock is not p
44.6 - July 28, 2023
* Hide "Search the Web for" context menu item in web app mode (#2097, Cleo
Menezes Jr.)
* Fix Save Password? permission requests, broken since 44.4 (#2113)
* Fix unencoded % characters in URLs causing session to fail to save (#2128,
Vanadiae)
* Fix w
- Remove unneeded patches
What’s new in the WebKitGTK 2.40.5 release?
- Fix several crashes and rendering issues.
What’s new in the WebKitGTK 2.40.4 release?
- Fix a bug in JavaScript reading variable arguments in a call.
What’s new in the WebKitGTK 2.40.3 release?
- Make
On Wed, Aug 2, 2023 at 06:38 AM, Bruce Ashfield wrote:
>
> On Wed, Aug 2, 2023 at 9:15 AM Joel Stanley wrote:
>
>> On Wed, 2 Aug 2023 at 12:45, Frédéric Martinsons
>> wrote:
>>
>>>
>>>
>>> On Wed, 2 Aug 2023 at 13:47, Joel Stanley wrote:
>>>
The one liner tests using `[ ] && action`
I am trying to add support for the INITRAMFS_MAXSIZE into the meta-ti
layer for our tiny image.
I have added the following to our tiny image file:
INITRAMFS_FSTYPES += "cpio cpio.xz"
INITRAMFS_MAXSIZE = "65536"
But I'm not seeing any errors about the image being too big being printed.
In lo
Andrew Geissler escreveu no dia quarta, 2/08/2023
à(s) 17:08:
> On Wed, Aug 2, 2023 at 06:38 AM, Bruce Ashfield wrote:
>
> On Wed, Aug 2, 2023 at 9:15 AM Joel Stanley wrote:
>
> On Wed, 2 Aug 2023 at 12:45, Frédéric Martinsons
> wrote:
>
>
>
> On Wed, 2 Aug 2023 at 13:47, Joel Stanley wrote:
>
Luca
On Wed, Aug 2, 2023 at 1:12 AM Luca Bocassi wrote:
>
> On Mon, 31 Jul 2023 at 19:00, Luca Boccassi wrote:
> >
> > On Mon, 31 Jul 2023 at 18:37, Alexander Kanavin
> > wrote:
> > >
> > > A better option: fix the libpam recipe to say:
> > >
> > > ANY_OF_DISTRO_FEATURES = "pam systemd"
> > >
Image builds obey IMAGE_FSTYPES. Initramfs images set that to
INITRAMFS_FSTYPES, so it's comparing the two as a check to see if this is
an initramfs image. It isn't making sure it matches a hardcoded list, so
intersection isn't necessary.
On Wed, Aug 2, 2023 at 9:41 AM Ryan Eatmon via lists.openem
On Wed, 2 Aug 2023 at 18:14, Khem Raj wrote:
>
> Luca
>
> On Wed, Aug 2, 2023 at 1:12 AM Luca Bocassi wrote:
> >
> > On Mon, 31 Jul 2023 at 19:00, Luca Boccassi wrote:
> > >
> > > On Mon, 31 Jul 2023 at 18:37, Alexander Kanavin
> > > wrote:
> > > >
> > > > A better option: fix the libpam recip
There is already a patch for this CVE in kirkstone:
https://git.yoctoproject.org/poky/commit/?h=kirkstone&id=4596433a54c12ee229e923ae39e3ec0d16d6f067
So I've dropped this patch from your series and adjusted the other two
to take into account the above commit.
Thanks!
Steve
On Tue, Aug 1, 2023
On Wed, Aug 2, 2023 at 10:21 AM Luca Boccassi wrote:
>
> On Wed, 2 Aug 2023 at 18:14, Khem Raj wrote:
> >
> > Luca
> >
> > On Wed, Aug 2, 2023 at 1:12 AM Luca Bocassi wrote:
> > >
> > > On Mon, 31 Jul 2023 at 19:00, Luca Boccassi
> > > wrote:
> > > >
> > > > On Mon, 31 Jul 2023 at 18:37, Alexa
'Unneeded patches' is not a good phrase to use: it's better to say
explicitly that the patches have been merged into the new release (or
if there is some other reason they are not needed anymore). I had to
go to upstream repo and check that, but I shouldn't have to.
Alex
On Wed, 2 Aug 2023 at 17:
From: Narpat Mali
Certifi is a curated collection of Root Certificates for validating
the trustworthiness of SSL certificates while verifying the identity
of TLS hosts. Certifi prior to version 2023.07.22 recognizes "e-Tugra"
root certificates. e-Tugra's root certificates were subject to an
inves
Piping results through sed is masking failures that aren't
picked up by sed expressions.
One such failure probes the source tree, and so isn't
relevant for target testing, and can be disabled.
Signed-off-by: Alexander Kanavin
---
meta/recipes-support/curl/curl/disable-tests | 2 ++
meta/recipes
I added some debugging to print out the various variables on interest
and got this output:
DEBUG: image_fstypes= tar.xz wic.xz wic.bmap tar.xz.md5sum cpio cpio.xz
DEBUG: initramfs_fstypes=cpio.gz cpio cpio.xz
DEBUG: initramfs_maxsize=65536.00
DEBUG: base_size=74366
So I'm not sure I agree
On Mon, Jul 31, 2023 at 12:59 PM Khem Raj wrote:
>
> On Mon, Jul 31, 2023 at 10:48 AM Sundeep KOKKONDA via
> lists.openembedded.org
> wrote:
> >
> > Hello Khem,
> >
> > There are 393 New Test Cases added with this update (Refer the attachment).
> > Out of those,
> > 88 Failed cases: Mostly from
In looking at the poky tiny initramfs image, it sets:
IMAGE_FSTYPES = "${INITRAMFS_FSTYPES}"
Which would then make the two variable the same and make the check kick
in. But I cannot find where it manual says that you have to make them
the same value and cannot generate an initramfs image al
From: Luca Boccassi
- Drop dependency on gnu-efi, add dependency on pyelftools for EFI builds
- Refresh patches
- Ship new files and directories
- Use meson target to build sd-boot instead of filenames
- Change libpam recipe to set ANY_OF_DISTRO_FEATURES = "pam systemd" to let
logind pull in pa
On Wed, 2 Aug 2023 at 18:42, Khem Raj wrote:
>
> On Wed, Aug 2, 2023 at 10:21 AM Luca Boccassi wrote:
> >
> > On Wed, 2 Aug 2023 at 18:14, Khem Raj wrote:
> > >
> > > Luca
> > >
> > > On Wed, Aug 2, 2023 at 1:12 AM Luca Bocassi
> > > wrote:
> > > >
> > > > On Mon, 31 Jul 2023 at 19:00, Luca Bo
On 8/2/23 11:54 AM, luca.bocca...@gmail.com wrote:
From: Luca Boccassi
- Drop dependency on gnu-efi, add dependency on pyelftools for EFI builds
- Refresh patches
- Ship new files and directories
- Use meson target to build sd-boot instead of filenames
- Change libpam recipe to set ANY_OF_DISTR
Some clues please. What does this error mean? How to solve it?
2023. 08. 02. 15:41 keltezéssel, Alexandre Belloni írta:
Hello,
This causes
sstatetests.SStateHashSameSigs3.test_sstate_sametune_samesigs to fail:
https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/5572/steps/14/logs
I think the culprit is the usage of MACHINE_ARCH. You can't have that
in regular recipes, as that makes them machine-specific, rather than
tune (i.e. architecture) specific.
Alex
On Wed, 2 Aug 2023 at 21:28, Böszörményi Zoltán wrote:
>
> Some clues please. What does this error mean? How to solve
From: Benjamin Bara
A build with vfpv3d16 (armv7at2hf-vfpv3d16) tune currently warns:
'+d16' is not a recognized feature for this target (ignoring feature)
This correlates with the supported target_features for arm[1].
With the now enabled features, rustc might use vdiv.f64 with register
d17, w
Currently, the only way to build a feed natively in OE is to build all
the desired packages and then manually run bitbake package-index. This
approach has a few drawbacks:
- The index creation methods ONLY work on the package deploy directory.
If there are packages that are not meant to be in the f
This change adds a new variable that defines where
feeds should be created when building a packagefeed.
A feed location for each package type is also added
to allow multiple package type feeds to be created
in parallel.
The location for feeds is ${DEPLOY_DIR}/feeds/ and
each package type will furt
Currently, the generate_index_files function only handles
the creation of index files in the DEPLOY_DIR_
directories. This change adds an optional isFeed input
that will instead point the index generation at a package
specific feed directory. If no feedname is specified,
the original behavior persi
To make the logic from create_feed_dir reusable, this
change splits the logic used to traverse the package
dependencies into a helper function.
Additionally, the logic used to find the initial task was
updated.
Signed-off-by: Charlie Johnston
---
meta/lib/oe/package_manager/__init__.py | 51 +++
Add a generate_feed_dirs method that will call the
create_packages_dir method for each package class supported
in the build environment. The value of the PACKAGE_CLASSES
determines which feed types are built. For each package
type, the new method will determine the proper name for the
package_write
Add a new bbclass that allows building a feed using the
new oe.package_manager class. Additionally, there are
packagefeed_ bbclasses to define package type
specific configurations.
The do_packagefeed task currently does no use SSTATE
data and is set to always run via [nostamp] = "1".
The variable
Since the packagefeed build logic does not use sstate,
the deploy directories will not be cleaned by a do_clean
or similar commands. This change adds a function to wipe
all feed deploy directories for the given feed when a
clean command is run. That is, regardless of the value
of PACKAGE_CLASSES, a
Yes, I checked that as well. I'm sorry I didn't comment in more detail.
On Wed, Aug 2 2023 at 07:42:53 PM +02:00:00, Alexander Kanavin
wrote:
'Unneeded patches' is not a good phrase to use: it's better to say
explicitly that the patches have been merged into the new release (or
if there is som
From: Luca Boccassi
- Drop dependency on gnu-efi, add dependency on pyelftools for EFI builds
- Refresh patches
- Ship new files and directories
- Use meson target to build sd-boot instead of filenames
- Change libpam recipe to set ANY_OF_DISTRO_FEATURES = "pam systemd" to let
logind pull in pa
On Wed, 2 Aug 2023 at 20:27, Khem Raj wrote:
>
> On 8/2/23 11:54 AM, luca.bocca...@gmail.com wrote:
> > From: Luca Boccassi
> >
> > - Drop dependency on gnu-efi, add dependency on pyelftools for EFI builds
> > - Refresh patches
> > - Ship new files and directories
> > - Use meson target to build
From: Joe Slater
Use QB_LOG_FILE to log to a file, and QB_LOG_LEVEL
to set the base log level. Example values -
QB_LOG_FILE="runq.log"
QB_LOG_LEVEL=DEBUG
Signed-off-by: Joe Slater
---
scripts/runqemu | 16
1 file changed, 12 insertions(+), 4 deletions(-)
diff --git a/script
On 2023-08-02 19:36, joe.sla...@windriver.com wrote:
From: Joe Slater
Use QB_LOG_FILE to log to a file, and QB_LOG_LEVEL
to set the base log level. Example values -
QB_LOG_FILE="runq.log"
QB_LOG_LEVEL=DEBUG
Signed-off-by: Joe Slater
---
scripts/runqemu | 16
1 file changed
meta/classes-recipe/npm.bbclass:85: DeprecationWarning: invalid escape sequence
'\.'
'--transform', 's,^\./,package/,',
Signed-off-by: Martin Jansa
Signed-off-by: Richard Purdie
---
meta/classes/npm.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/npm.
I think this recipe should simply be upgraded instead ...
Thanks,
Anuj
On Wed, 2023-08-02 at 17:57 +, Narpat Mali via
lists.openembedded.org wrote:
> From: Narpat Mali
>
> Certifi is a curated collection of Root Certificates for validating
> the trustworthiness of SSL certificates while ve
Hi Steve,
On 6/27/23 14:32, Siddharth wrote:
From: Siddharth Doshi
- Remove configure options no longer supported online.
Changelog:
=
[security] A query that prioritizes stale data over lookup
triggers a fetch to refresh the stale data in cache.
When ' include conf/bblock.conf' line can be more flexibly added to/removed
from local.conf, is there some specific reason why we should put it in
bitbake.conf by default?
Regards,
Qi
-Original Message-
From: openembedded-core@lists.openembedded.org
On Behalf Of Julien Stephan
Sent: W
On Wed, Aug 2, 2023 at 12:24 AM Alexander Kanavin
wrote:
> This can happen if running unpack task produces unrelated files and
> directories
> (e.g. if recipe_qa or other tasks run); in this case it's better to stop,
> rather
> than allow devtool to continue and error out much later with a messag
On Wed, Aug 2, 2023 at 12:24 AM Alexander Kanavin
wrote:
> With newly added recipe_qa task, the function needs to filter out its
> output as well.
>
> The issue wouldn't appear in selftest because it's triggered by
> buildhistory and
> selftest disables that.
>
> Signed-off-by: Alexander Kanavin
with newer systemd, if not specified, these paths are searched on build
host /usr dir
log.do_configure.2373278:Program /usr/sbin/loadkeys found: YES
(/usr/sbin/loadkeys)
log.do_configure.2373278:Program /usr/sbin/setfont found: YES
(/usr/sbin/setfont)
and if build host happens to have kbd insta
On 8/2/23 16:32, Alexander Kanavin wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
On Wed, 2 Aug 2023 at 10:30, Yu, Mingli wrote:
Did a simple check against core-image-
Signed-off-by: Khem Raj
---
...ake-malloc_trim-conditional-on-glibc.patch | 39 +++
...hared-Do-not-use-malloc_info-on-musl.patch | 50 +++
meta/recipes-core/systemd/systemd_254.bb | 2 +
3 files changed, 91 insertions(+)
create mode 100644
meta/recipes-core/sy
On 03-08-2023 07:43, Mittal, Anuj wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
I think this recipe should simply be upgraded instead ...
The current version python3-ce
2023. 08. 02. 21:54 keltezéssel, Alexander Kanavin írta:
I think the culprit is the usage of MACHINE_ARCH. You can't have that
in regular recipes, as that makes them machine-specific, rather than
tune (i.e. architecture) specific.
So, how to fix it?
Would putting this into the rpm recipe be en
Signed-off-by: Sudip Mukherjee
---
.../libgit2/{libgit2_1.6.4.bb => libgit2_1.7.0.bb}| 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-support/libgit2/{libgit2_1.6.4.bb => libgit2_1.7.0.bb}
(89%)
diff --git a/meta/recipes-support/libgit2/libgit2_1.6.4.bb
I have an unsolved mystery here.
If I build an image with "debug-tweaks" in [EXTRA_]IMAGE_FEATURES, I get a
normal image, where logging in as root works as expected.
If i replace "debug-tweaks" with other options, for example one of these:
EXTRA_IMAGE_FEATURES = "empty-root-password allow-empt
79 matches
Mail list logo