meta-virtualization.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: "Przemysław Chwiała" <przemekchwiala@gmail.com>
To: meta-virtualization@lists.yoctoproject.org
Subject: Docker-compose Go update on kirkstone
Date: Fri, 6 Oct 2023 17:22:58 +0200	[thread overview]
Message-ID: <1D32D17E-126F-413C-9F22-2E5CCF20E61F@gmail.com> (raw)

Hello,

I'm working on the kirkstone branch, where we still have python3-docker-compose_1.29.2.bb. I am wondering if there is any chance to upgrade to the Go version of docker-compose from the main branch? I tried to build the recipe from the main branch, but got some errors. Before I dig into fixing them, I'd like to ask if you see any additional issues that might block building docker-compose_git.bb from the main branch on kirkstone?

Thank you
Przemek

             reply	other threads:[~2023-10-06 15:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-06 15:22 Przemysław Chwiała [this message]
2023-10-06 18:21 ` [meta-virtualization] Docker-compose Go update on kirkstone Marko, Peter
2023-10-07  0:53   ` Bruce Ashfield
2023-10-14 15:37     ` Przemysław Chwiała

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=1D32D17E-126F-413C-9F22-2E5CCF20E61F@gmail.com \
    --to=przemekchwiala@gmail.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).