[Buildroot] [PATCH v1 1/1] package/docker-compose: bump version to v2.27.0

[Buildroot] [PATCH v1 1/1] package/docker-compose: bump version to v2.27.0

[Christian Stewart via buildroot]

https://github.com/docker/compose/releases/tag/v2.27.0

Signed-off-by: Christian Stewart <christian@aperture.us>
---
 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

Re: [Buildroot] [PATCH v1 1/1] package/docker-compose: bump version to v2.27.0

[Thomas Petazzoni via buildroot]

On Sat, 11 May 2024 16:56:09 -0700
Christian Stewart via buildroot <buildroot@buildroot.org> wrote:

> https://github.com/docker/compose/releases/tag/v2.27.0
> 
> Signed-off-by: Christian Stewart <christian@aperture.us>
> ---
>  package/docker-compose/docker-compose.hash | 2 +-
>  package/docker-compose/docker-compose.mk   | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH v1 1/1] package/docker-compose: bump version to v2.27.0

[Yann E. MORIN]

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

Re: [Buildroot] [PATCH v1 1/1] package/docker-compose: bump version to v2.27.0

[Peter Korsgaard]

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

Hi,

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

I believe the domain simply expired:

Registry Expiry Date: 2024-06-01T07:05:04.361

I reported it upstream to their issue tracker:

https://github.com/darccio/mergo/issues/252

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH v1 1/1] package/docker-compose: bump version to v2.27.0

[Peter Korsgaard]

>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:

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

 > I believe the domain simply expired:

 > Registry Expiry Date: 2024-06-01T07:05:04.361

 > I reported it upstream to their issue tracker:

 > https://github.com/darccio/mergo/issues/252

This is now fixed:

Registry Expiry Date: 2025-06-01T07:05:04.361Z

But we still have the hash mismatch:

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

What to do? Do we have the original tarball somewhere so we can compare
to see what changed? I see there is a 2.27.1 version that we could bump
to but I would feel more confident if we understood what went wrong
here.

https://github.com/docker/compose/releases/tag/v2.27.1

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH v1 1/1] package/docker-compose: bump version to v2.27.0

[Christian Stewart via buildroot]

[-- Attachment #1.1: Type: text/plain, Size: 2265 bytes --]

Peter,

On Tue, Jun 4, 2024, 6:15 AM Peter Korsgaard <peter@korsgaard.com> wrote:

> >>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
>
>  >> $ 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...
>
>  > I believe the domain simply expired:
>
>  > Registry Expiry Date: 2024-06-01T07:05:04.361
>
>  > I reported it upstream to their issue tracker:
>
>  > https://github.com/darccio/mergo/issues/252
>
> This is now fixed:
>
> Registry Expiry Date: 2025-06-01T07:05:04.361Z
>
> But we still have the hash mismatch:
>
> 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
>
> What to do? Do we have the original tarball somewhere so we can compare
> to see what changed? I see there is a 2.27.1 version that we could bump
> to but I would feel more confident if we understood what went wrong
> here.
>

Is this the correct version? (I'm on my phone and don't have a chance to
check right now).

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

Thanks,
Christian Stewart

[-- Attachment #1.2: Type: text/html, Size: 4270 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH v1 1/1] package/docker-compose: bump version to v2.27.0

[Yann E. MORIN]

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

Yes, that archive doies have the hash currently in Buildroot.

> 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

I'm investigating...

Thanks!

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

Re: [Buildroot] [PATCH v1 1/1] package/docker-compose: bump version to v2.27.0

[Yann E. MORIN]

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

Re: [Buildroot] [PATCH v1 1/1] package/docker-compose: bump version to v2.27.0

[Christian Stewart via buildroot]

[-- Attachment #1.1: Type: text/plain, Size: 3096 bytes --]

Yann,

On Tue, Jun 4, 2024, 9:18 AM Yann E. MORIN <yann.morin.1998@free.fr> wrote:

> 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?
>

I'm using "make foo-extract" and then hashing the file in dl/

Why is the buildroot host tar not used for this?

Thanks!
Christian

[-- Attachment #1.2: Type: text/html, Size: 3785 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH v1 1/1] package/docker-compose: bump version to v2.27.0

[Yann E. MORIN]

Christian, All,

On 2024-06-04 11:01 -0700, Christian Stewart via buildroot spake thusly:
> I'm using "make foo-extract" and then hashing the file in dl/
> 
> Why is the buildroot host tar not used for this?

Long story short: it should, but if you export TAR in the environment,
then it does not. That's a known issue, I'm working on it...

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