From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Different MD5 sums of glibc-ports-2.13.tar.bz2
Date: Thu, 27 Oct 2011 17:23:39 +0200 [thread overview]
Message-ID: <20111027152339.GH30634@pengutronix.de> (raw)
In-Reply-To: <4EA000BC.9030805@corscience.de>
On Thu, Oct 20, 2011 at 01:06:36PM +0200, Bernhard Seßler wrote:
> Comparing the package glibc-ports-2.13.tar.bz2 from
> http://www.pengutronix.de/software/ptxdist/temporary-src/glibc/glibc-ports-2.13.tar.bz2
> with the same package from other ptxdist mirrors
> ( e.g. http://ftp.uni-kl.de/pub/gnu/glibc/glibc-ports-2.13.tar.bz2 )
> shows that these packages have different MD5 sums:
>
> 99662ee86e19c36dd6605784c4774dd2 glibc-ports-2.13.pengutronix.tar.bz2
> 483f37cfdd619e81d8ca9e9d713944b5 glibc-ports-2.13.uni-kl.tar.bz2
>
> Doing a 'diff -r' on the extracted directories shows that the
> contents of both archives seem to be identical, but the timestamps
> and sizes differ.
> 'ls -l' shows:
>
> bsessler bsessler 625584 2011-02-07 20:12 glibc-ports-2.13.pengutronix.tar.bz2
> bsessler bsessler 625945 2011-03-06 20:12 glibc-ports-2.13.uni-kl.tar.bz2
>
> Building the OSELAS Toolchain 2010.03 therefore results in an error,
> if ptxdist attempts to use the package from the pengutronix mirror:
[...]
We created the one on the pengutronix mirror because at first upstream did
not provide a package. Now that the upstream package is available I guess I
should remove the one on our mirror.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2011-10-27 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 11:06 Bernhard Seßler
2011-10-27 15:23 ` Michael Olbrich [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=20111027152339.GH30634@pengutronix.de \
--to=m.olbrich@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