All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joanna Rutkowska <joanna@invisiblethingslab.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Different xen-3.4.3.tar.gz in Fedora RPM
Date: Fri, 18 Jun 2010 14:10:26 +0200	[thread overview]
Message-ID: <4C1B6232.1050705@invisiblethingslab.com> (raw)


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

So, the MD5 for the xen-3.4.3.tar.gz I downloaded from:

http://bits.xensource.com/oss-xen/release/3.4.3/xen-3.4.3.tar.gz

which for me reads:

f8d001eb9e08525c451d38deb93908b1

is *different* than expected by Fedora F13 RPM:

http://cvs.fedoraproject.org/viewvc/F-13/xen/sources?revision=1.59&view=markup

which is:

cbe84c44bc156ad1b4a20dc1c73464b8

So, I downloaded xen-3.4.3.tar.gz from fedora mirror (using their
original Makefile for RPM building), and diffed the two versions --
changes (cosmetic cleanup mostly) are innocent, but, hey, why would
anybody do such a thing? After allm we would expect only one version of
xen-XXX.tar.gz, right? Patches should be the proper way for customizing
tarballs for packaging, no?

Or am I missing something?

joanna.


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 226 bytes --]

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

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

             reply	other threads:[~2010-06-18 12:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-18 12:10 Joanna Rutkowska [this message]
2010-06-18 12:23 ` Different xen-3.4.3.tar.gz in Fedora RPM Joanna Rutkowska
2010-06-18 12:39   ` Pasi Kärkkäinen
2010-06-18 13:25     ` M A Young
2010-06-18 12:57 ` Keir Fraser
2010-06-18 13:07   ` Joanna Rutkowska
2010-06-18 13:19     ` Keir Fraser
2010-06-18 15:42       ` Ian Jackson
2010-06-18 16:00         ` Joanna Rutkowska
2010-06-18 13:47   ` M A Young
2010-06-18 13:31 ` John Haxby

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=4C1B6232.1050705@invisiblethingslab.com \
    --to=joanna@invisiblethingslab.com \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.