[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Error message when generating docbooks
From:       Freek de Kruijf <f.de.kruijf () gmail ! com>
Date:       2012-09-18 20:30:50
Message-ID: 1629412.djXnJaKJKi () eik122
[Download RAW message or body]

Op dinsdag 18 september 2012 19:27:50 schreef Albert Astals Cid:
> El Dimarts, 18 de setembre de 2012, a les 11:45:12, Yuri Chornoivan va
> 
> escriure:
> > Tue, 18 Sep 2012 10:44:11 +0300 було написано Freek de Kruijf
> > 
> > <f.de.kruijf@gmail.com>:
> > > I get the following error message when using scripts/update_xml for
> > > branch,
> > > right after starting the script.
> > > 
> > > Updating kdelibs root documentation
> > > remote: fatal: no such ref: KDE/4.9:doc
> > > remote: git upload-archive: archiver died with error
> > > tar: This does not look like a tar archive
> > > tar: Exiting with failure status due to previous errors
> > > 
> > > After that the generation goes OK.
> > 
> > KDE Git repositories have rather annoying problems with access during last
> > two months. It is sometimes impossible to generate docs for large Git
> > modules like kdeedu.
> > 
> > Please try later. It is possible that the repository become usable again
> > in a few minutes or few hours.
> 
> I suggest you to drop by #kde-sysadmin IRC channel if you can reproduce
> problems accessing git repositories, they should work fine. If you don't
> report problems they are not going to get fixed automagically.

I did participate in the channel, my first IRC session, and the problem lies 
in the use of the git command "git archive --remote=$1 $2 | tar -x" in 
sripts/populate_documentation.sh. $2 gets replaced by the fourth parameter in 
the lines in scripts/documentation_paths which for this git command is always 
KDE/4.9:doc. For trunk this is HEAD:doc. However a newer version of the git 
server does not allow the colon, which should be a space, which according to 
the conversation in IRC works with both versions of the server.

So I would recommend to change the script such that the colon get replaced in 
the script populate_documentation.sh by a space and leave 
scripts/documentation_paths untouched. So now I have to figure out how to 
replace the colon by a space and see if that works.


-- 
fr.gr.

Freek de Kruijf

[prev in list] [next in list] [prev in thread] [next in thread]