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 Mailing List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v1 1/1] package/docker-compose: bump version to v2.27.0
Date: Tue, 4 Jun 2024 18:18:20 +0200	[thread overview]
Message-ID: <Zl8-TDOdLCh5dq42@landeda> (raw)
In-Reply-To: <CA+h8R2qZ8dVMUH94QN85v5Vms1RtNXM5k4VR+5AqBHEOJzzwDg@mail.gmail.com>

Christian, All,

On 2024-06-04 08:47 -0700, Christian Stewart spake thusly:
> Is this the correct version? (I'm on my phone and don't have a chance to check
> right now).
> [15]https://mirror.skiffos.com/docker-compose/docker-compose-2.27.0-go2.tar.gz
> It seems to me that there is a difference between either Go versions vendor/
> format OR there is a difference between architectures (amd64 or arm). 
> Hopefully we can tell the difference from the tarball above

The deltas are all of the form of that one:

--- docker-compose-2.27.0-go2.tar.42e9d2.hex    2024-06-04 18:07:33.538588495 +0200
+++ docker-compose-2.27.0-go2.tar.448eaf.hex    2024-06-04 18:07:39.737437043 +0200
@@ -7,7 +7,7 @@
 00000060  00 00 00 00 30 30 30 30  36 34 34 00 30 30 30 30 |....0000644.0000|
 00000070  30 30 30 00 30 30 30 30  30 30 30 00 30 30 30 30 |000.0000000.0000|
 00000080  30 30 30 30 30 30 35 00  31 34 36 31 32 32 35 33 |0000005.14612253|
-00000090  32 33 36 00 30 31 34 31  31 35 00 20 30 00 00 00 |236.014115. 0...|
+00000090  32 33 36 00 30 31 35 33  35 35 00 20 30 00 00 00 |236.015355. 0...|
 000000a0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 |................|
 000000b0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 |................|
 000000c0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 |................|
@@ -18,8 +18,8 @@
 00000110  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 |................|
 00000120  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 |................|
 00000130  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 |................|
-00000140  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 |................|
-00000150  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 |................|
+00000140  00 00 00 00 00 00 00 00  00 30 30 30 30 30 30 30 |.........0000000|
+00000150  00 30 30 30 30 30 30 30  00 00 00 00 00 00 00 00 |.0000000........|
 00000160  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 |................|
 00000170  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 |................|
 00000180  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 |................|

The --- is the archive Peter and I generated, the +++ is yours.

What this shows, is that the dev major/minor fields are NULs for us,
while they are 0 (zero), ASCII 0x30) in your case.

This is exactly the change that went in in tar 1.35: our archives were
generated with tar 1.35, yours with an older tar (presumably, 1.34).

Peter had a similar issue, as he used to set the TAR environment
variable to point to a pre-built tar 1.35, like so:

    $ TAR=tar-1.35 make source

Are you doing something similar by chance?

In any case, the hash Peter and I get is the correct one, yours had a
fluke...

Thanks for providing your tarball, it helped right away! 👍

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  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-04 16:18 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
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 [this message]
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=Zl8-TDOdLCh5dq42@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