From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: "Abdurrahman Hussain (fib)" <fib@cisco.com>
Cc: Martin Jansa <Martin.Jansa@gmail.com>,
"meta-virtualization@lists.yoctoproject.org"
<meta-virtualization@lists.yoctoproject.org>
Subject: Re: [meta-virtualization] [kirkstone][PATCH] docker-ce: bump SRCREV_docker
Date: Tue, 5 Sep 2023 20:29:26 +0000 [thread overview]
Message-ID: <ZPePptxh09fsDwzh@gmail.com> (raw)
In-Reply-To: <BL1PR11MB6001A97256DB08EB45FAF76AADEAA@BL1PR11MB6001.namprd11.prod.outlook.com>
In message: RE: [meta-virtualization] [kirkstone][PATCH] docker-ce: bump SRCREV_docker
on 03/09/2023 Abdurrahman Hussain (fib) wrote:
> Hi Bruce,
>
> It seems docker in Dunfell is also affected with the same 'http: invalid Host header' issue.
> Can these patches be merged into Dunfell as well?
If the patches were simply cherry picked, that would involve a major
docker version change, which isn't something we'd typically do.
We need a specific / tested patch for dunfell for proper consideration.
Bruce
>
> Thanks,
> Abdurrahman
>
> -----Original Message-----
> From: meta-virtualization@lists.yoctoproject.org <meta-virtualization@lists.yoctoproject.org> On Behalf Of Bruce Ashfield
> Sent: Wednesday, August 16, 2023 6:36 AM
> To: Martin Jansa <Martin.Jansa@gmail.com>
> Cc: meta-virtualization@lists.yoctoproject.org
> Subject: Re: [meta-virtualization] [kirkstone][PATCH] docker-ce: bump SRCREV_docker
>
> Thanks Martin,
>
> This is merged.
>
> Bruce
>
> On Wed, Aug 16, 2023 at 2:09 AM Martin Jansa <Martin.Jansa@gmail.com> wrote:
> >
> > * fix my prevous commit where I've missed this update corresponding
> > to SRCREV_moby change in docker-moby recipe.
> >
> > * also re-order the patches in SRC_URI to match docker-moby, so
> > that they are easier to compare
> >
> > Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> > ---
> > recipes-containers/docker/docker-ce_git.bb | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/recipes-containers/docker/docker-ce_git.bb
> > b/recipes-containers/docker/docker-ce_git.bb
> > index 76ac41e..7142060 100644
> > --- a/recipes-containers/docker/docker-ce_git.bb
> > +++ b/recipes-containers/docker/docker-ce_git.bb
> > @@ -31,7 +31,7 @@ DESCRIPTION = "Linux container runtime \ # so we
> > get that tag, and make it our SRCREVS:
> > #
> >
> > -SRCREV_docker = "3056208812eb5e792fa99736c9167d1e10f4ab49"
> > +SRCREV_docker = "791d8ab87747169b4cbfcdf2fd57c81952bae6d5"
> > SRCREV_libnetwork = "dcdf8f176d1e13ad719e913e796fb698d846de98"
> > SRCREV_cli = "911449ca245308472a3d34a7f1a98b918e65c8c3"
> > SRCREV_FORMAT = "docker_libnetwork"
> > @@ -39,10 +39,10 @@ SRC_URI = "\
> > git://github.com/docker/docker.git;branch=20.10;name=docker;protocol=https \
> > git://github.com/docker/libnetwork.git;branch=master;name=libnetwork;destsuffix=git/libnetwork;protocol=https \
> > git://github.com/docker/cli;branch=20.10;name=cli;destsuffix=git/cli;protocol=https \
> > - file://0001-libnetwork-use-GO-instead-of-go.patch \
> > file://docker.init \
> > - file://0001-dynbinary-use-go-cross-compiler.patch \
> > + file://0001-libnetwork-use-GO-instead-of-go.patch \
> > file://0001-cli-use-external-GO111MODULE-and-cross-compiler.patch
> > \
> > + file://0001-dynbinary-use-go-cross-compiler.patch \
> > file://0001-Revert-go-updates-from-1.19.12-to-1.18.7.patch;patchdir=src/import \
> > file://0002-Revert-go-updates-from-1.18.7-to-1.17.13.patch;patchdir=src/import \
> >
> > file://0003-builder.go-avoid-using-strings.Cut-from-go-1.18.patch;patc
> > hdir=src/import \
> > --
> > 2.41.0
> >
> >
> >
> >
>
>
> --
> - 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:[~2023-09-05 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 6:09 [kirkstone][PATCH] docker-ce: bump SRCREV_docker Martin Jansa
2023-08-16 13:35 ` [meta-virtualization] " Bruce Ashfield
2023-09-03 5:21 ` Abdurrahman Hussain (fib)
2023-09-05 20:29 ` 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=ZPePptxh09fsDwzh@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=Martin.Jansa@gmail.com \
--cc=fib@cisco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.