Re: building and testing d-i with jenkins

Hi Steven, thanks for your feedback! On Sonntag, 30. Dezember 2012, Steven Chamberlain wrote: > > http://jenkins.debian.net/view/cd-tests/job/cd-test_wheezy_lxde/ > > doing a g-i installation of lxde desktop and producing a nice video > This is great! But what happened to that link, it is a 404

Re: d-i manual (Re: building and testing d-i with jenkins)

Hi Holger, On Samstag, 29. Dezember 2012, Holger Wansing wrote: > today I found the following on > http://jenkins.debian.net/view/d-i_manual/job/d-i_manual_pt_pdf/lastBuild/c > onsole > > rmdir: failed to remove `pdf/pt.amd64': Directory not empty > rmdir: failed to remove `pdf/pt.armel': Directo

Re: Re: building and testing d-i with jenkins

Hi Holger, On 5 Dec 2012 21:19:00, Holger Levsen wrote: > there is now > http://jenkins.debian.net/view/cd-tests/job/cd-test_wheezy_lxde/ > doing a g-i installation of lxde desktop and producing a nice video This is great! But what happened to that link, it is a 404 already? I see that wheezy d

Re: d-i manual (Re: building and testing d-i with jenkins)

Hi, today I found the following on http://jenkins.debian.net/view/d-i_manual/job/d-i_manual_pt_pdf/lastBuild/console rmdir: failed to remove `pdf/pt.amd64': Directory not empty rmdir: failed to remove `pdf/pt.armel': Directory not empty rmdir: failed to remove `pdf/pt.armhf': Directory not empty

Re: d-i manual (Re: building and testing d-i with jenkins)

Hi Holger, On Sonntag, 23. Dezember 2012, Holger Wansing wrote: > I just wondered why the pdf build for it, ca and pt_BR give a "fail" > as status of last build, but the html version build gives a "successful"? > Both build logs contain an error: there was a problem with the logparser configurati

Re: d-i manual (Re: building and testing d-i with jenkins)

Hi, Holger Levsen wrote: > there are still some warnings left, which you fixed in some languages already: > > the hurd-i386-'reference to non-existent ID "boot-usb-files"' problem still > exists in: > > http://jenkins.debian.net/view/d-i_manual/job/d-i_manual_fr_pdf/3/parsed_console/? > http:/

Re: building and testing d-i with jenkins

Hi, On Samstag, 24. November 2012, Holger Levsen wrote: > > d_i_build_* - there is one job for each git repo referred to in > > http://anonscm.debian.org/viewvc/d-i/trunk/.mrconfig?view=co > > Each job pdebuilds the master branch of its git repo on every git push in > > a sid environment. > proble

Re: building and testing d-i with jenkins

Hi Luca, On Samstag, 8. Dezember 2012, Luca Capello wrote: > I perfectly agree and I am sorry if my words sounded more like "you > should use BabelBox instead" than "BabelBox can help here". Indeed, > BabelBox already does at least the three tests you specifically > mentioned: > >

Re: building and testing d-i with jenkins

Hi Holger! On Thu, 06 Dec 2012 12:38:34 +0100, Holger Levsen wrote: > On Mittwoch, 5. Dezember 2012, Luca Capello wrote: >> I have patches to use it in a VirtualBox instance > > nice! but rather something else: I see babelbox more as a showcase for > events, > and surely it _can_ be used for tes

Re: building and testing d-i with jenkins

Hi Luca, On Mittwoch, 5. Dezember 2012, Luca Capello wrote: > This sounds to me like reinventing BabelBox, which IMHO is a better > solution given that we can use it outside Jenkins. If all you know is a hammer, everything looks like a hammer indeed ;-P > I have patches to use it in a VirtualBo

Re: building and testing d-i with jenkins

Hi Holger, On Donnerstag, 6. Dezember 2012, Holger Wansing wrote: > I just noticed, that under > http://jenkins.debian.net/ (root level of jenkins) this shows all the problematic builds (currently only the failed ones, but it would be trivial to add the unstable ones.) > there is "d-i_manual_eu

Re: building and testing d-i with jenkins

Hi, Holger Levsen wrote: > Hi, > > as you might have seen, I'm running certain d-i jobs on > http://jenkins.debian.net/ I just noticed, that under http://jenkins.debian.net/ (root level of jenkins) there is "d-i_manual_eu_html", which should be under the sublevel "d-i_manual" (ok it _is_ unde

Re: building and testing d-i with jenkins

Hi there! On Wed, 05 Dec 2012 21:19:00 +0100, Holger Levsen wrote: > there is now > http://jenkins.debian.net/view/cd-tests/job/cd-test_wheezy_lxde/ doing > a g-i installation of lxde desktop and producing a nice > video as in > http://jenkins.debian.net/view/cd-tests/job/cd-test_wheezy_lxde/lastS

Re: building and testing d-i with jenkins

Hi, there is now http://jenkins.debian.net/view/cd-tests/job/cd-test_wheezy_lxde/ doing a g-i installation of lxde desktop and producing a nice video as in http://jenkins.debian.net/view/cd-tests/job/cd-test_wheezy_lxde/lastSuccessfulBuild/artifact/results/cd-test-lxde-wheezy.ogv and I wonder ot

Re: d-i manual (Re: building and testing d-i with jenkins)

Hi, Holger Levsen wrote: > there are still some warnings left, which you fixed in some languages already: > > the hurd-i386-'reference to non-existent ID "boot-usb-files"' problem still > exists in: > > http://jenkins.debian.net/view/d-i_manual/job/d-i_manual_fr_pdf/3/parsed_console/? > http:/

Re: d-i manual (Re: building and testing d-i with jenkins)

Hi Holger, On Sonntag, 25. November 2012, Holger Wansing wrote: > Ok, you are right. There were additional warnings, but not in _that_ > language that I checked. > > 1. for da and nn there were warnings about not existing entity files. > I have added empty entity files to avoid that warnings. th

Re: d-i manual (Re: building and testing d-i with jenkins)

Hi Holger, On Sonntag, 25. November 2012, Holger Wansing wrote: > I investigated the build errors for korean pdf format. > That one builds fine here, but I had to install korean fonts additionally. > Maybe you also have the package ko.tex-base not installed on > jenkins? right, that was the cause

Re: d-i manual (Re: building and testing d-i with jenkins)

Hi, Holger Levsen wrote: > Hi, > > On Donnerstag, 22. November 2012, Holger Wansing wrote: > > > http://jenkins.debian.net/view/d-i_manual/job/d-i_manual_ro_html/1/parsed > > > _console/? would show a lot less warnings, but still some. I investigated the build errors for korean pdf format. That

Re: d-i manual (Re: building and testing d-i with jenkins)

Hi, Holger Wansing wrote: > 3. In de.html I found: > > Building in workspace /var/lib/jenkins/jobs/d-i_manual_de_html/workspace > Updating svn://svn.debian.org/svn/d-i/trunk to revision > '2012-11-19T20:31:15.498 +' > U manual/en/boot-installer/x86.xml > U manual/de/boot-ins

Re: d-i manual (Re: building and testing d-i with jenkins)

Quoting Holger Wansing (li...@wansing-online.de): > Hi, > > Holger Levsen wrote: This thread is funny to see in my MUA: Holger talks to Holger who answers to Holger, etc. I should use Holger as first name to add more confusion..:-) signature.asc Description: Digital signature

Re: d-i manual (Re: building and testing d-i with jenkins)

Hi, Holger Levsen wrote: > On Donnerstag, 22. November 2012, Holger Wansing wrote: > > > http://jenkins.debian.net/view/d-i_manual/job/d-i_manual_ro_html/1/parsed > > > _console/? would show a lot less warnings, but still some. > > At that url I see only warnings like "Warning: no PO file found f

Re: d-i manual (Re: building and testing d-i with jenkins)

Hi, Holger Levsen wrote: > On Donnerstag, 22. November 2012, Holger Wansing wrote: > > > http://jenkins.debian.net/view/d-i_manual/job/d-i_manual_ro_html/1/parsed > > > _console/? would show a lot less warnings, but still some. > > At that url I see only warnings like "Warning: no PO file found f

Re: building and testing d-i with jenkins

Hi, On Samstag, 17. November 2012, Holger Levsen wrote: > d_i_build_* - there is one job for each git repo referred to in > http://anonscm.debian.org/viewvc/d-i/trunk/.mrconfig?view=co > Each job pdebuilds the master branch of its git repo on every git push in a > sid environment. problems found:

Re: d-i manual (Re: building and testing d-i with jenkins)

Hi, On Donnerstag, 22. November 2012, Holger Wansing wrote: > > http://jenkins.debian.net/view/d-i_manual/job/d-i_manual_ro_html/1/parsed > > _console/? would show a lot less warnings, but still some. > At that url I see only warnings like "Warning: no PO file found for ...", > no others. I'm pre

Re: d-i manual (Re: building and testing d-i with jenkins)

Quoting Holger Wansing (li...@wansing-online.de): > We could change the workflow for the po based translations, so that all po > files > are existing, even if the are completely untranslated. > > Christian, what do you think? That could help having better stats, as a side effect, so I would be

Re: d-i manual (Re: building and testing d-i with jenkins)

Hello Holger, Holger Levsen wrote: > Those have quite a lot more failures and warnings... > > I'm not sure whether I should ignore these warnings: "Warning: no PO file > found for ..." - If I did that, > http://jenkins.debian.net/view/d-i_manual/job/d-i_manual_ro_html/1/parsed_console/? > would

Re: d-i manual (Re: building and testing d-i with jenkins)

Hi, On Samstag, 17. November 2012, Holger Wansing wrote: > As documented in manual/doc/translations_po.txt: > Use the following commands: > 1. ./scripts/merge_xml en > 2. ./scripts/update_pot > 3. ./scripts/update_po > 4. ./scripts/revert_pot > 5. ./s

Re: building and testing d-i with jenkins

Hi Holger, (btw: there are irc notifications now.) On Montag, 19. November 2012, Holger Wansing wrote: > 1. the error for arch hurd-i386 was a real error, which I fixed some > minutes ago (for en). nice! > 2. the other errors are no real errors. The architectures "hurd", > "kfreebsd" and "linu

Re: building and testing d-i with jenkins

Hi, Holger Levsen wrote: > ok, I've renamed the d_i_manual_$LANG jobs to d_i_manual_$LANG_html and > created all d_i_manual_$LANG_pdf, which are triggered by success of their > d_i_manual_$LANG_html job. > > And, all new d_i_manual_$LANG_pdf jobs resulted in "unstable" builds due to > the fo

Re: building and testing d-i with jenkins

Hi Joey, On Samstag, 17. November 2012, Joey Hess wrote: > You forgot to mention http://jenkins.debian.net/view/chroot-tests/ which > all test debootstrap and task installs. Right, thanks, these are indeed relevant for this list. > Of traslations to packages/po, presumably. Since these are in t

Re: d-i manual (Re: building and testing d-i with jenkins)

Hi Holger, On Samstag, 17. November 2012, Holger Wansing wrote: > > Instead of building the full installation-guide package on commits in > > /trunk/manual/po/$LANG I'd like to only build that language - how can I > > do this? > As documented in manual/doc/translations_po.txt: > Use the foll

Re: building and testing d-i with jenkins

Hi Holger, On Samstag, 17. November 2012, Holger Wansing wrote: > Holger Levsen wrote: > > d_i_manual_* - builds a language (on wheezy) on every commit of > > svn/trunk/manual/$LANG with "make languages=$LANG architectures=amd64 > > formats=html" > In the past I had errors in my d-i manual transl

Re: building and testing d-i with jenkins

Holger Levsen wrote: > as you might have seen, I'm running certain d-i jobs on > http://jenkins.debian.net/ > > There are three views showing d-i related jobs, which are > http://jenkins.debian.net/view/d-i_packages/ > http://jenkins.debian.net/view/d-i_manual/ > http://jenkins.debian.net/view

Re: d-i manual (Re: building and testing d-i with jenkins)

Hi, Holger Levsen wrote: > On Samstag, 17. November 2012, Holger Levsen wrote: > > d_i_manual - builds the full installation-guide package with pdebuild in > > sid on every commit to svn://svn.debian.org/svn/d-i/ matching these > > patterns: /trunk/manual/debian/.*, /trunk/manual/po/.*, > > /trun

Re: building and testing d-i with jenkins

Hi, Holger Levsen wrote: > d_i_manual_* - builds a language (on wheezy) on every commit of > svn/trunk/manual/$LANG with "make languages=$LANG architectures=amd64 > formats=html" In the past I had errors in my d-i manual translation, which only affected the pdf variant of the manual. So it wou

d-i manual (Re: building and testing d-i with jenkins)

Hi, On Samstag, 17. November 2012, Holger Levsen wrote: > d_i_manual - builds the full installation-guide package with pdebuild in > sid on every commit to svn://svn.debian.org/svn/d-i/ matching these > patterns: /trunk/manual/debian/.*, /trunk/manual/po/.*, > /trunk/manual/doc/.* /trunk/manual/sc

building and testing d-i with jenkins

Hi, as you might have seen, I'm running certain d-i jobs on http://jenkins.debian.net/ There are three views showing d-i related jobs, which are http://jenkins.debian.net/view/d-i_packages/ http://jenkins.debian.net/view/d-i_manual/ http://jenkins.debian.net/view/d-i_misc/ In these views 4