mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2 0/3] Freescale/NXP i.MX mfgtools 3.0
Date: Fri, 27 Mar 2020 14:16:13 +0100	[thread overview]
Message-ID: <20200327131613.GA29632@ravnborg.org> (raw)
In-Reply-To: <20200327124152.GC5618@pengutronix.de>

Hi Michael.

On Fri, Mar 27, 2020 at 01:41:52PM +0100, Michael Olbrich wrote:
> On Thu, Mar 26, 2020 at 05:03:57PM +0000, Denis Osterland-Heim wrote:
> > v1->v2:
> >  - 1/3 use tabs for defines, suggested by Roland Hiebler
> >  - 1/3 add dummy version before git hash, suggested by Michael Olbricht,
> >        Roland Hiebler and Guillermo Rodriguez Garcia
> >  - 1/3 remove obsolete CREDITS reference, suggested by Roland Hiebler
> >  - 3/3 version bump to 1.3.154
> >  - 3/3 write .tarball-version in extract.post, suggested by Michael Olbricht
> > 
> > 
> > This patch series adds support for the Freescale/NXP mfgtools 3.0.
> > You can use them with vanilla kernel and barebox.
> > 
> > There are two known issues:
> >  - the git downloads => no stable md5 sum
> 
> Huh? I've not seen any changing md5 sums for such gitlab URLs.
> And the previous explicit git downloads used git-archive. The  md5 sums
> should be stable as well for such URLs.

This reminds me of something reported for buildroot - fixed
by following commit:

commit 2218dc85bef9bb1c9d27788e5ac69593144fe268
Author: Yann E. MORIN <yann.morin.1998@free.fr>
Date:   Sat Nov 17 18:15:51 2018 +0100

    support/dependencies: add a check for a suitable gzip

    Recently, some hash mismatch have been reported, both by users as well
    as autobuilder failures, about tarballs generated from git repositories.

    This turned out to be caused by users having the 'gzip' command somehow
    aliased to 'pigz' (which stand for: parallel implementation of gzip,
    which takes advantage of multi-processor system to parallelise the
    compression).

    ...

If this is even remotely relevant for ptxdist I let you conclude.
I remember because I was hit by this when I toyed with buildroot
some time ago.

	Sam

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      parent reply	other threads:[~2020-03-27 13:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 17:03 Denis Osterland-Heim
2020-03-26 17:03 ` [ptxdist] [PATCH v2 1/3] imx-uuc: new package Denis Osterland-Heim
2020-03-27 12:06   ` Michael Olbrich
2020-03-27 13:07     ` Denis Osterland-Heim
2020-03-31  5:29     ` [ptxdist] [PATCH v2] fixup! " Denis Osterland-Heim
2020-04-01 15:08       ` Michael Olbrich
2020-04-02  6:28         ` Denis Osterland-Heim
2020-04-02  6:39           ` Michael Olbrich
2020-04-02 15:03   ` [ptxdist] [v2] " Michael Olbrich
2020-04-03  5:58   ` [ptxdist] [APPLIED] [v2,1/3] " Michael Olbrich
2020-03-26 17:03 ` [ptxdist] [PATCH v2 3/3] host-mfgtools: " Denis Osterland-Heim
2020-04-02 15:03   ` [ptxdist] [v2,3/3] " Michael Olbrich
2020-03-26 17:03 ` [ptxdist] [PATCH v2 2/3] host-libzip: " Denis Osterland-Heim
2020-04-03  5:58   ` [ptxdist] [APPLIED] [v2,2/3] " Michael Olbrich
2020-03-27 12:41 ` [ptxdist] [PATCH v2 0/3] Freescale/NXP i.MX mfgtools 3.0 Michael Olbrich
2020-03-27 13:01   ` Denis Osterland-Heim
2020-03-27 13:16   ` Sam Ravnborg [this message]

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=20200327131613.GA29632@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=ptxdist@pengutronix.de \
    /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