hgserve encoding

[Jérôme Godbout]

Finaly found the problems, the 00manifest.i file was corrupted. We replaced the main repos .hg with one of the workstation clone and eveything is back to normal. Not sure why this got corrupted, but we will keep a tight backup on this. I guess the error was early sign of the file corruption.

Next step, remove the samba and use NFS!

> On Aug 10, 2017, at 8:34 AM, Yuya Nishihara <yuya at tcha.org> wrote:
> 
> On Wed, 9 Aug 2017 09:09:55 -0400, Jérôme Godbout wrote:
>> I have some trouble with the hgserve with apache2 with .cgi and my repos
>> hosting, it mostly work except when it tell me I have corrupted file, but
>> using the repos into local map drive work just fine and verify/recover
>> doesn't show any problems with it either.
>> 
>> I known the setup is totally weird, but we try to get ride of many Windows
>> machines (it's a work in progress).
>> 
>> I have the repos that was originally made under Windows copied to a Linux
>> based machine. The Linux repos file server is sharing it with Samba so
>> developer can pull/push to it. This work flawlessly.
>> 
>> I would like to finish the apache2/hg cgi to have all user stop using the
>> map drive and use the web server instead. But right now I have a lot of
>> weird problems.
>> 
>> I have a second Linux server that mount the samba share and have the
>> apache2 with the hgconfig for cgi-bin. I can browse the page, pull from it
>> but when I try to see some history (not all of them), raw or diff for some
>> file it tell me my file are corrupted.
> 
> Does "hg verify" pass on the samba share? The first thing I would try is
> to stop using shared filesystem behind hgweb to see if it is a filesystem
> issue or not.
> 
>> I think I might have some encoding problems. Since the repos was made under
>> Windows (porbably cp-1251 or wwindows-1251) and I'm using Linux for the
>> hgweb.
> 
> Character encoding could be a problem if the repository has files of non-ASCII
> name, and if the underlying filesystem is encoding-aware (e.g. Samba.) If the
> repository is stored in local Unix filesystems (and if clients are Windows),
> filenames are just bytes so cp1251 filenames should just work.