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 Sun, 2020-01-12 at 18:38 +0100, Holger Wansing wrote: > > A new build has taken place, however on the website we still have a > > mixup of old and newer files, and still no example-preseed.txt. > > While in the lessoften log it looks fine. > > No installmanual build available to me tough... > > The file exists, and the "often" cron is currently running. So I guess > it just needs a little more patience. > > -rw-rw-r-- 1 debwww debwww 18873 Jan 12 15:42 /srv/ > www.debian.org/www/releases/buster/example-preseed.txt You were right! Now everything is fine: https://www.debian.org/releases/stable/installmanual now has the correct version of the manual in all languages and all formats. And it has the example-preseed file. Thanks to all involved. 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 Sun, 2020-01-12 at 18:38 +0100, Holger Wansing wrote: > A new build has taken place, however on the website we still have a > mixup of old and newer files, and still no example-preseed.txt. > While in the lessoften log it looks fine. > No installmanual build available to me tough... The file exists, and the "often" cron is currently running. So I guess it just needs a little more patience. -rw-rw-r-- 1 debwww debwww 18873 Jan 12 15:42 /srv/ www.debian.org/www/releases/buster/example-preseed.txt 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, Laura Arjona Reina wrote: > El 10/1/20 a las 20:55, Holger Wansing escribió: > > Laura Arjona Reina wrote: > >> El 9/1/20 a las 20:49, Holger Wansing escribió: > >>> > >>> To make a new build happen, manual intervention is > >>> needed now ( because there is no new source package > >>> version available for installation-guide since the last build, no new > >>> build is trigered). > >>> One need to go to > >>> /srv/www.debian.org/cron/log/ig-stable-built.txt > >>> and change that file (for example just change into an > >>> empty file). > >>> This is documented in the 1installation-guide script in > >>> lessoften (cron git-repo). > >>> That will trigger a new build at the next day. > >> > >> I've just done this (copied > >> /srv/www.debian.org/cron/log/ig-stable-built.txt to > >> /srv/www.debian.org/cron/log/ig-stable-built.txt.old and then changed > >> ig-stable-built.txt to be an empty file). > > > > Hrr, this did not work. Sorry > > > > The variant with the empty file was my first idea, but that did not work. > > So I changed that, now the file has to be removed. > > > > May I bother you again, to remove the file instead? > > (Also, there is no need to keep the old file. You can remove it too.) > > I have just updated the documentation in the 1installation-guide lessoften > > script accordingly. > > > > No problem. > > I have removed the file, unfortunately I couldn't do it before today's > lessoften script run, so we need to wait until tomorrow to see if that > worked. A new build has taken place, however on the website we still have a mixup of old and newer files, and still no example-preseed.txt. While in the lessoften log it looks fine. No installmanual build available to me tough... 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 ]
Hello El 10/1/20 a las 20:55, Holger Wansing escribió: > Hi Laura, > > Laura Arjona Reina wrote: >> Hi >> >> El 9/1/20 a las 20:49, Holger Wansing escribió: >>> >>> To make a new build happen, manual intervention is >>> needed now ( because there is no new source package >>> version available for installation-guide since the last build, no new build >>> is trigered). >>> One need to go to >>> /srv/www.debian.org/cron/log/ig-stable-built.txt >>> and change that file (for example just change into an >>> empty file). >>> This is documented in the 1installation-guide script in >>> lessoften (cron git-repo). >>> That will trigger a new build at the next day. >> >> I've just done this (copied /srv/www.debian.org/cron/log/ig-stable-built.txt >> to >> /srv/www.debian.org/cron/log/ig-stable-built.txt.old and then changed >> ig-stable-built.txt to be an empty file). > > Hrr, this did not work. Sorry > > The variant with the empty file was my first idea, but that did not work. > So I changed that, now the file has to be removed. > > May I bother you again, to remove the file instead? > (Also, there is no need to keep the old file. You can remove it too.) > I have just updated the documentation in the 1installation-guide lessoften > script accordingly. > No problem. I have removed the file, unfortunately I couldn't do it before today's lessoften script run, so we need to wait until tomorrow to see if that worked. Cheers -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
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 Laura, Laura Arjona Reina wrote: > Hi > > El 9/1/20 a las 20:49, Holger Wansing escribió: > > > > To make a new build happen, manual intervention is > > needed now ( because there is no new source package > > version available for installation-guide since the last build, no new build > > is trigered). > > One need to go to > > /srv/www.debian.org/cron/log/ig-stable-built.txt > > and change that file (for example just change into an > > empty file). > > This is documented in the 1installation-guide script in > > lessoften (cron git-repo). > > That will trigger a new build at the next day. > > I've just done this (copied /srv/www.debian.org/cron/log/ig-stable-built.txt > to > /srv/www.debian.org/cron/log/ig-stable-built.txt.old and then changed > ig-stable-built.txt to be an empty file). Hrr, this did not work. Sorry The variant with the empty file was my first idea, but that did not work. So I changed that, now the file has to be removed. May I bother you again, to remove the file instead? (Also, there is no need to keep the old file. You can remove it too.) I have just updated the documentation in the 1installation-guide lessoften script accordingly. Many thanks + Sorry again 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 ]
Hi El 9/1/20 a las 20:49, Holger Wansing escribió: > > To make a new build happen, manual intervention is > needed now ( because there is no new source package > version available for installation-guide since the last build, no new build > is trigered). > One need to go to > /srv/www.debian.org/cron/log/ig-stable-built.txt > and change that file (for example just change into an > empty file). > This is documented in the 1installation-guide script in > lessoften (cron git-repo). > That will trigger a new build at the next day. I've just done this (copied /srv/www.debian.org/cron/log/ig-stable-built.txt to /srv/www.debian.org/cron/log/ig-stable-built.txt.old and then changed ig-stable-built.txt to be an empty file). Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
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, Am Donnerstag, 9. Januar 2020 schrieb Adam D. Barratt: > On Thu, 2020-01-09 at 14:24 +0100, Laura Arjona Reina wrote: > > So, please count my ACK to apply the patch adding fonts-nanum and > > fonts-nanum-coding. > > Thanks: > > The following NEW packages will be installed: > fonts-nanum fonts-nanum-coding > The following packages will be upgraded: > debian.org-www-master.debian.org > 1 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. > Need to get 10.1 MB of archives. > After this operation, 30.0 MB of additional disk space will be used. > ... > Setting up fonts-nanum (20140930-1) ... > Setting up fonts-nanum-coding (2.0-10) ... > Processing triggers for fontconfig (2.11.0-6.7+b1) ... > Setting up debian.org-www-master.debian.org (68~20200109T190309.1) ... Looks fine. Thanks! To make a new build happen, manual intervention is needed now ( because there is no new source package version available for installation-guide since the last build, no new build is trigered). One need to go to /srv/www.debian.org/cron/log/ig-stable-built.txt and change that file (for example just change into an empty file). This is documented in the 1installation-guide script in lessoften (cron git-repo). That will trigger a new build at the next day. Thanks Holger -- Sent from my Jolla phone http://www.jolla.com/
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 Thu, 2020-01-09 at 14:24 +0100, Laura Arjona Reina wrote: > So, please count my ACK to apply the patch adding fonts-nanum and > fonts-nanum-coding. Thanks: The following NEW packages will be installed: fonts-nanum fonts-nanum-coding The following packages will be upgraded: debian.org-www-master.debian.org 1 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 10.1 MB of archives. After this operation, 30.0 MB of additional disk space will be used. ... Setting up fonts-nanum (20140930-1) ... Setting up fonts-nanum-coding (2.0-10) ... Processing triggers for fontconfig (2.11.0-6.7+b1) ... Setting up debian.org-www-master.debian.org (68~20200109T190309.1) ... 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 ]
Hello El 7/1/20 a las 19:56, Adam D. Barratt escribió: > On Sun, 2020-01-05 at 17:46 +0100, Holger Wansing wrote: >> Hi, >> >> Holger Wansing wrote: > [...] >>> 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? >> >> Patch (from git format-patch) again DSA's debian.org repo is >> attached. > > I'm happy to do that, but I'd prefer an ACK from a member of the > webmaster group for completeness - Laura? > Sorry for the delay. I have reviewed this thread and the proposed solution looks good to me. So, please count my ACK to apply the patch adding fonts-nanum and fonts-nanum-coding. Thanks for the work! Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
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 Sun, 2020-01-05 at 17:46 +0100, Holger Wansing wrote: > Hi, > > Holger Wansing wrote: [...] > > 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? > > Patch (from git format-patch) again DSA's debian.org repo is > attached. I'm happy to do that, but I'd prefer an ACK from a member of the webmaster group for completeness - Laura? 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, Holger Wansing wrote: > 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? Patch (from git format-patch) again DSA's debian.org repo is attached. Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076 >From ba54e249ceda995b6d7c16e634afabd553f81f0e Mon Sep 17 00:00:00 2001 From: Holger Wansing Date: Sun, 5 Jan 2020 17:38:39 +0100 Subject: [PATCH] Add additional build-depends for installation-guide --- debian/changelog | 5 + debian/control | 2 ++ 2 files changed, 7 insertions(+) diff --git a/debian/changelog b/debian/changelog index bce2069..2af469a 100644 --- a/debian/changelog +++ b/debian/changelog @@ -16,6 +16,11 @@ debian.org (68) UNRELEASED; urgency=medium + python3 + python3-debian + [ Holger Wansing ] + * www-master.d.o - additional build dependencies for installation-guide: ++ fonts-nanum ++ fonts-nanum-coding + -- Aurelien Jarno Sat, 21 Dec 2019 17:44:08 +0100 debian.org (67) stable; urgency=medium diff --git a/debian/control b/debian/control index ddae7cd..08e62c9 100644 --- a/debian/control +++ b/debian/control @@ -304,6 +304,8 @@ Depends: debiandoc-sgml, texlive-latex-extra, texlive-latex-recommended, fonts-wqy-microhei, + fonts-nanum, + fonts-nanum-coding, fonts-vlgothic, tidy, time, -- 2.20.1
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, Holger Wansing wrote: > "Adam D. Barratt" wrote: > > On Sat, 2020-01-04 at 15:44 +0100, Holger Wansing wrote: > > > > 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. > > This part is of course an error of mine (means a problem in the lessoften > cron script changed by me). > > Will try to work on that these days. I've fixed that now. The built manual files are only copied to www dir, if the build was successful, and I cleaned the www directory before copying, to avoid such mixup of files from old and new versions in the future. Also added an error to cron log in case of build error, to make the error more visible. (The above does not fix the build error and the current situation on the website we already have, though.) 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 ]
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
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
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, 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. 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). But this is only an assumption, I cannot say for sure, because I have no access rights for wolkenstein. @debian-www: Maybe you want to grant me access to wolkenstein machine for similar jobs? Holger > El 1 de enero de 2020 14:45:21 CET, Holger Wansing > escribió: > >Hi, > > > >Samuel Thibault wrote: > >> Samuel Thibault, le dim. 29 déc. 2019 22:15:59 +0100, a ecrit: > >> > Holger Wansing, le dim. 29 déc. 2019 21:59:02 +0100, a ecrit: > >> > > do you it would be possible for you to do another upload for the > >> > > installation-guide some day? > >> > > >> > Ah, sure, I'm on it, then. > >> > >> Done! > > > >Thanks for the quick upload! > > > >However, I noticed that this does not fix the problem in #930846. > >And while looking at the details, I came (again) to the longstanding problem > >with the built of installation-guide for the website. > > > >Therefore, I have changed the 1installation-guide script in cron's > >lessoften part (see > >https://salsa.debian.org/webmaster-team/cron/commit/eb181b214009878967197a673a3488821d1c2258 > > ) > > > >It changes the way of building the installation-guide: > >instead of hardcoding release codenames and always pulling the latest package > >version from the archive, it now parses the release codenames from the webwml > >repo, and package version is determined via rmadison. > > > > > >@Laura: could you see, if there is something needed on wolkenstein, to make > >this > >going live? (I assume a simply "git pull"?) -- 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 ]
Hi The cron job will do the 'git pull' on wolkenstein the next time it runs. Kind regards El 1 de enero de 2020 14:45:21 CET, Holger Wansing escribió: >Hi, > >Samuel Thibault wrote: >> Samuel Thibault, le dim. 29 déc. 2019 22:15:59 +0100, a ecrit: >> > Holger Wansing, le dim. 29 déc. 2019 21:59:02 +0100, a ecrit: >> > > do you it would be possible for you to do another upload for the >> > > installation-guide some day? >> > >> > Ah, sure, I'm on it, then. >> >> Done! > >Thanks for the quick upload! > >However, I noticed that this does not fix the problem in #930846. >And while looking at the details, I came (again) to the longstanding problem >with the built of installation-guide for the website. > >Therefore, I have changed the 1installation-guide script in cron's >lessoften part (see >https://salsa.debian.org/webmaster-team/cron/commit/eb181b214009878967197a673a3488821d1c2258 > ) > >It changes the way of building the installation-guide: >instead of hardcoding release codenames and always pulling the latest package >version from the archive, it now parses the release codenames from the webwml >repo, and package version is determined via rmadison. > > >@Laura: could you see, if there is something needed on wolkenstein, to make >this >going live? (I assume a simply "git pull"?) > > >Thanks >Holger > > -- Laura Arjona Reina https://wiki.debian.org/LauraArjona Sent with K-9 mail
