From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15754] The docker-engine and docker-cli versions are not compatible with go 1.19.12 version
Date: Wed, 13 Sep 2023 20:23:54 +0000 [thread overview]
Message-ID: <bug-15754-163-Va2ww6v3pc@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15754-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15754
--- Comment #3 from Stefan Agner <stefan@agner.ch> ---
What patches are you referring to exactly? The bump to Docker 24.0.5?
From what I can tell this is really a breakage introduced by go v1.19.11, and
has been resolve in v1.19.13. By updating go to v1.19.13 the problem seems to
be gone for me.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-09-13 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 13:36 [Buildroot] [Bug 15754] New: The docker-engine and docker-cli versions are not compatible with go 1.19.12 version bugzilla
2023-09-05 7:16 ` [Buildroot] [Bug 15754] " bugzilla
2023-09-06 19:09 ` bugzilla
2023-09-07 9:19 ` bugzilla
2023-09-13 20:23 ` bugzilla [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=bug-15754-163-Va2ww6v3pc@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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