From: Arkadiusz Miskiewicz <arekm@maven.pl>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.5.2.2
Date: Sun, 17 Jun 2007 12:30:37 +0200 [thread overview]
Message-ID: <200706171230.37659.arekm@maven.pl> (raw)
In-Reply-To: <7vodjf1gxl.fsf@assigned-by-dhcp.pobox.com>
On Sunday 17 of June 2007, Junio C Hamano wrote:
> The latest maintenance release GIT 1.5.2.2 is available at the
> usual places:
>
> http://www.kernel.org/pub/software/scm/git/
>
> git-1.5.2.2.tar.{gz,bz2} (tarball)
> git-htmldocs-1.5.2.2.tar.{gz,bz2} (preformatted docs)
> git-manpages-1.5.2.2.tar.{gz,bz2} (preformatted docs)
> RPMS/$arch/git-*-1.5.2.2-1.$arch.rpm (RPM)
Should git testsuite (make test) go without any problem? (I'm asking because
some projects have test suites where some tests are expected to fail).
I have 4 failures on amd64/linux and this git release:
* FAIL 11: compare delta flavors
perl -e '
defined($_ = -s $_) or die for @ARGV;
exit 1 if $ARGV[0] <= $ARGV[1];
' test-2-$packname_2.pack test-3-$packname_3.pack
[...]
* FAIL 16: corrupt a pack and see if verify catches
cat test-1-${packname_1}.idx >test-3.idx &&
cat test-2-${packname_2}.pack >test-3.pack &&
if git-verify-pack test-3.idx
then false
else :;
fi &&
: PACK_SIGNATURE &&
cat test-1-${packname_1}.pack >test-3.pack &&
dd if=/dev/zero of=test-3.pack count=1 bs=1 conv=notrunc seek=2
&&
if git-verify-pack test-3.idx
then false
else :;
fi &&
: PACK_VERSION &&
cat test-1-${packname_1}.pack >test-3.pack &&
dd if=/dev/zero of=test-3.pack count=1 bs=1 conv=notrunc seek=7
&&
if git-verify-pack test-3.idx
then false
else :;
fi &&
: TYPE/SIZE byte of the first packed object data &&
cat test-1-${packname_1}.pack >test-3.pack &&
dd if=/dev/zero of=test-3.pack count=1 bs=1 conv=notrunc seek=12
&&
if git-verify-pack test-3.idx
then false
else :;
fi &&
: sum of the index file itself &&
l=`wc -c <test-3.idx` &&
l=`expr $l - 20` &&
cat test-1-${packname_1}.pack >test-3.pack &&
dd if=/dev/zero of=test-3.idx count=20 bs=1 conv=notrunc seek=$l
&&
if git-verify-pack test-3.pack
then false
else :;
fi &&
:
[...]
* FAIL 18: fake a SHA1 hash collision
test -f .git/objects/c8/2de19312b6c3695c0c18f70709a6c535682a67 &&
cp -f .git/objects/9d/235ed07cd19811a6ceb342de82f190e49c9f68
\
.git/objects/c8/2de19312b6c3695c0c18f70709a6c535682a67
* FAIL 19: make sure index-pack detects the SHA1 collision
git-index-pack -o bad.idx test-3.pack
* failed 4 among 19 test(s)
--
Arkadiusz Miśkiewicz PLD/Linux Team
arekm / maven.pl http://ftp.pld-linux.org/
next prev parent reply other threads:[~2007-06-17 10:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 1:57 [ANNOUNCE] GIT 1.5.2.2 Junio C Hamano
2007-06-17 10:30 ` Arkadiusz Miskiewicz [this message]
2007-06-18 3:43 ` Shawn O. Pearce
2007-06-18 6:21 ` Arkadiusz Miskiewicz
2007-06-18 6:29 ` Shawn O. Pearce
2007-06-18 6:35 ` Arkadiusz Miskiewicz
2007-06-18 3:27 ` Shawn O. Pearce
2007-06-20 8:34 ` Jakub Narebski
2007-07-12 20:57 ` [ANNOUNCE] GIT 1.5.2.4 Junio C Hamano
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=200706171230.37659.arekm@maven.pl \
--to=arekm@maven.pl \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).