From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Brian Buchalter <bal711@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: error: unable to create file: Illegal byte sequence
Date: Sat, 3 Feb 2018 10:01:52 +0100 [thread overview]
Message-ID: <CACBZZX4qH-w3YevoaW8RXAoFrjpfGerLWpBhetrO2tV-FGr3cQ@mail.gmail.com> (raw)
In-Reply-To: <CAANr7CBNhkYJ=u8Bq-NG3KkSYY8yczJCt_25KcZU4VMFsS399A@mail.gmail.com>
On Sat, Feb 3, 2018 at 4:17 AM, Brian Buchalter <bal711@gmail.com> wrote:
> I am attempting to repair a git repo which has an illegal byte
> sequence but am not sure how to proceed. Steps to reproduce: `git
> clone https://github.com/christopherpow/nes-test-roms.git` results in:
>
> ```
> Cloning into 'nes-test-roms'...
> remote: Counting objects: 1049, done.
> remote: Total 1049 (delta 0), reused 0 (delta 0), pack-reused 1049
> Receiving objects: 100% (1049/1049), 5.23 MiB | 8.97 MiB/s, done.
> Resolving deltas: 100% (406/406), done.
> error: unable to create file other/Duelito - L�eme.txt: Illegal byte sequence
> fatal: unable to checkout working tree
> warning: Clone succeeded, but checkout failed.
> You can inspect what was checked out with 'git status'
> and retry the checkout with 'git checkout -f HEAD'
> ```
You can clone my fork of this which fixes the issue:
https://github.com/avar/nes-test-roms
As for fixing this yourself, if your FS can't represent files in the
repo the easiest thing is to clone it on a VM with an OS that can
(e.g. Linux), or alternatively (and harder for non-experts) is to
clone it with --bare and manually create a fixed tree with the various
plumbing commands mentioned in "man git".
prev parent reply other threads:[~2018-02-03 9:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-03 3:17 error: unable to create file: Illegal byte sequence Brian Buchalter
2018-02-03 9:01 ` Ævar Arnfjörð Bjarmason [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACBZZX4qH-w3YevoaW8RXAoFrjpfGerLWpBhetrO2tV-FGr3cQ@mail.gmail.com \
--to=avarab@gmail.com \
--cc=bal711@gmail.com \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).