Bug#1053445: Merge request regarding 'Please migrate Release Notes to reStructuredText'
Ah, OK - that makes sense. Thank you Laura. On Sat, Oct 7, 2023, 08:59 Laura Arjona Reina wrote: > Hello James > > Thanks for caring. > > We should keep the packages related to docbook because we still build > release notes for stable and oldstable (only trixie notes have been > migrated to sphinx). There are other manuals under www.debian.org/doc > that still use docbook, too. > > Kind regards > > El 7 de octubre de 2023 2:07:39 CEST, James Addison > escribió: > >Package: www.debian.org > >Followup-For: Bug #1053445 > >X-Debbugs-Cc: larj...@debian.org, debian-...@lists.debian.org, > debian-...@lists.debian.org > > > >> I think we should open an RT ticket to ask DSA to install several > packages in > >> www-master that are needed now. From the info in the README file, these > are the > >> ones not present currently in www-master: > >> > >> - latexmk > >> - python3-distro-info > >> - python3-sphinx > >> - python3-stemmer > >> - tex-gyre > >> - texinfo > >> > >> I'm trying a local build to see if any other package is also needed, > and will > >> open an RT ticket later in the day or tomorrow, if nobody beats me to > it. > > > >It's possible/likely I'm stating the obvious, but just in case: this > could also > >be a good opportunity to remove (or plan to remove) packages that are no > longer > >necessary to build the old-style release notes. > > > > -- > Laura Arjona Reina > https://wiki.debian.org/LauraArjona > Sent with K-9 mail >
Bug#1053445: Merge request regarding 'Please migrate Release Notes to reStructuredText'
Hello James Thanks for caring. We should keep the packages related to docbook because we still build release notes for stable and oldstable (only trixie notes have been migrated to sphinx). There are other manuals under www.debian.org/doc that still use docbook, too. Kind regards El 7 de octubre de 2023 2:07:39 CEST, James Addison escribió: >Package: www.debian.org >Followup-For: Bug #1053445 >X-Debbugs-Cc: larj...@debian.org, debian-...@lists.debian.org, >debian-...@lists.debian.org > >> I think we should open an RT ticket to ask DSA to install several packages >> in >> www-master that are needed now. From the info in the README file, these are >> the >> ones not present currently in www-master: >> >> - latexmk >> - python3-distro-info >> - python3-sphinx >> - python3-stemmer >> - tex-gyre >> - texinfo >> >> I'm trying a local build to see if any other package is also needed, and >> will >> open an RT ticket later in the day or tomorrow, if nobody beats me to it. > >It's possible/likely I'm stating the obvious, but just in case: this could also >be a good opportunity to remove (or plan to remove) packages that are no longer >necessary to build the old-style release notes. > -- Laura Arjona Reina https://wiki.debian.org/LauraArjona Sent with K-9 mail
Bug#1053445: Merge request regarding 'Please migrate Release Notes to reStructuredText'
Package: www.debian.org Followup-For: Bug #1053445 X-Debbugs-Cc: larj...@debian.org, debian-...@lists.debian.org, debian-...@lists.debian.org > I think we should open an RT ticket to ask DSA to install several packages in > www-master that are needed now. From the info in the README file, these are > the > ones not present currently in www-master: > > - latexmk > - python3-distro-info > - python3-sphinx > - python3-stemmer > - tex-gyre > - texinfo > > I'm trying a local build to see if any other package is also needed, and will > open an RT ticket later in the day or tomorrow, if nobody beats me to it. It's possible/likely I'm stating the obvious, but just in case: this could also be a good opportunity to remove (or plan to remove) packages that are no longer necessary to build the old-style release notes.
Bug#1053445: Merge request regarding 'Please migrate Release Notes to reStructuredText'
Hello all Thanks all for the work. The build of the new release notes in ReStructuredText still fails in www-master: /srv/www.debian.org/release-notes/build.log-sphinx-build -b text -D language=en -d build/en source build/en/text /srv/www.debian.org/release-notes/build.log-make: sphinx-build: No such file or directory /srv/www.debian.org/release-notes/build.log:make: *** [Makefile:97: build/en/text/release-notes.txt] Error 127 I think we should open an RT ticket to ask DSA to install several packages in www-master that are needed now. From the info in the README file, these are the ones not present currently in www-master: - latexmk - python3-distro-info - python3-sphinx - python3-stemmer - tex-gyre - texinfo I'm trying a local build to see if any other package is also needed, and will open an RT ticket later in the day or tomorrow, if nobody beats me to it. Kind regards El 4/10/23 a las 18:42, Holger Wansing escribió: Hi, Am 4. Oktober 2023 17:05:16 MESZ schrieb Laura Arjona Reina : Hello all Sorry for jumping into the thread withour having reading all of it, but the changes to the website cron jobs to build the trixie release notes (MR 13) have been integrated in the codebase (see https://salsa.debian.org/webmaster-team/cron/-/blob/master/parts/7release-notes ) and we're getting an error in the build process (hence the recent "ddp build failed" message in the debian-doc list). I think there are two issues: Thanks for the quick merge. That being done now, I need to push the 'Migrate r-n to restructuredText' changings to master. Please be patient. Holger A) 7release-notes script now calls for trixie (https://salsa.debian.org/webmaster-team/cron/-/blob/master/parts/7release-notes#L208 ): make install DESTDIR=$crondir/tmp >> $notesdir/build.log 2>&1 while for the other releases the call is (https://salsa.debian.org/webmaster-team/cron/-/blob/master/parts/7release-notes#L242 ) make -C $notesdir/release-notes publish \ PUBLISHTARBALL=yes PUBLISHDIR=$webtopdir/www/releases/$release >> $notesdir/build.log 2>&1 I believe that the Makefile of release-notes understands "publish" instead of "install" but I'm not sure about how should we update L208 of the 7release-notes script. B) On the other hand, if I look at the master branch of the release-notes repo, I see that it's still written in docbook, not restructuredtext. I guess the files in the new format are still in https://salsa.debian.org/holgerw/release-notes and should be merged into the original release-notes repo first so we actually build them and not the old docbook ones, but not 100% sure about this point because I couldn't follow all the related threads with all the attention they needed (apologies!). Kind regards, El 4/10/23 a las 12:23, Holger Wansing escribió: Hi, Thomas Lange wrote (Wed, 4 Oct 2023 10:29:35 +0200): Hi Holger, I really like the idea no to produce release notes for each architecture but only one. Moving to sphinx is also nice. Sorry, if I broke your MR, by adding code that checks if something changed in the git repo. I think I can easily add this to your code later. So maybe we copy your version of 7release-notes and after that I add my code. That would be really great! Do you know how long the build process takes using sphinx? I've added the code, because the build took around 90 minutes using docbook. I expect the build time to be reduced dramatically (rughly ~ 1/9, due to building only one arch instead of nine), but I have no definite values, expecially not for the run on www-master. Any other things I should keep an eye on? None at the moment. Thanks for considering this MR. It would give us the possibility to move r-n to sphinx, which would be a great deal! Holger -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#1053445: Merge request regarding 'Please migrate Release Notes to reStructuredText'
Hi, Am 4. Oktober 2023 17:05:16 MESZ schrieb Laura Arjona Reina : >Hello all >Sorry for jumping into the thread withour having reading all of it, but the >changes to the website cron jobs to build the trixie release notes (MR 13) >have been integrated in the codebase (see >https://salsa.debian.org/webmaster-team/cron/-/blob/master/parts/7release-notes > ) and we're getting an error in the build process (hence the recent "ddp >build failed" message in the debian-doc list). > >I think there are two issues: Thanks for the quick merge. That being done now, I need to push the 'Migrate r-n to restructuredText' changings to master. Please be patient. Holger >A) > >7release-notes script now calls for trixie >(https://salsa.debian.org/webmaster-team/cron/-/blob/master/parts/7release-notes#L208 > ): > >make install DESTDIR=$crondir/tmp >> $notesdir/build.log 2>&1 > >while for the other releases the call is >(https://salsa.debian.org/webmaster-team/cron/-/blob/master/parts/7release-notes#L242 > ) > > >make -C $notesdir/release-notes publish \ >PUBLISHTARBALL=yes PUBLISHDIR=$webtopdir/www/releases/$release >> > $notesdir/build.log 2>&1 > >I believe that the Makefile of release-notes understands "publish" instead of >"install" but I'm not sure about how should we update L208 of the >7release-notes script. > >B) >On the other hand, if I look at the master branch of the release-notes repo, I >see that it's still written in docbook, not restructuredtext. >I guess the files in the new format are still in >https://salsa.debian.org/holgerw/release-notes and should be merged into the >original release-notes repo first so we actually build them and not the old >docbook ones, but not 100% sure about this point because I couldn't follow all >the related threads with all the attention they needed (apologies!). > > >Kind regards, > >El 4/10/23 a las 12:23, Holger Wansing escribió: >> Hi, >> >> Thomas Lange wrote (Wed, 4 Oct 2023 10:29:35 +0200): >>> Hi Holger, >>> >>> I really like the idea no to produce release notes for each >>> architecture but only one. Moving to sphinx is also nice. >>> >>> Sorry, if I broke your MR, by adding code that checks if something >>> changed in the git repo. I think I can easily add this to your code >>> later. So maybe we copy your version of 7release-notes and after that >>> I add my code. >> >> That would be really great! >> >>> Do you know how long the build process takes using sphinx? I've added >>> the code, because the build took around 90 minutes using docbook. >> >> I expect the build time to be reduced dramatically (rughly ~ 1/9, due to >> building only one arch instead of nine), but I have no definite values, >> expecially not for the run on www-master. >> >>> Any other things I should keep an eye on? >> >> None at the moment. >> >> Thanks for considering this MR. >> It would give us the possibility to move r-n to sphinx, which would be a >> great deal! >> >> >> Holger >> >> > -- Sent from /e/ OS on Fairphone3
Bug#1053445: Merge request regarding 'Please migrate Release Notes to reStructuredText'
Hello all Sorry for jumping into the thread withour having reading all of it, but the changes to the website cron jobs to build the trixie release notes (MR 13) have been integrated in the codebase (see https://salsa.debian.org/webmaster-team/cron/-/blob/master/parts/7release-notes ) and we're getting an error in the build process (hence the recent "ddp build failed" message in the debian-doc list). I think there are two issues: A) 7release-notes script now calls for trixie (https://salsa.debian.org/webmaster-team/cron/-/blob/master/parts/7release-notes#L208 ): make install DESTDIR=$crondir/tmp >> $notesdir/build.log 2>&1 while for the other releases the call is (https://salsa.debian.org/webmaster-team/cron/-/blob/master/parts/7release-notes#L242 ) make -C $notesdir/release-notes publish \ PUBLISHTARBALL=yes PUBLISHDIR=$webtopdir/www/releases/$release >> $notesdir/build.log 2>&1 I believe that the Makefile of release-notes understands "publish" instead of "install" but I'm not sure about how should we update L208 of the 7release-notes script. B) On the other hand, if I look at the master branch of the release-notes repo, I see that it's still written in docbook, not restructuredtext. I guess the files in the new format are still in https://salsa.debian.org/holgerw/release-notes and should be merged into the original release-notes repo first so we actually build them and not the old docbook ones, but not 100% sure about this point because I couldn't follow all the related threads with all the attention they needed (apologies!). Kind regards, El 4/10/23 a las 12:23, Holger Wansing escribió: Hi, Thomas Lange wrote (Wed, 4 Oct 2023 10:29:35 +0200): Hi Holger, I really like the idea no to produce release notes for each architecture but only one. Moving to sphinx is also nice. Sorry, if I broke your MR, by adding code that checks if something changed in the git repo. I think I can easily add this to your code later. So maybe we copy your version of 7release-notes and after that I add my code. That would be really great! Do you know how long the build process takes using sphinx? I've added the code, because the build took around 90 minutes using docbook. I expect the build time to be reduced dramatically (rughly ~ 1/9, due to building only one arch instead of nine), but I have no definite values, expecially not for the run on www-master. Any other things I should keep an eye on? None at the moment. Thanks for considering this MR. It would give us the possibility to move r-n to sphinx, which would be a great deal! Holger -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#1053445: Merge request regarding 'Please migrate Release Notes to reStructuredText'
Hi, Thomas Lange wrote (Wed, 4 Oct 2023 10:29:35 +0200): > Hi Holger, > > I really like the idea no to produce release notes for each > architecture but only one. Moving to sphinx is also nice. > > Sorry, if I broke your MR, by adding code that checks if something > changed in the git repo. I think I can easily add this to your code > later. So maybe we copy your version of 7release-notes and after that > I add my code. That would be really great! > Do you know how long the build process takes using sphinx? I've added > the code, because the build took around 90 minutes using docbook. I expect the build time to be reduced dramatically (rughly ~ 1/9, due to building only one arch instead of nine), but I have no definite values, expecially not for the run on www-master. > Any other things I should keep an eye on? None at the moment. Thanks for considering this MR. It would give us the possibility to move r-n to sphinx, which would be a great deal! Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#1053445: Merge request regarding 'Please migrate Release Notes to reStructuredText'
Hi Holger, I really like the idea no to produce release notes for each architecture but only one. Moving to sphinx is also nice. Sorry, if I broke your MR, by adding code that checks if something changed in the git repo. I think I can easily add this to your code later. So maybe we copy your version of 7release-notes and after that I add my code. Do you know how long the build process takes using sphinx? I've added the code, because the build took around 90 minutes using docbook. Any other things I should keep an eye on? -- regards Thomas
Bug#1053445: Merge request regarding 'Please migrate Release Notes to reStructuredText'
Hi, Holger Wansing wrote (Wed, 4 Oct 2023 09:27:34 +0200): > > I have just requested webmaster to switch the bookworm build from the > > master branch to the bookworm branch [1]. After that request gets merged > > and deployed, I'd like you to publish your work in the master branch > > such that we can work from there (and see the results too [2]). Because > > in your worked we stopped making notes per architecture, we probably > > need to make further changes to the webmaster archive, but let's first > > build something. > > Hey webmaster team, > > please consider MR13 in webmaster's cron repo: > > https://salsa.debian.org/webmaster-team/cron/-/merge_requests/13 I filed this MR ~ 6 weeks ago, but no reaction so far. And yesterday other commits made this MR broken, unable to merge it now. Needs to be overworked now. Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#1053445: Merge request regarding 'Please migrate Release Notes to reStructuredText'
Package: www.debian.org Severity: normal [Re-send attempt 3; simply mentioning a bug number in the subject apparently leads to the mail being sent to that bug; and therefore you have a mail, which tries to create a new bug, while replying to an exiting one; and this seems to be rejected by the BTS] Paul Gevers wrote (Thu, 24 Aug 2023 14:10:41 +0200): > Hi Holger, > > On 29-07-2023 21:29, Holger Wansing wrote: > > I have worked out the last big blocker for this migration now. > > That is, to allow the build on wolkenstein, which is happening via the > > parts/7release-notes script in webmaster-team/cron git repo. > > I have just requested webmaster to switch the bookworm build from the > master branch to the bookworm branch [1]. After that request gets merged > and deployed, I'd like you to publish your work in the master branch > such that we can work from there (and see the results too [2]). Because > in your worked we stopped making notes per architecture, we probably > need to make further changes to the webmaster archive, but let's first > build something. Hey webmaster team, please consider MR13 in webmaster's cron repo: https://salsa.debian.org/webmaster-team/cron/-/merge_requests/13 Thanks Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
