| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Two tests to cover both installing package with IMAGE_INSTALL as
well as installing versioned dependencies of the package (using perl (>=
5.XX).
Related: [Yocto #13338] [Yocto #14995] [Yocto #14066]
Signed-off-by: Pavel Zhukov <pavel@zhukoff.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Some of the packages require versioned providers
(DEPENDS: perl (>= 5.38) is an example and for such packages
do_populate_sdk fails because dummy packages provided unversioned
packages (PROVIDES: perl) which doesn't meet the version requirement.
Specify 999.9-r9 version for such provides to work this around
Fixes [Yocto #14995]
Signed-off-by: Pavel Zhukov <pavel@zhukoff.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
dpkg and apt seem to handle versioned provides correctly now [1] so this
workaround is not needed anymore.
This fixes [Yocto #14995] for package_deb.
[1] https://www.debian.org/doc/debian-policy/ch-relationships.html#virtual-packages-provides
Signed-off-by: Pavel Zhukov <pavel@zhukoff.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
if packages is provided by dummysdk and in the same time marked for
installation with IMAGE_INSTALL it causes conflict in apt because virtual providers are
not taken into account if package is asked to be installed explicitly.
Filter such packages from provides/conflicts to workaround this problem.
This workaround brakes RPM usecase because of file conlicts with
DUMMYPROVIDES, use DUMMYPROVIDES_PACKAGES_MULTILIB instead (which
doesn't include file based conflicts).
While this is needed for the case of package_deb only adding it for all
package managers to not complicate the code.
Fixes: [Yocto #13338] [Yocto #14066]
Fixes:
The following information may help to resolve the situation:
The following packages have unmet dependencies:
target-sdk-provides-dummy : Conflicts: bash
E: Unable to correct problems, you have held broken packages.
Signed-off-by: Pavel Zhukov <pavel@zhukoff.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This reverts commit a25654ee14cc4dd0685ccc722b61bbfd7559b273.
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Currently DEPLOY_DIR/licenses is added to SSTATE_ALLOW_OVERLAP_FILES. This
leads to bugs since when one MACHINE_ARCH recipes is cleaned, it removes the
files for another which then results in later build failures as license files
disappear.
The solution is to include SSTAGE_PKGARCH in the path names to the license files.
That does mean a search has to be used to find the correct license files for a
given PN but that can be done via SSTATE_ARCHS.
The implication for other tools is the layout has changed so tools will need to
adapt to the new paths. The benefit is no more strange build failures such as from
patterns like:
MACHINE=qemux86-64 bitbake core-image-minimal
MACHINE=genericx86-64 bitbake core-image-minimal
MACHINE=qemux86-64 bitbake linux-yocto -c clean
MACHINE=genericx86-64 bitbake core-image-minimal -C rootfs
[YOCTO #14123]
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This reverts commit cd265a1a1f00fdf3274f5a910bb0b86d05d1b378.
|
|
This reverts commit e2e378a8a0fd295823947361d8db1c0e9cc69976.
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This reverts commit ca978ad2fef6f095bd55e53485382bba769307aa.
|
|
This reverts commit 9ad844ef767880bf80a4683bbb38456cebae4bcb.
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Prefer the new function run_serial_socket. Change calls where the modification
is easy.
(From OE-Core rev: 0f1fc49f44db5e867ae831c74602ed2d55184942)
Signed-off-by: Louis Rannou <lrannou@baylibre.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(Bitbake rev: 9415c62852583746a7b96afca19e17b93747e0a9)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(Bitbake rev: 6a168415436ced39268eb569cb4e047a61091d83)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
kernel.bbclass
Writing a simple recipe that inherits kernel.bbclass and downloads a kernel
tarball (e.g. a mainline release from kernel.org) via http or ftp fails
with either:
ERROR: linux-acme-6.3.3-r0 do_configure: oe_runmake failed
...
| make: *** No rule to make target 'oldnoconfig'. Stop.
or (seen on a different setup, based on kirkstone):
... do_populate_lic: QA Issue: ... LIC_FILES_CHKSUM points to an invalid file: .../work-shared/.../kernel-source/COPYING [license-checksum]
This happens when not setting S in the recipe. In this case, kernel.bbclass
sets it to ${STAGING_KERNEL_DIR}
(${TMPDIR}/work-shared/${MACHINE}/kernel-source). This means that in
do_symlink_kernsrc(), the 'if s != kernsrc' never triggers and thus the
kernel tree will not me moved into work/shared, which results in an empty
work-shared/.../kernel-source directory.
When downloading a tarball it is usually not required to set S in recipes,
so this is not obvious here and the error message does not point to the
problem or its solution.
There is such a check in kernel-yocto.bbclass though, so move it to
kernel.bbclass so that also kernel recipes not based on kernel-yocto can
benefit from it.
The check is moved:
- from the beginning of do_kernel_checkout() in kernel-yocto
- to the end of do_symlink_kernsrc() in kernel.bbclass
and since do_kernel_checkout is executed 'after do_symlink_kernsrc', the
code flow does not change in a relevant way when using linux-yocto.
(From OE-Core rev: 8b5a8924204287737f47c660efe9ea7a89313d57)
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
testimage.bbclass requires that ssh communication with target works
and then it runs oeqa runtime tests with that. Tests like df.py
check that there is more than 5Mb free space on the rootfs on target. Sadly
latest core-image-minimal only has 1.5 Mb free space if
ssh-server-dropbear is added to it. Thus by default, core-image-minimal
is now failing oeqa rutime df.py test.
Fix this by increasing core-image-minimal rootfs size by 5Mb if
testimage.bbclass is used which implies adding either
ssh-server-dropbear or ssh-server-openssh to the target rootfs.
(From OE-Core rev: 0210c1314a066c807dd5876c091cdc8dd04d2fda)
Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This patch fixes warnings when useradd-staticids.bbclass is used and
USERADD_PARAM is used to add the user to a group that has not been
explicitly created yet. By adding the GROUPADD_PARAM for the new group
being used the warnings for changing the gid from GID-OLD to GID-NEW
is eliminated.
Warning fixed:
ppp-dialin: Changing groupname nogroup's gid from (WXYZ) to (JKLM), verify configuration files!
(From OE-Core rev: e0713aace14b1a2600ea1ad4c72e5e0aa962b639)
Signed-off-by: JD Schroeder <sweng5080@gmail.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This reverts commit 373b92d12788c2d2f6f50f17f80ded7f94b2c556.
test_fetch_file_mirror_of_mirror (bb.tests.fetch.FetcherNetworkTest.test_fetch_file_mirror_of_mirror)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/media/build/poky/bitbake/lib/bb/tests/fetch.py", line 959, in test_fetch_file_mirror_of_mirror
self.assertEqual(os.path.getsize(self.dldir + "/bitbake-1.0.tar.gz"), 57749)
AssertionError: 7061 != 57749
test_urireplace (bb.tests.fetch.MirrorUriTest)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/pokybuild/yocto-worker/oe-selftest-armhost/build/bitbake/lib/bb/tests/fetch.py", line 500, in test_urireplace
self.assertEqual([v], newuris)
AssertionError: Lists differ: ['file:///somewhere/1234/sstate-cache/sstate-xyz.tgz'] != ['file:///somewhere/1234/sstate-cache']
First differing element 0:
'file:///somewhere/1234/sstate-cache/sstate-xyz.tgz'
'file:///somewhere/1234/sstate-cache'
- ['file:///somewhere/1234/sstate-cache/sstate-xyz.tgz']
? ---------------
+ ['file:///somewhere/1234/sstate-cache']
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(Bitbake rev: 66158b0282bd65a32c0ded1d6d09d5f0ef3606ad)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: e8ef97254393bd8d100b5169d513ecd883b4788c)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
We've needed a way to queue/note/sync docs changes with our manuals, migration
guides and release notes. Add a file which we can use to "stage" information.
We can then ask users submitting changes which need docs changes to add
information here. This will then make it easier for the docs to be brought
into sync as we'll have a much better idea of when something merged and
what changes are needed.
(From OE-Core rev: 560714209a5a1df1d93881b675a80e4202fa03ce)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From OE-Core rev: 312a6a4f0a586f5e4c85bd59c34667e4928b6869)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
[YOCTO #15061]
Rust multilib sdks broken because of the conflicts between attempted installs of rust-cross-canadian for arm and aarch64.
Arm and aarch64 target architectures are trying to install cargo.sh and rust.sh in the same path which resulted in the issue.
The current patch modifies CARGO_ENV_SETUP_SH and RUST_ENV_SETUP_SH macros based on the architecture.
Hence, creates different file names for the environment setup scripts and resolves the issue.
(From OE-Core rev: 97f0272681be5c20182d2e2115d4dfa7da456168)
Signed-off-by: Deepthi Hemraj <Deepthi.Hemraj@windriver.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
- Add the recipe to the RM_WORK_EXCLUDE
With rm_work active, external module signing throws an error:
scripts/sign-file: error while loading shared libraries: libcrypto.so.3: can not open shared object file: No such file or directory
Preserve libraries that sign-file script needs during runtime.
Some solutions [1][2] for this problem have already been submitted
on the mailing list but none of them get merged:
[1] Fix using RM_WORK_EXCLUDE_ITEMS
https://lists.openembedded.org/g/openembedded-core/message/180113
[2] Fix using static linking
https://lists.openembedded.org/g/openembedded-core/message/182024
(From OE-Core rev: 2a3decb71286773814b26fa56deba2321939ff04)
Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Drop CFLAGS (containing host paths) from installed pkg-config file.
(From OE-Core rev: 6ef8aca5587161ac63cbf6a04386792f0121884f)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From meta-yocto rev: edbcdba22a33502c1c5e899d76637a0713212503)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This reverts commit 3777470e2ba418bac68e114311fbaeae08c42cee.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This reverts commit e1f59a805bc9e82495a249270375b4338f02204d.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This tests for 13904, that postinst-useradd-* run in order.
(From OE-Core rev: 7fd42fa233e471cb98cb1b3f6d1204845f3cfe8c)
Signed-off-by: Eilís 'pidge' Ní Fhlannagáin <pidge@baylibre.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This reverts commit fd9261726b19bbdd6e7709f7d1ae2dc4a2dfa59b.
(From OE-Core rev: c8cb0636909de594ce460c47940e91a0ebea8c48)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
If you build openssh, bump the version of base-passwd, then rerun openssh:do_create_spdx,
it will fail due to references to the old version of base-passwd. This is due to
base-passwd being listed in SIGGEN_EXCLUDERECIPES_ABISAFE.
Ignore these recipes for the purposes of create_spdx and force rebuilds when things change.
(From OE-Core rev: 5d7098077b177208a064b3edfbe680ca78408fbb)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Document the tribal knowledge that we have to disable ptests for gplv3.
Also document the workaround for update-alternatives issues with bash
and opkg-utils.
As with anything in this file, the exclusions come at a cost.
(From OE-Core rev: 9553861ba13effe72d0dbec71b11e416115b2556)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This reverts commit 8c26b2a7ca4556457e6f5d3483f005d57d1003d8.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
These entries, usually in layer.conf are part of an old, pre-layers
part of bitbake for overlay/collection support. This is not really
used any more and was replaced by the idea of layers.
In a recent discussion, we asked the question "When do you need to
use proprities?" and the answer was "almost never" given all the other
tools and techniques now available in layers.
These layer priorities cause users huge amounts of confusion. It is
unclear to people how the "magic values" work if it is unset
and if they are set differently, users don't expect the way it
actually works and the effects it has between layers.
In discussions I've had, there has been surprisingly strong support
for removing them entirely, even if that does means we'd need to fix
some corner cases.
I wholly agree and support that idea, so lets remove the support
and take a simplification where we can. The functionality had a
time and place but it has passed and we've moved on.
Developers are about to need to change layer.conf to update the
series compatibility for the next release so it is a good time to
do it.
This patch removes the core support and replaces it with a warning.
It does not chase down every last reference or function parmeter,
that can follow as time allows.
(Bitbake rev: af2e1c6d7f453f82b2c3db964831edc6104e3fe1)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
set the package-database of a "lower image" to unpack and build upon when
installing packages for the current image. This way a lean image will be
created, which only holds the packages that are not already present in the lower
image, that then could be used with overlayfs or systemd-sysext to extend the
"lower image" on demand; for development purposes on an RO lower image for
example.
(From OE-Core rev: a867c4363562ac328618e2ea0070ee6cf5af0ec2)
Signed-off-by: Johannes Schneider <johannes.schneider@leica-geosystems.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
systemd-sysext can load a raw-image containing usr/ and opt/ folders
to mount them as RO overlay over the rootfs, to "extend" the systems.
This class provides the necessary changes/additions to the enclosed
file-system so that systemd-sysext accepts the extension for "merge"
into the rootfs.
With such an created image, placed into the correct folder (see [1]),
`systemd-sysext list` should be able to list the "extension" and
`systemd-sysext merge` should enable the overlay. On both commands a
preceding "SYSTEMD_LOG_LEVEL=debug" can aide in figuring out what is
amiss.
The strict name checking systemd-sysext does against the name of
extension-release.NAME file, is disabled, as there is only one such in
the resulting image. This is done to allow a user to freely rename the
resulting image file.
Note that for e.g. squashfs, the kernel needs CONFIG_SQUASHFS_XATTR=y
Link: https://www.freedesktop.org/software/systemd/man/latest/systemd-sysext.html
Link: https://0pointer.net/blog/testing-my-system-code-in-usr-without-modifying-usr.html
(From OE-Core rev: 516497879379d20ec8db85c158dc557d05b92958)
Signed-off-by: Johannes Schneider <johannes.schneider@leica-geosystems.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
Richard Purdie
Pavel Zhukov
Louis Rannou
Luca Ceresoli
Mikko Rapeli
JD Schroeder
Deepthi Hemraj
Jose Quaresma
Alexander Kanavin
Eilís 'pidge' Ní Fhlannagáin
Johannes Schneider