Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Christian Stewart <christian@aperture.us>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 1/1] package/docker-compose: bump version to v2.27.0
Date: Sun, 2 Jun 2024 11:00:55 +0200	[thread overview]
Message-ID: <Zlw0x-GMNwen_N31@landeda> (raw)
In-Reply-To: <20240511235609.88305-1-christian@aperture.us>

Christian, All,

On 2024-05-11 16:56 -0700, Christian Stewart via buildroot spake thusly:
> https://github.com/docker/compose/releases/tag/v2.27.0
> 
> Signed-off-by: Christian Stewart <christian@aperture.us>

We have a download failure for docker-compose (as noticed by Peter):

    http://autobuild.buildroot.net/results/cd3a19e9172fb49591fe3a1a7da28c09a4919495/build-end.log

    ERROR: while checking hashes from package/docker-compose/docker-compose.hash
    ERROR: docker-compose-2.27.0-go2.tar.gz has wrong sha256 hash:
    ERROR: expected: 448eaf225c2984a2d78b4faa3fe74a4aa1e2bb791f90ac8d4970d3d046e638df
    ERROR: got     : 42e9d2a33806656bd145ec742a3ba00b64acc3f88b500793d3b78319c39e25e0
    ERROR: Incomplete download, or man-in-the-middle (MITM) attack

I can't even reproduce localy, with this defconfig for example:

    $ cat <<_EOF_ >.config
    BR2_aarch64=y
    BR2_TOOLCHAIN_EXTERNAL=y
    BR2_TOOLCHAIN_EXTERNAL_BOOTLIN=y
    BR2_PACKAGE_DOCKER_CLI=y
    BR2_PACKAGE_DOCKER_COMPOSE=y
    _EOF_
    $ make oldddefconfig

    $ make docker-compose-source
    [...]
    go: downloading dario.cat/mergo v1.0.0
    [...]
    go: downloading github.com/imdario/mergo v0.3.16
    [...]
    go: github.com/docker/compose/v2/cmd/compose imports
            github.com/docker/cli/cli/command/container imports
            github.com/docker/cli/cli/compose/loader imports
            dario.cat/mergo: unrecognized import path "dario.cat/mergo": https fetch: Get "https://dario.cat/mergo?go-get=1": dial tcp: lookup dario.cat on 127.0.0.53:53: server misbehaving

As I understand it, dario.cat is a "vanity URL" [0] so it should not be
resolved by the resolver, but by go-pkg, but apparently that did not
happen for me...

Do you have any idea what's going on?

[0] https://pkg.go.dev/dario.cat/mergo#readme-important-notes

Regards,
Yann E. MORIN.

> ---
>  package/docker-compose/docker-compose.hash | 2 +-
>  package/docker-compose/docker-compose.mk   | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/package/docker-compose/docker-compose.hash b/package/docker-compose/docker-compose.hash
> index cda4a130d5..1fd454e3fa 100644
> --- a/package/docker-compose/docker-compose.hash
> +++ b/package/docker-compose/docker-compose.hash
> @@ -1,3 +1,3 @@
>  # Locally computed
> -sha256  821aac932d0a3bbe583ea290ae777cec785a77f987c5007a30970fa6568e9322  docker-compose-2.26.1-go2.tar.gz
> +sha256  448eaf225c2984a2d78b4faa3fe74a4aa1e2bb791f90ac8d4970d3d046e638df  docker-compose-2.27.0-go2.tar.gz
>  sha256  58d1e17ffe5109a7ae296caafcadfdbe6a7d176f0bc4ab01e12a689b0499d8bd  LICENSE
> diff --git a/package/docker-compose/docker-compose.mk b/package/docker-compose/docker-compose.mk
> index 66a88ac7e7..32b2236a91 100644
> --- a/package/docker-compose/docker-compose.mk
> +++ b/package/docker-compose/docker-compose.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -DOCKER_COMPOSE_VERSION = 2.26.1
> +DOCKER_COMPOSE_VERSION = 2.27.0
>  DOCKER_COMPOSE_SITE = $(call github,docker,compose,v$(DOCKER_COMPOSE_VERSION))
>  DOCKER_COMPOSE_LICENSE = Apache-2.0
>  DOCKER_COMPOSE_LICENSE_FILES = LICENSE
> -- 
> 2.43.0
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2024-06-02  9:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-11 23:56 [Buildroot] [PATCH v1 1/1] package/docker-compose: bump version to v2.27.0 Christian Stewart via buildroot
2024-05-12  7:06 ` Thomas Petazzoni via buildroot
2024-06-02  9:00 ` Yann E. MORIN [this message]
2024-06-02 10:26   ` Peter Korsgaard
2024-06-04 13:14     ` Peter Korsgaard
2024-06-04 15:47       ` Christian Stewart via buildroot
2024-06-04 16:03         ` Yann E. MORIN
2024-06-04 16:18         ` Yann E. MORIN
2024-06-04 18:01           ` Christian Stewart via buildroot
2024-06-04 21:20             ` Yann E. MORIN

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=Zlw0x-GMNwen_N31@landeda \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=christian@aperture.us \
    --cc=thomas.petazzoni@bootlin.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox