From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: ChenQi <Qi.Chen@windriver.com>
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization][PATCH 1/4] oci-image-tools: remove unneeded deps
Date: Tue, 27 Feb 2024 22:27:08 -0500 [thread overview]
Message-ID: <CADkTA4NnO7_yoNpjfb_fZjPBKFnjGdUuXuTcn+Lc5FeS4b08vA@mail.gmail.com> (raw)
In-Reply-To: <3468b594-13dd-1d98-5336-19b5839449c7@windriver.com>
On Tue, Feb 27, 2024 at 9:50 PM ChenQi <Qi.Chen@windriver.com> wrote:
>
> On 2/27/24 21:56, Bruce Ashfield wrote:
> > This patch is fine. I'll queue it shortly, once I work through some
> > other upgrade issues.
> >
> > Bruce
>
> Thanks Bruce.
>
> I'm also going to upgrade some go recipes in meta-virt. I will not touch
> those queued in master-next. Is there any other recipe you're working on
> or planning to work on?
I have upgrades in flight for pretty much all the packages in meta-virt,
this is the window that I do the updates. I do one early in the cycle, and
then another in the m3 timeframe. I won't take or do any more package
bumps (except for significant CVEs) until post release once I get
done with these upgrades.
So there's no need to send updates to any of those packages at this
time. If there's a package that I need help with, I tend to push it as
broken to master-next, ceph is the only remaining one like that currently
on master-next.
I've just finished up with docker-compose and will move through testing
the rest over the next few days.
>
> I found, just two days ago, that the go version in oe-core is 1.20. At
> the same time, I found oe-core has feature freezed. This would cause
> some trouble, I guess. So my initial plan was to upgrade the go recipes
> in meta-virt to the highest version that are compatible with go 1.20.
See my recent updates on master-next. I'm already taking care of the
updates, and I've managed to get some upgraded that claim they need
1.21 through some build side tweaks.
Bruce
>
> Now there are patches in mailing list to upgrade go to 1.21. Given the
> feature freeze fact, I'm not sure if the go 1.21 upgrade will make it
> into this LTS 5.0 release, especially with the dynlinking issue. I've
> also replied the email to check.
>
> Regards,
>
> Qi
>
>
> >
> > On Tue, Feb 27, 2024 at 12:12 AM Chen Qi via lists.yoctoproject.org
> > <Qi.Chen=windriver.com@lists.yoctoproject.org> wrote:
> >> From: Chen Qi <Qi.Chen@windriver.com>
> >>
> >> These deps no longer have any effect. Remove them.
> >>
> >> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> >> ---
> >> .../oci-image-tools/oci-image-tools_git.bb | 9 ---------
> >> 1 file changed, 9 deletions(-)
> >>
> >> diff --git a/recipes-containers/oci-image-tools/oci-image-tools_git.bb b/recipes-containers/oci-image-tools/oci-image-tools_git.bb
> >> index b925a2a7..ade6534d 100644
> >> --- a/recipes-containers/oci-image-tools/oci-image-tools_git.bb
> >> +++ b/recipes-containers/oci-image-tools/oci-image-tools_git.bb
> >> @@ -3,15 +3,6 @@ SUMMARY = "A collection of tools for working with the OCI image format specifica
> >> LICENSE = "Apache-2.0"
> >> LIC_FILES_CHKSUM = "file://LICENSE;md5=e3fc50a88d0a364313df4b21ef20c29e"
> >>
> >> -DEPENDS = "\
> >> - oci-image-spec \
> >> - oci-runtime-spec \
> >> - go-digest \
> >> - go-errors \
> >> - spf13-cobra \
> >> - spf13-pflag \
> >> - "
> >> -
> >> SRC_URI = "git://github.com/opencontainers/image-tools.git;branch=master;protocol=https;destsuffix=git/src/github.com/opencontainers/image-tools \
> >> file://0001-config-make-Config.User-mapping-errors-a-warning.patch \
> >> file://0001-tool-respect-GO-and-GOBUILDFLAGS-when-building.patch"
> >> --
> >> 2.42.0
> >>
> >>
> >> -=-=-=-=-=-=-=-=-=-=-=-
> >> Links: You receive all messages sent to this group.
> >> View/Reply Online (#8586): https://lists.yoctoproject.org/g/meta-virtualization/message/8586
> >> Mute This Topic: https://lists.yoctoproject.org/mt/104598180/1050810
> >> Group Owner: meta-virtualization+owner@lists.yoctoproject.org
> >> Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [bruce.ashfield@gmail.com]
> >> -=-=-=-=-=-=-=-=-=-=-=-
> >>
> >
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
prev parent reply other threads:[~2024-02-28 3:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 5:12 [meta-virtualization][PATCH 1/4] oci-image-tools: remove unneeded deps Qi.Chen
2024-02-27 5:12 ` [meta-virtualization][PATCH 2/4] crun: " Qi.Chen
2024-02-27 13:58 ` Bruce Ashfield
2024-02-27 5:12 ` [meta-virtualization][PATCH 3/4] meta-virt: remove pure go source packages Qi.Chen
2024-02-27 13:48 ` Bruce Ashfield
2024-02-28 2:23 ` ChenQi
2024-02-27 5:12 ` [meta-virtualization][PATCH 4/4] meta-virt: rename containerd-opencontainers to containerd Qi.Chen
2024-02-27 13:45 ` Bruce Ashfield
2024-02-27 13:56 ` [meta-virtualization][PATCH 1/4] oci-image-tools: remove unneeded deps Bruce Ashfield
2024-02-28 2:50 ` ChenQi
2024-02-28 3:27 ` Bruce Ashfield [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADkTA4NnO7_yoNpjfb_fZjPBKFnjGdUuXuTcn+Lc5FeS4b08vA@mail.gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=Qi.Chen@windriver.com \
--cc=meta-virtualization@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).