Re: [OE-core] master/main branch renaming and bitbake

On Thu, May 13, 2021, at 3:08 AM, Richard Purdie wrote: > > I had a look at the code to try and remind myself why it is doing this. Thanks! > The best answer I found is that it does support filtered fetching of > remotes, i.e. it can and will only pull the branch it wants/needs rather > than

Re: [OE-core] [PATCH] libnotify: Make gtk+3 dependency optional

On Thu, 13 May 2021 at 16:36, Mike Crowe via lists.openembedded.org wrote: > +PACKAGECONFIG[gtk+] = "--enable-tests,--disable-tests,,gtk+3" > Was the --enable-tests scenario tested? Specifying gtk+3 after two ,,s seems weird. Alex -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent

Re: [OE-core] [PATCH v2] libnotify: Make gtk+3 dependency optional

On Thu, May 13, 2021 at 9:15 AM Mike Crowe via lists.openembedded.org wrote: > > libnotify only requires gtk+3 for its tests. Let's disable them by > default. > > Signed-off-by: Mike Crowe > --- > meta/recipes-gnome/libnotify/libnotify_0.7.9.bb | 7 --- > 1 file changed, 4 insertions(+), 3

[OE-core] [PATCH] libnotify: Make gtk+3 dependency optional

libnotify only requires gtk+3 for its tests. Let's disable them by default. Signed-off-by: Mike Crowe --- meta/recipes-gnome/libnotify/libnotify_0.7.9.bb | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/meta/recipes-gnome/libnotify/libnotify_0.7.9.bb

Re: [OE-core] [PATCH] libnotify: Make gtk+3 dependency optional

On Thursday 13 May 2021 at 17:06:23 +0100, Richard Purdie wrote: > On Thu, 2021-05-13 at 16:43 +0200, Alexander Kanavin wrote: > > On Thu, 13 May 2021 at 16:36, Mike Crowe via lists.openembedded.org < > > yocto=mac.mcrowe@lists.openembedded.org> wrote: > > > +PACKAGECONFIG[gtk+] =

[OE-core] [PATCH] npm.bbclass: Allow nodedir to be overridden by NPM_NODEDIR

Node modules may need to be built against multiple Node versions. Setting nodedir in the NPM configuration stops older ways of doing this, such as setting npm_config_target and npm_config_disturl, from working. Signed-off-by: Mike Crowe --- meta/classes/npm.bbclass | 6 -- 1 file changed, 4

Re: [OE-core] master/main branch renaming and bitbake

> -Original Message- > From: openembedded-core@lists.openembedded.org c...@lists.openembedded.org> On Behalf Of Richard Purdie > Sent: den 13 maj 2021 09:09 > To: Andre McCurdy ; Alexander Kanavin > > Cc: Colin Walters ; OE-core c...@lists.openembedded.org> > Subject: Re: [OE-core]

Re: [OE-core] master/main branch renaming and bitbake

On Thu, May 13, 2021 at 9:27 AM colin walters wrote: > > > > On Thu, May 13, 2021, at 3:08 AM, Richard Purdie wrote: > > > > I had a look at the code to try and remind myself why it is doing this. > > Thanks! > > > The best answer I found is that it does support filtered fetching of > > remotes,

Re: [OE-core] [PATCH] rng-tools: disable the CPU affinity mask

On Mon, May 10, 2021 at 8:23 AM Jack Mitchell wrote: > > On 10/05/2021 10:48, Richard Purdie wrote: > > On Mon, 2021-05-10 at 10:33 +0800, Yu, Mingli wrote: > >> From: Mingli Yu > >> > >> For the jitter entropy source, each task thread will create an internal > >> counter timer thread when the

Re: [OE-core] [PATCH] libnotify: Make gtk+3 dependency optional

On Thu, 2021-05-13 at 16:43 +0200, Alexander Kanavin wrote: > On Thu, 13 May 2021 at 16:36, Mike Crowe via lists.openembedded.org < > yocto=mac.mcrowe@lists.openembedded.org> wrote: > > +PACKAGECONFIG[gtk+] = "--enable-tests,--disable-tests,,gtk+3" > > > > > Was the --enable-tests scenario

[OE-core] [PATCH v2] libnotify: Make gtk+3 dependency optional

libnotify only requires gtk+3 for its tests. Let's disable them by default. Signed-off-by: Mike Crowe --- meta/recipes-gnome/libnotify/libnotify_0.7.9.bb | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/meta/recipes-gnome/libnotify/libnotify_0.7.9.bb

Re: [OE-core] [PATCH] libnotify: Make gtk+3 dependency optional

On Thursday 13 May 2021 at 16:43:15 +0200, Alexander Kanavin wrote: > On Thu, 13 May 2021 at 16:36, Mike Crowe via lists.openembedded.org mac.mcrowe@lists.openembedded.org> wrote: > > > +PACKAGECONFIG[gtk+] = "--enable-tests,--disable-tests,,gtk+3" > > > > Was the --enable-tests scenario

Re: [OE-core] [PATCH] libnotify: Make gtk+3 dependency optional

On 5/13/21 7:43 AM, Alexander Kanavin wrote: On Thu, 13 May 2021 at 16:36, Mike Crowe via lists.openembedded.org > wrote: +PACKAGECONFIG[gtk+] = "--enable-tests,--disable-tests,,gtk+3" Was the --enable-tests

Re: [OE-core] [PATCH 1/2] ovmf: Disable lto to aid reproducibility

On Wed, May 12, 2021 at 4:12 PM Richard Purdie wrote: > > On Wed, 2021-05-12 at 16:04 -0700, Khem Raj wrote: > > On Wed, May 12, 2021 at 2:32 PM Richard Purdie > > wrote: > > > > > > lto tends to break reproducibility and makes ovmf near impossible to debug > > > reproducibility issues in.

Re: [OE-core] master/main branch renaming and bitbake

On Thu, May 13, 2021 at 3:02 PM Benjamin Gilbert wrote: > > On Thu, May 13, 2021 at 06:36 AM, Bruce Ashfield wrote: > > The problem is that your build system is penalizing upstream projects that > are trying to migrate > to using `main`. > > Similarly those same projects are completely deleting

Re: [OE-core] master/main branch renaming and bitbake

On Thu, May 13, 2021 at 01:07 PM, Alexander Kanavin wrote: > > It's not that different from deleting or archiving old tarball downloads - > yes it keeps things clean and tidy for upstream, but it will break > someone's automated build that way, no matter how obsolete the code being > downloaded.

[OE-core] [PATCH 1/8] gdk-pixbuf: rewrite the cross-build support for tests

It was scattered over four different patches, and wasn't guarded by a configuration option. Hopefully the new patch is acceptable to upstream. Signed-off-by: Alexander Kanavin --- .../0001-Add-use_prebuilt_tools-option.patch | 171 ++

[OE-core] [PATCH 2/8] gnome: drop upstream even condition from a few recipes

They have adopted the new gnome version scheme where the distinction is no longer: https://lwn.net/Articles/831746/ Signed-off-by: Alexander Kanavin --- meta/recipes-gnome/epiphany/epiphany_40.1.bb| 2 +- meta/recipes-gnome/gnome/adwaita-icon-theme_3.34.3.bb | 2 +-

[OE-core] [PATCH 3/8] expat: upgrade 2.2.10 -> 2.3.0

Drop 0001-Add-output-of-tests-result.patch (difficult to rebase). I have verified that ptests still pass, and print PASS for every test. If they start failing we can revisit what kind of output would be beneficial. Signed-off-by: Alexander Kanavin --- .../0001-Add-output-of-tests-result.patch

[OE-core] [PATCH 4/8] meson: update 0.57.2 -> 0.58.0

Rebase patches; dropped chunks (and cross-prop-default.patch) have been removed upstream. Move native-only patches to all-patches, as they're a pain to rebase separately. Signed-off-by: Alexander Kanavin --- meta/recipes-devtools/meson/meson.inc | 11 +-

[OE-core] [PATCH 6/8] nativesdk-meson: correctly set cpu_family

This was a warning before, but with the patch that turns it into an error, it needs to be properly addressed. Signed-off-by: Alexander Kanavin --- .../meson/nativesdk-meson_0.58.0.bb| 14 ++ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git

[OE-core] [PATCH 7/8] gstreamer1.0-plugins-base: backport a patch to fix meson 0.58 builds

Signed-off-by: Alexander Kanavin --- ...c91697a141fea7317aff7f0f28e5a861db99.patch | 50 +++ .../gstreamer1.0-plugins-base_1.18.4.bb | 1 + 2 files changed, 51 insertions(+) create mode 100644

[OE-core] [PATCH 8/8] qemu: backport a patch to fix meson 0.58 builds

Signed-off-by: Alexander Kanavin --- meta/recipes-devtools/qemu/qemu.inc | 1 + ...igure-fix-detection-of-gdbus-codegen.patch | 53 +++ 2 files changed, 54 insertions(+) create mode 100644

[OE-core] [PATCH 5/8] meson.bbclass: split python routines into a separate class

This allows reusing them in nativesdk-meson without copy-pasting code. Signed-off-by: Alexander Kanavin --- meta/classes/meson-routines.bbclass | 51 meta/classes/meson.bbclass | 52 + 2 files changed, 52 insertions(+), 51

Re: [OE-core] master/main branch renaming and bitbake

On Thu, May 13, 2021 at 3:25 PM Benjamin Gilbert wrote: > > On Thu, May 13, 2021 at 12:04 PM, Bruce Ashfield wrote: > > Deleting the branch penalizes existing developers, which projects might be > willing to do. Git branch names don't usually have any effect on users. > > I'm not sure I see the

Re: [OE-core] master/main branch renaming and bitbake

On 13.05.21 21:54, Benjamin Gilbert wrote: On Thu, May 13, 2021 at 12:36 PM, Alexander Kanavin wrote: They're not useless though. As a layer maintainer I absolutely want those checks, as I want to be aware of any branch configuration changes upstream, and to ensure I'm not accepting

Re: [OE-core] master/main branch renaming and bitbake

On Thu, May 13, 2021 at 06:36 AM, Bruce Ashfield wrote: > > >> The problem is that your build system is penalizing upstream projects that >> are trying to migrate >> to using `main`. > > Similarly those same projects are completely deleting those branches, > versus no longer making them the

Re: [OE-core] master/main branch renaming and bitbake

On Thu, 13 May 2021 at 21:25, Benjamin Gilbert wrote: > Deleting the branch normally affects people who are in the project's > developer community and pay attention to its announcements. Those folks > can then simply update their local checkouts and move on with their lives. > Everyone else

Re: [OE-core] master/main branch renaming and bitbake

On Thu, 2021-05-13 at 09:27 -0400, colin walters wrote: > > On Thu, May 13, 2021, at 3:08 AM, Richard Purdie wrote: > > > > I had a look at the code to try and remind myself why it is doing this. > > Thanks! > > > The best answer I found is that it does support filtered fetching of > >

Re: [OE-core] master/main branch renaming and bitbake

On Thu, May 13, 2021 at 12:04 PM, Bruce Ashfield wrote: > > >> Deleting the branch penalizes existing developers, which projects might be >> willing to do. Git branch names don't usually have any effect on users. > > I'm not sure I see the distinction you are trying to draw. Deleting the

Re: [OE-core] master/main branch renaming and bitbake

And IMHO deleting branches upstream is just bad practice. From a Yocto/OE perspective I have to consider that people might want to build stuff in 5yrs or even 10yrs from now. a more reasonable pattern would be to branch off from master to main, make main the new default but leave master

Re: [OE-core] master/main branch renaming and bitbake

On Thu, May 13, 2021 at 12:36 PM, Alexander Kanavin wrote: > > They're not useless though. As a layer maintainer I absolutely want those > checks, as I want to be aware of any branch configuration changes > upstream, and to ensure I'm not accepting a change in source revision that > points to an

Re: [OE-core] master/main branch renaming and bitbake

On Thu, 13 May 2021 at 22:34, Benjamin Gilbert wrote: > Tarballs, commits on published branches, and annotated tags are all > supposed to be stable artifacts. But I don't know of any general > expectation that a specific branch continues to exist, other than the one > created by Bitbake.

Re: [OE-core][dunfell 00/25] Pull request (cover letter only)

On Wed, 2021-05-12 at 04:47 -1000, Steve Sakoman wrote: > The following changes since commit 834a8e357bc999a0163e7c5bafbcc1a8816448d4: > >   license_image.bbclass: Fix symlink to generic license files (2021-05-03 > 04:56:23 -1000) > > are available in the Git repository at: > >   

Re: [OE-core] master/main branch renaming and bitbake

On Thu, 13 May 2021 at 21:54, Benjamin Gilbert wrote: > They're not useless though. As a layer maintainer I absolutely want those > checks, as I want to be aware of any branch configuration changes upstream, > and to ensure I'm not accepting a change in source revision that points to > an

Re: [OE-core] master/main branch renaming and bitbake

On Thu, May 13, 2021 at 01:09 PM, Richard Purdie wrote: > > Some of our users have complained, yes. That isn't a conscious decision on > > "our" part, just a rather unfortunate and unplanned consequence of the > fact > we're pretty strict about declaring where we get our sources. > > The

Re: [OE-core] master/main branch renaming and bitbake

On Thu, 2021-05-13 at 14:25 +, Peter Kjellerstedt wrote: > > Another reason we have the branch name is so that we can ls-remote the > > repo > > when using AUTOREV for SRCREV. We've tried to make it so that once a url > > is established in SRC_URI, you can make it use AUTOREV without changes

[OE-core] [PATCH 2/2] gstreamer1.0-libav: remove explicit LICENSE_FLAGS

From: Yann Dirson This flag does not describe the gst-libav package, but ffmpeg instead. It gets in the way of using finer-grained LICENSE_FLAGS in ffmpeg. It is above all not needed, the real problem is even more clear without it: ffmpeg was skipped: because it has a restricted license

[OE-core] [PATCH 1/2] gst-examples,gstreamer1.0-libav: Add option to exclude from world build

When LICENSE_FLAGS_WHITELIST does not have commercial in it then the the dependencies like ffmpeg will become invisible and render these packages unbuildable, therefore world build will report parse issues its better to exclude them from world build in such cases Signed-off-by: Khem Raj Cc:

Re: [OE-core] master/main branch renaming and bitbake

On Thu, May 13, 2021, at 4:08 PM, Richard Purdie wrote: > > The advice to anyone hitting this issue is to add in the correct branch > to the SRC_URI. It is simple and easy to do, can be in bbappends > or even changed via anonymous python and similar if necessary. We've already > found the issue

[OE-core] [PATCH 3/4] vulkan-loader: upgrade 1.2.170.0 -> 1.2.176.0

Signed-off-by: Wang Mingyu --- .../{vulkan-loader_1.2.170.0.bb => vulkan-loader_1.2.176.0.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-graphics/vulkan/{vulkan-loader_1.2.170.0.bb => vulkan-loader_1.2.176.0.bb} (96%) diff --git

[OE-core] [PATCH 2/4] vulkan-headers: upgrade 1.2.170.0 -> 1.2.176.0

Signed-off-by: Wang Mingyu --- ...{vulkan-headers_1.2.170.0.bb => vulkan-headers_1.2.176.0.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-graphics/vulkan/{vulkan-headers_1.2.170.0.bb => vulkan-headers_1.2.176.0.bb} (93%) diff --git

[OE-core] [PATCH 4/4] vulkan-tools: upgrade 1.2.170.0 -> 1.2.176.0

Signed-off-by: Wang Mingyu --- .../{vulkan-tools_1.2.170.0.bb => vulkan-tools_1.2.176.0.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-graphics/vulkan/{vulkan-tools_1.2.170.0.bb => vulkan-tools_1.2.176.0.bb} (94%) diff --git

[OE-core] [PATCH 1/4] vulkan-samples: update to latest revision

Signed-off-by: Wang Mingyu --- meta/recipes-graphics/vulkan/vulkan-samples_git.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-graphics/vulkan/vulkan-samples_git.bb b/meta/recipes-graphics/vulkan/vulkan-samples_git.bb index 32502a1f7a..e89f75baac 100644 ---

[OE-core] [PATCH] rpcbind: upgrade 1.2.5 -> 1.2.6

refresh rpcbind_add_option_to_fix_port_number.patch Signed-off-by: Zheng Ruoqin --- ...pcbind_add_option_to_fix_port_number.patch | 58 +-- .../{rpcbind_1.2.5.bb => rpcbind_1.2.6.bb}| 4 +- 2 files changed, 31 insertions(+), 31 deletions(-) rename

[OE-core] [PATCH] sysklogd: upgrade 2.2.2 -> 2.2.3

Signed-off-by: Zheng Ruoqin --- .../sysklogd/{sysklogd_2.2.2.bb => sysklogd_2.2.3.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-extended/sysklogd/{sysklogd_2.2.2.bb => sysklogd_2.2.3.bb} (96%) diff --git

Re: [OE-core] couple questions about creating companion debug filesystem

On Thu, May 13, 2021 at 3:36 AM Robert P. J. Day wrote: > > couple colleagues asked me about the details of how the debug > filesystem is created, and since i wasn't entirely clear on the > mechanics of it myself, i thought i'd dig into it, so a couple > preliminary questions to make sure i'm

Re: [OE-core] master/main branch renaming and bitbake

On Thu, 2021-05-13 at 17:33 -0400, colin walters wrote: > > On Thu, May 13, 2021, at 4:08 PM, Richard Purdie wrote: > > > > The advice to anyone hitting this issue is to add in the correct branch > > to the SRC_URI. It is simple and easy to do, can be in bbappends > > or even changed via

[OE-core] Layer list's certificate expired

Hi, On opening OE-layers browsers complain that certificate has expired yesterday 13.th of May. Just wanted to let you know. Cheers, Andreas -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#151744):

[OE-core] [PATCH] rng-tools: upgrade 6.11 -> 6.12

Signed-off-by: Zheng Ruoqin --- .../rng-tools/{rng-tools_6.11.bb => rng-tools_6.12.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-support/rng-tools/{rng-tools_6.11.bb => rng-tools_6.12.bb} (97%) diff --git

[OE-core] [PATCH] python3-attrs: upgrade 20.3.0 -> 21.2.0

Signed-off-by: Wang Mingyu --- .../{python3-attrs_20.3.0.bb => python3-attrs_21.2.0.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-devtools/python/{python3-attrs_20.3.0.bb => python3-attrs_21.2.0.bb} (74%) diff --git

[OE-core] [PATCH] python3-six: upgrade 1.15.0 -> 1.16.0

Signed-off-by: Wang Mingyu --- meta/recipes-devtools/python/python3-six_1.15.0.bb | 5 - meta/recipes-devtools/python/python3-six_1.16.0.bb | 5 + 2 files changed, 5 insertions(+), 5 deletions(-) delete mode 100644 meta/recipes-devtools/python/python3-six_1.15.0.bb create mode 100644

Re: [OE-core] master/main branch renaming and bitbake

On Wed, 2021-05-12 at 17:11 -0700, Andre McCurdy wrote: > On Wed, May 12, 2021 at 2:23 PM Alexander Kanavin > wrote: > > > > And by the way, another reason to check that revision is linked to a  > > branch is when SRCREV is updated - we need some reassurance that the  > > updated SRCREV comes

[OE-core] couple questions about creating companion debug filesystem

couple colleagues asked me about the details of how the debug filesystem is created, and since i wasn't entirely clear on the mechanics of it myself, i thought i'd dig into it, so a couple preliminary questions to make sure i'm on the right track. trivially, if you want that companion

[OE-core] [PATCH] meta/lib/oe/rootfs.py: "Restoreing" -> "Restoring"

Signed-off-by: Robert P. J. Day --- diff --git a/meta/lib/oe/rootfs.py b/meta/lib/oe/rootfs.py index 4b48cdbb65..ad9fd77c8b 100644 --- a/meta/lib/oe/rootfs.py +++ b/meta/lib/oe/rootfs.py @@ -167,7 +167,7 @@ class Rootfs(object, metaclass=ABCMeta): pass

Re: [OE-core] [PATCH 7/8] meson: update 0.57.2 -> 0.58.0

I'm addressing that as well, thanks for notifying. Alex On Thu, 13 May 2021 at 07:44, Lee, Chee Yang wrote: > > I think these error is related to this patch or the gdk-pixbuf patch in > this series . > meson > >

[OE-core] [PATCH] go: upgrade 1.16.3 -> 1.16.4

Signed-off-by: Wang Mingyu --- meta/recipes-devtools/go/{go-1.16.3.inc => go-1.16.4.inc} | 4 ++-- ...{go-binary-native_1.16.3.bb => go-binary-native_1.16.4.bb} | 4 ++-- ...o-cross-canadian_1.16.3.bb => go-cross-canadian_1.16.4.bb} | 0 .../go/{go-cross_1.16.3.bb => go-cross_1.16.4.bb}

[OE-core] [PATCH] image.bbclass: fix comment "pacackages" -> "packages"

Signed-off-by: Robert P. J. Day --- diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass index 353cc67175..67603d958d 100644 --- a/meta/classes/image.bbclass +++ b/meta/classes/image.bbclass @@ -38,7 +38,7 @@ IMAGE_FEATURES[validitems] += "debug-tweaks read-only-rootfs