er to follow :)
Do you know if yocto-patches@ will be available via lore.kernel.org?
Thanks,
--
Paul Barker
OpenPGP_0x27F4B3459F002257.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all message
The check_oldest_kernel() function requires utsrelease.h to be
generated. This file is generated during do_compile, so we need to delay
calling check_oldest_kernel() until after this.
With this change in place, I now see the expected warning when building
Linux 5.10.y.
Signed-off-by: Paul Barker
robably create a specific MACHINE anyway.
If we take the other approach of building up the kernel config from
fragments, how would we know that all SystemReady IR capable systems
will be supported? Yocto Project doesn't have the resources to test
every platform.
For the Renesas RZ SoCs I wo
On Tue, Nov 07, 2023 at 10:52:53AM -0500, Neal Caidin wrote:
>The Yocto Project website has had a refresh (www.yoctoproject.org)
The new website looks great!
Just a quick note - the links at the bottom of the page are mostly going
to https://yocto.dev-lfprojects3.linuxfoundation.org/.
E.g.
: 2e669bf797b15d803e7d6a700e449bdc467a4bcc)
Signed-off-by: Ryan Eatmon
Signed-off-by: Richard Purdie
Signed-off-by: Alexander Sverdlin
Signed-off-by: Steve Sakoman
Backported from kirkstone commit 7e177848f97e.
Signed-off-by: Paul Barker
---
Re-sending this for the mailing list. My first send was dropped as I
wasn't
and newer releases.
Signed-off-by: Paul Barker
---
meta/conf/licenses.conf | 7 +++
1 file changed, 7 insertions(+)
diff --git a/meta/conf/licenses.conf b/meta/conf/licenses.conf
index 5b309eb3851f..0149b1dc4445 100644
--- a/meta/conf/licenses.conf
+++ b/meta/conf/licenses.conf
@@ -13,24 +13,31
On 11/08/2022 08:59, Richard Purdie wrote:
On Thu, 2022-08-11 at 08:57 +0100, Paul Barker wrote:
On 10/08/2022 20:45, Richard Purdie wrote:
diff --git a/meta/lib/oeqa/runtime/cases/rtc.py
b/meta/lib/oeqa/runtime/cases/rtc.py
index c4e66813249..223cf7b95d9 100644
--- a/meta/lib/oeqa/runtime
'\' has slipped in here.
Thanks,
--
Paul Barker
OpenPGP_0x74975C81B7E66BAC.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#169233):
https
On 14/01/2022 13:21, Paul Barker wrote:
From: Bruce Ashfield
The 5.16 kernel introduced mandatory schema checking on any dtb file
built through the kernel.
That funcionality is provided via python3-dt-schema.
The dependencies to enable that functionality is not small, and may
not always
guage wiki page.
https://wiki.yoctoproject.org/wiki/Inclusive_language
Thanks
Special thanks to Richard Purdie, Michael Opdenacker. Marta
Rybczynska, Scott Murray, Jan-Simon Moeller, Saul Wold, and Armin
Kuster for providing their time, technical details, text, and feedback
on this task.
Thanks all, it's g
't think any changes are needed in oe-core, the info is now here in
case it affects others though.
Thanks,
--
Paul Barker
Principal Software Engineer
SanCloud Ltd
e: paul.bar...@sancloud.com
w: https://sancloud.co.uk/
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this gro
-by: Bruce Ashfield
Signed-off-by: Richard Purdie
Backported from oe-core commit 2566563ad49d.
Signed-off-by: Paul Barker
---
meta/conf/distro/include/maintainers.inc | 1 +
.../python3-dtschema-wrapper/dt-doc-validate | 20 +++
.../dtc/python3-dtschema-wrapper/dt-mk-schema
-by: Bruce Ashfield
Signed-off-by: Richard Purdie
Backported from oe-core commit 2566563ad49d.
Signed-off-by: Paul Barker
---
meta/conf/distro/include/maintainers.inc | 1 +
.../python3-dtschema-wrapper/dt-doc-validate | 20 +++
.../dtc/python3-dtschema-wrapper/dt-mk-schema
Hi all,
I'm unable to take the lead on organising a virtual stand for
OpenEmbedded at FOSDEM 2022. I'm forwarding this mail to the lists to
see if anyone else would like to take over - you'll need to review how
the virtual stands work, update the website content as detailed below
and be
On 20/12/2021 22:34, Richard Purdie wrote:
On Mon, 2021-12-20 at 17:01 +, Paul Barker wrote:
On 17/12/2021 15:36, Matt Madison wrote:
This patch series switches to using the OE_IMPORTS mechanism
for installing the crate fetcher. This simplifies the addition
and clears up issues
meta/lib/crate.py | 2 ++
4 files changed, 3 insertions(+), 31 deletions(-)
delete mode 100644 meta/classes/crate-fetch.bbclass
Would a better solution here be to move the crate fetcher into
lib/bb/fetch2/ in bitbake?
--
Paul Barker
Principal Software
python3-dtschema-wrapper seems like the way to go, either into a very
small mixin layer or into oe-core.
Thanks,
--
Paul Barker
e: p...@pbarker.dev
w: https://pbarker.dev/
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#159286):
https
Hi Anuj,
Please could you consider backporting the following commit to hardknott:
af2a9c92d449 ("kernel-yocto: Simplify no git repo case in do_kernel_checkout")
This has already been backport to dunfell. The patch cherry-picks
cleanly to hardknott.
Thanks,
--
Paul Ba
mcopy_cmd = "mcopy -i %s %s ::/etc/fstab" % (rootfs,
> self.updated_fstab_path)
> exec_native_cmd(mcopy_cmd, native_sysroot)
>
This looks like the right approach. However, you're still missing the
handling for filesystems other than ext2/3/4 & msdos. See
http://gi
is
introduced. By default this is set to the expected archive name based on
the PyPI package name, version and extension but it can be set to a
different value if needed in a recipe which inherits the pypi class.
Signed-off-by: Paul Barker
---
meta/classes/pypi.bbclass | 6 +++---
1 file changed, 3
in the rootfs.
Signed-off-by: Paul Barker
---
meta/recipes-bsp/u-boot/u-boot.inc | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-bsp/u-boot/u-boot.inc
b/meta/recipes-bsp/u-boot/u-boot.inc
index 4340b17cb6..971fdbb102 100644
--- a/meta/recipes-bsp/u-boot/u-boot.inc
end changing the option in ksparser to '--no-fstab-update'
to match the argument you can pass to wic itself. That way you can pass
'--no-fstab-update' to wic to set the option for all partitions, or
include it in the wks file to set the option per-partition.
Thanks,
--
Paul Barker
https://pbarke
.
This also removes the assumption that the default git branch name will
be "master". Prior to this change, the final git checkout command in
do_kernel_checkout could fail if a local git repo was created and the
user had changed init.defaultBranch in their gitconfig.
Signed-off-by: P
of the mainline commit hash we want to use
for linux-yocto-upstream.
Signed-off-by: Paul Barker
---
meta/recipes-kernel/linux/linux-yocto_5.13.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.13.bb
b/meta/recipes-kernel/linux/linux
follow newer kernel releases
as they're added to linux-yocto recipes by setting the preferred version
to 'upstream%' (or maybe 'upstream+%' to be more restrictive). That
would then avoid the build breaking when the 5.13 recipe disappears and
is replaced by 5.14 or something else later.
Thanks,
On Tue, 29 Jun 2021 at 17:19, Persian Prince wrote:
>
> @Paul Barker
>
> I spent days and nights for testing the outcome of my PEP8.sh script and I
> used it on more than 100 repos to check the results, what you see now is the
> result of that.
>
> People at https:/
on to the
specifics of openembedded-core/bitbake. In my opinion that approach is
a waste of maintainer's time.
--
Paul Barker
Konsulko Group
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#153432):
https://lists.openembedded.org/g/openembedded-core/
The new prserv connect() function decouples the code in oe-core from the
exact classes and implementation details used within bitbake. This
allows us to more easily switch over to a new asyncrpc based prservice.
Signed-off-by: Paul Barker
---
meta/lib/oe/prservice.py | 2 +-
1 file changed, 1
aming to self
>
> Martin Jansa (2):
> base.bbclass: use os.path.normpath instead of just comparing WORKDIR
> and S as strings
> license.bbclass: Add COMMON_LICENSE_DIR and LICENSE_PATH dirs to
> PSEUDO_IGNORE_PATHS
>
> Mingli Yu (2):
> tcl: adapt to potentia
On Mon, 25 Jan 2021 at 16:25, Steve Sakoman wrote:
>
> On Mon, Jan 25, 2021 at 5:42 AM Paul Barker wrote:
> >
> > On Mon, 25 Jan 2021 at 14:51, Steve Sakoman wrote:
> > >
> > > Issues with undetected file mode corruption in pseudo have been
> > > i
pseudo changes.
If this is just brought in to allow clean cherry-picks I think it
would be better left out and instead do the small bit of rebasing
required in the patches. We don't know what downstream users are doing
with TERM so minimising unnecessary changes in the stable b
On Thu, 14 Jan 2021 at 11:02, Robert ber...@yocto.user
wrote:
>
> Hi,
>
> On 13/01/2021 23:33, Paul Barker wrote:
> > Hi folks,
> >
> > * Any participants in the project who want to help host the Matrix
> > chat room between 09:00 and 18:00 each day of the
in the partition image.
Signed-off-by: Paul Barker
---
scripts/lib/wic/partition.py | 27 +++-
scripts/lib/wic/plugins/source/rootfs.py | 9 +---
2 files changed, 28 insertions(+), 8 deletions(-)
diff --git a/scripts/lib/wic/partition.py b/scripts/lib/wic
content). We can also follow up with further
optimisations after this commit. So this second solution is chosen.
Fixes [Yocto #13994]
Signed-off-by: Paul Barker
---
scripts/lib/wic/partition.py | 5 +++-
scripts/lib/wic/plugins/imager/direct.py | 36
scripts/lib
iles &
directories from the copied rootfs to ensure that the copied pseudo db
is updated.
Signed-off-by: Paul Barker
---
scripts/lib/wic/plugins/source/rootfs.py | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/scripts/lib/wic/plugins/source/rootfs.py
b/scripts
see the
'tmp-wic' directory under WORKDIR.
Fixes [Yocto #14129]
Signed-off-by: Paul Barker
---
meta/classes/image_types_wic.bbclass | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/meta/classes/image_types_wic.bbclass
b/meta/classes/image_types_wic.bbclass
index
If a path is specified for the internal wic working directory using
the -w/--workdir argument then it must not already exist. Re-using a
previous workdir could easily result in rootfs and intermediate files
from a previous build being added to the current image.
Signed-off-by: Paul Barker
ec] = "1"
Have you tested whether the archiver class is still working after this
change? If not it'd be helpful to run `oe-selftest -r archiver` to
check.
--
Paul Barker
Konsulko Group
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#146993):
ht
deletions(-)
>
> --
> 2.17.1
I think the `[meta-oe]` tag in the email subject is wrong here. You
don't need to resend the patch though as that isn't included in the
commit message. This is just a note for next time.
Thanks,
--
Paul Barker
Konsulko Group
-=-=-=-=-=-=-=-=-=-=-=-
ux86 bootparams="psplash=false"
>runqemu path/to/-.wic
>runqemu path/to/-.wic.vmdk
> + runqemu path/to/-.wic.vhdx
> + runqemu path/to/-.wic.vhd
> """)
>
> def check_tun():
> @@ -179,7 +181,7 @@ class BaseConfig(object):
> self.
oad videos is expected in the near future but for now it would be
good to just collect folks who are interested so we can discuss this
further.
If you're interested in any of the above please reply to me and/or the
list. I look forward to virtually seeing many of you at FOSDEM 2021!
Thanks,
--
Paul
when do_image_wic finishes, the path to
`tmp-wic` should no longer be present in the pseudo db. The error seen
here may be due to a race condition but the underlying question of
whether `tmp-wic` is removed outside a pseudo context (leaving the
path in the db) should hopefully be dete
On Mon, 11 Jan 2021 at 14:22, Paul Barker wrote:
>
> On Mon, 11 Jan 2021 at 14:17, Lee, Chee Yang wrote:
> >
> > You might want to update scripts/lib/wic/help.py with description for this
> > new features too
>
> /me looks at help.py
>
> That is really
d-written duplicate
information.
--
Paul Barker
Konsulko Group
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#146593):
https://lists.openembedded.org/g/openembedded-core/message/146593
Mute This Topic: https://lists.openembedded.org/mt/79592782/21
On Mon, 11 Jan 2021 at 12:19, Milan Shah wrote:
>
> Hi All,
>
> This is a gentle reminder to review this patch.
Looks like this is also in master already:
https://git.openembedded.org/openembedded-core/commit/?id=6b4e2eafa6eb71ca94ccc8a18d05b473b352367c
--
Paul Barker
Ko
On Mon, 11 Jan 2021 at 10:37, Alexander Kanavin wrote:
>
> Oh right nevermind - it's an optimization, not an actual fix which is
> elsewhere.
Yes, for other fstypes we just fallback on copying the rootfs
directory (using hardlinks if possible).
--
Paul Barker
Konsu
On Mon, 11 Jan 2021 at 00:46, Steve Sakoman wrote:
>
> From: Paul Barker
>
> The oe-selftest code already keeps the selftest build directory in place
> if any tests failed. By default the build directory is deleted if all
> tests pass but there may be cases where it's
in the partition image.
Signed-off-by: Paul Barker
---
scripts/lib/wic/partition.py | 27 +++-
scripts/lib/wic/plugins/source/rootfs.py | 9 +---
2 files changed, 28 insertions(+), 8 deletions(-)
diff --git a/scripts/lib/wic/partition.py b/scripts/lib/wic
content). We can also follow up with further
optimisations after this commit. So this second solution is chosen.
Fixes [Yocto #13994]
Signed-off-by: Paul Barker
---
scripts/lib/wic/partition.py | 5 +++-
scripts/lib/wic/plugins/imager/direct.py | 36
scripts/lib
This allows programs from HOSTTOOLS (e.g. 'install', 'rm', 'mv', etc) to
be more easily executed by wic. Without this change only programs from
an actual *-native recipe built by bitbake can be executed by wic.
Signed-off-by: Paul Barker
---
meta/classes/image_types_wic.bbclass | 2 +-
scripts
iles &
directories from the copied rootfs to ensure that the copied pseudo db
is updated.
Signed-off-by: Paul Barker
---
scripts/lib/wic/plugins/source/rootfs.py | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/scripts/lib/wic/plugins/source/rootfs.py
b/scripts
This allows the path for the temporary workdir used by wic to be set
when running wic from bitbake or directly from the command line.
Signed-off-by: Paul Barker
---
scripts/lib/wic/plugins/imager/direct.py | 2 +-
scripts/wic | 2 ++
2 files changed, 3 insertions
see the
'tmp-wic' directory under WORKDIR.
Fixes [Yocto #14129]
Signed-off-by: Paul Barker
---
meta/classes/image_types_wic.bbclass | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/meta/classes/image_types_wic.bbclass
b/meta/classes/image_types_wic.bbclass
index
test runs.
Signed-off-by: Paul Barker
---
meta/lib/oeqa/selftest/context.py | 17 +
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/meta/lib/oeqa/selftest/context.py
b/meta/lib/oeqa/selftest/context.py
index dd3609c1d6..1659926975 100644
--- a/meta/lib/oeqa
currpos = result.output.find('usage: oe-pkgdata-util [-h] [-d] [-p
> PKGDATA_DIR] ')
In my opinion this is still too restrictive a test, it would need
updating when any further arguments are added to the oe-pkgdata-util
tool. I'd recommend just checking for "usage: oe-pkgdata-util"
5-r0/build/contrib'
> sed: can't read
> /home/dingo/STX/build/tmp/work/corei7-64-poky-linux/postgresql/11.5-r0/image/var/lib/postgresql/.bash_profile:
> No such file or directory
> WARNING: exit code 2 from a shell command.
> ERROR: Function failed: do_install (log file is located at
> /h
On Tue, 22 Dec 2020 at 14:57, Erik Botö wrote:
>
> On Tue, Dec 22, 2020 at 2:50 PM Paul Barker wrote:
> >
> > On Tue, 22 Dec 2020 at 10:03, Richard Purdie
> > wrote:
> > >
> > > On Tue, 2020-12-22 at 10:08 +0100, Erik Boto wrote:
> > > > The
gt; Richard
Looking at that bug (#14129) I wonder why "${WORKDIR}/build-wic" was
added to PSEUDO_IGNORE_PATHS in
https://git.openembedded.org/openembedded-core/commit/?id=ad8f5532ffaead9a5ad13e1034fe9e5e1b7979f4.
Is anything likely to explode if we drop that addition?
Thanks,
--
Paul Barker
Konsulko Gro
EL_DEVICETREE_FLAGS}" ]; then
> + export DTC_FLAGS="${KERNEL_DEVICETREE_FLAGS}"
> + fi
> +
> for dtbf in ${KERNEL_DEVICETREE}; do
> dtb=`normalize_dtb "$dtbf"`
> oe_runmake $dtb CC="${KERNEL_CC
this test case is expected to catch but
perhaps just checking for the return code of 2 and the string "usage:
oe-pkgdata-util" somewhere in the output is enough.
Thanks,
--
Paul Barker
Konsulko Group
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
.
Signed-off-by: Paul Barker
---
meta-selftest/lib/pseudo_pyc_test1.py | 1 +
meta-selftest/lib/pseudo_pyc_test2.py | 1 +
.../pseudo-pyc-test/pseudo-pyc-test.bb| 15 +++
meta/conf/bitbake.conf| 4 +--
meta/lib/oeqa/selftest/cases
ackage_,${WORKDIR}/sstate-build-image_complete,${TMPDIR}/sysroots-components,${BUILDHISTORY_DIR},${TMPDIR}/pkgdata,${TOPDIR}/cache,${COREBASE}/scripts,${COREBASE}/meta,${CCACHE_DIR}"
>
> export PSEUDO_DISABLED = "1"
> #export PSEUDO_PREFIX = "${STAGING_DIR_NATIVE}${p
On Mon, 7 Dec 2020 at 12:46, Richard Purdie
wrote:
>
> On Mon, 2020-12-07 at 12:04 +, Paul Barker wrote:
> > On Mon, 7 Dec 2020 at 10:29, Paul Barker
> > wrote:
> > To follow up some more: The entries in PSEUDO_IGNORE_PATHS are
> > treated
> >
On Mon, 7 Dec 2020 at 10:29, Paul Barker wrote:
>
> On Tue, 1 Dec 2020 at 18:12, Peter Kjellerstedt
> wrote:
> >
> > Instead of ignoring ${COREBASE}/meta in PSEUDO_IGNORE_PATHS (which may
> > or may not ignore all layers depending on how they are named and placed
>
fic reason why you need to ignore all
layer directories? I'm not 100% sure why "${COREBASE}/meta" is ignored
anyway though I guess it is to reduce pseudo db size and so speed up
builds.
Thanks,
--
Paul Barker
Konsulko Group
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages
HDDs.
With NVMe drives I see no need to limit at the top end of the systems
I've built on (12c/24t).
--
Paul Barker
Konsulko Group
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#145248):
https://lists.openembedded.org/g/openembedded-core/message/145248
Mu
way to handle recipes like this which don't require external
source code is to say that they have the same license as the core
metadata itself (MIT) and reference the license text in
"meta/COPYING.MIT". See for example
meta/recipes-bsp/formfactor/formfactor_0.0.bb.
Thanks,
--
Paul Bar
On Tue, 24 Nov 2020 at 15:14, Paul Barker wrote:
>
> The autobuilder contains workers for both of these distros.
>
> Signed-off-by: Paul Barker
> ---
> meta-poky/conf/distro/poky.conf | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta-poky/conf/distro
The autobuilder no longer contains a worker for this distro.
Signed-off-by: Paul Barker
---
meta-poky/conf/distro/poky.conf | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta-poky/conf/distro/poky.conf b/meta-poky/conf/distro/poky.conf
index bdf46f4038..35c9b1a27c 100644
--- a/meta-poky
The autobuilder contains workers for both of these distros.
Signed-off-by: Paul Barker
---
meta-poky/conf/distro/poky.conf | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta-poky/conf/distro/poky.conf b/meta-poky/conf/distro/poky.conf
index 31dc110bf6..bdf46f4038 100644
--- a/meta-poky
On Tue, 24 Nov 2020 at 12:44, Paul Barker wrote:
>
> The `qemuarmv5` and `qemuriscv64` machines have been support since the
> warrior and zeus releases respectively. Add them to the local.conf
> sample so that they're easier for new users to discover.
>
> Signed-off-by: Paul Bar
The `qemuarmv5` and `qemuriscv64` machines have been support since the
warrior and zeus releases respectively. Add them to the local.conf
sample so that they're easier for new users to discover.
Signed-off-by: Paul Barker
---
meta/conf/local.conf.sample | 2 ++
1 file changed, 2 insertions
e to archive the git project in a way, that the GIT history
> can be examined later?
> 2. If this is not possible, I would have to put my changes in an
> "external" patch file alongside the bitbake recipe, right?
> 3. Is there any value archiving the .git directory at al
any changes as part of this patch series.
I'll run as much of the selftest suite as I can on this series as-is
to see if there are any other issues.
Thanks,
--
Paul Barker
Konsulko Group
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Onlin
ion that may be privileged or confidential and
> is the property of the KPIT Technologies Ltd. It is intended only for the
> person to whom it is addressed. If you are not the intended recipient, you
> are not authorized to read, print, retain copy, disseminate, distribute, or
> use
On Thu, 9 Jul 2020 at 11:42, Fredrik Gustafsson
wrote:
>
> Hi,
> is there something I can do to make this series move forward?
>
I guess it's waiting for at least one person to review it in detail.
It's in my backlog, I should get to it on Monday.
--
Paul Barker
Ko
sting code into separate modules without making any
functional changes. I'll let others give their opinions as well, I'm
happy to review this one if we do want to look at this piecemeal.
--
Paul Barker
Konsulko Group
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply
reed.
Joe, how are you configuring the archiver here?
Also, are you not providing your layers along with the copies of the
upstream source code? If you're providing the layers then you
shouldn't need to worry about files like these being picked up by the
archiver.
Thanks,
--
Paul Barker
Konsul
On Wed, 1 Jul 2020 at 11:12, Richard Purdie
wrote:
>
> On Wed, 2020-07-01 at 11:11 +0100, Richard Purdie via
> lists.openembedded.org wrote:
> > On Wed, 2020-07-01 at 10:54 +0100, Richard Purdie via
> > lists.openembedded.org wrote:
> > > On Wed, 2020-07-01 at
r choice so it can be
overridden easily. Other than that, this looks good.
> +
> +python () {
> +list = d.getVar("NO_PACKAGES_DELTASKS").split()
> +for task in list:
> +bb.build.deltask(task, d)
> +}
> --
> 2.20.1
--
Paul Barker
Konsulko Group
f one recipe per dependency works well for
Python since it's not common to distribute a built artifact which
statically links all those dependencies together. That's often not the
case with rust and golang projects though. I still think one recipe
per upstream project with dependencies fully expressed in
s." exit 1 }
>
>
> can somebody help me how i can add distro for raspberrypi??
If you're unsure what a distro is in the context of Yocto Project /
OpenEmbedded then I recommend you find one of the many tutorials
online and work through it. Also, his question is not specific to
open
-arch_var = ["SDK_PACKAGE_ARCHS", None][target is True]
> -os_var = ["SDK_OS", None][target is True]
> -return RpmPkgsList(d, rootfs_dir).list_pkgs()
> -elif img_type == "ipk":
> -conf_file_var = ["IPK
nagers/rpm/package_manager.py
> +++ b/meta/lib/oe/package_managers/rpm/package_manager.py
> @@ -384,8 +384,11 @@ class RpmIndexer(Indexer):
>
> self.d.getVar('PACKAGE_FEED_GPG_PASSPHRASE_FILE'),
> armor=is
On Thu, 25 Jun 2020 at 11:22, Fredrik Gustafsson
wrote:
>
> Let the code that is only used by opkg package manager live in that
Typo here: This commit moves the dpkg indexer not the opkg one.
--
Paul Barker
Konsulko Group
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all message
r=None, progress_reporter=None,
> logcatcher=None):
> env_bkp = os.environ.copy()
>
> -img_type = d.getVar('IMAGE_PKGTYPE')
> -from oe.package_managers.rpm.rootfs import RpmRootfs
> -from oe.package_managers.ipk.rootfs import OpkgRootfs
> -from oe.package_m
gt; self.d.getVar('TARGET_VENDOR')
> )
> diff --git a/meta/lib/oe/package_managers/rpm/sdk.py
> b/meta/lib/oe/package_managers/rpm/sdk.py
> index d2f7447657..abd3ce5569 100644
> --- a/meta/lib/oe/package_managers/rpm/sdk.py
> +++ b/meta/lib/oe/package_managers/rpm/sdk.py
mport_module('oe.package_managers.deb.manifest').PkgManifest(d,
> self.manifest_dir, Manifest.MANIFEST_TYPE_SDK_TARGET)
> +self.host_manifest =
> importlib.import_module('oe.package_managers.deb.manifest').PkgManifest(d,
> self.manifest_dir, Manifest.MANIFEST_TYPE_SDK_HOST)
&
> new file mode 100644
> index 00..a2094304c9
> --- /dev/null
> +++ b/meta/lib/oe/package_managers/rpm/__init__.py
> @@ -0,0 +1,3 @@
> +#
> +# SPDX-License-Identifier: GPL-2.0-only
> +#
These directories can be created as needed in later patches, there's
no need
(d, manifest_dir).populate()
> -elif img_type == "deb":
> -DpkgSdk(d, manifest_dir).populate()
> +import importlib
> +importlib.import_module('oe.package_managers.' +
> d.getVar('IMAGE_PKGTYPE') + '.sdk').PkgSdk(d, manifest_dir).populate()
>
> os.environ
ckagedata do_package_setscene
> do_package_write_rpm_setscene do_package_write_ipk_setscene
> do_package_write_deb_setscene do_package_qa_setscene do_packagedata_setscene"
Could we use a more descriptive name here, e.g. NO_PACKAGES_DELTASKS?
--
Paul Barker
Konsulko Group
-=-=-=-=-
face level reading, I think the way you're submitting this
still needs some work before it's in a state where we can properly
review the changes in detail. Right now it's too big and too easy to
get confused when looking through 26 large patches.
I'm very supportive of tidying this up
ole git repository? Typically this issue
wouldn't be seen as .git would not be part of the installed package.
Perhaps instead of running `cp -rf $(srcdir)/../git
$(DESTDIR)/bzip2-tests` you need to copy a more specific subset of
files & directories.
--
Paul Barker
Konsulko Group
-=-=-=-=-=-=-=-=
nager. That suggests you could
start by just splitting out the rootfs code from each package manager,
leaving the rest in package_manager.py. Then on the next commit move
the sdk handling, etc. That would make each commit easier to reason
about.
I'd also recommend adding a __init__.py file in
gt; # fix dynamic loader paths in all ELF SDK binaries
> native_sysroot=$($SUDO_EXEC cat $env_setup_script |grep
> 'OECORE_NATIVE_SYSROOT='|cut -d'=' -f2|tr -d '"')
> dl_path=$($SUDO_EXEC find $native_sysroot/lib -name "ld-linux*")
> --
> 2.17.1
--
P
ry new to yocto
> can you help me out ??
Why do you want to use an old patch release in the 5.4 series? You
should be using the latest patch release in a stable series so that
you've got all the bug and security fixes.
Thanks,
--
Paul Barker
Konsulko Group
-=-=-=-=-=-=-=-=-=-=-=-
Links: You re
y left as an exercise for the reader. Patches are
welcome :)
You could also look at the linux-yocto recipes in openembedded-core.
Thanks,
--
Paul Barker
Konsulko Group
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#139423):
https://lis
s), it is a sumo build.
Sumo is now EOL (https://wiki.yoctoproject.org/wiki/Releases), you'll
probably need to update to something more recent to support Debian
testing.
--
Paul Barker
Konsulko Group
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
This allows tests to switch to selftest-ed-native which has far fewer
dependencies than selftest-ed.
Signed-off-by: Paul Barker
---
meta-selftest/recipes-test/selftest-ed/selftest-ed_0.5.bb| 2 ++
meta-selftest/recipes-test/selftest-ed/selftest-ed_1.14.1.bb | 2 ++
2 files changed, 4
)
oe-selftest () - Ran 15 tests in 257.170s
Signed-off-by: Paul Barker
---
meta/lib/oeqa/selftest/cases/archiver.py | 30
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/meta/lib/oeqa/selftest/cases/archiver.py
b/meta/lib/oeqa/selftest/cases/archiver.py
1 - 100 of 521 matches
Mail list logo
