Bug#932957: New theme for docs in reStructuredText (was: Re: Bug#932957: #932957 Please migrate Release Notes to reStructuredText)
Hello Holger And since there has been a call for a Debian theme for Sphinx (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053549), a proposal for that can be found at https://people.debian.org/~holgerw/sphinx-theme-for-debian/alabaster/release-notes/ (for those, who are uncomfortable with the greenish theme). I've had a quick look at the theme inhttps://people.debian.org/~holgerw/sphinx-theme-for-debian/alabaster/release-notes/ and looks very nice both in my computer and my phone, and I think it's a good improvement for the current theme. Thank you *very much*. I don't know which is the better way forward, maybe add a repo for the theme in the ddp-team umbrella, and then file a bug for every documentation manual using Sphinx, suggesting including it? I also know there are some other bugs related to Debian Documentation using Sphinx (search box, javascript-related issues) but it's hard for me to find an enough-long chunk of time to look at them, apologies. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Re: 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
Re: 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#1032268: release-notes: upgrading a xen VM to bookworm will change network interface name to predictable scheme
Hello El 23 de mayo de 2023 13:30:28 CEST, Paul Gevers escribió: >Control: tags -1 patch > [...]. > >Can you elaborate what those changes are? Or is that extremely straightforward >if you're a Xen user? > >Proposed text handled here: >https://salsa.debian.org/ddp-team/release-notes/-/merge_requests/175 > I'm not sure about all the possible cases where this issue would need to be handled (and probably there are different 'ways' like changing the name in all the files where the interface is referenced, or disabling the predictable naming scheme) so a generic text as you propose looks the best to me. Thanks! Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona Sent with K-9 mail
Bug#932957: #932957 Please migrate Release Notes to reStructuredText
Hello We have an open bug related to creating a Debian theme for the documentation that uses Sphinx: #915583 debian-policy: More attractive sphinx theme, please https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915583 Unfortunately I think nobody could put on time on this yet. Other bugs related to Sphinx in Debian documentation that may need to be taken into account: #987943 www.debian.org: Developers Reference: Sphinx search non-functional: searchindex.js missing https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987943 #1026446 Static javascript resources for Policy and DevRef give 404 errors, breaking search https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026446 Kind regards, El 19/5/23 a las 1:58, Richard Lewis escribió: On Thu, 18 May 2023 22:39:11 +0200 Holger Wansing wrote: I worked on this recently, and I have something like a prototype ready. It can be found (as html) at https://people.debian.org/~holgerw/release-notes_sphinx/ I hope the below doesn't come across as negative - it;s not meant to be: i've been submitted MRs for release-notes and found the XML syntax adds complexity to the source that mostly only results in the output using bold or fixed-width: So it would be great to simplify to rst! Unfortunately, my first impression is that it the output has quite a few issues which make it a lot harder to read than the docbook version - which im sure is because it's still only a prototype, but thought it might helpful to list the things that jumped out at me: - It is a lot more cluttered than the docbook version - it feels off-putting and dense to read - it's all a bit 'blue' - i'd suggest red is more on-brand for debian - the "next"/"prev" links at the bottom-right are white on green --- I totally missed at first, and found hard to read - i was a bit confused by the "12.1" version number at the bottom of every page, and having 'sphinx' reminded me of websites with "hosted by geocities" - are the red hyphens in eg the 'deb...' line near the top of https://people.debian.org/~holgerw/release-notes_sphinx/en/html/issues.html meant to be red? (maybe it is a syntax error?) - package names are no longer distinguished from other text (eg 'ntp' in https://people.debian.org/~holgerw/release-notes_sphinx/en/html/issues.html#changes-to-packages-that-set-the-system-clock) - the order in the contents pane on the left is a bit...unusual: it starts with the current section, then does previous, then next, so eg on chapter 2, https://people.debian.org/~holgerw/release-notes_sphinx/en/html/whats-new.html it lists chapters 2, then 1, then 3. - https://people.debian.org/~holgerw/release-notes_sphinx/en/html/genindex.html is completely blank - not sure "show source" on the left is all that useful for readers I'm sure these are easy to fix! while the git repo containing the migration is at https://salsa.debian.org/holgerw/release-notes Im sure i am being dumb, but i couldnt spot where the actual rst files are? - i still see eg https://salsa.debian.org/holgerw/release-notes/-/blob/master/en/issues.dbk in XML as far as I know, sphinx/reStructuredText is still lacking some functionality, which is heavily used in the release-notes. That is the use of substitutions within URLs. You could always keep the entities and do a 'sed s//bookworm/g' etc before "building" with sphinx. Actually if i click 'show source' l get to https://people.debian.org/~holgerw/release-notes_sphinx/en/html/_sources/about.rst.txt which seems to have |RELEASE| and |RELEASENAME| rather than 12 and bookworm: perhaps sphinx supports entities after all? -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#1032268: release-notes: upgrading a xen VM to bookworm will change network interface name to predictable scheme
Package: release-notes Severity: normal X-Debbugs-CC: pkg-systemd-maintain...@lists.alioth.debian.org Dear Maintainer, I upgraded a virtual machine (xen guest) from Debian 11 to bookworm, everything went well, but lost network on reboot. The interface had changed its name from eth0 to enX0, I guess due to this change in systemd v 250: * The predictable naming logic for network interfaces has been extended to generate stable names from Xen netfront device information. (ref: https://github.com/systemd/systemd/releases/tag/v250 ) I wonder if it would be nice to mention this in the systemd NEWS file or in the release notes, so people do the needed changes in their machines before rebooting the system after upgrade. Sending this bug to release-notes but CC'ng pkg-systemd-maintainers@ Thanks! -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Release notes builds for bullseye and bookworm (not for buster)
Dear all Thanks Paul Gevers the cron jobs that build the Debian website have been updated to build release notes for bookworm from now on (in addition to bullseye) [1]. [1] https://salsa.debian.org/webmaster-team/cron/-/merge_requests/11 They will appear under https://www.debian.org/releases/bookworm/*/release-notes/ and https://www.debian.org/releases/testing/*/release-notes/ in the following hours. With this change, release notes for buster (and former releases) won't be built regularly (their last build (e.g. from last night for buster) will remain online). I see that buster is LTS until June 2024, but last commit for its release notes is from 11 months ago. So I think that the current status is ok. In any case, if anybody commits updates to the release notes of buster and needs them to be rebuilt once again (to show these updates in the Debian website), please ping us at debian-...@lists.debian.org or submit a MR to the cron repo (in a similar way of the change above). Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Re: Different Chinese
Hello all El 11 de mayo de 2022 15:10:26 CEST, DU Haoran escribió: >Hi, >According to the link, the first "Chinese" is zh-CN and the second one is >zh-TW. Thanks. I guess Sebul's question implicitly has a request for us to display the Chinese variant in the web page. I've had a look and I believe the issue comes because in /english/doc/manuals.def we remove the second part of the name of the locale: https://salsa.debian.org/webmaster-team/webwml/-/blob/master/english/doc/manuals.defs#L92 This is fine for our current status of Portuguese translations (in the website there is only the Brazilian variant and we display "Portuguese") but not fine for Chinese because we usually have more than one variant. I will try to do some local tests omiting this line and see the build result or maybe add code to not to remove the variant part in the case of cn locales, but I guess the manuals.def is used in several other web pages so better to see the side effects of the change in local tests prior to commit changes. If anybody has time or better idea please go ahead. CC'ing debian-doc for the case they know better or find the time to do tests and fix this before I can come back to this. Kind regards >Yours, >Haoran > >Yours faithfully, >Haoran Du > >From: sebuls >Sent: Wednesday, May 11, 2022 7:00:01 AM >To: debian-...@lists.debian.org >Subject: Different Chinese > >Hi. ><https://www.debian.org/doc/user-manuals.en.html#quick-reference>https://www.debian.org/doc/user-manuals.en.html#quick-reference >shows two Chinese. >Chinese: [HTML] [plain text] [PDF] >Chinese: [HTML] [plain text] [PDF] >One is zh-cn and the other is zh-tw. >How to distinguish ? > > >[https://confirm.mail.kakao.com/v1/users/sebuls%40kakao%2Ecom/cmails/20220511080001%2EG1u-k_I5SAaNJuOGQ3hZoQ%40sebuls%2Ekakao%2Ecom/recipients/debian-www%40lists%2Edebian%2Eorg] -- Laura Arjona Reina https://wiki.debian.org/LauraArjona Sent with K-9 mail
Re: Constitution A.6 - "V(A,D) is strictly great"
Hi all I have changed the constitution files in the website repo to match the updated text currently now in doc-debian package: https://salsa.debian.org/webmaster-team/webwml/-/commit/e3d525d9f092f9014e00417cc847900ac5a99649 The fix will be available online after the next build. I didn't close the bug because I don't know if a decision has been taken about which one of the two sources (website repo or debian-doc package repo) should be the "canonical" one. In my opinion, the website, but I'm biased of course :-) Kind regards, El 4/4/21 a las 11:05, Kurt Roeckx escribió: > On Sun, Apr 04, 2021 at 09:31:46AM +0200, Niels Thykier wrote: >> Hi, >> >> In https://www.debian.org/devel/constitution#item-A, there is the >> following sentence under A.6. bullet 3.2.: >> >>> An option A defeats the default option D by a majority ratio N, if V(A,D) >>> is greater or equal to N * V(D,A) and V(A,D) is strictly great >> >> The "... and V(A,D) is strictly great" looks like an incomplete >> sentence. Is that something we can fix as an editorial correction (i.e. >> without a vote)? > > See #896067. > > > Kurt > -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Re: [debwww cron] often failed (at parts/7doc: python3)
Hi Holger El 15/3/21 a las 16:07, Holger Wansing escribió: > Hi Laura, > > FYI: I noticed that the often cron script failed, due to the python-policy > document. > Oh, I've been afk for some time and received the mails but didn't look too much to their contents :/ > They have moved the doc to -dev package and converted to Sphinx. > I have fixed the scripts to deal with this (fingers crossed). > Thank you very much! > If you like, you could add my mail address for those cron scripts, to make > more people getting notice of such errors... > The addresses receiving debwww cron mails are setup in the "webwml-monitor:" entry in /srv/www.debian.org/mail/aliases file in www-master machine (currently wolkenstein.debian.org). I have added your mail address there. I still couldn't work on bug #911896 (Review, update and document the mail setup of www.debian.org-related addresses), not sure about the better place to put such info, maybe in a wiki page? Thanks again! -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Re: odd emacs version in project-history
Hi I think the mistake is in "Emacs", it should be Exim (Exim 4.88 was shipped with Debian 9 stretch): https://www.debian.org/releases/stretch/amd64/release-notes/ch-whats-new.en.html Kind regards, El 13/4/20 a las 9:18, Fabrice BAUZAC-STEHLY escribió: > Hello, > > 황병희 writes: > >> While i read the project history, i found somewhat odd words which was >> Emacs version [1] for Stretch release. >> >> There is special Emacs version naming rule? >> >> [1] "Emacs 4.88": >> https://salsa.debian.org/ddp-team/project-history/-/blob/master/project-history.en.dbk#L1435 > > This version number 4.88 comes from Javier's commit > 41a115fd66703a32e728f6cc3ddbc207dac5ac02. > > This looks like a little mistake to me indeed; apparently in Stretch the > latest Emacs version available is 25.1. > > I guess 25.1 is the correct version? I've just created this merge > request [2], can we merge it? > > [2] https://salsa.debian.org/ddp-team/project-history/-/merge_requests/5 > > Thanks! > > Best regards > > -- > Fabrice BAUZAC-STEHLY > PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D > -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Re: Publishing a new book
Hello Mechtilde El 30/3/20 a las 17:37, Mechtilde Stehmann escribió: > hello ddp-team, > > can someone of the owners can add me to the group > > https://salsa.debian.org/ddp-team > Done, thanks! Kind regards, > Kind regards > > Mechtilde > Am 22.03.20 um 16:39 schrieb Mechtilde Stehmann: >> Hello, >> >> I'm working on a book about packaging with gbp-buildpackage. >> >> The book includes the program which builds a Debian package step-by-step. >> >> It is a LaTeX/NoWeb document written in German. The program itself has >> an English UI. >> >> I want to publish it in the group ddp-team. >> >> I is licensed under CC By-SA 4.0 >> >> If you need more information please ask. >> >> Kind regards >> > -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Re: Fwd: "A Brief History of Debian: Chapter 2 - Leadership" online page needs some update
Hi all El 28/3/20 a las 22:11, Andrei POPESCU escribió: > On Sb, 28 mar 20, 21:24:36, l0f...@tuta.io wrote: >> Andrei, >> >> 28 mars 2020 à 17:02 de andreimpope...@gmail.com: >> >>> Might I suggest you provide a patch? The sources appear to be on Salsa. >>> https://salsa.debian.org/ddp-team/project-history >>> >> I'm not used to Salsa but are you sure your link is correct? >> Indeed, no merge request about this is in process and everything seems >> to be already OK >> at >> https://salsa.debian.org/ddp-team/project-history/-/blob/master/project-history.en.dbk: >> "Sam Hartman was elected in April 2019 and is our current leader." > > Dear Debian Web Team, > > It seams the project history on www is not up to date, Sam Hartman is > missing from the list of Project Leaders. Yes, unfortunately this is one of the consequences of the bug #92: we need to adapt the cron script that generate the manuals, so they work with the repos in salsa (they are failing since the migration alioth -> salsa). https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922222 I guess that until now, nobody could find the time/energy to fix this, so any help is welcome. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Debian's application for Season of Docs 2019 was unsuccessful
Dear all Thanks everybody for your interest and enthusiasm in Debian's participation in Google Season of Docs. Unfortunately Debian’s application was not successful this year. You can view the accepted organisations in https://developers.google.com/season-of-docs/docs/participants/ We'll stay in touch to see the progress of this first edition of GSoD and learn for future editions, hopefully with Debian's participation. Some of the GSoD project ideas that were added in https://wiki.debian.org/SeasonOfDocs2019/Projects (or other documentation-related projects) may appear soon as project ideas for the next rounds of Outreachy. In any case, if any of you is interested in contributing your skills and free time to improve Debian's documentation, the usual ways to get involved in Debian are valid :-) Don't hesitate to get in touch and we'll try to do our best to guide your first steps. Here you can find some tips: * Visit https://wiki.debian.org/Teams/Welcome and get in touch with the Welcome team if you want to contribute but you need guidance to find the Debian team or area more suitable for you. * Visit https://wiki.debian.org/Teams/Outreach and get in touch with the Outreach team to help extending Debian and participate in (next edition of) programs like GSoC, Outreachy or GSoD. * Visit https://wiki.debian.org/Teams/DDP and get in touch with the Documentation team to start contributing improving Debian's documentation Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Debian's participation in Google Season of Docs program
Dear all, TL;DR: We want Debian to participate in the first edition of Google Season of *Docs*. Deadline for org application is really soon (23 April 20:00UTC). The program itself will start in September until end of November. We think we have enough workforce to handle the program, but we need more mentors (we have several ideas with 1 mentor and we need 2 mentors per project). You can submit more ideas but tomorrow we'll discard the ideas with less than two mentors and submit Debian's application for 1-2 projects. Details in https://wiki.debian.org/SeasonOfDocs2019 Long version: Google Open Source has announced its first edition of the "Google Season of Docs" program, aimed to bring together technical writers and open source projects, in a program similar to the Google Summer of Code, but focused in documentation. https://developers.google.com/season-of-docs/ We think that it could be a good opportunity for Debian to participate this year, with this goals in mind: * As one more outreach program: extend Debian to new groups of people * Improve Debian documentation, by means of collaborative work of the people involved in GSoD and the corresponding Debian teams * Retain talent and motivation to further work in documentation areas (not only during the program) This year is the first edition and there will be a maximum of 2 technical writers per organisation. Some people in the outreach team have talked about participating and we think we can have enough workforce to apply and handle 1 or 2 persons in 1 or 2 different projects. This is our proposal of organisation and guidelines: * Program Admins: Pranav Jain (outreach team) and Laura Arjona Reina (website, i18n team) * Coordination list: debian-outre...@lists.debian.org * Deadline for Debian submissions: 23 April 20:00 UTC * The program/mentorship will be: September-October-November 2019 * Guidelines for GSoD Projects in Debian: see wiki page https://wiki.debian.org/SeasonOfDocs2019 * Initial Project ideas: English proofread, Profile parser to get involved in Debian, Mixed tasks for the Debian website. For more details see: https://wiki.debian.org/SeasonOfDocs2019 As you can see we have provided some projects as "Project ideas" already. We're open for more ideas and overall *we need more mentors/co-mentors* (at least 2 per project, so help is appreciated!). Please keep in mind that we'll finally offer/be accepted in only 2 projects max, so we appreciate to sum forces better than spread them in many different subprojects. We have added a field to add stars "*" to let people show interest in that project idea happening so you can edit the page and add your "stars" (3 for your favorite project) so we can prioritise the ideas when submitting Debian's application. But of course the most prioritised projects will be the ones having more mentors :-) (in fact, we'll have to discard the ideas with less than 2 mentors prior to submitting...) We'll submit Debian application on April 23rd around 18:00 UTC (deadline is April 23rd 20:00 UTC) so we encourage interested people in helping with GSoD (mentoring, helping with paperwork, spreading the word or welcoming applicants...) to get in touch (in debian-outre...@lists.debian.org) ASAP. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona signature.asc Description: OpenPGP digital signature
Re: Bug#926558: Cleanup of /doc/ddp
CC'in debian-doc@lists.debian.org I still have no opinion about this bug, I'll try to put time on getting #92 fixed first https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=92 so we can see the bigger picture. Kind regards, El 6/4/19 a las 23:35, Thomas Lange escribió: > > Package: www.debian.org > User: debian-...@lists.debian.org > Usertags: content > > I like to remove very old and outdated content. > > Links -> "Debian Linux Installation & Getting Started article in the Linux > Gazette" links to an article from 1997. > > The section "Todo List" has two links which point to the same > page. The last addition to /doc/todo was in 2005. > > /doc/topics is "DDP current topics". The last change of the content > was in 2000. > > Any objections about just removing those? > > > "Problematic manuals" > > I want to replace the whole section with a link to > https://salsa.debian.org/ddp-team/attic > > We can then also remove doc/obsolete.wml > -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
RFA: www.debian.org/doc/books
Dear all As part of the recent web team sprint [1] (report will come in the following days hopefully), we have reviewed several areas of the website that were in need of maintenance. [1] https://wiki.debian.org/Sprints/2019/DebianWebTeam For the /english/doc/books page [2], we need maintainer(s) to keep up-to-date the database of books, process new requests, and care about the bugs related to the list of books, if any. [2] https://www.debian.org/books This is a call for help, or request for "adoption": would anybody volunteer to this task? In the /english/doc folder of our repo [3] you can find the books-related files. [3] https://salsa.debian.org/webmaster-team/webwml/blob/master/english/doc/ Maintaining the /doc/books section can be a nice entry point for somebody to get involved in the Debian web team. Technically speaking, it's an easy job, but the "curation" task that a human provides is very appreciated by our users. On the contrary, an outdated or unmaintained list of books looses its value very quickly. If somebody is interested in adoption, they won't be alone (at least at the beginning). I've included my address in the alias bo...@debian.org to work together with them until they find a suitable workflow and they feel comfortable doing the task themselves. We'll also document everything for others to jump in too. If nobody steps ahead at the end of the year, we'll move the current (English) content to a page under wiki.debian.org, removing the section (English and translations) from www.debian.org. If you are interested, reply to this message in the public mailing list (debian-...@lists.debian.org) or privately to bo...@debian.org and I'll point to detailed steps to start. You can also join #debian-www IRC channel (in irc.debian.org). Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Re: debian-history: two git repositories at salsa ???
Hi all El 9/3/19 a las 19:00, Holger Wansing escribió: > Hi all, > > it came to my attention, that apparently there are two repositories for > debian-history at salsa: > > https://salsa.debian.org/ddp-team/project-history > https://salsa.debian.org/publicity-team/debian-history > > Or am I missing something? > > Looking at the commit history, it seems that the former is the "correct" one, > while the latter is a later created fork? > > What's the rationale for this? > The one under the publicity team was created some time ago to test sgml -> po conversion and help the Spanish translation. Unfortunately nor Ana nor me could find much time to advance the work. Now I see that the project has moved to dbk + po files, thanks! I'll try to compare both Spanish translations, merge translations (if needed) to the ddp-team repo, and remove our old repo. Thanks for caring, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#904525: release-notes: Links to buster release notes don't work
Hello again El 12/2/19 a las 19:35, Niels Thykier escribió: > Niels Thykier: > Hi, > > I got a reply on IRC and have now created a MR request here: > > https://salsa.debian.org/webmaster-team/cron/merge_requests/2 > Merged, thanks! I'll check the result of the next builds and when I see everything ok in the website I'll close the bug(s) (hopefully in the next hours/day). Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#904525: release-notes: Links to buster release notes don't work
Hi El 12 de febrero de 2019 19:16:00 CET, Niels Thykier escribió: >Baptiste Jammet: >> Hello all, >> (adding -release to Cc since they are "in charge" for the release >notes) >> >> Dixit Martin Michlmayr, le 12/02/2019 : >> >>> Since the freeze has started, are there plans to get the release >notes >>> for buster published (even if only a draft)? >> >> I think we are still trying to find time to do this ! >> >> Technically: >> Do we create a branch for Stretch and use master for Buster, >> or use a branch for Buster? (what's the use of master?) >> I prefer the first solution. >> > >Ack, lets move along with using master for buster. I have pushed a >stretch branch now, so it can be used for the job. > Great, thanks! >> In any case, -www should be asked to update cron/parts/7release-notes >> to add the build for the website. >> >> If nobody disagree or run faster, I can do it in the next few >> days. >> >> Thanks for the reminder. >> Baptiste >> > >Is there a salsa repo for that ? I might be tempted to do a MR for it >if there is. > Yes: https://salsa.debian.org/webmaster-team/cron Thanks again -- Laura Arjona Reina https://wiki.debian.org/LauraArjona Sent with K-9 mail
add member to DDP group in salsa (was: Re: [debian refcard] call for translation update)
Hi all El 10/1/19 a las 16:40, Holger Wansing escribió: Hi, Am Donnerstag, 10. Januar 2019 schrieb Kamen Naydenov: On Wed, Jan 9, 2019 at 1:04 PM Holger Wansing wrote: Then tell me your username, you chose there. Hi, my username is pau4o-guest - https://salsa.debian.org/pau4o-guest @debian-doc: Could someone add Kamen (Bulgarian translator for the Debian refcard) to the "Debian Documentation Project" group, please? Done. Welcome Kamen Naydenov! Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Re: Fw: Request to join the Debian Documentation Project group
El 26 de diciembre de 2018 11:39:05 CET, Holger Wansing escribió: >Hi, > >could someone please add Asalle-guest to the group? >He is Ukranian translator for the refcard. > Done. Welcome Asal! Kind regards >Thanks > >Holger > > > > > >Date: Wed, 26 Dec 2018 09:06:56 + >From: Debian GitLab >To: holg...@debian.org >Subject: Request to join the Debian Documentation Project group > > >Asal Mirzaieva (https://salsa.debian.org/Asalle-guest) requested >Developer access to the Debian Documentation Project group. > >https://salsa.debian.org/groups/ddp-team/-/group_members -- Laura Arjona Reina https://wiki.debian.org/LauraArjona Sent with K-9 mail
Re: Access request to Debian Documentation Project on Salsa
El 28 de noviembre de 2018 14:07:16 CET, Andrei POPESCU escribió: >Hello -doc, > >Please note I just sent an access request via Salsa. Granted, thanks! >If time allows I would like to have a Romanian translation of the >Release Notes for buster as we had as in previous releases (except >stretch). > Great! Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona Sent with K-9 mail
Re: 7doc_manuals cron script fails (trying to access svn repo in Alioth)
Hello web and documentation teams, El 31/5/18 a las 23:57, Laura Arjona Reina escribió: Hello Debian Documentation team: One of the scripts that we use to build the Debian website (www.debian.org), 7doc_manuals, does not work anymore. Source code: https://salsa.debian.org/webmaster-team/cron/blob/master/parts/7doc_manuals It tries to access svn repo(s) in alioth: svn export --force svn://svn.debian.org/svn/ddp/manuals . > svn.log 2>&1 and they are not available anymore. Can you update it to access the corresponding repo in salsa? (or give us a hint about what to do). I've been looking at the code of the 7doc_manuals script: https://salsa.debian.org/webmaster-team/cron/blob/master/parts/7doc_manuals and the current organisation of the ddp repos in Salsa. I've listed all the manuals that were built from the original SVN "manuals" repo, reviewed case by case, and this is my proposal: 1.- The following manuals show "Obsolete documentation" in their first page of the content, and also are hosted now under https://salsa.debian.org/ddp-team/attic: apt-howto book-suggestions ddp-policy -> would close #147164 www.debian.org: DDP: DDP policy is too out of date dictionary debian-euro-support meta network-administrator programmer repository-howto system-administrator tutorial user users-guide so I propose remove them from the "7doc_manuals" build script and remove the manuals from the Debian website. Then, in the pages where we link to them, change the link to point to the corresponding attic repo and add a note about "obsolete documentation" (if it's not there yet). The person wanting to get the obsolete manuals, can download the repo and build themselves. 2.- The following manuals don't include the text "Obsolete documentation", but they are hosted in https://salsa.debian.org/ddp-team/attic, so I'm not sure what to do: debian-bugs (in attic) distribute-deb (in attic) dselect-beginner (in attic) fr/debian-fr-howto intro-i18n For now, I propose to remove them from the build script and keep the copy built in May 2018 in the Debian website. Maybe add a README file in the webwml repo in english/doc explaining where are the repos for the case it's needed to build them again. 3.- The following manuals are current, so I (if nobody beats me to it) will adapt the script to get the last changes from the current git repo, and build: https://salsa.debian.org/ddp-team/hamradio-handbook.git https://salsa.debian.org/ddp-team/java-faq.git 4.- The following manuals are current, but the current "make" command in the 7doc_manuals script would not work even if we get the git repos. I appreciate help to adapt the 7doc_manuals script for these: https://salsa.debian.org/ddp-team/project-history.git make -C project-history publish PUBLISHDIR=/srv/www.debian.org/www/doc/manuals install_file="install -p -m 664" install_dir="install -d -m 2775" make: *** No rule to make target 'publish'. Stop. https://salsa.debian.org/ddp-team/securing-debian-manual.git make -C securing-howto publish PUBLISHDIR=/srv/www.debian.org/www/doc/manuals install_file="install -p -m 664" install_dir="install -d -m 2775" make: *** No rule to make target 'publish'. Stop. Comments welcome. Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Re: Documenting installer issues for jessie LTS
El 10/11/18 a las 22:55, Laura Arjona Reina escribió: > > For the website, I have created the merge request with a proposal: > > https://salsa.debian.org/webmaster-team/webwml/merge_requests/40 > > (I'm attaching the diff too). > Sorry, I forgot the attachment. Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona diff --git a/english/releases/jessie/debian-installer/index.wml b/english/releases/jessie/debian-installer/index.wml index 70c6d2b3ba7..b53aaa6022a 100644 --- a/english/releases/jessie/debian-installer/index.wml +++ b/english/releases/jessie/debian-installer/index.wml @@ -156,6 +156,24 @@ for other known problems. ## Translators: copy/paste from devel/debian-installer/errata + +Errata for release 8.11 + + + pkgsel does not install updates with ABI changes (by default) + + Bug https://bugs.debian.org/908711;>#908711: + during installation with network sources enabled, the + installed security updates don't include updates that depend on a new + binary package, due to a kernel or library ABI change. + + Status: This has been fixed in the installer included + for newer releases (Debian 9 stretch). For Debian 8 installations, since no new + Debian installer is provided, security updates that depend on new packages + should be installed manually, by running + apt-get upgrade --with-new-pkgs after the first install and reboot. + + Errata for release 8.0
Re: Documenting installer issues for jessie LTS
Hello all El 9/11/18 a las 2:50, Ben Hutchings escribió: > I recently discovered a bug in the installer (#908711). During > installation with network sources enabled, security update are normally > installed. However, this didn't include updates that depend on a new > binary package, due to a kernel or library ABI change. > > I fixed this bug in unstable and in a stable update that will be > included in Debian 9.6. However, since there are no stable updates > during the LTS period, this bug will remain unfixed in the installer > for jessie. > > I have updated the wiki LTS/Installing page and added post-installation > steps to install the missed upgrades. However, I wonder whether it > would be helpful and possible to update the release notes or other > official documentation at this stage? > > Ben. > Thanks for reporting. For the website, I have created the merge request with a proposal: https://salsa.debian.org/webmaster-team/webwml/merge_requests/40 (I'm attaching the diff too). Comments and/or improvements very welcome (CC'ing debian-boot). If there is no activity, I plan to merge this in a week or so. Respect to the release notes, I'm not sure if this documentation should go there and in which section specifically (CC'ing debian-doc for help). We have fixed our cron script for publishing the release notes against git (thanks Baptiste Jammet, and sorry for the delay!) and this means that if a patch is accepted in the jessie branch of the release notes (https://salsa.debian.org/ddp-team/release-notes/ ), it will be published in the website too (we will build jessie release notes for the website at least until the LTS support finishes). Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Re: The Documentation Webpage for Each Debian Release?
Hello Rajib El 25/9/18 a las 10:51, Susmita/Rajib escribió: Dear Ms. Reina, I apologise to appear persuasive, while my only intent is to further clarify my requirements. No problem :-) I can of course have the "Debian Reference" manual for Wheezy from packages, untar them and read them. That was going to be my next suggestion (thanks Documentation team for the hint!). But there appears to be no link to the older online versions of the document. It is understood that the older versions are not hosted any longer. Only the current one is. That's correct. Maybe you can get old versions using the wayback machine of archive.org, for example: https://web.archive.org/web/*/https://www.debian.org/doc/manuals/debian-reference/ Not an issue. I hope that I have been able to express myself better this time. I sincerely apologise for causing confusion. May I please be forgiven. No problem at all! Thanks for using Debian. Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Re: The Documentation Webpage for Each Debian Release?
Hello Rajib El 24/9/18 a las 13:03, Susmita/Rajib escribió: Dear List Administrator, Every current Debian Release has a documentation page here: Documentation https://www.debian.org/doc/ Unfortunately, the documentation webpage for the older releases can not being found. For example, I wanted to read the web documentation page for Debian Wheezy. But can no longer find it. Could you please help? The documentation related to Debian Wheezy (installation guide, release notes) can be found in the page about the Wheezy release: https://www.debian.org/releases/wheezy I am not sure if we should add some lines to https://www.debian.org/doc/ explaining this; so I'm attaching a proposal and CC'ing debian-doc mailing list. Note: I don't like my wording, I'm sure there is a simpler/clearer way to express the idea, but I couldn't find it... Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona diff --git a/english/doc/index.wml b/english/doc/index.wml index 749afa580a2..e3c7ffa18ea 100644 --- a/english/doc/index.wml +++ b/english/doc/index.wml @@ -48,6 +48,7 @@ These documents come in these basic categories: HOWTOs FAQs other shorter documents + documentation for other releases different than stable Manuals @@ -221,6 +222,12 @@ images. +Documentation for other releases different than stable + +If you are looking for documentation (installation guide, release notes) of a certain +Debian release, please go to the https://www.debian.org/releases/;>web page about Debian releases +and click on the link for that particular release. +
Bug#901180: release notes fails to build in a clean checkout
Package: release-notes Severity: normal Hello I have cloned the release-notes repo and did "make" to build the release notes, but I got an error (attached complete log, here an extract): LANG=C ./transcount en ca cs >> statistics.txt svn: E155007: '/srv/www.debian.org/release-notes/release-notes/en/moreinfo.dbk' is not a working copy svn: E155007: '/srv/www.debian.org/release-notes/release-notes/en/issues.dbk' is not a working copy svn: E155007: '/srv/www.debian.org/release-notes/release-notes/en/old-stuff.dbk' is not a working copy svn: E155007: '/srv/www.debian.org/release-notes/release-notes/en/installing.dbk' is not a working copy svn: E155007: '/srv/www.debian.org/release-notes/release-notes/en/upgrading.dbk' is not a working copy svn: E155007: '/srv/www.debian.org/release-notes/release-notes/en/release-notes.dbk' is not a working copy svn: E155007: '/srv/www.debian.org/release-notes/release-notes/en/about.dbk' is not a working copy svn: E155007: '/srv/www.debian.org/release-notes/release-notes/en/whats-new.dbk' is not a working copy Traceback (most recent call last): File "./transcount", line 37, in if revision >= revisions[fn]: KeyError: 'moreinfo.dbk' Makefile:346: recipe for target 'statistics.txt' failed make: *** [statistics.txt] Error 1 I guess the "transcount" script needs to be adapted to use git instead of subversion. However, if I run again "make", the build goes on and finishes correctly. If I do "make clean" and then "make" again, I face the issue again. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona for l in en da de es fr it ja nl pt-br pt ro ru sv sk pl; do \ make FORCE LINGUA=$l; \ done make[1]: Entering directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Nothing to be done for 'FORCE'. make[1]: Leaving directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Entering directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Nothing to be done for 'FORCE'. make[1]: Leaving directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Entering directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Nothing to be done for 'FORCE'. make[1]: Leaving directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Entering directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Nothing to be done for 'FORCE'. make[1]: Leaving directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Entering directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Nothing to be done for 'FORCE'. make[1]: Leaving directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Entering directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Nothing to be done for 'FORCE'. make[1]: Leaving directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Entering directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Nothing to be done for 'FORCE'. make[1]: Leaving directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Entering directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Nothing to be done for 'FORCE'. make[1]: Leaving directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Entering directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Nothing to be done for 'FORCE'. make[1]: Leaving directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Entering directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Nothing to be done for 'FORCE'. make[1]: Leaving directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Entering directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Nothing to be done for 'FORCE'. make[1]: Leaving directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Entering directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Nothing to be done for 'FORCE'. make[1]: Leaving directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Entering directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Nothing to be done for 'FORCE'. make[1]: Leaving directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Entering directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Nothing to be done for 'FORCE'. make[1]: Leaving directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Entering directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Nothing to be done for 'FORCE'. make[1]: Leaving directory '/srv/www.debian.org/release-notes/release-notes' make en/old-stuff.dbk LINGUA=`basename en` make[1]: Entering directory '/srv/www.debian.org/release-notes/release-notes' make[1]: Nothing to be done for 'en/old-stuff.dbk'. make[1]: Leaving directory '/srv/www.debian.org/release-notes/release-notes' make en/release-notes.dbk LINGUA=`basename en` make[1]
Bug#901172: update 7release-notes script to use the git repo of "release-notes"
Package: www.debian.org Severity: normal User: debian-...@lists.debian.org Usertags: scripts Tags: patch X-Debbugs-CC: debian-doc@lists.debian.org Hello all The "often" cron job for building the release notes (for the Debian website) currently fails because it's still using svn and alioth. Here is the log: https://www-master.debian.org/build-logs/webwml/release-notes.log and its content: Sat Jun 9 16:55:05 UTC 2018 rebuilding the release notes for wheezy Updating '.': svn: E170013: Unable to connect to a repository at URL 'svn://svn.debian.org/svn/ddp/manuals/branches/release-notes/wheezy' svn: E670002: Unknown hostname 'svn.debian.org' The job script is here: https://salsa.debian.org/webmaster-team/cron/blob/master/parts/7release-notes I'm attaching a patch to update the job to use git. Reviews are appreciated. Some notes: 1.- With svn we had one folder for each branch that was storing the release notes of one release. So, now we have this structure in www-master.debian.org: /srv/www.debian.org/release-notes /srv/www.debian.org/release-notes/stretch /srv/www.debian.org/release-notes/jessie /srv/www.debian.org/release-notes/wheezy /srv/www.debian.org/release-notes/squeeze /srv/www.debian.org/release-notes/lenny /srv/www.debian.org/release-notes/etch /srv/www.debian.org/release-notes/build.log /srv/www.debian.org/release-notes/build.log.* In git we have branches but everything is in the same folder. So in my patch I assume that we have a clone of the release-notes repo, and thus we would have this structure in www-master.debian.org: /srv/www.debian.org/release-notes /srv/www.debian.org/release-notes/release-notes (git repo) /srv/www.debian.org/release-notes/build.log /srv/www.debian.org/release-notes/build.log.* and use git checkout to each release (branch). 2.- I have cloned locally the release-notes repo to try to test my changes to the cron script, but the local build fails. I will file a separate bug about this against release-notes. When that issue is fixed I will try to build the notes locally and test my patch, but in the meanwhile any comment is welcome. Cheers -- Laura Arjona Reina https://wiki.debian.org/LauraArjona From f143f2a3e7f7e7c918664d050b22008a03be241a Mon Sep 17 00:00:00 2001 From: Laura Arjona Reina Date: Sat, 9 Jun 2018 20:37:42 +0200 Subject: [PATCH] Update 7release-notes script to use the git repo in Salsa --- parts/7release-notes | 15 +-- 1 file changed, 5 insertions(+), 10 deletions(-) diff --git a/parts/7release-notes b/parts/7release-notes index 395607f..664da58 100755 --- a/parts/7release-notes +++ b/parts/7release-notes @@ -13,18 +13,13 @@ date > $notesdir/build.log # Add the release name once released/branched out of trunk for release in wheezy jessie stretch ; do echo "rebuilding the release notes for $release" >> $notesdir/build.log -if ! [ -d "$notesdir/$release" ] ; then -echo "directory $notesdir/$release does not exist. checking out SVN" >> $notesdir/build.log -cd $notesdir -if [ "$release" = "stretch" ]; then -svn checkout svn://svn.debian.org/svn/ddp/manuals/trunk/release-notes $release >> $notesdir/build.log 2>&1 -else -svn checkout svn://svn.debian.org/svn/ddp/manuals/branches/release-notes/$release >> $notesdir/build.log 2>&1 -fi +cd $notesdir/release-notes +if [ "$release" = "stretch" ]; then +git checkout master && git pull >> $notesdir/build.log 2>&1 else -(cd $notesdir/$release && svn update) >> $notesdir/build.log 2>&1 +git checkout $release && git pull >> $notesdir/build.log 2>&1 fi - make -C $notesdir/$release publish \ +make -C $notesdir/release-notes publish \ PUBLISHTARBALL=yes PUBLISHDIR=$webtopdir/www/releases/$release >> $notesdir/build.log 2>&1 done -- 2.11.0
7release-notes cron script fails (trying to access svn repo in Alioth)
Hello again El 31/05/18 a las 23:57, Laura Arjona Reina escribió: > Hello Debian Documentation team: > > One of the scripts that we use to build the Debian website > (www.debian.org), 7doc_manuals, does not work anymore. > Similar issue with 7release-notes script. Source code: https://salsa.debian.org/webmaster-team/cron/blob/master/parts/7release-notes It tries to access the svn repo(s) in alioth: svn checkout svn://svn.debian.org/svn/ddp/manuals/trunk/release-notes $release >> $notesdir/build.log 2>&1 [...] svn checkout svn://svn.debian.org/svn/ddp/manuals/branches/release-notes/$release >> $notesdir/build.log 2>&1 svn.debian.org is not available anymore. Thanks! -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
7doc_manuals cron script fails (trying to access svn repo in Alioth)
Hello Debian Documentation team: One of the scripts that we use to build the Debian website (www.debian.org), 7doc_manuals, does not work anymore. Source code: https://salsa.debian.org/webmaster-team/cron/blob/master/parts/7doc_manuals It tries to access svn repo(s) in alioth: svn export --force svn://svn.debian.org/svn/ddp/manuals . > svn.log 2>&1 and they are not available anymore. Can you update it to access the corresponding repo in salsa? (or give us a hint about what to do). If you prefer that I file a bug, just tell (against www.debian.org pseudopackage or against which other package?). Thanks! -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Re: Move of DDP SVN repository to Salsa?
Hello El 08/05/18 a las 15:26, Javier Fernandez-Sanguino escribió: > Dear colleagues, > > Is anyone currently working on moving the entire DDP SVN repository from > Alioth > to Salsa? > > It appears the tasks listed below are still outstanding, I can work on these > or > split the work with others. Any volunteers? > > Please feel free to add to the list below of tasks. If there are people who > can > help with the list below maybe we should first put it in the Wiki to > coordinate. > > Tasks to do > > > To move DDP to Salsa, the following needs to be done: > > - Create a project in Salsa [ DONE - https://salsa.debian.org/debian/ddp] > - Add all of Alioth's DDP users to Salsa > - Migrate Alioth DDP SVN to Salsa Git > - Change www-master.debian.org <http://www-master.debian.org> for it to > update > from Salsa's GIT repository instead of Alioth's SVN (requires DA support I don't understand what "DA support" means. There is needed to update the scripts in https://salsa.debian.org/webmaster-team/cron/ to use git and salsa instead of svn and alioth. I can help with that, once the repos are in salsa. I don't know if you were referring to this in that "Change www-master.debian.org" line, or they are 2 different tasks. I can try to help with whatever is needed in www-master.debian.org (for example, if webwml permissions are required). > - Update the Website (more specifically https://www.debian.org/doc/) to point > to > the new location of the repository in all the different pages > (https://www.debian.org/doc/cvs, but also in the description of the different > manuals) I will try to help with those ones, too. Cheers -- Laura Arjona https://wiki.debian.org/LauraArjona > - Update the Wiki - mainly https://wiki.debian.org/Teams/DDP, but also links > to > repository in other pages (such as https://wiki.debian.org/ReleaseNotes) > - Change and upload the different documentation packages to update the VCS URL > (at least debian-faq and debian-doc) > > > Regards > > Javier -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Re: Bug#893397: adapt the cron scripts to use http:// instead of ftp://
Hello
I've been doing some tests and this is what I have, for now:
* the current script is in:
https://anonscm.debian.org/cgit/debwww/cron.git/tree/parts/1ftpfiles
(and it works, not sure when/if it will stop working...).
* There, changing ftp:// for http:// is not enough, because we were getting
files using wildcards (which I guess worked for ftp:// but it does not work for
http://).
* Relevant code is a function "wgetfiles" which is called in 3 ways:
wgetfiles "" "" ftp://${ftpsite}/debian/doc/ 2 doc
wgetfiles emacsen-common emacsen-common_*.deb
wgetfiles dpkg dpkg-doc_1.9.21_all.deb
http://snapshot.debian.org/archive/debian/20050312T00Z/pool/main 7
And the specific wget call inside the function wgetfiles is, currently:
wget --timeout=60 --quiet --recursive --timestamping --no-host-directories \
--cut-dirs=${cutdirs} --directory-prefix=${prefix} \
${ftpurl}/${initial}/${namesrc}/${namebin}
I've learned that with wget we can use wildcards with --recursive and -A
"pattern" and we should probably add --no-parent to avoid the recursive go to
other places.
Then I've transformed the wget call into this:
wget -e robots=off --no-parent --timeout=60 --recursive --timestamping
--no-host-directories \
--cut-dirs=${cutdirs} --directory-prefix=${prefix} \
--reject "*.html*" -A "${namebin}" ${ftpurl}/${initial}/${namesrc}/
(see also the complete diff and the 'new' 1ftpfiles, attached).
This seems to work (I've run the script in local and later checked that the
files were downloaded in /srv/www.debian.org/cron/ftpfiles), but it needs
improvements, because:
* I've workarounded the robots.txt with "-e robots=off" but I guess that this is
not the correct/elegant/respectful way?
* wget downloads all the files and then removes the ones that don't match the
pattern specified with -A. Maybe there is a more efficient way to do this?
Cheers
--
Laura Arjona Reina
https://wiki.debian.org/LauraArjona
diff --git a/parts/1ftpfiles b/parts/1ftpfiles
index f4fcade..3bd4229 100755
--- a/parts/1ftpfiles
+++ b/parts/1ftpfiles
@@ -14,7 +14,7 @@ wget --timeout=60 --quiet --timestamping http://${ftpsite}/debian/indices/Mainta
[ -d $webtopdir/webwml/english/devel/wnpp ] || mkdir -p $webtopdir/webwml/english/devel/wnpp
ln -sf $crondir/ftpfiles/Maintainers $webtopdir/webwml/english/devel/wnpp/Maintainers
-ftpurlmain=ftp://${ftpsite}/debian/pool/main
+ftpurlmain=http://${ftpsite}/debian/pool/main
wgetfiles()
{
namesrc=$1 # source package name: dpkg
@@ -24,9 +24,9 @@ cutdirs=${4:-5} # number of / in to drop + 3: default 5
prefix=${5:-pool} # download directory
echo -n " ${namesrc}"
initial=$(echo "${namesrc}"|sed -e "s/^\(.\).*$/\1/")
-wget --timeout=60 --quiet --recursive --timestamping --no-host-directories \
+wget -e robots=off --no-parent --timeout=60 --recursive --timestamping --no-host-directories \
--cut-dirs=${cutdirs} --directory-prefix=${prefix} \
- ${ftpurl}/${initial}/${namesrc}/${namebin}
+ --reject "*.html*" -A "${namebin}" ${ftpurl}/${initial}/${namesrc}/
}
# needed for 7doc_updates
@@ -34,7 +34,7 @@ wget --timeout=60 --quiet --recursive --timestamping --no-host-directories \
# Refresh $crondir/ftpfiles/doc
rm -rf $crondir/ftpfiles/doc
-wgetfiles "" "" ftp://${ftpsite}/debian/doc/ 2 doc
+wgetfiles "" "" http://${ftpsite}/debian/doc/ 2 doc
# Refresh $crondir/ftpfiles/pool
rm -rf $crondir/ftpfiles/pool
#!/bin/sh -e
# this script fetches some stuff from the FTP stuff that's needed
# and puts it in /srv/www.debian.org/cron/ftpfiles
. `dirname $0`/../common.sh
[ -d $crondir/ftpfiles ] || mkdir -p $crondir/ftpfiles
cd $crondir/ftpfiles
ftpsite=ftp.de.debian.org
# needed for WNPP, webwml/english/devel/wnpp/wnpp.pl
wget --timeout=60 --quiet --timestamping
http://${ftpsite}/debian/indices/Maintainers
[ -d $webtopdir/webwml/english/devel/wnpp ] || mkdir -p
$webtopdir/webwml/english/devel/wnpp
ln -sf $crondir/ftpfiles/Maintainers
$webtopdir/webwml/english/devel/wnpp/Maintainers
ftpurlmain=http://${ftpsite}/debian/pool/main
wgetfiles()
{
namesrc=$1 # source package name: dpkg
namebin=$2 # binary package name (glob): dpkg-doc_*.deb
ftpurl=${3:-$ftpurlmain} # ${ftpsite}/
cutdirs=${4:-5} # number of / in to drop + 3: default 5
prefix=${5:-pool} # download directory
echo -n " ${namesrc}"
initial=$(echo "${namesrc}"|sed -e "s/^\(.\).*$/\1/")
wget -e robots=off --no-parent --timeout=60 --recursive --timestamping
--no-host-directories \
--cut-dirs=${cutdirs} --directory-prefix=${prefix} \
--reject "*.html*" -A "${namebin}" ${ftpurl}/${initial}/${namesrc}/
}
# needed for 7doc_updates
# this is FTP because otherwise we get all those ugly HTML thingies
# Refresh $crondir/ftpfiles/d
Bug#893397: adapt the cron scripts to use http:// instead of ftp://
Package: www.debian.org User: www.debian@packages.debian.org Usertag: scripts Severity: normal X-Debbugs-CC: debian-doc@lists.debian.org Hi! Turning this conversation into a bug report so it does not get lost. El 18/03/18 a las 16:07, Osamu Aoki escribió: > Hi, > [...] > By the way, we have a fundamental problem with www.debian.org > > The contents of debian-reference are published to the www.debian.org > servers from the latest released packages by the cron script run on > the master www.debian.org server and they are mirrored to all the > www.debian.org servers. > > https://anonscm.debian.org/git/debwww/cron.git (Maybe moving to salsa > soon) > parts/1ftpfiles > parts/7doc > > As the 1ftpfiles indicates, packages are gatherted from ftp package site > which is now non-sup[ported officially. (Now we are supposed to use > http sites) > Since this requires significant coding, AFAIK we just change ftp:// for http:// and it should work isn't it? In any case I'll have a deeper look later. this code updates requires to be > done by someone with shell access to www.debian.org. > I think that the copy of cron scripts in www-master.debian.org is updated automatically by some of those scripts, but if we need to do anything else in www-master.debian.org, I'll try to help. > I know you were thinking to migrate www.debian.org building > infrastructure to git based system from the current CVS. Did you also > looked into parts/1ftpfiles issues? > Not yet. If you know other issues different than the ftp:// -> http:// one, please let us (debian-...@lists.debian.org) know or file bugs against www.debian.org pseudopackages. Thanks for caring! -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Re: Change upstream repo for weblate debian-reference
Hello Osamu and Debian Documentation Team El 11/03/18 a las 13:04, Osamu Aoki escribió: > Hi, > > I am the upstream of debian-reference > https://salsa.debian.org/debian/debian-reference > https://tracker.debian.org/pkg/debian-reference > https://www.debian.org/doc/manuals/debian-reference/ > > Someone set up weblate service previously pointing to alioth git repo. > As you know Debian is moving repository to salsa.debian.org. > debian-reference is no exception, here. > I've updated the URLs in the website repository: https://anonscm.debian.org/viewvc/webwml/webwml/english/doc/user-manuals.defs?r1=1.25=1.26=date Please correct me if I did it wrong. If there are more manuals already moved to Salsa, just tell. Regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Re: Are not ddp manuals maintained now?
Hello Sebul El 03/03/18 a las 11:34, sebul escribió: > Hello. > > https://www.debian.org/doc/cvs introduces > https://anonscm.debian.org/viewvc/ddp/manuals/trunk/ > > When I see > https://anonscm.debian.org/viewvc/ddp/manuals/trunk/ > many documents marked obsolete and > many documents have been going on for years. > > Are not ddp manuals maintained now? Yes, they are maintained. Maybe some of those repos refer to old documentation that is superseded by new manuals. I suggest to ask in the debian-doc mailing list (in CC) for details about specific manuals. Best regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Re: A directory tree of www.debian.org/doc/ ?
Hello Richard El 02/03/18 a las 15:19, Richard Owlett escribió: > By a convoluted set of links, I arrived at > > > That page did not have the specific details I wanted. However its format > suggested how to organize some data I already had. I went up a level to > > > Unfortunately clicking on "Parent Directory" led me to a HTML document, > not a list of sister directories of <.../packaging-manuals>. > > When I started this post I was thinking "Debian bibliography". But that > has inappropriate connotations for my goal. > > Suggestions? > TIA > I'm not sure of what is the question/request here. Richard, do you mind to be more specific? I'm including the debian-doc mailing list in the conversation, since they maintain that part of the Debian website and probably can suggest/review proposals for modification. Cheers -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#878105: release-notes: problems building the release-notes (jessie) for the Debian website
El 01/11/17 a las 18:45, Baptiste Jammet escribió: > Hi Laura, > > Dixit Laura Arjona Reina, le 10/10/2017 : > >>> maybe >>> >>> works for jessie? >>> >> >> Thanks for the suggestion. >> Attaching new patch. > > Your patch seems to be sufficient, and is surely not very intrusive. > Please apply. Applied for the jessie/en version. If this works (we'll see today in the website builds), I'll apply a similar patch for the other languages. Cheers -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#878105: release-notes: problems building the release-notes (jessie) for the Debian website
Hello El 10/10/17 a las 04:54, victory escribió: > instead of adding useless item for old distribution, > maybe > > works for jessie? > Thanks for the suggestion. Attaching new patch. Best regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona Index: whats-new.dbk === --- whats-new.dbk (revisión: 11716) +++ whats-new.dbk (copia de trabajo) @@ -106,8 +106,8 @@ - - + + Support for iop32x was dropped
Bug#878105: release-notes: problems building the release-notes (jessie) for the Debian website
Package: release-notes
Severity: normal
Tags: patch
Dear release-notes maintainers
Thanks for your work in the release notes for every Debian release!
The script that automatically builds the release notes for the Debian website
throws some errors when building the release notes in PDF format.
Those errors appear for any architecture except armel and any language, for the
jessie release notes.
The errors are of the type:
---
Build stdin.pdf
xelatex failed
stdin.tex:292: Something's wrong--perhaps a missing \item.
stdin.tex:292: leading text: \end{description}
Unexpected error occured
Error: xelatex compilation failed
Makefile:214: recipe for target 'en/release-notes.amd64.pdf' failed
---
I've checked the "stdin.tex" generated file, did some tests, and probably the
culprit is this:
file jessie/en/whats-new.dbk
Support for iop32x was dropped
On armel, support for
the iop32x subarchitecture was dropped. Other
armel subarchitectures
continue to be supported, including ixp4xx, kirkwood, orion
and versatile.
The above code produces this LaTeX output:
\begin{description}
\end{description}
in all the architectures except armel, and then xelatex complains about a
missing \item inside the {description} block.
I searched for similar paragraphs in the dbk files and found this:
file jessie/en/installing.dbk
[...]
I'm attaching a diff for the file
svn.debian.org/svn/ddp/manuals/branches/release-notes/jessie/en/
that adds a similar empty paragraph to fix the issue.
Please merge it if you find it useful, and I'll check the logs of the
subsequent website builds to see if the error dissapear for jessie/en. If yes,
then I would try to produce another patch for the rest of the languages.
Best regards
Laura Arjona Reina
https://wiki.debian.org/LauraArjona
-- System Information:
Debian Release: 8.9
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: i386 (i686)
Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Index: en/whats-new.dbk
===
--- en/whats-new.dbk (revisión: 11716)
+++ en/whats-new.dbk (copia de trabajo)
@@ -107,6 +107,19 @@
+
+
+
+
+
+
+
+
+
+
+
+
Support for iop32x was dropped
Outreachy project about improving documentation and website content (Re: Sign up to mentor for Outreachy Round 15)
Hello Keerthana El 10/09/17 a las 06:24, Keerthana Krishnan escribió: > Dear Molly, > > On 6 September 2017 at 19:43, Molly de Blanc <debl...@riseup.net > <mailto:debl...@riseup.net>> wrote: > > Hi Keerthana, > > That all sounds great! Debian has had documentation and translation > interns > before. I think not everyone who has signed up to be a mentor (or who has > been one) is a DD or DM. This shouldn't be a problem, as long as you're > ready to help someone go through the process of submitting their work > upstream (if necessary). > > Ofcourse, I'd do my best to help > > > There's a form / template on the projects page: > https://wiki.debian.org/Outreachy/Round15/Projects > <https://wiki.debian.org/Outreachy/Round15/Projects>. > > > I've created a basic plan for the project here : [1] > <https://wiki.debian.org/Outreachy/Round15/NCProjects/Improving%20Documentation%20in%20Debian#preview> > > I did some initial recon and this is my project idea : > > "The goal of this project is to verify and improve the documentation and the > website content in Debian. Due to its sheer size and variety, many parts of > the > Debian wiki and websites are in dire need of upgrades and fact-checking. > Another > goal is to create beginner-friendly docs to various sections of the Debian > project to encourage more first-time contributions. " > > Essentially, I want to improve the docs and hopefully make it easier for the > first-time contributor. > > > > Do you want to talk a bit about your project idea and what the application > project should be? Do you want to have a co-mentor or co-mentors? > > > Yes, since I'm very new myself it would be awesome to have someone a bit more > experienced with the documentation and websites to be a co-mentor. I've done > documentation before, but never for Debian. > CC'ing website and documentation teams for the case anybody can co-mentor with you. What follows is about the website part, I'm not member of the documentation team nor am much familiarized with their repos/sources. I never mentored in Outreachy/GSoC and I think I personally have not enough spare time to devote to do a full mentoring (or co-mentoring) in this term, but I can help in the technical part of changing the website (for example, helping with the wml syntax, or if the intern submits the proposed changes as bugs to the www.debian.org pseudopackages, I can review them and upload them when they are ready. Well, if the outreachy intern sends their "deliverables" in form of patches, anybody in the website team can review/upload ;) I just mean that I would try to prioritize those so you can evaluate their work as mentor based in the team output). Maybe you can find useful to use usertags https://wiki.debian.org/bugs.debian.org/usertags to categorize as "content" or "documentation" the website bugs that the intern can work on: For now, we have the following bugs tagged as "content": https://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=content=www.debian.org%40packages.debian.org Maybe there is another (better) way to do this, but as I said, I have no experience mentoring. Best regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona > Also, due to this inexperience, I wouldn't mind being a co-mentor who supports > with the writing and documentation part while someone else with more > familiarity > to the Debian systems is the main mentor > > > Thanks for reaching out. It's really cool when people who were mentored > want > to help others get involved. :) > > > It feels so great to give back in any way I can! > > > Cheers, > Molly > > > > [1] : > https://wiki.debian.org/Outreachy/Round15/NCProjects/Improving%20Documentation%20in%20Debian#preview > <https://wiki.debian.org/Outreachy/Round15/NCProjects/Improving%20Documentation%20in%20Debian#preview> > > > Regards, > Keerthana
Re: volunteers for reading bo...@debian.org (and maintain the page www.debian.org/doc/books)?
Hello El 20 de agosto de 2017 19:41:22 CEST, Paul Wise <p...@debian.org> escribió: >On Wed, Aug 16, 2017 at 6:37 AM, Laura Arjona Reina wrote: > >> but I think the mails people send to bo...@debian.org do not arrive >any >> person, currently: > >Looks like the default is for the WEBMASTER field from the .mailfilter >file. > >> I think we should add some address in BOOKS="" > >I wonder if it would be better to migrate all the places that >reference it to mailto: links that submit bug reports against >www.debian.org. The mailto link could include all the usual bug >metadata, including usertags and a message saying that the mail will >be public. > I think it's a good idea. We would need to add somebody in any case, because not everybody will use the "prepared" mailto link (e.g. I can just see that mail address, then open my mail client and write a "normal" message). We can add debian-...@lists.debian.org and leave a note in the webpage /docs/books that the mail will arrive public archives (debian-www and the bts). I'll wait for some more time to see if anybody has objections of books@d.o being "processed in the open". >PS: I note that MERCHANDISE and PREINSTALLVENDORS are in a similar >situation. Mmm similar opinion. I've never done processing of those requests either, so I'm not sure if it's totally ok than their mails go through the public mailing list. Cheers Laura Arjona Reina https://wiki.debian.org/LauraArjona
volunteers for reading bo...@debian.org (and maintain the page www.debian.org/doc/books)?
Dear all (website, doc teams members) I've seen some past commits in the list of books that we show in the website (thanks!): https://www.debian.org/doc/books https://anonscm.debian.org/viewvc/webwml/webwml/english/doc/books.data?view=log but I think the mails people send to bo...@debian.org do not arrive any person, currently: I've gone to www-master.debian.org:/srv/www.debian.org/mail and cat aliases says: books: |maildrop /org/www.debian.org/mail/.mailfilter and in the .mailfilter file, it says: BOOKS="" I think we should add some address in BOOKS="" so the mail arrives a person or a list (if it's a public list, I can modify the webpage leaving a note that the mail will be publicly archived). Correct me if I am wrong... Volunteers? (if you prefer to volunteer privately, just send me a mail with the address you'd like to include). I guess the task is not heavy, once you deal with the spam. For now, we have pending: * A question about a recent removal: https://lists.debian.org/debian-www/2017/08/msg00055.html * A request of addition: https://lists.debian.org/debian-www/2017/07/msg00073.html and https://lists.debian.org/debian-www/2017/08/msg00030.html * Whatever you'll find in the "books" mailbox file where past mails are stored. I can help on skimming that mailbox, if other person(s) volunteers to actually handle the requests. Thanks! -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Re: debian-www / debian-doc teams no longer responsive [Was: Re: Bad release in install documentation]
Hi On 6 de marzo de 2016 13:13:45 GMT+01:00, Holger Wansing <li...@wansing-online.de> wrote: >Hi, > >Holger Wansing <li...@wansing-online.de> wrote: >> Hi, >> >> Holger Wansing <li...@wansing-online.de> wrote: >> > Hi, >> > >> > Cyril Brulebois <k...@debian.org> wrote: >> > > Samuel Thibault <sthiba...@debian.org> (2016-02-06): >> > > > Hello, >> > > > >> > > > a a, on Wed 03 Feb 2016 11:03:19 +, wrote: >> > > > > https://www.debian.org/releases/stable/i386/index.html.en. It >says in >> > > > > abstract that the documentation is for debian strech and the >url says >> > > > > about stable release. >> > > > >> > > > It's worse than that: it seems it's really the current Stretch >> > > > installation guide which ended up on the website in stable/, I >don't >> > > > know why. Www people, any idea? >> > > >> > > Because >http://anonscm.debian.org/cgit/debwww/cron.git/tree/lessoften-parts/1installation-guide >> > > >> > > It would be nice if it could put stuff targetting s(-p-u) under >stable, and >> > > stuff targetting unstable under testing, but I didn't reach this >point of my >> > > todo list yet. >> > >> > For the time being: >> > >> > Looking at >> > >http://anonscm.debian.org/cgit/debwww/cron.git/commit/lessoften-parts/1installation-guide?id=c8148aba41b484964cb7a627c5c954a19f056d38 >> > it seems, we have the same situation again now: >> > >> > The latest upload of installation-guide was for Stretch (Changelog >does >> > not mention that explicitly, but there are several changings >effecting >> > Stretch), so that script has to be adapted around that: >> > >> > all occurences of 'jessie' have to be changed into 'stretch' and >> > all 'wheezy' be changed into 'jessie'. >> > >> > >> > Am I correct? >> > If yes, could someone commit that, please !!! >> >> I have tried to apply this, but I'm lacking proper permissions. >> >> Anyone? > >I have asked for membership in the relevant alioth project "debwww" >~ 10 days ago, but got no answer yet :-(( > >What can be done about this? > >Somebody here, who minds doing the above changing? >(Noone on debian-www objected against this for weeks, so I assume >change >this is the right thing to do, to get the problem solved.) > > >Holger I'm in debwww since some days ago and this is one of the things I wanted to look at, but couldn't put time yet. I hope I can have a look at it in the following days. Thanks Holger, and sorry for the delay! Best regards Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#789356: release-notes: Titles in PDF versions are made of incorrect characters
Hi There's a bug in TexLive: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787759 I'm not sure if something can be done meanwhile the fix arrives a point release, maybe changing the fonts? Thank you for working in the Debian release notes. Best regards -- Laura Arjona https://wiki.debian.org/LauraArjona signature.asc Description: OpenPGP digital signature
Re: Bug#721215: The Debian Administration Handbook and https://www.debian.org/doc
Hi El 10/06/15 a las 06:45, Joost van Baal-Ilić escribió: Hi, I can't find any Debian Administrator's Manual which is DFSG-free and packaged in Debian; as mentioned by original bug submitter. (I _did_ find the Debian GNU/Linux System Administrator's Manual (obsolete, Copyright © 1997 Ardo van Rangelrooij Copyright © 1998 Oliver Elphick Copyright © 1998 Tapio Lehtonen); there's an old copy still at http://debian.man.ac.uk/non-debian/LDP/LDP/www.debian.org/doc/manuals/system-administrator .) Indeed, it seems we're talking about The Debian Administration Handbook. I agree with the bug's submitter that that one needs a more prominent place under http://www.debian.org/doc . An entry under Users' manuals, and an entry on https://www.debian.org/doc/user-manuals (which could be renamed from DDP Users' Manuals to Users' Manuals) would be appropriate, imho. Is it important to state whether a piece of documentation belongs to the Debian Documentation Project or not? I think yes (I'm not part of DDP, though...), and I think it's better to create a new section than removing the DDP part of the title in user-manuals and add the handbook there. Any other opinion? https://www.debian.org/doc/books could refer to the new https://www.debian.org/doc/user-manuals#debian-handbook . I would update the entry of books, to reference the page/section where we finally add the Handbook. Thanks Bye, Joost On Wed, Jun 10, 2015 at 01:29:57AM +0200, Laura Arjona Reina wrote: Hi everybody If you refer to The Debian Administration Handbook (the first reference listed in the subpage https://www.debian.org/doc/books), I have no clear idea about what to do. On one side, the reference should stay there even if we add an entry in user manuals, because it's a printed book. On the other side, I'm not sure if user manuals is for the documentation maintained by the Debian Documentation Project (and then, the Handbook shouldn't be there, even if there is a package available, several translations, and it's DFSG-free). Finally, I suppose we could change the title of the section Other, shorter documents to Other, and shorter documents and include a link as first reference in that section, but I think it's not a good solution. CC'ing debian-doc mailing list, I hope they can give advice about how to proceed. Regards -- Laura Arjona https://wiki.debian.org/LauraArjona -- Laura Arjona https://wiki.debian.org/LauraArjona -- To UNSUBSCRIBE, email to debian-doc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55781f37.1070...@larjona.net
Please mention Debian Administrator's Manual in the main list of documentation
Hi everybody If you refer to The Debian Administration Handbook (the first reference listed in the subpage https://www.debian.org/doc/books), I have no clear idea about what to do. On one side, the reference should stay there even if we add an entry in user manuals, because it's a printed book. On the other side, I'm not sure if user manuals is for the documentation maintained by the Debian Documentation Project (and then, the Handbook shouldn't be there, even if there is a package available, several translations, and it's DFSG-free). Finally, I suppose we could change the title of the section Other, shorter documents to Other, and shorter documents and include a link as first reference in that section, but I think it's not a good solution. CC'ing debian-doc mailing list, I hope they can give advice about how to proceed. Regards -- Laura Arjona https://wiki.debian.org/LauraArjona signature.asc Description: OpenPGP digital signature
