(Let's keep the DDP CVS discussion at -doc only) On Thu, Apr 07, 2005 at 09:17:23PM +0200, Osamu Aoki wrote: > > Here is info on situation of DDP CVS: > $ cvs up (...) > It seems there is problem with RCS file of > /cvs/debian-doc/ddp/manuals.sgml/apt-howto/apt-howto.ja.sgml Actually, the following RCS files are broken: ./ddp/manuals.sgml/apt-howto/apt-howto.en.sgml,v: data ./ddp/manuals.sgml/apt-howto/apt-howto.ja.sgml,v: data ./ddp/manuals.sgml/apt-howto/apt-howto.ko.sgml,v: data ./ddp/manuals.sgml/apt-howto/apt-howto.pl.sgml,v: data ./ddp/manuals.sgml/apt-howto/apt-howto.ru.sgml,v: data ./ddp/manuals.sgml/developers-reference/developers-reference.sgml,v: data ./ddp/manuals.sgml/maint-guide/maint-guide.de.sgml,v: data ./ddp/manuals.sgml/project-history/Makefile,v: data ./ddp/manuals.sgml/project-history/project-history.sgml,v: data ./ddp/manuals.sgml/project-history/project-history.es.sgml,v: data ./ddp/manuals.sgml/securing-howto/zh-cn/appendix.sgml,v: data ./ddp/manuals.sgml/securing-howto/Makefile,v: data ./ddp/manuals.sgml/securing-howto/es/intro.sgml,v: data ./ddp/manuals.sgml/securing-howto/en/appendix.sgml,v: data ./ddp/manuals.sgml/securing-howto/en/sec-tools.sgml,v: data ./ddp/manuals.sgml/securing-howto/de/after-compromise.sgml,v: data ./ddp/manuals.sgml/securing-howto/de/after-install.sgml,v: data ./ddp/manuals.sgml/securing-howto/de/appendix.sgml,v: data ./ddp/manuals.sgml/securing-howto/de/before-install.sgml,v: data ./ddp/manuals.sgml/securing-howto/default.ent,v: data ./ddp/manuals.sgml/libpkg-guide/en/libpkg-guide.xml,v: data ./manpages/english/pppconfig/pppconfig.8,v: data So that means that several documents can not be used properly through CVS right now. > Please note this original file apt-howto.ja.sgml uses ja_JP.eucJP > encoding. Editing file under UTF-8 locale editor will destroy file > contents. You need to use dumb 8 bit clean editor like mcedit (from mc) > preferably under C locale. I'm not going to edit the files manually, I will try to find if there's a RCS file from the backups that could be restored (overwritting the current file, which is corrupted). Regards Javier
Attachment:
signature.asc
Description: Digital signature