unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: John Kehayias via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "50665@debbugs.gnu.org" <50665@debbugs.gnu.org>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: bug#50665: Docker 19.03 is no longer receiving updates.
Date: Tue, 28 Jun 2022 00:36:02 +0000	[thread overview]
Message-ID: <vAJvNVcSvaTGAle7fafLgo9fgkHFIQcYHD2oKV8ZF33jooTaXGj63fj_9VFOzzf2feL_Y0NSC-21kGbcWcV3G9zyx_jVV9HOzizhpobbXrk=@protonmail.com> (raw)
In-Reply-To: <86o88phcbf.fsf@mgsn.dev>

Hello,

I believe this can be closed with Docker having been updated to the latest version in this patch series: https://issues.guix.gnu.org/52790

However, on the Go front, this leaves docker-compose to be updated to v2 which moves to Go. I tried to import the go package definition but it fails if using recursive to get the (many many) dependencies:

guix import go github.com/docker/compose/v2 -r
...
ice-9/boot-9.scm:1683:16: In procedure raise-exception:
Git error: reference 'refs/tags/v0.30.0' not found

In just doing the base package and finding what dependencies are missing, I hit this again with

guix import go k8s.io/client-go -r
...
ice-9/boot-9.scm:1683:16: In procedure raise-exception:
Git error: reference 'refs/tags/v0.9.20' not found

Anyway, I should open (after searching for any relevant issues) an issue for the Go importer and/or docker-compose updates. Just thought I capture what I've seen so far in trying to complete the Docker update.

John




  parent reply	other threads:[~2022-06-28  0:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-18 20:13 bug#50665: Docker 19.03 is no longer receiving updates Sarah Morgensen
2021-09-23  3:47 ` Maxim Cournoyer
2022-06-28  0:36 ` John Kehayias via Bug reports for GNU Guix [this message]
2022-07-06 13:03   ` Maxim Cournoyer

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='vAJvNVcSvaTGAle7fafLgo9fgkHFIQcYHD2oKV8ZF33jooTaXGj63fj_9VFOzzf2feL_Y0NSC-21kGbcWcV3G9zyx_jVV9HOzizhpobbXrk=@protonmail.com' \
    --to=bug-guix@gnu.org \
    --cc=50665@debbugs.gnu.org \
    --cc=john.kehayias@protonmail.com \
    --cc=maxim.cournoyer@gmail.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).