From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] git source checkout checksum error
Date: Wed, 3 Aug 2016 10:10:36 +0200 [thread overview]
Message-ID: <20160803081036.GW17874@pengutronix.de> (raw)
In-Reply-To: <20160803075930.GF11824@pengutronix.de>
On Wed, Aug 03, 2016 at 09:59:31AM +0200, Michael Olbrich wrote:
> Hi,
>
> On Tue, Aug 02, 2016 at 11:00:50AM +0000, Gieseler, Christian wrote:
> > I have some trouble with the download of trace-cmd on my centos 6
> >
> > $ ./p targetinstall trace-cmd
> >
> > -------------------------------
> > target: trace-cmd-2.5.2.tar.bz2
> > -------------------------------
> >
> > git: fetching 'http://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git into '/globalPtxdistsrc/git.kernel.org.pub.scm.linux.kernel.git.rostedt.trace-cmd.git'...
> > Initialized empty shared Git repository in /globalPtxdistsrc/git.kernel.org.pub.scm.linux.kernel.git.rostedt.trace-cmd.git/
> > remote: Counting objects: 7375, done.
> > remote: Total 7375 (delta 0), reused 0 (delta 0)
> > Receiving objects: 100% (7375/7375), 3.21 MiB | 1.12 MiB/s, done.
> > Resolving deltas: 100% (5575/5575), done.
> > From http://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd
> > * [new branch] master -> master
> > * [new branch] rfc/profile -> rfc/profile
> > * [new branch] trace-cmd-stable-v1 -> trace-cmd-stable-v1
> > ...
> > snip
> > ...
> > * [new tag] trace-cmd-v2.5.4 -> trace-cmd-v2.5.4
> > * [new tag] trace-cmd-v2.6 -> trace-cmd-v2.6
> >
> > ---------------------
> > target: trace-cmd.get
> > ---------------------
> >
> > ptxdist: error: Wrong md5sum for 'trace-cmd' (/globalPtxdistsrc/trace-cmd-2.5.2.tar.bz2)
> > make: *** [/home/christian/3.linuxBSP/eks-ptxdist-bsp/platform-e-light/state/trace-cmd.get] Error 1
> >
> > On the other hand it works fine on centos 7.
> > git: fetching 'http://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git into '/buildserverhome/globalPtxdistsrc/git.kernel.org.pub.scm.linux.kernel.git.rostedt.trace-cmd.git'...
> [...]
> > Git checkout trace-cmd-v2.5.2 results in the same response HEAD is now at 63df703... trace-cmd: Version 2.5.2 Still the checkout is not the same as the diff above shows.
> > Centos 6 has git version 1.7.1. Centos 7 1.8.3.1.
> > Has someone an idea whats wrong here.
>
> PTXdist uses git-archive to generate the tarballs. I'm guessing, somthing
> changed there. Try to compare the resulting tarballs to see what changed.
Do a good and a bad .tar.bz2 match when unpacked?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-08-03 8:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 11:00 Gieseler, Christian
2016-08-03 7:59 ` Michael Olbrich
2016-08-03 8:10 ` Uwe Kleine-König [this message]
2016-08-03 8:44 ` Gieseler, Christian
2016-08-03 10:11 ` Michael Olbrich
2016-08-03 11:06 ` Gieseler, Christian
2016-08-03 11:09 ` Uwe Kleine-König
2016-08-03 12:30 ` Gieseler, Christian
2016-08-04 6:38 ` Michael Olbrich
2016-08-04 6:50 ` Gieseler, Christian
2016-08-04 6:59 ` Michael Olbrich
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=20160803081036.GW17874@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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