From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] hg on plan 9
Date: Thu, 27 Oct 2011 00:26:38 -0700 [thread overview]
Message-ID: <CABwSpPD2Zm5Ha=gjB40a89QBWZB+0Cmb277VuNMdEa-UD4cknQ@mail.gmail.com> (raw)
In-Reply-To: <f373eb4c863014d57a355420f533b69c@ladd.quanstro.net>
I made a change to hg:
mercurial/store.py:
in def _buildencodefun():
- win_reserved = [ord(x) for x in '\\:*?"<>|']
+ win_reserved = [ord(x) for x in '\\:*?"<>| ']
in def _build_lower_encodefun():
- win_reserved = [ord(x) for x in '\\:*?"<>|']
+ win_reserved = [ord(x) for x in '\\:*?"<>| ']
This got me through the errors with filenames
with spaces in them (it converts spaces to '~')
but I have errors of a different sort now:
cpu% hg clone https://code.google.com/p/nix-os/
destination directory: nix-os
requesting all changes
adding changesets
adding manifests
adding file changes
added 112 changesets with 14878 changes to 14527 files
updating working directory
Traceback (most recent call last):
File "/bin/hg", line 31, in <module>
mercurial.dispatch.run()
File "./mercurial/dispatch.py", line 16, in run
File "./mercurial/dispatch.py", line 27, in dispatch
File "./mercurial/dispatch.py", line 43, in _runcatch
File "./mercurial/dispatch.py", line 449, in _dispatch
File "./mercurial/dispatch.py", line 317, in runcommand
File "./mercurial/dispatch.py", line 501, in _runcommand
File "./mercurial/dispatch.py", line 454, in checkargs
File "./mercurial/dispatch.py", line 448, in <lambda>
File "./mercurial/util.py", line 402, in check
File "/sys/lib/python/commands.py", line 636, in clone
File "/sys/lib/python/mercurial/hg.py", line 317, in clone
_update(dest_repo, uprev)
File "/sys/lib/python/mercurial/hg.py", line 335, in update
stats = _merge.update(repo, node, False, False, None)
File "/sys/lib/python/mercurial/merge.py", line 470, in update
stats = applyupdates(repo, action, wc, p2)
File "/sys/lib/python/mercurial/merge.py", line 308, in applyupdates
repo.wwrite(f, t, flags)
File "/sys/lib/python/mercurial/localrepo.py", line 555, in wwrite
self.wopener(filename, 'w').write(data)
File "./mercurial/util.py", line 874, in __call__
IOError: invalid mode: wb
Anyone have a more thorough patch?
Thanks,
ak
On Wed, Sep 14, 2011 at 8:58 PM, erik quanstrom <quanstro@quanstro.net> wrote:
> looks like spaces in file names are a problem, at least
> on my system.
>
> minooka; hg clone https://code.google.com/p/nix-os/
> destination directory: nix-os
> requesting all changes
> adding changesets
> adding manifests
> adding file changes
> transaction abort!
> rollback completed
> abort: Bad file number: /n/other/quanstro/nix-os/.hg/store/data/lib/font/bit/anonpro/_anonymous _pro.ttf.i
>
> - erik
>
>
next prev parent reply other threads:[~2011-10-27 7:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 3:58 erik quanstrom
2011-09-15 4:37 ` Federico G. Benavento
2011-09-15 4:38 ` erik quanstrom
2011-09-15 9:45 ` dexen deVries
2011-10-27 7:26 ` Akshat Kumar [this message]
2011-10-27 13:02 ` cinap_lenrek
[not found] ` <CABwSpPD2Zm5Ha=gjB40a89QBWZB+0Cmb277VuNMdEa-UD4cknQ@mail.gmail.c>
2011-10-27 13:10 ` erik quanstrom
2011-10-27 20:13 ` Akshat Kumar
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='CABwSpPD2Zm5Ha=gjB40a89QBWZB+0Cmb277VuNMdEa-UD4cknQ@mail.gmail.com' \
--to=akumar@mail.nanosouffle.net \
--cc=9fans@9fans.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 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).