From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7016] New: Git issues in resulting buildroot tar
Date: Tue, 1 Apr 2014 19:41:38 +0000 (UTC) [thread overview]
Message-ID: <bug-7016-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=7016
Summary: Git issues in resulting buildroot tar
Product: buildroot
Version: 2014.02
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: brian at brianclements.net
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Hi There,
Sorry if this isn't the correct place for this bug, please forward me if so.
I've built a pretty standard busybox chain using many different options and
versions of git by this point, but the end result has been the same: using git
in this freshly built image fails on anything involved decompressing objects
(git clone among other things).
The context here has been to make a Docker image of busybox with a complete git
install contained therein. All my reproducible steps are here:
https://github.com/brianclements/dockerfile-busyboxplus/blob/gitbug/tarmaker/Dockerfile
I've even tried substituting different versions of buildroot (2013.08.1,
2014.02) and different versions of git (1.8.3, 1.8.5.3, 1.9.0) all with the
same result. The build succeeds, and the resulting image works as far as I can
tell, but running "git clone" on a larger repository that involves compression
of objects (smaller repos of text only work fine) will fail with:
fatal: serious inflate inconsistency
fatal: index-pack failed
Any thoughts or further testing I can try to tweak the git build?
Thanks.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2014-04-01 19:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 19:41 bugzilla at busybox.net [this message]
2014-04-02 7:35 ` [Buildroot] [Bug 7016] Git issues in resulting buildroot tar bugzilla at busybox.net
2014-04-07 7:26 ` brianclements
2014-04-07 13:38 ` Thomas De Schampheleire
2014-04-07 18:59 ` brianclements
2014-04-11 13:40 ` Thomas De Schampheleire
2014-04-22 20:02 ` Thomas De Schampheleire
2014-05-01 18:25 ` brianclements
2014-05-01 18:35 ` Thomas De Schampheleire
2014-05-01 20:26 ` brianclements
2014-05-02 5:35 ` Thomas De Schampheleire
2014-05-02 6:14 ` brianclements
2014-05-05 9:50 ` Thomas De Schampheleire
2014-05-08 12:02 ` bugzilla at busybox.net
2014-05-14 8:13 ` bugzilla at busybox.net
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=bug-7016-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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.