Re: Broken workflow (was: ddp build failed)
Hi,
On Thu, Oct 31, 2013 at 01:19:54PM -0400, David Prévot wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Le 31/10/2013 11:50, Osamu Aoki a écrit :
>
> > This builds OK on my machine though.
>
> Does it build on Wheezy?
I have not tried it recently. Wheezy package did not build PDF.
> If new dependencies need to be installed,
> please request them to webmaster@ (preferably before introducing
> disruptive changes).
As I see maint-guide building, this is not because of missing package.
It is an internal bug in dblatex. debian-reference has more
complicated XML mark-ups which seems to generate broken LaTex code.
> Again, I’m in favor of disabling the build on www-master, it only gives
> pain to maintain buildable packages in both stable and unstable. Release
> often is a good way to keep documentation in shape, and does the right
> thing by calling for translation before the upload.
I see your point.
> The current workflow does not only break parts of the documentation
> (will the PDF build be broken or deactivated, the online document will
> still be outdated compared to the HTML version), but it always break
> part of the translations (and there is currently no way for translators
> to be aware that they need to update their translation, except
> monitoring the Subversion commits)…
Except for "the online document will still be outdated compared to the
HTML version", I agree your points. I think current work flow is easier
to fix minor bug fix so HTML English version is always current in
current form than packaged ones.
> Many online documents are already published from the latest Sid package
> (policy, dev-ref, refcard, etc.) and I hope more would follow that trend
> (I’m happy, as a webmaster, to handle the needed changes for the
> packages we’d agree upon).
In my previous experience, in order to communicate with some
translators, it is good idea to have latest build result of the latest
VCS contents somewherre. So if I go along with new scheme, I want to
set up build result somewhere. This should not be too difficult.
(Also, if possible, I would like to move source to git repo. This new
scheme allow me to do so.)
Also, I would like to see the code doing this new scheme. Where can I
see the pertinent code for publishing installed sid package data to
www-master?
TIA,
Osamu
Reply to: