Re: Updating Debian sparc portage web page
On 1/5/20 1:25 AM, Joost van Baal-Ilić wrote: > On Sat, Dec 28, 2019 at 01:34:37PM +0100, Alban Vidal wrote: >> >> I've created a MR on the Debian website repository [2]. >> If it's good for you, we can merge it. >> Moreover, don't hesitate to tell us if you wich update the credits page [3]. >> >> [2] https://salsa.debian.org/webmaster-team/webwml/merge_requests/321 >> [3] https://www.debian.org/ports/sparc/credits > > Thanks for your work; much appreciated. The credits page looks _very_ old to > me. It'd be better to remove it, or add a note it's obsolete, or update it. I'd rather keep them for historic reasons. The statements made there are still valid after all. You may add me, James Clarke and Aurelien Jarno who have worked on the 64-bit SPARC port and maybe anyone else whom I forgot :). Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Updating Debian sparc portage web page
Hi Alban, On Sat, Dec 28, 2019 at 01:34:37PM +0100, Alban Vidal wrote: > > I've created a MR on the Debian website repository [2]. > If it's good for you, we can merge it. > Moreover, don't hesitate to tell us if you wich update the credits page [3]. > > [2] https://salsa.debian.org/webmaster-team/webwml/merge_requests/321 > [3] https://www.debian.org/ports/sparc/credits Thanks for your work; much appreciated. The credits page looks _very_ old to me. It'd be better to remove it, or add a note it's obsolete, or update it. My € 0,02. Bye, Joost
Re: New development of how to build the installation-guide for the website [ Re: Bug#930846: partman-auto-lvm: debconf show guided_size during auto install ]
Hi, "Adam D. Barratt" wrote: > On Sat, 2020-01-04 at 15:44 +0100, Holger Wansing wrote: > > Hi, > > > > Huh? > > I'm totally confused. See below... > > > > "Adam D. Barratt" wrote: > > > On Wed, 2020-01-01 at 19:52 +0100, Holger Wansing wrote: > > > > Hi, > > > > > > > > Laura Arjona Reina wrote: > > > > > Hi > > > > > > > > > > The cron job will do the 'git pull' on wolkenstein the next > > > > > time it > > > > > runs. > > > > > > > > yes, that worked, thanks. > > > > So, the build was performed via the new script, and thanks to > > > > that we > > > > now have the manual for buster on the webpage for buster :-) > > > > (the last two days there was the manual for bullseye there.) > > > > > > > > Thus, that part works fine so far. > > > > > > Only for languages up to and including Japanese (see below). A > > > number > > > of languages currently have no installation manual there. > > > > Hmm. I wonder where you found this... > > I did not saw such build errors on > > https://www-master.debian.org/build-logs/webwml/ > > It's in /srv/www.debian.org/installmanual/buster.log on www-master, as > produced by the lessoften cron. I have no idea if that's exported. > > > and looking here at > > https://www.debian.org/releases/stable/installmanual > > I see manuals for all languages and all formats available and > > correctly > > displayed, including Korean pdf! > > Yes, but: > > -rw-rw-r-- 1 debwww debwww 565570 Mar 24 2019 > /srv/www.debian.org/www/releases/buster/i386/install.pdf.ko > -rw-rw-r-- 1 debwww debwww 467581 Mar 24 2019 > /srv/www.debian.org/www/releases/buster/i386/install.txt.ko > -rw-rw-r-- 1 debwww debwww 793159 Mar 24 2019 > /srv/www.debian.org/www/releases/buster/i386/install.pdf.nl > -rw-rw-r-- 1 debwww debwww 495077 Mar 24 2019 > /srv/www.debian.org/www/releases/buster/i386/install.txt.nl > -rw-rw-r-- 1 debwww debwww 734356 Mar 24 2019 > /srv/www.debian.org/www/releases/buster/i386/install.pdf.pt > -rw-rw-r-- 1 debwww debwww 453409 Mar 24 2019 > /srv/www.debian.org/www/releases/buster/i386/install.txt.pt > -rw-rw-r-- 1 debwww debwww 718640 Mar 24 2019 > /srv/www.debian.org/www/releases/buster/i386/install.pdf.ru > -rw-rw-r-- 1 debwww debwww 403421 Mar 24 2019 > /srv/www.debian.org/www/releases/buster/i386/install.txt.ru > -rw-rw-r-- 1 debwww debwww 719953 Mar 24 2019 > /srv/www.debian.org/www/releases/buster/i386/install.pdf.sv > -rw-rw-r-- 1 debwww debwww 433775 Mar 24 2019 > /srv/www.debian.org/www/releases/buster/i386/install.txt.sv > -rw-rw-r-- 1 debwww debwww 767819 Mar 24 2019 > /srv/www.debian.org/www/releases/buster/i386/install.pdf.vi > -rw-rw-r-- 1 debwww debwww 500863 Mar 24 2019 > /srv/www.debian.org/www/releases/buster/i386/install.txt.vi > -rw-rw-r-- 1 debwww debwww 612601 Mar 24 2019 > /srv/www.debian.org/www/releases/buster/i386/install.pdf.zh-cn > -rw-rw-r-- 1 debwww debwww 353216 Mar 24 2019 > /srv/www.debian.org/www/releases/buster/i386/install.txt.zh-cn > -rw-rw-r-- 1 debwww debwww 693231 Jan 1 14:49 > /srv/www.debian.org/www/releases/buster/i386/install.pdf.en > [etc] > > [...] > > > > Makefile:8: recipe for target 'ko.i386' failed > > > make: *** [ko.i386] Error 2 > > > Ok, now I see. However, the build went completely fine, when I tested my changes to the lessoften cron script locally on my laptop. And the "invalid fontname" error on Korean PDF rings a bell here now. I think the point is a missing build depends on wolkenstein. With the version 20190622, a change got applied to change the used font for Korean PDF. And in the light of this build errors, I assume the needed font is not installed on wolkenstein. Which means, that package version never built successful on that machine! And that in turn would be the reason why the example-preseed.txt file on the webpage was an old version for months! (This version was uploaded 2019-06-22, and at 2019-07-15 I have reported under https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930846#47 that the example-preseed.txt file is still the old one, so I think the build failed the same way that time as I does today. Just noone noticed that ...) We could ask DSA to install 'fonts-nanum' and 'fonts-nanum-coding' at wolkenstein, to get that build successful again. Would that be an option? > > > buildweb.sh uses "set -e", so the failing Korean build causes the > > > script to abort, and the example-preseed.txt is never generated. > > > > > > The build script on www-master, conversely, simply continues and > > > deploys whatever has been built up to that point. > > > > As above, I am confused: > > isn't the buildweb.sh script being used on www-master, triggered by > > the lessoften cron script I changed on 2020-01-01 ? > > Yes, but I'm not sure how that disagrees with what I said. > > The section I was referring to starts at > https://sources.debian.org/src/installation-guide/20191229/build/buildweb.sh/#L51 > > If the "make" invocation there fails, the following preseed section
Re: New development of how to build the installation-guide for the website [ Re: Bug#930846: partman-auto-lvm: debconf show guided_size during auto install ]
On Sat, 2020-01-04 at 15:44 +0100, Holger Wansing wrote: > Hi, > > Huh? > I'm totally confused. See below... > > "Adam D. Barratt" wrote: > > On Wed, 2020-01-01 at 19:52 +0100, Holger Wansing wrote: > > > Hi, > > > > > > Laura Arjona Reina wrote: > > > > Hi > > > > > > > > The cron job will do the 'git pull' on wolkenstein the next > > > > time it > > > > runs. > > > > > > yes, that worked, thanks. > > > So, the build was performed via the new script, and thanks to > > > that we > > > now have the manual for buster on the webpage for buster :-) > > > (the last two days there was the manual for bullseye there.) > > > > > > Thus, that part works fine so far. > > > > Only for languages up to and including Japanese (see below). A > > number > > of languages currently have no installation manual there. > > Hmm. I wonder where you found this... > I did not saw such build errors on > https://www-master.debian.org/build-logs/webwml/ It's in /srv/www.debian.org/installmanual/buster.log on www-master, as produced by the lessoften cron. I have no idea if that's exported. > and looking here at > https://www.debian.org/releases/stable/installmanual > I see manuals for all languages and all formats available and > correctly > displayed, including Korean pdf! Yes, but: -rw-rw-r-- 1 debwww debwww 565570 Mar 24 2019 /srv/www.debian.org/www/releases/buster/i386/install.pdf.ko -rw-rw-r-- 1 debwww debwww 467581 Mar 24 2019 /srv/www.debian.org/www/releases/buster/i386/install.txt.ko -rw-rw-r-- 1 debwww debwww 793159 Mar 24 2019 /srv/www.debian.org/www/releases/buster/i386/install.pdf.nl -rw-rw-r-- 1 debwww debwww 495077 Mar 24 2019 /srv/www.debian.org/www/releases/buster/i386/install.txt.nl -rw-rw-r-- 1 debwww debwww 734356 Mar 24 2019 /srv/www.debian.org/www/releases/buster/i386/install.pdf.pt -rw-rw-r-- 1 debwww debwww 453409 Mar 24 2019 /srv/www.debian.org/www/releases/buster/i386/install.txt.pt -rw-rw-r-- 1 debwww debwww 718640 Mar 24 2019 /srv/www.debian.org/www/releases/buster/i386/install.pdf.ru -rw-rw-r-- 1 debwww debwww 403421 Mar 24 2019 /srv/www.debian.org/www/releases/buster/i386/install.txt.ru -rw-rw-r-- 1 debwww debwww 719953 Mar 24 2019 /srv/www.debian.org/www/releases/buster/i386/install.pdf.sv -rw-rw-r-- 1 debwww debwww 433775 Mar 24 2019 /srv/www.debian.org/www/releases/buster/i386/install.txt.sv -rw-rw-r-- 1 debwww debwww 767819 Mar 24 2019 /srv/www.debian.org/www/releases/buster/i386/install.pdf.vi -rw-rw-r-- 1 debwww debwww 500863 Mar 24 2019 /srv/www.debian.org/www/releases/buster/i386/install.txt.vi -rw-rw-r-- 1 debwww debwww 612601 Mar 24 2019 /srv/www.debian.org/www/releases/buster/i386/install.pdf.zh-cn -rw-rw-r-- 1 debwww debwww 353216 Mar 24 2019 /srv/www.debian.org/www/releases/buster/i386/install.txt.zh-cn -rw-rw-r-- 1 debwww debwww 693231 Jan 1 14:49 /srv/www.debian.org/www/releases/buster/i386/install.pdf.en [etc] [...] > > > Makefile:8: recipe for target 'ko.i386' failed > > make: *** [ko.i386] Error 2 > > > > > > buildweb.sh uses "set -e", so the failing Korean build causes the > > script to abort, and the example-preseed.txt is never generated. > > > > The build script on www-master, conversely, simply continues and > > deploys whatever has been built up to that point. > > As above, I am confused: > isn't the buildweb.sh script being used on www-master, triggered by > the lessoften cron script I changed on 2020-01-01 ? Yes, but I'm not sure how that disagrees with what I said. The section I was referring to starts at https://sources.debian.org/src/installation-guide/20191229/build/buildweb.sh/#L51 If the "make" invocation there fails, the following preseed section never gets run. The lessoften script does: cd $ig_dir_stable/build && manual_release=$stable_codename destination=$webtopdir/installmanual/$stable_codename/ ./buildweb.sh > $webtopdir/installmanual/$stable_codename.log 2>&1 echo "copying $stable_codename installmanual in place..." >> $crondir/log/lessoften.log rm -f $webdir/releases/$stable_codename/example-preseed.txt cp -a $webtopdir/installmanual/$stable_codename/* $webdir/releases/$stable_codename/ without checking the result of the "make" invocation, so the partial output from the new build is added to the already existing output from the previous builds in releases/buster, as per the directory listing earlier in this mail. > Apparently I am missing something here ... (?) Apparently so, or I failed at explaining clearly enough. :-) Regards, Adam
Re: New development of how to build the installation-guide for the website [ Re: Bug#930846: partman-auto-lvm: debconf show guided_size during auto install ]
Hi,
Huh?
I'm totally confused. See below...
"Adam D. Barratt" wrote:
> On Wed, 2020-01-01 at 19:52 +0100, Holger Wansing wrote:
> > Hi,
> >
> > Laura Arjona Reina wrote:
> > > Hi
> > >
> > > The cron job will do the 'git pull' on wolkenstein the next time it
> > > runs.
> >
> > yes, that worked, thanks.
> > So, the build was performed via the new script, and thanks to that we
> > now have the manual for buster on the webpage for buster :-)
> > (the last two days there was the manual for bullseye there.)
> >
> > Thus, that part works fine so far.
>
> Only for languages up to and including Japanese (see below). A number
> of languages currently have no installation manual there.
Hmm. I wonder where you found this...
I did not saw such build errors on
https://www-master.debian.org/build-logs/webwml/
and looking here at
https://www.debian.org/releases/stable/installmanual
I see manuals for all languages and all formats available and correctly
displayed, including Korean pdf!
> > However, the part with the example-preseed.txt file remains open:
> > in the past it was not updated, now I have added a "remove the old
> > example file" line into the script, and as a result we have no file
> > at all now :-(
> >
> > Because the rest is working fine, I suspect the problem is not in the
> > build of the manual ifself, but in the sync to the www mirrors (DSA
> > provided, I think).
>
> The problem is that the Korean build is failing on www-master; a
> partial log from a manual run:
>
>
> xelatex -interaction=batchmode install.ko.profiled.tex
> kpathsea:make_tex: Invalid fontname `나눔명조/OT', contains ''
> ...
> xelatex failed
> install.ko.profiled.tex:29: ..
> install.ko.profiled.tex:29: leading text: \setCJKmainfont{나눔명조}
> ...
> .:300: leading text: }&
> /home/adsb/installation-guide-20190622/build/build.tmp.ko.i386/dblatex/tmpwMvRmH
> not removed
>
> A possible reason for transformation failure is invalid DocBook
> (as reported by xmllint)
>
> Error: xelatex compilation failed
> Error: build of pdf failed with error code 1
> Info: creating temporary .html file...
> Info: creating .txt file...
> Warning: The following formats failed to build: pdf
> Makefile:8: recipe for target 'ko.i386' failed
> make: *** [ko.i386] Error 2
>
>
> buildweb.sh uses "set -e", so the failing Korean build causes the
> script to abort, and the example-preseed.txt is never generated.
>
> The build script on www-master, conversely, simply continues and
> deploys whatever has been built up to that point.
As above, I am confused:
isn't the buildweb.sh script being used on www-master, triggered by
the lessoften cron script I changed on 2020-01-01 ?
Apparently I am missing something here ... (?)
Holger
--
Holger Wansing
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Re: New development of how to build the installation-guide for the website [ Re: Bug#930846: partman-auto-lvm: debconf show guided_size during auto install ]
On Wed, 2020-01-01 at 19:52 +0100, Holger Wansing wrote:
> Hi,
>
> Laura Arjona Reina wrote:
> > Hi
> >
> > The cron job will do the 'git pull' on wolkenstein the next time it
> > runs.
>
> yes, that worked, thanks.
> So, the build was performed via the new script, and thanks to that we
> now have the manual for buster on the webpage for buster :-)
> (the last two days there was the manual for bullseye there.)
>
> Thus, that part works fine so far.
Only for languages up to and including Japanese (see below). A number
of languages currently have no installation manual there.
> However, the part with the example-preseed.txt file remains open:
> in the past it was not updated, now I have added a "remove the old
> example file" line into the script, and as a result we have no file
> at all now :-(
>
> Because the rest is working fine, I suspect the problem is not in the
> build of the manual ifself, but in the sync to the www mirrors (DSA
> provided, I think).
The problem is that the Korean build is failing on www-master; a
partial log from a manual run:
xelatex -interaction=batchmode install.ko.profiled.tex
kpathsea:make_tex: Invalid fontname `나눔명조/OT', contains ''
...
xelatex failed
install.ko.profiled.tex:29: ..
install.ko.profiled.tex:29: leading text: \setCJKmainfont{나눔명조}
...
.:300: leading text: }&
/home/adsb/installation-guide-20190622/build/build.tmp.ko.i386/dblatex/tmpwMvRmH
not removed
A possible reason for transformation failure is invalid DocBook
(as reported by xmllint)
Error: xelatex compilation failed
Error: build of pdf failed with error code 1
Info: creating temporary .html file...
Info: creating .txt file...
Warning: The following formats failed to build: pdf
Makefile:8: recipe for target 'ko.i386' failed
make: *** [ko.i386] Error 2
buildweb.sh uses "set -e", so the failing Korean build causes the
script to abort, and the example-preseed.txt is never generated.
The build script on www-master, conversely, simply continues and
deploys whatever has been built up to that point.
Regards,
Adam
