Your message dated Thu, 28 Jan 2010 14:37:40 +0000
with message-id <20100128143734.gt30...@deprecation.cyrius.com>
and subject line Re: Bug#547503: git-core: "git clone" fails on armel
has caused the Debian Bug report #547503,
regarding git-core: "git clone" fails on armel
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
547503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: git-core
Version: 1:1.6.3.3-2
Severity: important
git clone fails on my Debian armel system:
sascha.si...@flatty:~$ git clone
git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild
Initialized empty Git repository in /home/sascha.silbe/sugar-jhbuild/.git/
remote: Counting objects: 4772, done.
remote: Compressing objects: 100% (2079/2079), done.
error: inflate: data stream error (invalid distance too far back)
fatal: pack has bad object at offset 616818: inflate returned -3
fatal: index-pack failed
sascha.si...@flatty:~$ git clone git://git.gnome.org/jhbuild
Initialized empty Git repository in /home/sascha.silbe/jhbuild/.git/
remote: Counting objects: 19804, done.
remote: Compressing objects: 100% (6374/6374), done.
fatal: pack has bad object at offset 487227: inflate returned -5
fatal: index-pack failed
sascha.si...@flatty:~$
The same repositories can be checked out fine on a Debian i386 system (inside
the same network):
sascha.si...@caravan:/tmp/sascha_silbe/tmpbox.PjGIP1AEY7$ git clone
git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild
Initialized empty Git repository in
/tmp/sascha_silbe/tmpbox.PjGIP1AEY7/sugar-jhbuild/.git/
remote: Counting objects: 4772, done.
remote: Compressing objects: 100% (2079/2079), done.
remote: Total 4772 (delta 2815), reused 4486 (delta 2638)
Receiving objects: 100% (4772/4772), 1.88 MiB | 607 KiB/s, done.
Resolving deltas: 100% (2815/2815), done.
sascha.si...@caravan:/tmp/sascha_silbe/tmpbox.PjGIP1AEY7$
strace doesn't show anything unusual; ltrace seems stuck inside an infinite
loop of "unexpected instruction 0xe5bcf76c at 0xac08" (addresses not changing)
if given "-f" to trace children (and without "-f" doesn't show anything useful).
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: armel (armv5tel)
Kernel: Linux 2.6.31-rc9-flatty-ocf-1-00293-g53a104c (PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages git-core depends on:
ii libc6 2.9-25 GNU C Library: Shared libraries
ii libcurl3-gnutls 7.19.5-1.1 Multi-protocol file transfer libra
ii libdigest-sha1-perl 2.12-1 NIST SHA-1 message digest algorith
ii liberror-perl 0.17-1 Perl module for error/exception ha
ii libexpat1 2.0.1-4 XML parsing C library - runtime li
ii libgcc1 1:4.4.1-1 GCC support library
ii perl-modules 5.10.0-25 Core Perl modules
ii zlib1g 1:1.2.3.3.dfsg-15+b2 compression library - runtime
Versions of packages git-core recommends:
ii less 436-1+b1 pager program similar to more
ii openssh-client [ssh-client] 1:5.1p1-7+b1 secure shell client, an rlogin/rsh
ii patch 2.5.9-5 Apply a diff file to an original
ii rsync 3.0.6-1 fast remote file copy program (lik
Versions of packages git-core suggests:
pn git-arch <none> (no description available)
pn git-cvs <none> (no description available)
pn git-daemon-run <none> (no description available)
pn git-doc <none> (no description available)
pn git-email <none> (no description available)
pn git-gui <none> (no description available)
pn git-svn <none> (no description available)
pn gitk <none> (no description available)
pn gitweb <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
* Jonathan Nieder <jrnie...@gmail.com> [2010-01-27 16:50]:
> The bug is in your hands now. :) If you want to try to reproduce it,
> I'd suggest reverting that commit on an armel machine and watching the
> fireworks. If you don't want to reproduce it, I think it should be
> pretty safe to close.
You showed that the bug is fixed in 2.6.32 and testing has 2.6.32 now,
so imho there's nothing left to do now. Furthermore, it seems the bug
was in highmem code and none of the Debian armel kernels enable
highmem. Closing.
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
