Bug#1016694: favicon.ico on packges.debian.org
Hello Thanks for the report. This was already reported in bug #1016694 (in CC), and I have committed the change in the packages repo: https://salsa.debian.org/webmaster-team/packages/-/commit/4a1f6cc787af10d1207d3127d679e93b48fcd99b I leave open the bug because this still needs to be deployed in packages.debian.org Kind regards El 12/1/24 a las 3:18, Nick Hastings escribió: Hi, http://packages.debian.org suggests emailing this list for problems with that web site. I noticed that packages.debian.org uses a different favicon.ico to that of www.debian.org. The reason that I noticed is because the packages.debian.org favicon does not look so great when rendered on a dark background. I wonder if could be updated to use the same one as www.debian.org? Note that there are other pages under debian.org that suffer this same problem and I have been attempting to contact the relevant people with mixed success. Eg https://search.debian.org/ Cheers, Nick. -- Laura Arjona Reina
Bug#1016694: favicon.ico on packges.debian.org
Hello Thanks for the report. This was already reported in bug #1016694 (in CC), and I have committed the change in the packages repo: https://salsa.debian.org/webmaster-team/packages/-/commit/4a1f6cc787af10d1207d3127d679e93b48fcd99b I leave open the bug because this still needs to be deployed in packages.debian.org Kind regards El 12/1/24 a las 3:18, Nick Hastings escribió: Hi, http://packages.debian.org suggests emailing this list for problems with that web site. I noticed that packages.debian.org uses a different favicon.ico to that of www.debian.org. The reason that I noticed is because the packages.debian.org favicon does not look so great when rendered on a dark background. I wonder if could be updated to use the same one as www.debian.org? Note that there are other pages under debian.org that suffer this same problem and I have been attempting to contact the relevant people with mixed success. Eg https://search.debian.org/ Cheers, Nick. -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#1053549: 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
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#1053549: Create a Debian theme for documentation based in Sphinx (reStructuredText)
Package: www.debian.org Severity: normal User: debian-...@lists.debian.org Usertags: design X-Debbugs-CC: debian-...@lists.debian.org,design-de...@alioth-lists.debian.net. Dear website, documentation and design teams, Several documentation manuals are being generated now using ReStructuredText and Sphinx, and it would be nice that a Debian theme in Sphinx is created and used to match our docs appearance with the Debian website colours etc. Currently in the website we publish, at least: * Debian Policy: https://www.debian.org/doc/debian-policy/ * Debian Developers Reference: https://www.debian.org/doc/manuals/developers-reference/index.en.html * Testing Release notes: currently in https://www.debian.org/releases/testing/release-notes/ but that may change The upstream documentation about theming is here: http://www.sphinx-doc.org/en/stable/theming.html Please take into account that currently the machine www-master where the website is built runs bullseye (sphinx version: 3.4.3-2, but at some time it will be upgraded to bookworm (sphinx version: 5.3.0-4). Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#1053517: find commands became noisy in urlcheck/cleanup.logs cron job
Package: www.debian.org
Severity: normal
User: debian-...@lists.debian.org
Usertags: scripts
Hello all
Since some time (maybe since the www-master machine (wolkenstein) was upgraded
to bullseye?) we're receiving (at webmas...@debian.org) daily mails with noisy
useless output of the "urlcheck" lessoften job:
-
Mensaje reenviado
Asunto: Cron cd /srv/www.debian.org/cron/urlcheck &&
./cleanup.logs
Fecha: Thu, 05 Oct 2023 13:05:01 +
De: Cron Daemon
Para: deb...@wolkenstein.debian.org
rm: cannot remove 'logs': Is a directory
gzip: logs is a directory -- ignored
-
The code producing the output is here:
https://salsa.debian.org/webmaster-team/cron/-/blob/master/urlcheck/cleanup.logs
Which is just 3 lines, so I copy them here:
---
#!/bin/sh
find logs -daystart -mtime +7 -exec rm {} \;
find logs -daystart -mtime +2 -not -name '*.gz' -exec gzip -9 {} \;
---
the "logs" folder is where other cron jobs store files so I guess we should keep
it, I'd like just the script to be more silent so we only get mails if there is
an actual error.
My bash skills are limited, if anybody can help, MR or patches or ideas are
welcome.
Kind regards,
Laura Arjona Reina
https://wiki.debian.org/LauraArjona
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'
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#1038109: Unify homepage CSS and how do we load CSS files
Package: www.debian.org
User: www.debian@packages.debian.org
Usertag: design
Severity: normal
It would be nice to reorganize the styles we use in the homepage in a
specific file. Currently we use, specifically for the homepage:
/5img-carousel-slider.css
./debhome.css
./startpage.css
The basic.wml and basic5.wml templates have this code to load the
corresponding CSS depending if a page has the header MAINPAGE (used not
only in frontpage, but also in the pages that have been redesigned, e.g.
the ones under /intro, /doc, /devel...):
>
{#style#:type="text/css" />
rel="stylesheet" type="text/css" media="all"/>
:#style#}
{#style#:type="text/css" />
type="text/css" />
rel="stylesheet" type="text/css" />
rel="stylesheet" type="text/css" media="all"/>
:#style#}
But then in the redesigned pages we load more CSS within the page:
It would be nice to unify the different styles of the homepage in a
single file, and also decide how do we load them (if via the template or
in each .wml file separately), and use the same procedure for all the
CSS we have in the website.
Note that a change in the basic*.wml templates probably triggers a
rebuild of most of the website, so adding/removing a CSS file there has
to be handled with care. This, and this bug, are the reasons behind
changing the 5img-carousel-slider.css file to show 6 images instead of 5
(see commit
https://salsa.debian.org/webmaster-team/webwml/-/commit/221bc933118b9f05c063776d7ef41d75a9bf2858
) without renaming the file, for now :/
Kind regards
--
Laura Arjona Reina
https://wiki.debian.org/LauraArjona
Bug#1037479: 500 Internal Server Error accessing https://packages.debian.org/testing/name_of_package
Package: www.debian.org User: www.debian@packages.debian.org Usertag: packages Severity: normal X-Debbugs-CC: kevin.torkel...@gmail.com, webmas...@debian.org Hi Kevin Thanks for the report. It seems that our website packages.debian.org still doesn't recognize trixie being testing. Not related to any package in particular, if I go to https://packages.debian.org/testing/ I obtain: couldn't read index file trixie/index.en.html: No such file or directory I'm creating a bug report about it, if you want to follow you can subscribe to the bug sending a mail to -subscr...@bugs.debian.org (being the bug number). Kind regards Laura Arjona Reina https://wiki.debian.org/LauraArjona Mensaje reenviado Asunto: 500 Internal Server Error Fecha: Tue, 13 Jun 2023 00:48:32 -0500 De: Kevin Torkelson Para: webmas...@debian.org While attempting to investigate why the KDE/Plasma "Discover" app isn't finding sources, just after allowing my "testing" system to update from Codename bullseye to trixie I went to visit the web site searching for a package "discover". https://packages.debian.org/testing/discover <https://packages.debian.org/testing/discover> I received a 500 error with a message to please inform the webmaster, thus I am. Additional details: GET https://packages.debian.org/testing/discover <https://packages.debian.org/testing/discover> [HTTP/2 500 Internal Server Error 583ms] GET /testing/discover HTTP/1.1 Host: packages.debian.org <http://packages.debian.org> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8 Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate, br Referer: https://packages.debian.org/ <https://packages.debian.org/> DNT: 1 Connection: keep-alive Upgrade-Insecure-Requests: 1 Sec-Fetch-Dest: document Sec-Fetch-Mode: navigate Sec-Fetch-Site: cross-site HTTP/2 500 Internal Server Error date: Tue, 13 Jun 2023 05:38:28 GMT server: Apache x-content-type-options: nosniff x-frame-options: sameorigin referrer-policy: no-referrer x-xss-protection: 1 permissions-policy: interest-cohort=() strict-transport-security: max-age=15552000 content-length: 603 content-type: text/html; charset=iso-8859-1 X-Firefox-Spdy: h2 favicon.ico returned 200: https://packages.debian.org/favicon.ico <https://packages.debian.org/favicon.ico> While attempting to investigate why the KDE/Plasma "Discover" app isn't finding sources, just after allowing my "testing" system to update from Codename bullseye to trixie I went to visit the web site searching for a package "discover". https://packages.debian.org/testing/discover <https://packages.debian.org/testing/discover> I received a 500 error with a message to please inform the webmaster, thus I am. Additional details: GET https://packages.debian.org/testing/discover <https://packages.debian.org/testing/discover> [HTTP/2 500 Internal Server Error 583ms] GET /testing/discover HTTP/1.1 Host: packages.debian.org <http://packages.debian.org> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8 Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate, br Referer: https://packages.debian.org/ <https://packages.debian.org/> DNT: 1 Connection: keep-alive Upgrade-Insecure-Requests: 1 Sec-Fetch-Dest: document Sec-Fetch-Mode: navigate Sec-Fetch-Site: cross-site HTTP/2 500 Internal Server Error date: Tue, 13 Jun 2023 05:38:28 GMT server: Apache x-content-type-options: nosniff x-frame-options: sameorigin referrer-policy: no-referrer x-xss-protection: 1 permissions-policy: interest-cohort=() strict-transport-security: max-age=15552000 content-length: 603 content-type: text/html; charset=iso-8859-1 X-Firefox-Spdy: h2 favicon.ico returned 200. https://packages.debian.org/favicon.ico <https://packages.debian.org/favicon.ico> Please don't hesitate to contact me if I may be of any additional assistance. Best Regards, Kevin Torkelson
Bug#1037324: d.o/CD/live refers to images no longer built
Thanks for the patch. I have applied the update to the description, since the tags were already updated. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#1037324: d.o/CD/live refers to images no longer built
Hello El 11/6/23 a las 12:42, Jonathan Wiltshire escribió: Package: www.debian.org Severity: serious X-Debbugs-Cc: debian...@lists.debian.org, j...@debian.org i386 live images are no longer built as of bookworm, but the download page still refers to them. It needs a bit of a rewrite because the only architecture now is amd64. I became aware because of direct user reports. Thanks for reporting. I have updated our files in commit https://salsa.debian.org/webmaster-team/webwml/-/commit/eccd7980c97d0e9c1c5580045cadbc68e6ca719e (below the diff), it will be online in the next hours. Please let me know if this fix is not enough, if I get no news I will close this bug reports in a few days. Kind regards, diff --git a/english/template/debian/release_images.wml b/english/template/debian/release_images.wml index 52c8be6dafee11dc1d3638d92a2f9eca97f1b8d9..ffdb0b8f041c2a5fe269998c7f69e0aac61cf405 100644 --- a/english/template/debian/release_images.wml +++ b/english/template/debian/release_images.wml @@ -51,19 +51,19 @@ live-images-url>https://cdimage.debian.org/debian-cd/-live - + - + - + - + - + # this needs to link a debian/ mirror rather than cdimage.d.o -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#1032453: non-free-firmware changes and documentation needs to happen after SC change
Hello Apologies for the late reply. I have reviewed our why_debian page (https://www.debian.org/intro/why_debian) and I don't see the need of update to reflect non-free-firmware related changes: The sentence about Debian being 100% free can stay the same as Social Contract §1 states; and the changes that were made to the Social Contract with the GR are not mentioned in our why_debian page. If you think that I'm wrong or have some specific proposal or paragraph that we should review again, please point to it with the complete URL so I can find my mistake and have a look. Kind regards, El 21/4/23 a las 18:43, Osamu Aoki escribió: Hi, On Fri, 2023-04-21 at 15:35 +0200, Laura Arjona Reina wrote: Hello El 21 de abril de 2023 14:30:24 CEST, Osamu Aoki escribió: ... So this why_debian page needs to be updated first. ... But in order to update this why_debian page properly, I think we need to wait SC change. (I CC debian-www@d.o ML) ... No agreement has been reached on SC text since that is the next planned action. This already happened: https://salsa.debian.org/webmaster-team/webwml/-/commit/79d1ad80a8ac84afa8c8a224b81fb50c327e6b4f Oops. Thanks. Once the new SC text is accepted, I will update this §2.1.5 following why_debian page on www.debian.org. In a first pass I thought that the page why_debian didn't need an update. I'll look at this more closely, comparing with Debian Reference and other updated documents, during this weekend (if anybody wants to go ahead, I'm also happy to read proposals from others). I see we can still argue Debian is 100% FREE and leave the text as they are. The question is how to address things written in updated SC in the updated why_debian /debian-reference §2.1.5. I mean the following part: Thus, although non-free works are not a part of Debian, we support their use and provide infrastructure for non-free packages (such as our bug tracking system and mailing lists). The Debian official media may include firmware that is otherwise not part of the Debian system to enable use of Debian with hardware that requires such firmware. Some short footnote may help. Since I don't like to use negated text, I may add text along following as footnote later. (This is my first thought. I may need to think more.) Debian project supports use of non-free works and provides infrastructure for non-free packages (such as our bug tracking system and mailing lists). The Debian official media may include firmware that is otherwise not part of the Debian system to enable use of Debian with hardware that requires such firmware. But before doing this, I want to see how why_debian deals this. Regards, Osamu -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#1030009: www.debian.org: addition of non-free-firmware for bookworm and higher
Hello I have reviewed Holger's proposals in the branch GR-non-free-firmware (thanks a lot!) and added updates to some other files, and updated the https://deb.li/1030009 pad The current status, as I see, is the following: * I agree with all the files reviewed with comment that don't need update * I agree with all the update proposals that are currently in the branch. The files releases/bookworm/errata.wml and devel/debian-installer/index.wml are already updated in the master branch so when merging we should discard changes in the GR-non-free-firmware affecting these files and keep the ones in master. * I agree that we shouldn't change Bugs/server-request.wml without checking first with BTS team if the BTS already knows about non-free-firmware. So leaving this for "after the Debian 12 release". * No idea if packages.debian.org already knows and allows to search about non-free-firmware but we can incorporate the updates to our files as Computer Enthusiastic (in CC) suggested and Holger committed, and then after the release we can try to help to update packages.d.o if needed. * The scripts that produce the data for the l10n dashboards would need update so I'm leaving international/l10n aside for now, I just added non-free-firmware in the synonyms list, and to the ddtp.wml file that says that non-free is not handled due to possible license issues ( adding here non-free-firmware does not harm, so I added it). * It's been suggested that we may need to update intro/why_debian.wml to reflect the changes in the GR about non-free-firmware but I have reviewed the file and I don't find the reason why whe should update it. * It's been suggested that we change the links https://cdimage.debian.org/cdimage/unofficial/non-free/firmware/ for https://cdimage.debian.org/cdimage/firmware/ (starting with bookworm) but since currently both URLs serve the same files, I'd would do it after the branch is merged, since many links are going away in the merge. So, in summary, I think we can merge the branch into master when we see suitable (1) and just need to be careful about not overwriting the files releases/bookworm/errata.wml and devel/debian-installer/index.wml. (1) when we see suitable: I guess right after the Debian 12 images are ready for download as "stable" release, but in fact I'm not sure how to handle this and the translations. I am available to merge the branch this weekend when the website is updated to the release, and can try to update the languages that have no active translator these days. For the rest, if nobody proposes better way, I will send a mail to debian-i18n and debian-www explaining that this branch will be merged during the weekend so people are prepared to do their changes in the corresponding language folder (if they choose to advance work in the branch, it will be merged and I'll try to update the commit-hashes later). Kind regards, -- 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#1035960: All of sudden, the Spanish PO debconf templates is getting full of alien translators :-)
Hello
The spiderinit job took very long but finally it re-created all the status
files and the html pages, and I think it worked well.
I have added code to use lockfiles in the spiderbts job:
https://salsa.debian.org/l10n-team/dl10n/-/commit/5d518000bf15762dde13ed7cd56dee77a2bf757b
And reenabled the cron.hourly job
I'll try to keep an eye on things these days, please report if you notice any
issue.
Kind regards
El 12 de mayo de 2023 23:50:54 CEST, Laura Arjona Reina
escribió:
>Thanks everybody for the extra info and Cyril for the research
>
>I have killed the spider jobs.
>I have modified the crontab in tye.debian.org to disable cron.hourly job
>(spiderbts) for now.
>
>I have removed the status files [1] and launched a job spiderinit [2] to
>re-create them.
>
>[1] in /srv/i18n.debian.org/dl10n/data/spiderbts/data/status.??
>[2] sudo -u debian-i18n /srv/i18n.debian.org/dl10n/git/cron/spiderinit &
>
>Tomorrow I'll have a look at the logs of the spiderinit job [3] and launch the
>cron.hourly job once.
>
>[3] /srv/i18n.debian.org/log/spiderinit/spiderinit.20230512-2134.[err|log]
>
>
>Then I'll see how long does it take and if there is any issue.
>If everything went well the webpages should show correct data. Then I'll set
>the "hourly" job to run 6 times a day and will keep an eye these days.
>
>I agree that a lockfile is needed, I'll try to work on that too and when it's
>set, and the issue is fixed, I'll update the cron to run hourly again.
>
>Kind regards
>
>
>El 12/5/23 a las 12:04, Cyril Brulebois escribió:
>> Cyril Brulebois (2023-05-12):
>>> I'll keeping looking at what's supposed to happen on tye, but I'm not
>>> sure I'll be able to get to the bottom of it on my own.
>>
>> At least there's a HUGE red flag on tye. Load to the roof, RAM/swap
>> almost full, lots of dl10n-spider processes running for the same
>> language, some of them started May 9th.
>>
>> kibi@tye:~$ uptime
>> 10:02:58 up 12 days, 21:47, 2 users, load average: 63.24, 64.57,
>> 66.51
>>
>> kibi@tye:~$ free -h
>> totalusedfree shared buff/cache
>> available
>> Mem: 1.9Gi 1.7Gi69Mi 1.0Mi 125Mi
>> 57Mi
>> Swap: 511Mi 511Mi 0.0Ki
>>
>> kibi@tye:~$ ps faux|grep dl10n-spider|grep -o -- '--check-bts
>> ..'|sort|uniq -c
>>4 --check-bts ca
>>1 --check-bts cs
>>1 --check-bts da
>> 51 --check-bts de
>>7 --check-bts es
>>2 --check-bts fr
>>
>> kibi@tye:~$ ps faux|awk '/CRON/ {print $9}'|sort|uniq -c
>> 11 May09
>> 23 May10
>> 23 May11
>>1 00:15
>>1 02:15
>>1 03:15
>>1 04:15
>>1 05:15
>>1 06:15
>>1 07:15
>>1 08:13
>>1 08:15
>>1 09:15
>>2 10:00
>>1 10:01
>>
>> Note that many de.po occurrences appear in the status file for other
>> languages, looks like processes heavily stomping onto others' feet?
>>
>>
>> It looks to me there should be some locking at the very least to avoid
>> that amount of concurrency. And that it would probably be best to start
>> afresh, killing all those processes, maybe disabling the cron jobs,
>> cleaning temporary and maybe corrupted data files, and triggering a
>> single run manually to see if it works.
>>
>> But then, I have 0 knowledge about the spider, and I'll leave that up to
>> someone else: I don't want to risk making the matter worse!
>>
>>
>> Cheers,
>
--
Laura Arjona Reina
https://wiki.debian.org/LauraArjona
Sent with K-9 mail
Bug#1035960: All of sudden, the Spanish PO debconf templates is getting full of alien translators :-)
Thanks everybody for the extra info and Cyril for the research
I have killed the spider jobs.
I have modified the crontab in tye.debian.org to disable cron.hourly job
(spiderbts) for now.
I have removed the status files [1] and launched a job spiderinit [2] to
re-create them.
[1] in /srv/i18n.debian.org/dl10n/data/spiderbts/data/status.??
[2] sudo -u debian-i18n /srv/i18n.debian.org/dl10n/git/cron/spiderinit &
Tomorrow I'll have a look at the logs of the spiderinit job [3] and
launch the cron.hourly job once.
[3] /srv/i18n.debian.org/log/spiderinit/spiderinit.20230512-2134.[err|log]
Then I'll see how long does it take and if there is any issue.
If everything went well the webpages should show correct data. Then I'll
set the "hourly" job to run 6 times a day and will keep an eye these days.
I agree that a lockfile is needed, I'll try to work on that too and when
it's set, and the issue is fixed, I'll update the cron to run hourly again.
Kind regards
El 12/5/23 a las 12:04, Cyril Brulebois escribió:
Cyril Brulebois (2023-05-12):
I'll keeping looking at what's supposed to happen on tye, but I'm not
sure I'll be able to get to the bottom of it on my own.
At least there's a HUGE red flag on tye. Load to the roof, RAM/swap
almost full, lots of dl10n-spider processes running for the same
language, some of them started May 9th.
kibi@tye:~$ uptime
10:02:58 up 12 days, 21:47, 2 users, load average: 63.24, 64.57, 66.51
kibi@tye:~$ free -h
totalusedfree shared buff/cache
available
Mem: 1.9Gi 1.7Gi69Mi 1.0Mi 125Mi
57Mi
Swap: 511Mi 511Mi 0.0Ki
kibi@tye:~$ ps faux|grep dl10n-spider|grep -o -- '--check-bts
..'|sort|uniq -c
4 --check-bts ca
1 --check-bts cs
1 --check-bts da
51 --check-bts de
7 --check-bts es
2 --check-bts fr
kibi@tye:~$ ps faux|awk '/CRON/ {print $9}'|sort|uniq -c
11 May09
23 May10
23 May11
1 00:15
1 02:15
1 03:15
1 04:15
1 05:15
1 06:15
1 07:15
1 08:13
1 08:15
1 09:15
2 10:00
1 10:01
Note that many de.po occurrences appear in the status file for other
languages, looks like processes heavily stomping onto others' feet?
It looks to me there should be some locking at the very least to avoid
that amount of concurrency. And that it would probably be best to start
afresh, killing all those processes, maybe disabling the cron jobs,
cleaning temporary and maybe corrupted data files, and triggering a
single run manually to see if it works.
But then, I have 0 knowledge about the spider, and I'll leave that up to
someone else: I don't want to risk making the matter worse!
Cheers,
--
Laura Arjona Reina
https://wiki.debian.org/LauraArjona
Bug#1035960: All of sudden, the Spanish PO debconf templates is getting full of alien translators :-)
Hi El 12 de mayo de 2023 9:52:02 CEST, "Camaleón" escribió: >Hello, > >It seems something is happeing on Spanish debconf templates. >The stats page is showing a lot of alien translators and old bugs :-) > >https://www.debian.org/international/l10n/po-debconf/es > >Can someone please take a look on this? > >Thank you, > Maybe this issue in the Spanish dashboards is related to the report #1035960 about issues in the German dashboards: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035960 I will try to investigate both issues but any help is welcome. If any of you is sure about the last date when you saw things were working well, please tell, so I can try to learn what happened since then that could cause the issue. Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona Sent with K-9 mail
Bug#1034444: www.debian.org: Incorrect information in https://www.debian.org/releases/
Hello Charles Thanks for your report. I have done the following updates: webwml master c5614b3 Laura Arjona Reina english/releases/ jessie/index.wml wheezy/index.wml * Update paragraph about LTS support, writing in past tense * https://salsa.debian.org/webmaster-team/webwml/-/commit/c5614b3 webwml master 318de67 Laura Arjona Reina english/releases/buster/index.wml * Update buster page to show currently under LTS * https://deb.li/3D5KV webwml master c79a49c Laura Arjona Reina english/releases/index.wml * Update info about releases under ELTS and current LTS. Closes: #103 * https://deb.li/BY31 I think the English pages should show the accurate information in the following hours (after the next website build). Translations should follow in the next days. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#1032440: www.d.o: please link to single html page version of developers-reference
Control: tags -1 patch Hello I'm attaching a patch that adds some logic to show manuals in single page html, and added that new "format" to the developers-reference manual definition. If anybody can improve it, please do. If nobody objects, I'll commit the patch in several days, and later will see if I can add this format to some other manuals, and update language tags so the "HTML (single page)" can be translated. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona El 6/3/23 a las 21:00, Holger Levsen escribió: package: www.debian.org severity: wishlist x-debbugs-cc: debian-de...@lists.debian.org hi, On Mon, Mar 06, 2023 at 07:46:43PM +, Holger Levsen wrote: [...], there's a single page HTML version available again, eg on https://www.debian.org/doc/manuals/developers-reference/developers-reference.html which could be linked from https://www.debian.org/doc/devel-manuals#devref again. & thank you for maintaining www.debian.org! From 436b254ce58fc84ae9956a33135d644371c65663 Mon Sep 17 00:00:00 2001 From: Laura Arjona Reina Date: Tue, 14 Mar 2023 19:08:46 +0100 Subject: [PATCH] Add logic to show developers reference manual in single page HTML (Closes: #1032440) --- english/doc/devel-manuals.defs | 2 +- english/doc/manuals.defs | 9 + 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/english/doc/devel-manuals.defs b/english/doc/devel-manuals.defs index 4a789a21abc..7e545bf6198 100644 --- a/english/doc/devel-manuals.defs +++ b/english/doc/devel-manuals.defs @@ -21,7 +21,7 @@ https://salsa.debian.org/debian/developers-reference; diff --git a/english/doc/manuals.defs b/english/doc/manuals.defs index bc26445b125..4c6fad930b1 100644 --- a/english/doc/manuals.defs +++ b/english/doc/manuals.defs @@ -114,8 +114,14 @@ /> /> + "^singlepagehtml$" action=report /> + +/> + "^singlepagehtml$" action=report /> + +/> /> "^$" action=report />> "^index$" action=report />> @@ -130,6 +136,9 @@ "txt" action=report />> plain text /> + "singlepagehtml$" action=report />> +HTML (single page) /> + [] # "(html|txt|pdf|ps)" action=report /> "" # -- 2.30.2
Bug#1032293: debian-timeline: validation errors in timeline.debian.net
Control: retitle -1 Using makes timeline empty (only header and footer are displayed) Hello again After researching a bit more, I think that the timeline software is not compatible with HTML5, at least the way it's used by debian-timeline. Similar issue was raised long time ago to upstream project: https://code.google.com/archive/p/simile-widgets/issues/450 with no answer :-/ I think I'll leave this bug here, my HTML/js skills are not enough to try to solve it, and rename it to reflect that the only validation issue left is the HTML5 doctype compatibility. Kind regards El 3/3/23 a las 11:14, Laura Arjona Reina escribió: Hello again I have committed the changes and later removed the DOCTYPE declaration, and it seems all the validation erros have been gone, except the one about the DOCTYPE declaration. I don't know which DOCTYPE is the best one to use with the timeline. I've had searched for info in http://simile-widgets.org/timeline/ https://github.com/simile-widgets/timeline/ https://groups.google.com/g/simile-widgets and I guess we can use but we would need to make some adjustments to correctly load the xml files with the events, releases and release eras. I'll continue working on this. Kind regards, El 3/3/23 a las 9:09, Laura Arjona Reina escribió: Package: debian-timeline Version: 45 Followup-For: Bug #1032293 Hello, I have tried to fix the validation errors with commit 8d6c753ecb6be22915a9c8430b3db50ec1a566a3 (patch attached), but deploying it in timeline.debian.net resulted in the headers and footers of the page being rendered, but not the actual body with the timeline of events (i.e. the same result than installing the package locally (bugs #1032166 and maybe #655664 (this time in Firefox too)) . So I guess more fixes are needed. I'll try to work on this. Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#1032166: timeline data not shown in browser (from local install)
Hello, I have done some tests and I think that the issue is related to
CORS policy of the browsers.
If I install debian-timeline and I do:
chromium --allow-file-access-from-files
file:///usr/share/debian-timeline/index.html &
I cannot see the events, but if I press F12 I can see them. So I think
it's because 62-63 lines in media/debian-timeline.js:
Timeline.loadXML("xml/events.xml?" + random, function(xml, url) {
events.loadXML(xml, url); });
Timeline.loadXML("xml/releases.xml?" + random, function(xml, url) {
releases.loadXML(xml, url); });
Timeline.loadXML("xml/release_eras.xml?" + random, function(xml, url) {
release_eras.loadXML(xml, url); });
result in trying to load the data with the file:/// scheme, and thus,
blocked by the browser. I think this does not happen in
https://timeline.debian.net because there is a web server serving the
files, so no file:/// is used.
I'll try to see if there is other way to load the data so a browser is
happy with a local install; I'll also investigate if this issue is also
related to the problems declaring the DOCTYPE as html5 (bug #1032293:
when we set DOCTYPE html, the data is not rendered either and the
timeline appears as empty).
Kind regards
--
Laura Arjona Reina
https://wiki.debian.org/LauraArjona
Bug#1032293: debian-timeline: validation errors in timeline.debian.net
Hello again I have committed the changes and later removed the DOCTYPE declaration, and it seems all the validation erros have been gone, except the one about the DOCTYPE declaration. I don't know which DOCTYPE is the best one to use with the timeline. I've had searched for info in http://simile-widgets.org/timeline/ https://github.com/simile-widgets/timeline/ https://groups.google.com/g/simile-widgets and I guess we can use but we would need to make some adjustments to correctly load the xml files with the events, releases and release eras. I'll continue working on this. Kind regards, El 3/3/23 a las 9:09, Laura Arjona Reina escribió: Package: debian-timeline Version: 45 Followup-For: Bug #1032293 Hello, I have tried to fix the validation errors with commit 8d6c753ecb6be22915a9c8430b3db50ec1a566a3 (patch attached), but deploying it in timeline.debian.net resulted in the headers and footers of the page being rendered, but not the actual body with the timeline of events (i.e. the same result than installing the package locally (bugs #1032166 and maybe #655664 (this time in Firefox too)) . So I guess more fixes are needed. I'll try to work on this. Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#1032293: debian-timeline: validation errors in timeline.debian.net
Package: debian-timeline Version: 45 Followup-For: Bug #1032293 Hello, I have tried to fix the validation errors with commit 8d6c753ecb6be22915a9c8430b3db50ec1a566a3 (patch attached), but deploying it in timeline.debian.net resulted in the headers and footers of the page being rendered, but not the actual body with the timeline of events (i.e. the same result than installing the package locally (bugs #1032166 and maybe #655664 (this time in Firefox too)) . So I guess more fixes are needed. I'll try to work on this. Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjonaFrom 8d6c753ecb6be22915a9c8430b3db50ec1a566a3 Mon Sep 17 00:00:00 2001 From: Laura Arjona Reina Date: Fri, 3 Mar 2023 08:40:19 +0100 Subject: [PATCH] Fix validation errors (reported by w3c validator, bug #1032293) --- debian/changelog | 6 ++ index.html | 16 +--- 2 files changed, 15 insertions(+), 7 deletions(-) diff --git a/debian/changelog b/debian/changelog index 6b6251b..e11c4d2 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +debian-timeline (47) UNRELEASED + + [ Laura Arjona Reina ] + * Fix validation errors (Closes: #1032293) + + debian-timeline (46) unstable; urgency=medium * Team upload. diff --git a/index.html b/index.html index 277d3a1..6e01a90 100644 --- a/index.html +++ b/index.html @@ -1,15 +1,17 @@ - + + + Debian Project Timeline - a timeline of the Debian Project - - +<link rel="stylesheet" href="media/debian-timeline.css" type="text/css"> +<script> Timeline_ajax_url='media/timeline_ajax/simile-ajax-api.js'; Timeline_urlPrefix='media/timeline_js/'; Timeline_parameters='bundle=true'; - - - + + + @@ -22,7 +24,7 @@ - Originally compiled by http://chris-lamb.co.uk/;>lamby and others. Email corrections and additions to: https://wiki.debian.org/Teams/Publicity/Timeline;>the Debian publicity team. https://salsa.debian.org/publicity-team/debian-timeline;>Git repository. + Originally compiled by http://chris-lamb.co.uk/;>lamby and others. Email corrections and additions to: https://wiki.debian.org/Teams/Publicity/Timeline;>the Debian publicity team. https://salsa.debian.org/publicity-team/debian-timeline;>Git repository. This timeline is not guaranteed to be accurate nor complete and should not be used as an official source. -- 2.30.2
Bug#1032293: debian-timeline: validation errors in timeline.debian.net
Package: debian-timeline Version: 45 Severity: normal I have passed the w3c validator (https://validator.w3.org/nu/?doc=https%3A%2F%2Ftimeline.debian.net%2F) to timeline.debian.net (which is built based on git master) and found the following results: Warning: Consider adding a lang attribute to the html start tag to declare the language of this document. From line 1, column 1; to line 1, column 6 ↩For further guidance, consult Declaring the overall language of a page and Choosing language tags. If the HTML checker has misidentified the language of this document, please file an issue report or send e-mail to report the problem. --- Error: The character encoding was not declared. Proceeding using windows-1252. https://timeline.debian.net/ --- Error: Start tag seen without seeing a doctype first. Expected html>. From line 1, column 1; to line 1, column 6 ↩Info: Trailing slash on void elements has no effect and interacts badly with unquoted attribute values. From line 4, column 1; to line 4, column 74 t Time --- Warning: The type attribute is unnecessary for JavaScript resources. From line 10, column 1; to line 10, column 64 ↩
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
Bug#791506: [www.debian.org] Content negotiation doesn't work properly with pt_BR at the Release Notes web page
Hello Content negotiation works well: if you have pt-BR and pt locales enabled in browser, and go to https://www.debian.org/releases/bullseye/releasenotes you are presented a "pt" translation of the page (because there is no pt-br translation of that page) and thus the links to "Português" are in bold instead of the links to "Português (Brasileiro)". OTOH if you click the links that are on top of the page (e.g. "Release Notes para PC 64 bits (amd64)") or go directly to https://www.debian.org/releases/bullseye/amd64/release-notes/, you will get the pt-br translation of the release notes (because for release notes, there are pt and pt-br versions). Notes: 1.- Our website does not admit, currently, pt + pt-br variants (the release notes docs allow pt and pt-br, but not our webwml pages). 2.- If a person only has pt-br locale (and not "pt"), for the webwml pages they will get a fallback language, because in the config of Apache of our website we say that for pt-br they should serve a pt-br page (not a pt one): https://salsa.debian.org/dsa-team/mirror/dsa-puppet/-/blob/production/modules/roles/templates/apache-www.debian.org.erb But if we'd change the Apache config to serve .pt files for pt-br locale, I think that the pt-br versions of release notes and maybe other documents wouldn't be served. So (correct me if I'm wrong) I think the best is leave things as they are, suggest users to include both pt-br and pt locales in their browser, and close this bug. CC'ing the Portuguese language team, for the case I'm missing something or they have a better idea. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona El 5/2/23 a las 13:12, James Addison escribió: Package: www.debian.org Followup-For: Bug #791506 Dear Maintainer, When I have *both* pt-BR and pt locales enabled in my browser (Firefox 102), then this bug appears: the 'pt' Release Notes links appear in bold instead of the expected 'pt_BR' links appearing in bold. When I remove pt, then the page is negotiated to a fallback language (en-based with my browser settings). Is it possible that content-negotiation is only enabled currently for two-character language codes, and not for country+locale combinations? Thank you, James
Bug#1030009: www.debian.org: addition of non-free-firmware for bookworm and higher
Hello again I have made a list of website files under /english, mentioning nonfree or non-free. Not all of them may need updates but I think we should review them all to be sure. I have created a pad to ease the collaborative work of reviewing files: https://storm.debian.net/shared/Daxsx1pQoBV0v1aPODgReIShC_qnpevLdvXNwQewADa Shortened URL: https://deb.li/1030009 I'm pasting the list of files below for reference. I still didn't start to review any file, and some of them I think other teams can help (CDVendors, internationalization scripts...) I'll CC them when I get to those files and post here (in the bug report) my proposals, with commits to the GR-non-free-firmware branch. List of files that need review/update Relevant files mentioning nonfree or non-free blends/index.wml Bugs/server-request.wml CD/faq/index.wml CD/http-ftp/index.wml CD/live/index.wml CD/netinst/index.wml CD/torrent-cd/index.wml devel/debian-installer/images.data devel/debian-installer/index.wml devel/join/nm-step3.wml distrib/archive.wml distrib/index.wml distrib/netinst.wml distrib/search_packages-form.inc download.wml intro/about.wml intro/philosophy.wml legal/cryptoinmain.wml legal/licenses/index.wml releases/bookworm/debian-installer/index.wml releases/bookworm/errata.wml releases/trixie/debian-installer/index.wml releases/trixie/errata.wml releases/bullseye/debian-installer/index.wml releases/bullseye/errata.wml releases/buster/debian-installer/index.wml releases/buster/errata.wml (etc, similar for former releases) releases/proposed-updates.wml security/faq.wml security/index.wml template/debian/legal_tags.wml template/debian/release_images.wml template/debian/release_info.wml CD/vendors/debiancd.db CD/vendors/getvendors.pl international/l10n/data/synonyms international/l10n/ddtp.wml international/l10n/po4a/pot.wml international/l10n/po-debconf/errors-by-pkg.inc international/l10n/po-debconf/ok.inc international/l10n/po-debconf/pot.wml international/l10n/po-debconf/todo.inc international/l10n/po-debconf/untranslated.inc international/l10n/po/ok.inc international/l10n/po/pot.wml international/l10n/po/todo.inc international/l10n/po/todo.wml international/l10n/po/untranslated.inc international/l10n/README international/l10n/scripts/fix-files.sh international/l10n/scripts/gen-files.pl international/l10n/scripts/transmonitor-check mirror/mirror_list.pl Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#1030009: www.debian.org: addition of non-free-firmware for bookworm and higher
Thanks Cyril for creating this bug and all the work you're doing related to implement the decisions of the general resolution about non-free-firmware. I have created 2 branches in the webwml repo: 1.- branch GR-non-free-firmware Where I plan to work on reflecting the changes that we should do in the website on this topic 2.- branch bookworm to prepare the changes for the website related to bookworm release that at not related with non-free-firmware (e.g. website banner, the usual changes we do for releases [1], etc) Both of them are empty for now, but I plan to put some work in the following days, and encourage everybody to help too. [1] I think it's not well documented but I usually use these 2 wiki page as reference: https://wiki.debian.org/Teams/Publicity/ReleasePointAnnouncements https://wiki.debian.org/Teams/ReleaseTeam/ReleaseCheckList/BookwormCheckList Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona El 30/1/23 a las 7:21, Cyril Brulebois escribió: Package: www.debian.org Severity: important Hi, This was mentioned a few days ago on debian-project@ by Gunnar: https://lists.debian.org/debian-project/2023/01/msg00018.html but much work has happened since then, with debian-installer components having been extended to leverage this new component. The next release of the installer should happen within the next two weeks. I'm also trying to get documentation ready, and you can read more about it in two merge requests (freshly opened, not reviewed yet): - https://salsa.debian.org/installer-team/installation-guide/-/merge_requests/23 - https://salsa.debian.org/ddp-team/release-notes/-/merge_requests/138 Unless you fancy reviewing what changed in the installer, I'd skip the former and concentrate on the latter, which briefly explains why non-free-firmware was added. It's available for bookworm suites and above (might be for other suites, but I don't expect packages to show there). TL;DR: - bullseye systems are likely to have a sources.list configured this way: deb http://deb.debian.org/debian bullseye main contrib non-free - bullseye systems getting upgraded to bookworm should be modified with the following configuration (to make sure non-free firmware packages that might be installed have a chance to get upgraded): deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware - new bookworm systems are likely to be configured with either of these (unless one picks an expert install, enabling contrib and/or non-free explicitly): deb http://deb.debian.org/debian bookworm main deb http://deb.debian.org/debian bookworm main non-free-firmware There's also some related ongoing work, about adding some hints in apt (linking back to the release notes), and about fixing command-not-found in bullseye: - https://salsa.debian.org/apt-team/apt/-/merge_requests/282 - https://bugs.debian.org/1029803 Cheers,
Bug#1017109: Bug #1017109: www.debian.org/devel/website/stats/ works only in English
Hello all After upgrading www-master from Debian 10 buster (wml 2.12.2) to Debian 11 bullseye (wml 2.32.0), we experienced an issue when building the stats files for the website (https://www.debian.org/devel/website/stats/* ) I could set up some work around in the Makefiles so the pages in English language are built correctly, but couldn't make it work for the other languages. Thus, if you for example go to https://www.debian.org/devel/website/stats/fr.en you see the correct stats for French language (page displayed in English), but if you go to https://www.debian.org/devel/website/stats/fr.fr or https://www.debian.org/devel/website/stats/fr.es (e.g. to see the French stats displayed in French or Spanish), these pages are outdated. I have removed the outdated html files from www-master (it will be propagated online in the next hours), so for now, until the bug is fixed, the pages are displayed in only English but with current stats. If anybody can have a look at the bug report and have any idea of how to fix the issue, any help is welcome: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017109 Thanks -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#1017109: Bug #1017109: issue building the /*/devel/website/stats/*.wml files with Debian 11's wml version
It seems that the changes in Makefile work for Chinese too, I may have a missing dependency y my local environment causing my former failures. I'll leave this open for a while for the case somebody comes with a better solution. If not, will close the bug in several days. Note that the change also fixed the path to CSS (mentioned in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924172#75 ) so I may close that bug too. Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona Sent with K-9 mail
Bug#1017109: issue building the /*/devel/website/stats/*.wml files with Debian 11's wml version
", "UNDEFuZH\@uHKuCNHKuHKTWuTWHK:ar.zh-hk.html.tmp\@ g+w", "-o", "UNDEFuZH\@uTWuCNTWuHKTWuTWHK:ar.zh-tw.html.tmp\@g+w", "-o", "/tmp/yNBXp5m6Qz/wml.tmp2", ...) called at /usr/share/wml/TheWML/Frontends/Wml/PassObj.pm line 85 TheWML::Frontends::Wml::PassObj::dosource(TheWML::Frontends::Wml::PassObj=HASH(0x564e54622fb0), TheWML::Frontends::Wml::PassesManager=HASH(0x564e545526b8), "/u sr/share/wml/exec/wml_p9_slice", " -o 'UNDEFuZH\@uCNuCNHKuCNTW:ar.zh-cn.html.tmp\@g+w' -o 'UNDEF"..., CODE(0x564e54a34528)) called at /usr/share/wml/TheWML/Frontends/ Wml/PassesManager.pm line 148 TheWML::Frontends::Wml::PassesManager::_generic_do(TheWML::Frontends::Wml::PassesManager=HASH(0x564e545526b8), 9, "wml_p9_slice", " -o 'UNDEFuZH\@uCNuCNHKuCNT W:ar.zh-cn.html.tmp\@g+w' -o 'UNDEF"..., Path::Tiny=ARRAY(0x564e54a70b90), Path::Tiny=ARRAY(0x564e54bc8df0), CODE(0x564e54a34528)) called at /usr/share/wml/TheWML/Fron tends/Wml/PassesManager.pm line 293 TheWML::Frontends::Wml::PassesManager::pass9(TheWML::Frontends::Wml::PassesManager=HASH(0x564e545526b8), " -o 'UNDEFuZH\@uCNuCNHKuCNTW:ar.zh-cn.html.tmp\@g+w' -o 'UNDEF"..., Path::Tiny=ARRAY(0x564e54a70b90), Path::Tiny=ARRAY(0x564e54bc8df0), Path::Tiny=ARRAY(0x564e54bc89b8)) called at /usr/share/wml/TheWML/Frontends/Wml/Pas sesManager.pm line 86 TheWML::Frontends::Wml::PassesManager::__ANON__(TheWML::Frontends::Wml::PassesManager=HASH(0x564e545526b8), " -o 'UNDEFuZH\@uCNuCNHKuCNTW:ar.zh-cn.html.tmp\@g +w' -o 'UNDEF"..., Path::Tiny=ARRAY(0x564e54a70b90), Path::Tiny=ARRAY(0x564e54bc8df0), Path::Tiny=ARRAY(0x564e54bc89b8)) called at /usr/share/wml/TheWML/Frontends/Wml/ Runner.pm line 380 TheWML::Frontends::Wml::Runner::_run_pass(TheWML::Frontends::Wml::Runner=HASH(0x564e545524f0), 9, SCALAR(0x564e54a9f108), REF(0x564e54a9f0d8), REF(0x564e54a9f0 f0)) called at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 440 TheWML::Frontends::Wml::Runner::_passes_loop(TheWML::Frontends::Wml::Runner=HASH(0x564e545524f0)) called at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 727 TheWML::Frontends::Wml::Runner::_output_and_cleanup(TheWML::Frontends::Wml::Runner=HASH(0x564e545524f0)) called at /usr/share/wml/TheWML/Frontends/Wml/Runner.p m line 932 TheWML::Frontends::Wml::Runner::run_with_ARGV(TheWML::Frontends::Wml::Runner=HASH(0x564e545524f0), HASH(0x564e546cbf10)) called at /usr/bin/wml line 47 I'll leave things like this, I hope somebody can help to fix this issue, if not, I'll give a second thought/try in the following days. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#924139: www.debian.org: migrate from python to python3
Hello thanks everybody for the work and sorry to get to this so late. I think that currently our Python2 code is in these files: Webwml repo: ./english/mirror/timestamps/archive_mirror_check.py ./english/mirror/timestamps/mirror_check.py Cron repo: /urlcheck/test.py /urlcheck/urlcheck.py I'll try to apply the patch [0002-Python-scripts-modify-to-use-Python3-syntax.patch] that Carsten provided and do some tests, and that would cover the webwml repo. For the cron repo, I tried to pass the 2to3 tool and follow the instructions but had some issues and couldn't complete the migration. I'll do another try during this weekend and post here my results, but if anybody is familiarised with Python coding, any help is appreciated. Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#1009253: translations needed: bug #1009253 remove debian-www list from the footer; direct people to the contact page instead
thanks for the translations already present! A correction in my instructions: El 12 de mayo de 2022 23:39:25 CEST, Laura Arjona Reina escribió: How to do it: > >* Update your local repo (git pull) >* Go to your language/po folder and do "update-po" Go to your language/po folder and run "make update-po" >* Complete the translation in templates.po file >* Commit changes (thanks!) > sorry for the missed "make" Thanks again! Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona Sent with K-9 mail
Bug#1009253: translations needed: bug #1009253 remove debian-www list from the footer; direct people to the contact page instead
Dear translators Thanks Paul Wise and Justin B. Rye, we have updated the website footer to change the contact address in the from debian-www to the contact page, in order to help people ask in the right place (bug #1009253, commit https://salsa.debian.org/webmaster-team/webwml/-/commit/39793d99332303af2dc56ed4b1a556019997bb86). We would need translations of the new string. How to do it: * Update your local repo (git pull) * Go to your language/po folder and do "update-po" * Complete the translation in templates.po file * Commit changes (thanks!) Since the footer is used in almost all the pages, the website build has been stopped until we get some translations, so we avoid several consecutive long builds (one for each translation if they don't arrive together). I hope we get at least 3-4 languages during this time, and then activate the cron job to do the builds maybe around noon UTC. Note: if your language has no active translator group or coordinator but you want to help, just reply this mail to debian-www with your the name of the language and translation. The sentence is quite short: "See our [contact page] to get in touch. Web site source code is [available]." Thanks! -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#1009971: Our current validation script does not work with html5 files
Package: www.debian.org User: www.debian@packages.debian.org Usertag: scripts Severity: important Hi all I'm starting to work in the bug #980921 (Pages in HTML5) and, as it is mentioned there, we need to adapt our "validate" script so it correctly processes the pages declared as HTML5 (currently, only the homepage in the different languages). The current status is following: Related scripts: https://salsa.debian.org/webmaster-team/cron/-/blob/master/lessoften executed once a day, calling (via run-parts) the following script: https://salsa.debian.org/webmaster-team/cron/-/blob/master/scripts/999Xvalidate which gets the list of languages and folders to process and then calls: https://salsa.debian.org/webmaster-team/cron/-/blob/master/scripts/validate Which is the actual script doing the HTML validation, using the onsgmls command (part of opensp package). This command validates a SGML file based on a DTD. The issue (as far as I know) is that there is no "official" SGML DTD template to use when parsing HTML5 files. I have tried adapting the "validate" script to be able to recognize the DOCTYPE header used for html5 files, and then tried to pass a DTD (I tried downloading the ones here http://sgmljs.net/docs/w3c-html5-dtd.html and here http://sgmljs.net/docs/w3c-html52-dtd.html and also here https://jkorpela.fi/html5-dtd.html ) but couldn't make it work, and also was not convinced it is the better approach. I've tried to look at what w3c validator uses and they use Nu.checker: https://validator.w3.org/nu/about.html https://github.com/validator/validator/releases/latest But I'm not sure if this is packaged in Debian in any of its flavours. I have searched https://packages.debian.org/search?keywords=html5 but none of the results looks like a commandline tool that we could call instead of onsgmls So I don't know what to do at this point. In my local machine, I have downloaded the vnu.jar file from the latest Nu checker release " and tried to validate files and it works. But I don't know if asking DSA to install openjdk in www-master and include a copy of vnu.jar in our cron scripts is good and/or elegant. Opinions, advice and patches are very welcome. Meanwhile, I guess we can modify 99Xvalidate to add file exclusions, and exclude, for now, /index.*.html and later the few other files we have with html5 tags for now. I don't know how to exclude the index.*.html files on top folder only and not in subfolders but I guess playing with find -wholename and prune will do the treak (if you know, please go ahead). Kind regards, -- Laura Arjona https://wiki.debian.org/LauraArjona
Bug#980921: Pages in HTML5
Hi all I have added a basic5.wml and template5.wml templates in /english/templates/debian to start using them in the files that already have HTML5 tags. https://salsa.debian.org/webmaster-team/webwml/-/commit/8dc031327d5b4147c02030aac97866283094286d I have changed mainpage.wml to use the new templates (mainpage.wml is only used in the homepage). https://salsa.debian.org/webmaster-team/webwml/-/commit/a10f9519aee4f29278a7c597da8071cd42f9df97 I have updated the recent_list.wml template so the datetime values are produced in correct format. https://salsa.debian.org/webmaster-team/webwml/-/commit/2597b5a9d1a8517d803da5ed03b87ac8cf24a11e I have checked my tests with the homepage with https://validator.w3.org/ and looks fine. I'll try to have a look at the validation script and move other pages to use these html5 templates, and fix the issues that arise. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#1006326: issues connecting to https://bugs.debian.org/cgi-bin/soap.cgi (generation of wnpp related pages)
Hello all The code I added to show more info when it fails didn't help, we get the same messages in the build logs. I have tried to use groups of 300 bugs instead of 500, and also groups of 1000 bugs, but it seems it makes no difference. I have looked at the date of the wnpp.data file in www-master.d.o and it's from today 03:29, so I guess the script runs successfully the first time of the day, and then it fails on the later builds. Looking at the Makefile, that tries to generate the wnpp.data for English in every build, and also deletes the file on error, I'm thinking about moving the code generating the wnpp.data file to the "lessoften" cron scripts so it runs once a day, and let the webwml repo to just use the wnpp.data file of that day. Opinions? Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#1006326: issues connecting to https://bugs.debian.org/cgi-bin/soap.cgi (generation of wnpp related pages)
Hello
I have added some lines to the wnpp.pl script (see commit below) so when it
fails, it shows the point of the process when the connection failed.
Kind regards,
--
Laura Arjona Reina
https://wiki.debian.org/LauraArjona
commit 2727d89ba5faed7d30faab1c58cf3b6e7c6fe841 (HEAD -> master, origin/master,
origin/HEAD)
Author: Laura Arjona Reina
Date: Wed Mar 2 11:40:34 2022 +0100
add messages and numbers to be shown when the connections to bugs.d.o fails
(related: bug #1006326 )
diff --git a/english/devel/wnpp/wnpp.pl b/english/devel/wnpp/wnpp.pl
index 53aff43cefc..ef34ff41c2d 100644
--- a/english/devel/wnpp/wnpp.pl
+++ b/english/devel/wnpp/wnpp.pl
@@ -40,10 +40,15 @@ while () {
my $soap = SOAP::Lite->uri('Debbugs/SOAP')->proxy('https://bugs.debian.org/cgi-bin/soap.cgi')
or die "Couldn't make connection to SOAP interface: $@";
-my $bugs = $soap->get_bugs(package=>'wnpp')->result;
+my $bugs = $soap->get_bugs(package=>'wnpp')->result
+ or die "Failed to get the list of bugs for package wnpp";
my $status = {};
+my $count = 0;
+my $total = @$bugs;
while (my @slice = splice(@$bugs, 0, 500)) {
-my $tmp = $soap->get_status(@slice)->result() or die;
+$count = $count + 1;
+my $tmp = $soap->get_status(@slice)->result()
+or die "Failed to get status for bunch $count (of 500 bugs), total bugs to
process: $total)";
%$status = (%$status, %$tmp);
}
Bug#1006326: issues connecting to https://bugs.debian.org/cgi-bin/soap.cgi (generation of wnpp related pages)
Package: www.debian.org
User: www.debian@packages.debian.org
Usertag: scripts
Severity: normal
Dear all
Since several days, the script wnpp.pl fails intermittently when trying to
connect to bugs.debian.org, and when it fails, we receive the following
messages in the webwml build log:
[...]
make -C wnpp install
make[3]: Entering directory '/srv/www.debian.org/webwml/english/devel/wnpp'
wml -q -D CUR_YEAR=2022 -o UNDEFuEN:../../../english/devel/wnpp/wnpp.data@g+w
-W7,-Squotes ../../../english/devel/wnpp/wnpp.pl
ePerl:Error: Perl runtime error (interpreter rc=2)
Contents of STDERR channel: -
500 Can't connect to bugs.debian.org:443 (Connection refused) at
/tmp/wml.12011.tmp1 line 147.
--
** WML:Break: Error in Pass 3 (rc=1).
Died at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 403.
TheWML::Frontends::Wml::Runner::_run_pass(TheWML::Frontends::Wml::Runner=HASH(0x55f9849f2458),
3, SCALAR(0x55f984f718d8), SCALAR(0x55f984f718a8), SCALAR(0x55f984f718c0))
called at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 441
TheWML::Frontends::Wml::Runner::_passes_loop(TheWML::Frontends::Wml::Runner=HASH(0x55f9849f2458))
called at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 726
TheWML::Frontends::Wml::Runner::_output_and_cleanup(TheWML::Frontends::Wml::Runner=HASH(0x55f9849f2458))
called at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 930
TheWML::Frontends::Wml::Runner::run_with_ARGV(TheWML::Frontends::Wml::Runner=HASH(0x55f9849f2458),
HASH(0x55f984b252b8)) called at /usr/bin/wml line 47
make[3]: *** [Makefile:34: ../../../english/devel/wnpp/wnpp.data] Error 2
make[3]: Leaving directory '/srv/www.debian.org/webwml/english/devel/wnpp'
make[2]: [../../Makefile.common:84: wnpp-install] Error 2 (ignored)
make[2]: Leaving directory '/srv/www.debian.org/webwml/english/devel'
[...]
Since the line refers to a temp file, I'm not 100% sure about which is the
command that causes the failure, but the code in wnpp.pl that uses
bugs.debian.org I think is restricted to these lines (initial connection, and
retrieval of bug info to build the wnpp.data local database):
https://salsa.debian.org/webmaster-team/webwml/-/blob/master/english/devel/wnpp/wnpp.pl#L41
(L41 to 48)
my $soap =
SOAP::Lite->uri('Debbugs/SOAP')->proxy('https://bugs.debian.org/cgi-bin/soap.cgi')
or die "Couldn't make connection to SOAP interface: $@";
my $bugs = $soap->get_bugs(package=>'wnpp')->result;
my $status = {};
while (my @slice = splice(@$bugs, 0, 500)) {
my $tmp = $soap->get_status(@slice)->result() or die;
%$status = (%$status, %$tmp);
}
Some people commented the issue in the #debian-admin IRC channel, for the case
there was some issue in the bugs.d.o servers or some configuration change, but
it seems the failures are related to the connections being blocked by the http
rate-limiting. It's not clear, however, why these issues are appearing now
(nothing in the script changed in the recent times, and the amount of bugs is
not drastically bigger than weeks before). In addition to this, some other days
the script is tolerated well (for example, we had failures on 2022/02/18 and
2022/02/22, but today 2022/02/23 the builds are finishing successfully).
Looking at the code, I see we're processing bugs in groups of 500 bugs. I'm not sure if
we could try to reduce the number of the bugs in the group and introduce some
"sleep" time between queries, or it's better to do the opposite, increase the
number of bugs in a group to reduce the total number of queries.
Other approach could be to rewrite the wnpp.pl script so it uses queries
against UDD instead of the SOAP CGI interface of bugs.debian.org
I don't know which approach is better, and also my Perl skills are not enough
to propose a patch myself for none of this two options. If anybody can and
wants to work on this, it's very appreciated.
I'll point the Debbugs team to this bug one it is created for the case they
changed any configuration in their deployment that caused the connection
failures, or for the case they have any advice about the better way to connect
or retrieve the information we need to create the WNPP-related web pages.
Kind regards,
Laura Arjona Reina
https://wiki.debian.org/LauraArjona
Bug#940528: installation-reports: b43 firmware not found or installed (Debian 11 bullseye installer from image with firmware non-free)
Hello I recently installed Debian 11 bullseye on a laptop with BCM4312 with a non-free firmware image, and could reproduce this issue. Below you can find my installation report. TL;DR: The installer reported: failed to load B43/ucode15.fw for my wireless card. I continued the installation with the Ethernet adapter. After finishing installing Debian and rebooting I had wired network but no wireless network. Manually installing firmware-b43-installer package solved the problem. I'm not sure if debian-installer is able to automatically install firmware-b43-installer or the mechanics is designed for simpler firmware packages (the ones that include the firmware in the proper package, not downloading it on the fly as firmware-b43-installer does). Kind regards, -- Laura Arjona https://wiki.debian.org/LauraArjona Boot method: USB Image version: https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.1.0+nonfree/i386/iso-cd/firmware-11.1.0-i386-netinst.iso Date: 2021-10-09 14:15 564M Machine: Compaq N110 netbook (intel Atom, 1GB RAM, Wireless Broadcom BCM4312 LP-PHY) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [E] Detect media: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: The installer reported: failed to load B43/ucode15.fw for my wireless card. I continued the installation with the Ethernet adapter. I was expecting the ISO including firmware to install automatically the firmware-b43-installer package After manually installing it, I could use my wireless card. This is the relevant dmesg output after installing firmware-b43-installer package and rebooting: [ 29.831448] b43-phy0: Broadcom 4312 WLAN found (core revision 15) [ 29.876277] b43-phy0: Found PHY: Analog 6, Type 5 (LP), Revision 1 [ 29.876303] b43-phy0: Found Radio: Manuf 0x17F, ID 0x2062, Revision 2, Version 0 [ 29.892558] Broadcom 43xx driver loaded [ Features: PNLS ] [ 29.987553] b43 ssb0:0: firmware: direct-loading firmware b43/ucode15.fw [ 30.001227] b43 ssb0:0: firmware: direct-loading firmware b43/lp0initvals15.fw [ 30.006248] b43 ssb0:0: firmware: direct-loading firmware b43/lp0bsinitvals15.fw [ 30.006326] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 431.884370] b43-phy0: Loading firmware version 784.2 (2012-08-15 21:35:19) [ 441.397152] b43-phy0: Loading firmware version 784.2 (2012-08-15 21:35:19) Below you can find the info that installer-report gathered: -- Package-specific info: == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="11 (bullseye) - installer build 20210731+deb11u1" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux portatil21 5.10.0-9-686 #1 SMP Debian 5.10.70-1 (2021-09-30) i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GSE Express Memory Controller Hub [8086:27ac] (rev 03) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:308f] lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:308f] lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:308f] lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition Audio Controller [8086:27d8] (rev 02) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:308f] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 1 [8086:27d0] (rev 02) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 2 [8086:27d2] (rev 02) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 [8086:27c8] (rev 02) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:308f] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci_hcd lspci -knn: 00:1d.1 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 [8086:27c9] (rev 02) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:308f] lspci -knn: Kernel
Bug#991941: linux: Don't use nouveau with Nvidia GeForce 8500 GT or alert in dmesg that firmware is needed
Hello again El 10 de agosto de 2021 2:56:01 CEST, Ben Hutchings escribió: >Control: tag -1 moreinfo > >On Fri, 2021-08-06 at 12:03 +0200, Laura Arjona Reina wrote: >> Source: linux >> Severity: normal >> >> Dear Maintainer, >> >> *** Reporter, please consider answering these questions, where >> appropriate *** >> >> * What led up to the situation? >> >> I have installed Debian 11 (debian installer RC3) on a PC having a >> Nvidia GeForce 8500 GT as main graphics card. >> The graphicall install process went well. After finishing the >> installation and reboot, I got a blank screen and "Input not supported" >> on my monitor. >> I changed to tty2 and logged in, and saved the dmesg output (attached), >> I noticed that "nouveau" driver was loaded but there was no info about >> my card not supported or needing additional firmware. > >The missing firmware should have been fixed in installer RC3 *if* you >use an installer image that includes firmware, but not if you use the >default images. Which did you use? > I used the official image without firmware but was expecting that using isenkram-autoinstall-firmware afterwards was equivalent. >On the kernel side we should try to fix the blank screen with an >earlier check for firmware in nouveau, similarly to the way we patch >the amdgpu and radeon drivers. (Although those patches now seem not to >be completely effective.) > >> * What exactly did you do (or not do) that was effective (or >> ineffective)? >> >> I have rebooted and edited the "linux" line during Grub menu, to add >> "nomodeset" and then I could have a fallback graphics mode. >> I have installed the isenkram-cli package and ran >> isenkram-autoinstall-firmware as suggested in the release notes and it >> installed firmware for my realtek card (unrelated) and >> firmware-misc-nonfree, but rebooting makes Linux pick the nouveau driver >> again. >[...] > >Well that's expected. The kernel driver and firmware are two different >things that work together. Installing the firmware should allow >nouveau to work properly. > >Are you saying that even with firmware-misc-nonfree installed, you >still get a black screen when you don't use "nomodeset"? > Exactly. At the end of August or beginning of September I can do an install using the image with firmware but I'll suspect that the results will be the same, because the needed firmware is not in Debian non-free either (card not supported in Bullseye). I think that nouveau should somehow output that message (card not supported) so the user gets a hint about what's happening. Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona Sent with K-9 mail
Bug#954093: desktop-base: Integration with KDE plasma on debian testing no longer works
Hello again I formerly said that my desktop was all Homeworld-themed except the wallpaper, but I just found out that the lockscreen also had the "Shells" background instead of the proposed Homeworld image for lockscreen. I'm not sure if Plymouth is also well integrated or not because this computer never shows the Plymouth animations. OTOH I see that there's another customizable image, the "Welcome screen", that in this system shows the Breeze welcome screen (I don't know if we provide a Homeworld welcome screen or not). Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#991941: attaching dmesg and lspci output
I'm attaching the dmesg and lspci output for the case they are useful. Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona Sent with K-9 mail[0.00] Linux version 5.10.0-8-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.46-3 (2021-07-28) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64 root=UUID=02117186-1520-493e-b434-e6e4c856a515 ro quiet [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009d7ff] usable [0.00] BIOS-e820: [mem 0x0009d800-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xb9aa1fff] usable [0.00] BIOS-e820: [mem 0xb9aa2000-0xb9aa8fff] ACPI NVS [0.00] BIOS-e820: [mem 0xb9aa9000-0xba2d7fff] usable [0.00] BIOS-e820: [mem 0xba2d8000-0xba4f3fff] reserved [0.00] BIOS-e820: [mem 0xba4f4000-0xca8befff] usable [0.00] BIOS-e820: [mem 0xca8bf000-0xca956fff] reserved [0.00] BIOS-e820: [mem 0xca957000-0xca993fff] usable [0.00] BIOS-e820: [mem 0xca994000-0xcaa56fff] ACPI NVS [0.00] BIOS-e820: [mem 0xcaa57000-0xcaffefff] reserved [0.00] BIOS-e820: [mem 0xcafff000-0xcaff] usable [0.00] BIOS-e820: [mem 0xcb80-0xcf9f] reserved [0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved [0.00] BIOS-e820: [mem 0xfed0-0xfed03fff] reserved [0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xff00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00012f5f] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.7 present. [0.00] DMI: Gigabyte Technology Co., Ltd. H81M-S1/H81M-S1, BIOS FH 08/10/2015 [0.00] tsc: Fast TSC calibration using PIT [0.00] tsc: Detected 3392.039 MHz processor [0.000461] e820: update [mem 0x-0x0fff] usable ==> reserved [0.000464] e820: remove [mem 0x000a-0x000f] usable [0.000469] last_pfn = 0x12f600 max_arch_pfn = 0x4 [0.000472] MTRR default type: uncachable [0.000473] MTRR fixed ranges enabled: [0.000474] 0-9 write-back [0.000475] A-B uncachable [0.000475] C-C write-protect [0.000476] D-E7FFF uncachable [0.000477] E8000-F write-protect [0.000477] MTRR variable ranges enabled: [0.000478] 0 base 00 mask 7F write-back [0.000479] 1 base 01 mask 7FE000 write-back [0.000480] 2 base 012000 mask 7FF000 write-back [0.000481] 3 base 00E000 mask 7FE000 uncachable [0.000481] 4 base 00D000 mask 7FF000 uncachable [0.000482] 5 base 00CC00 mask 7FFC00 uncachable [0.000483] 6 base 00CB80 mask 7FFF80 uncachable [0.000483] 7 base 012F80 mask 7FFF80 uncachable [0.000484] 8 base 012F60 mask 7FFFE0 uncachable [0.000485] 9 disabled [0.000746] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [0.000947] e820: update [mem 0xcb80-0x] usable ==> reserved [0.000952] last_pfn = 0xcb000 max_arch_pfn = 0x4 [0.006871] found SMP MP-table at [mem 0x000fd6c0-0x000fd6cf] [0.013870] Using GB pages for direct mapping [0.014409] RAMDISK: [mem 0x33041000-0x35817fff] [0.014411] ACPI: Early table checksum verification disabled [0.014414] ACPI: RSDP 0x000F0490 24 (v02 ALASKA) [0.014417] ACPI: XSDT 0xCAA24078 6C (v01 ALASKA A M I 01072009 AMI 00010013) [0.014421] ACPI: FACP 0xCAA30620 00010C (v05 ALASKA A M I 01072009 AMI 00010013) [0.014425] ACPI: DSDT 0xCAA24178 00C4A7 (v02 ALASKA A M I 0088 INTL 20091112) [0.014427] ACPI: FACS 0xCAA55080 40 [0.014429] ACPI: APIC 0xCAA30730 72 (v03 ALASKA A M I 01072009 AMI 00010013) [0.014431] ACPI: FPDT 0xCAA307A8
Bug#954093: desktop-base: Integration with KDE Plasma on Debian 11 no longer works
Package: desktop-base Version: 11.0.3 Followup-For: Bug #954093 Dear Maintainer, I've just installed a PC with KDE Plasma desktop task using the Debian 11 installer RC3 and this bug is still present. My computer is all HomeWorld-themed except the desktop wallpaper (I got the "Shells" one). I could change it to HomeWorld successfully with right click, "Configure Desktop and Wallpaper", and choosing the "Homeworld" wallpaper. But I was expecting that the Debian theme wallpaper was shown directly after install. I have checked the .js script and looks the same as the first reporter informed, and also checked if there's a debian-theme as suggested but it isn't. Kind regards, Laura Arjona Reina https://wiki.debian.org/LauraArjona -- System Information: Debian Release: 11.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages desktop-base depends on: ii fonts-quicksand 0.2016-2.1 ii librsvg2-common 2.50.3+dfsg-1 Versions of packages desktop-base recommends: ii plymouth-label 0.9.5-3 Versions of packages desktop-base suggests: ii kde-standard 5:111 -- no debconf information
Bug#991941: linux: Don't use nouveau with Nvidia GeForce 8500 GT or alert in dmesg that firmware is needed
Source: linux Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I have installed Debian 11 (debian installer RC3) on a PC having a Nvidia GeForce 8500 GT as main graphics card. The graphicall install process went well. After finishing the installation and reboot, I got a blank screen and "Input not supported" on my monitor. I changed to tty2 and logged in, and saved the dmesg output (attached), I noticed that "nouveau" driver was loaded but there was no info about my card not supported or needing additional firmware. * What exactly did you do (or not do) that was effective (or ineffective)? I have rebooted and edited the "linux" line during Grub menu, to add "nomodeset" and then I could have a fallback graphics mode. I have installed the isenkram-cli package and ran isenkram-autoinstall-firmware as suggested in the release notes and it installed firmware for my realtek card (unrelated) and firmware-misc-nonfree, but rebooting makes Linux pick the nouveau driver again. I have installed manually the nvidia-detect package and then I learned that this card needs the nvidia-legacy-340xx package, which is not present in bullseye. I tried to install manually the nvidia-legacy-340xx-driver package from sid and got the system showing a graphical environment without the need of adding "nomodeset" to the grub linux line. However later I read https://wiki.debian.org/NvidiaGraphicsDrivers and found: "Version 340.108 (legacy GPUs) (supported devices) Older legacy driver, for GeForce 8 series through GeForce 300 series. No Vulkan support, supports up to OpenGL 3.3 depending on your card. Use of the 340-series driver is strongly discouraged. It is not included in stable releases of Debian anymore, has serious unfixable security vulnerabilities, and may not be updated for new kernels in a timely manner. You are highly recommended to use the built-in Nouveau driver if security is a priority. " So I uninstalled the package. * What was the outcome of this action? I'm not sure which is the best way to get this system working, but anyway I think the average user would get puzzled about dmesg not alerting anything wrong but the system not showing graphics unless "nomodeset". * What outcome did you expect instead? I think that dmesg should alert the user that the card is not well supported by nouveau and/or would need to install additional firmware or be used in fallback mode. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona -- System Information: Debian Release: 11.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#990104: Use of uninitialized value in english/international/l10n/scripts/gen-files.pl
Package: www.debian.org Severity: normal User: www.debian@packages.debian.org Usertags: scripts X-Debbugs-CC: debian-i...@lists.debian.org Hi all, looking at the build logs of the website ( https://www-master.debian.org/build-logs/webwml/wml_run.log ) I've found some Perl warnings when building the l10n-related pages: perl ../../../../english/international/l10n/scripts/gen-files.pl --sort=../../../../english/international/l10n/data/popcon --dist=unstable --l10ndir=../../../../english/international/l10n --langs --po --podebconf --po4a Use of uninitialized value in hash element at ../../../../english/international/l10n/scripts/../../../../Perl/Debian/L10n/Db.pm line 264, line 26457. [...] Use of uninitialized value within %LanguageList in concatenation (.) or string at ../../../../english/international/l10n/scripts/gen-files.pl line 331. [...] (the "[...]" means a lot (hundreds) of repetitions of the same warning). I've seen this script is called in these makefiles: english/international/l10n/po4a/Makefile:39:perl $(L10N_DIR)/scripts/gen-files.pl --sort=$(SORT_PKGS) --dist=$(DIST) --l10ndir=$(L10N_DIR) --langs --po --podebconf --po4a english/international/l10n/po/Makefile:46: perl $(L10N_DIR)/scripts/gen-files.pl --sort=$(SORT_PKGS) --dist=$(DIST) --l10ndir=$(L10N_DIR) --langs --po --podebconf --po4a english/international/l10n/po-debconf/Makefile:52: perl $(L10N_DIR)/scripts/gen-files.pl --sort=$(SORT_PKGS) --dist=$(DIST) --l10ndir=$(L10N_DIR) --langs --po --podebconf --po4a but I don't know how to fix the issue. I'm creating this bug as a request for help. Kind regards, Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#956192: Any progress or missing information?
Hi I have added an exception about manpages-l10n in a similar way than was already for manpages-fr-extra (thanks David Prévot for the hint): https://salsa.debian.org/webmaster-team/webwml/-/commit/017f1d07c22c906dcb76ad48d7db75ff615b9b99 Closing the bug, feel free to reopen if you see something broken or not working as expected (I think the scripts run once a day, so we need to wait a bit to see the efects of the change made in the webwml repo). Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona El 10/4/21 a las 19:18, Helge Kreutzmann escribió: > Dear webmasters, > one year ago I requested that manpages-l10n should be removed from > https://www.debian.org/international/l10n/po/de > > as it does not make sense to track it. David Prevot reported that in > the past the (no longer existing) manpages-fr-extra had been removed > from being listed there as well. > > Please remove it for the other languages as well (fr, es, mk, ..), > tracking it here really is useless and (speaking as part of upstream) > have good working relationship with the translators (as far as they > are still active). > > If you require any further input from my side please let me know. > > Thanks! > > Greetings > > Helge > -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#896067: 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
Bug#983178: Created a merge request fixing this issue
Hello Marcin thank you very much for working on this! I have had a look at the merge request in salsa, but couldn't test the script myself (yet). For what I understood (please correct me if I am wrong), the output is filtered when composing the mail, so for languages having only the same validation issues than English, translators would get a mail anyway, just with almost empty content. I wonder if it's maybe better to filter and rewrite the log files, so the languages having derived from English issues don't receive mail (at least until English is fixed), or better to just add a sentence like "you may have additional validation issues that need to be fixed in the corresponding English file(s), too." to the mail. Kind regards, El 4 de marzo de 2021 22:24:11 CET, Marcin Owsiany escribió: >I created https://salsa.debian.org/webmaster-team/cron/-/merge_requests/6 >which fixes this issue. >It would be great if someone could review and/or merge. > >Marcin -- Laura Arjona Reina https://wiki.debian.org/LauraArjona Sent with K-9 mail
Bug#980921: Pages in HTML5
Package: www.debian.org User: www.debian@packages.debian.org Usertag: scripts Severity: normal Hi, we have talked a bit in the past about migrating the website to HTML5, and we have now HTML5 tags in the homepage, that produce validation errors. In Salsa we have the Merge Request 619: "webwml | Replace article tags to fix validation issue (!619)" https://salsa.debian.org/webmaster-team/webwml/-/merge_requests/619 proposing to remove those tags, to make the document valid for the current declaration (HTML 4.01 strict), but I agree with Boyuan Yang that we should consider migrating to HTML5 instead. I think that we can create a basic_html5.wml template and make the pages that are ready to use that, and also the new pages that we write, so all the new content uses HTML5, and then after a while we can consider migrating the "difficult" pages. I have created a branch for this work: https://salsa.debian.org/webmaster-team/webwml/-/tree/html5 where I have made the minimal change to the basic.wml template (in the basic_html5.wml file): --- basic.wml 2021-01-22 13:19:18.512335720 +0100 +++ basic_html5.wml 2021-01-24 12:38:24.172801930 +0100 @@ -7,7 +7,7 @@ http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\;>" - "http://www.w3.org/TR/html4/strict.dtd\;>" + "" /> And then made the mainpage to use it. Then I built the /english/index.en.html file and uploaded to https://validator.nu/, and found these errors: 1.- Error: Bad value 05 Dec 2020 for attribute datetime on element time: The literal did not satisfy the time-datetime format. From line 235, column 31; to line 235, column 106 ect-news"> tags in the file) 3.- Warning: Potentially bad value copyright for attribute rel on element a: The keyword copyright for the rel attribute should not be used. Consider using license instead. From line 292, column 61; to line 292, column 96 hers; See licens Now, 3 questions: 1.- I don't know if the change to the template is enough (at least to start) or we need to declare the HTML5 in other way. 2.- About the datetime errors in the homepage, those strings are generated by the function newsdate in the ctime.html template (called by the get_top_news() function in the recent_list template). I think the code that needs to be reviewed is L530 to L550 in the recent_list.wml template, but having into account that this: * will affect how the date is displayed, including translations * when we migrate to HTML5 other pages using the recent_list function this problem will arise too, since the code I refer is the part related to the homepage only. 3.- The warning about the rel="copyright" could be easily changed by changing the footer.wml template, but I don't know if the proposed rel="license" is html4.01 strict-compatible, or we should create a footer_html5.wml template for the pages that are switching to html5. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#973544: www.debian.org: LTS Security Advisories RSS links to wrong locations
Hi Nobuhiro Ban, Thanks for reporting this issue. The build of those RSS feeds is done via the get_recent_list() function in the recent_list template: https://salsa.debian.org/webmaster-team/webwml/-/blob/master/english/template/debian/recent_list.wml However, that function is not prepared for security advisories in other path different than www.debian.org/security. In any case, I see that other security lists now call to a different (improved) template: https://salsa.debian.org/webmaster-team/webwml/-/blob/master/english/template/debian/recent_list_security.wml But I couldn't find the correct way to call the function get_recent_security_list_rdf so it creates the RSS feed. CC'ing the debian-lts mailing list for the case they can have a look. Kind regards, El 1/11/20 a las 16:40, Nobuhiro Ban escribió: > Package: www.debian.org > Severity: normal > > Dear Maintainer, > > Debian LTS Security Advisories RSS (https://www.debian.org/lts/security/dla) > links to wrong locations. > > For example: > >> https://www.debian.org/security/2020/dla-2425; /> > > It should be https://www.debian.org/lts/security/2020/dla-2425 . > > > Regards, > Nobuhiro Ban > -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#972357: [INTL:sv] Swedish debconf template, fixing charset (no strings update)
Hi Felix The data in unstable is parsed in several ways, for a particular package I guess the URL to see the status of the po-debconf templates is: https://i18n.debian.org/l10n-pkg-status/X/name_of_package.html X being the initial of the name of the package. For example, for mdadm: https://i18n.debian.org/l10n-pkg-status/m/mdadm.html Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#972357: [INTL:sv] Swedish debconf template, fixing charset (no strings update)
Package: mdadm Version: 4.1-6 Severity: wishlist Tags: l10n patch X-Debbugs-CC: debian-l10n-swed...@lists.debian.org Hi, at the website team we're receiving tidy validation errors in this page: https://www.debian.org/international/l10n/po-debconf/sv.en.html (and translations) It seems it's due to a bad encoding of the last translator name in mdadm package: mdadm 80% (8t;0f;2u) sv.po Martin Ã…gren I've had a look at the corresponding file and I think the issue appears because the text is written as UTF-8, but the .po file declares another charset (ISO-8859-1). (If I open the .po file with a "normal" editor it's shown correctly, but if opened with POEdit it shows many character issues). I'm attaching a new sv.po files where I change the line declaring the charset of the file, to be UTF-8. With this change, the strings are correctly shown in POEdit and I guess the Debian website will be happy, too. CC'ing the debian-l10n-swedish mailing list for the case anybody is working on updating the translation, so they take this issue into account. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona # translation of mdadm_2.6.7-3_sv.po to Swedish # Translators, if you are not familiar with the PO format, gettext # documentation is worth reading, especially sections dedicated to # this format, e.g. by running: # info -n '(gettext)PO Files' # info -n '(gettext)Header Entry' # Some information specific to po-debconf are available at # /usr/share/doc/po-debconf/README-trans # or http://www.debian.org/intl/l10n/po-debconf/README-trans # Developers do not need to manually edit POT or PO files. # # Martin Ågren , 2008. msgid "" msgstr "" "Project-Id-Version: mdadm_2.6.7-3_sv\n" "Report-Msgid-Bugs-To: md...@packages.debian.org\n" "POT-Creation-Date: 2019-02-09 08:48+0100\n" "PO-Revision-Date: 2008-07-23 18:34+0200\n" "Last-Translator: Martin Ågren \n" "Language-Team: Swedish \n" "Language: sv\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Generator: KBabel 1.11.4\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Type: boolean #. Description #: ../mdadm.templates:2001 msgid "Should mdadm run monthly redundancy checks of the MD arrays?" msgstr "Ska mdadm köra månatliga redundanskontroller av MD-kedjorna?" #. Type: boolean #. Description #: ../mdadm.templates:2001 msgid "" "If the kernel supports it (versions greater than 2.6.14), mdadm can " "periodically check the redundancy of MD arrays (RAIDs). This may be a " "resource-intensive process, depending on the local setup, but it could help " "prevent rare cases of data loss. Note that this is a read-only check unless " "errors are found; if errors are found, mdadm will try to correct them, which " "may result in write access to the media." msgstr "" "Om din kärna har stöd för det (versioner senare än 2.6.14), kan mdadm " "periodvis kontrollera redundansen för dina MD-kedjor (RAID). Det här kan " "vara en resurskrävande process, beroende på din konfiguration, men den kan " "hjälpa till att förhindra ovanliga fall av dataförluster. Observera att det " "är en skrivskyddad kontroll såvida inte fel påträffas; om fel hittas kommer " "mdadm försöka att rätta till dem, vilket kan leda till skrivåtkomst till " "mediet." #. Type: boolean #. Description #: ../mdadm.templates:2001 msgid "" "The default, if turned on, is to check on the first Sunday of every month at " "01:06." msgstr "" "Standardvärdet, om påslagen, är att kontrollera på den första söndagen i " "varje månad klockan 01.06." #. Type: boolean #. Description #: ../mdadm.templates:3001 msgid "Should mdadm check once a day for degraded arrays?" msgstr "" #. Type: boolean #. Description #: ../mdadm.templates:3001 msgid "" "mdadm can check once a day for degraded arrays and missing spares to ensure " "that such events don't go unnoticed." msgstr "" #. Type: boolean #. Description #: ../mdadm.templates:4001 msgid "Do you want to start the MD monitoring daemon?" msgstr "Vill du starta MD-övervakningsdemonen?" #. Type: boolean #. Description #: ../mdadm.templates:4001 msgid "" "The MD (RAID) monitor daemon sends email notifications in response to " "important MD events (such as a disk failure)." msgstr "" "MD-övervakningsdemonen (RAID) skickar e-postnotifieringar för viktiga MD-" "händelser (såsom ett diskfel)." #. Type: boolean #. Description #: ../mdadm.templates:4001 msgid "Enabling this option is recommen
Bug#971623: review and simplify the /devel/wnpp section
Package: www.debian.org User: www.debian@packages.debian.org Usertag: scripts Severity: normal Hi, we received the proposal to add listing of orphaned packages by popularity in this merge request: https://salsa.debian.org/webmaster-team/webwml/-/merge_requests/553 I find the idea valuable, but the approach (linking to wnpp.debian.net) is very different from what we already have in /devel/wnpp section (we build some lists ourselves with the wnpp.pl script [1], using the data gathered by the 1ftpfiles script from the cron repo [2]. [1] https://salsa.debian.org/webmaster-team/webwml/-/blob/master/english/devel/wnpp/wnpp.pl [2] https://salsa.debian.org/webmaster-team/cron/-/blob/master/parts/1ftpfiles Having a look at both the resulting listings that we provide in www.debian.org/devel/wnpp, and the ones provided in wnpp.debian.net, I think maybe we could review our old approach and remove most of the listings we were providing, and link to wnpp.debian.net instead. This of course would require changes in the wml files in /devel/wnpp section, the Makefiles, and the scripts in the cron repo. What do you think? Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#969553: urlcheck.py script tries to parse compressed GIMP image files
Package: www.debian.org User: www.debian@packages.debian.org Usertag: scripts Severity: normal Hi the scripts "urlcheck" generate this log in the /logos folder: Looking into http://www.debian.org/logos/openlogo.xcf.gz Error reading page: http://www.debian.org/logos/openlogo.xcf.gz Looking into http://www.debian.org/logos/officiallogo.xcf.gz Error reading page: http://www.debian.org/logos/officiallogo.xcf.gz Looking into http://www.debian.org/logos/officiallogo-nd.xcf.gz Error reading page: http://www.debian.org/logos/officiallogo-nd.xcf.gz I guess this means it tries to parse the xcf.gz files and probably we need to update the script to skip such files (compressed images). Anybody familiarised with Python, who can help? The code of the script is here: https://salsa.debian.org/webmaster-team/cron/-/tree/master/urlcheck (I guess the main script, urlcheck.py, is where maybe the fix should be made). The script is called by 3 cron jobs: 17 3 * * * cd /srv/www.debian.org/cron/urlcheck && ./run.urlcheck 36 12 * * * cd /srv/www.debian.org/cron/urlcheck && ./make.bad_link.pages 5 13 * * * cd /srv/www.debian.org/cron/urlcheck && ./cleanup.logs and the daily logs are here: https://www-master.debian.org/build-logs/urlcheck/ (check logos folder). Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#968862: what to do with https://www.debian.org/devel/people page (and script)
Package: www.debian.org User: www.debian@packages.debian.org Usertag: scripts Severity: normal X-Debbugs-CC: debian...@lists.debian.org,n...@debian.org Hi Debian web team, Debian QA team and FrontDesk, in https://www.debian.org/devel/people we have a huge list that was dynamically generated once a day, gathering the Packages and Sources files from a Debian Archive mirror and then processing them to retrieve the maintainers data (wether individuals or teams) together with the list of packages they maintain. In the web team sprint in 2019 we talked about this page and agreed that this kind of list makes not much sense in www.debian.org nowadays. As part of this work towards a simpler website, the scripts gathering the data and creating the list were removed from the "cron" repo: https://salsa.debian.org/webmaster-team/cron/-/commit/87d13915be4958ad868ffd98bf3758b0c37726ab But unfortunately, the new pages we wanted (a mention about the "people" in the home page, a "community" folder that probably would explain the different ways to participate in the Debian Project and link to nm.debian.org and contributors.debian.org for lists of people) are not done yet. So currently we show an old list (since we don't update anymore the file people.names present in www-master) :/ I was planning to edit people.wml to remove the list and just point to contributors.debian.org and nm.debian.org, but then I've read this note in the people.wml file: ## This page is redirected to by qa.d.o/developer.php?all=1 I have no idea if the page is linked in other places and/or the info is valuable for the QA team or others. My proposal is: 1.- To update our people.wml page removing the current list, and link to nm.debian.org for a list of Debian members and contributors.debian.org for other kind of contributions (explaining that probably there are people participating in Debian who is not listed in any of those pages). 2.- if any of the QA team or the maintainers of nm.d.o/contributors.d.o considers valuable this kind of list, I can help them to retrieve the corresponding cron scripts if they want to host them and produce the list in the corresponding [qa|nm|contributors].debian.org server. Then we would add a link there from our "people" page, too. 3.- If you think the info does not belong to your "areas" and know a better place, just tell. Please send your comments to the bug report and we'll act in the following days accordingly. Thanks! -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#924172: extra "/english" added to path of CSS and other files in /devel/website/stats
Hi all The issue with sitemaps was fixed with commit https://salsa.debian.org/webmaster-team/webwml/-/commit/83f7cae0178074e5e4f913168b4b42c7be90af13 as explained before :-) However, a similar issue has been discovered in the https://www.debian.org/devel/website/stats/ pages (all languages): the paths linking to CSS and other places (header and navbar) include an extra /english/ that breaks the link (and thus, for example, CSS is not loaded). I guess this is due to the way the files are called in the Makefile: https://salsa.debian.org/webmaster-team/webwml/blob/master/english/devel/website/stats/Makefile But I have no idea about how to solve it. The only thing that comes to mind is to make a substitution in the *.html files to remove the string "/english" (or "english/"), prior to copy the files to the www folder. Even in this case, I'm not sure I can provide a patch... Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#968486: FTBFS turkish folder in Debian 10 buster in www-master: locale or UTF-8 or wml or perl issue
Hi all, Thanks Holger for trying. I guess it must be another package. As per https://www.debian.org/devel/website/translating, it seems that this variable is only needed for correctly sort stuff in the corresponding language, so, for now (until we find the fix), I have removed the ""-D CUR_LOCALE=tr_TR.UTF-8" line in /turkish/.wmlrc so the build at least starts. This has been made in commit 2bf084fcb1cae633a6e5b8f044003bdea7e87c4a Note that in former message I quoted perl documentation that mentions that the Turkic locales are correctly handled in Perl 5.30, but we have 5.28.1 in buster. I have checked 5.28.1 documentation and the relevant paragraphs are: "Locale '%s' contains (at least) the following characters which have unexpected meanings: %s The Perl program will use the expected meanings (W locale) You are using the named UTF-8 locale. UTF-8 locales are expected to have very particular behavior, which most do. This message arises when perl found some departures from the expectations, and is notifying you that the expected behavior overrides these differences. In some cases the differences are caused by the locale definition being defective, but the most common causes of this warning are when there are ambiguities and conflicts in following the Standard, and the locale has chosen an approach that differs from Perl's. One of these is because that, contrary to the claims, Unicode is not completely locale insensitive. Turkish and some related languages have two types of "I" characters. One is dotted in both upper- and lowercase, and the other is dotless in both cases. Unicode allows a locale to use either the Turkish rules, or the rules used in all other instances, where there is only one type of "I" , which is dotless in the uppercase, and dotted in the lower. The perl core does not (yet) handle the Turkish case, and this message warns you of that. Instead, the Unicode::Casing module allows you to mostly implement the Turkish casing rules." Maybe the fix is installing libunicode-utf8-perl package? Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#968486: FTBFS turkish folder in Debian 10 buster in www-master: locale or UTF-8 or wml or perl issue
Package: www.debian.org User www.debian@packages.debian.org Usertag: scripts Severity: normal X-Debbugs-CC: debian-l10n-turk...@lists.debian.org , debian-i...@lists.debian.org Hi all In bug #924365, we discovered that the "tr_TR" locale in .wmlrc file was wrong and causing FTBFS issues in the turkish folder in buster machines, so we changed to "tr_TR.UTF-8" and our local tests were building fine. However, now that www-master migrated to Debian 10 buster, we're facing FTBFS issues anyway in the turkish folder: wml -q -D CUR_YEAR=2020 -o UNDEFuTR:index.tr.html@g+w index.wml ePerl:Error: Perl runtime error (interpreter rc=0) Contents of STDERR channel: - Locale 'tr_TR.UTF-8' contains (at least) the following characters which have unexpected meanings: I i The Perl program will use the expected meanings; codeset=UTF-8 -- ** WML:Break: Error in Pass 3 (rc=1). Died at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 403. Since I cannot reproduce the issue in my local machine, I guess there is some missing package that we should install in www-master. However, I cannot tell which one is it. The Perl documentation says: "Starting in Perl v5.30, Perl detects Turkic locales by their behaviour, and seamlessly handles both types; previously only the non-Turkic one was supported. The name of the locale is ignored, if your system has a tr_TR.UTF-8 locale and it doesn't behave like a Turkic locale, perl will treat it like a non-Turkic locale." I have done "dpkg -l | grep locale" both in my machine and www-master and compared the results and didn't find much difference. I have done "dpkg -l | grep urkish" and neither (but I have task-turkish, task-turkish-desktop and task-turkish-kde-desktop installed) I have done dpkg -l | grep UTF and here I think maybe it's the package we need: (www-master) dpkg -l | grep UTF ii libutf8proc2:amd642.3.0-1 amd64C library for processing UTF-8 Unicode data (shared library) ii uni2ascii 4.18-3 amd64UTF-8 to 7-bit ASCII and vice versa converter (local machine) dpkg -l | grep UTF ii libperlio-utf8-strict-perl0.007-2+b1 amd64fast and correct UTF-8 Perl IO module ii libunicode-utf8-perl 0.62-1 amd64encoding and decoding of UTF-8 encoding form ii libutf8-all-perl 0.024-1 all Perl pragma to turn on UTF-8 everywhere ii libutf8proc2:amd642.3.0-1 amd64C library for processing UTF-8 Unicode data (shared library) Can anybody reproduce the issue (just go to the "turkish" folder and do "make", and get the error), and see if installing some of these packages (libperlio-utf8-strict-perl or libunicode-utf8-perl or libutf8-all-perl) the turkish folder builds fine? Thanks! -- -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#952593: Debian RT - please install libgd-perl in wolkenstein.debian.org
Hello DSA Thanks for installing liblocale-codes-perl in wolkenstein. Sorry to bother again, we're still facing build errors in www-master with Debian 10 (error text below), it seems that the package libgd-perl is also needed. I'm attaching a patch for the debian.org-www-master.debian.org dependencies including the new dependency. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona wml -q -D CUR_YEAR=2020 -o UNDEFuEN:devel-manuals.en.html@g+w devel-manuals.wml ePerl:Error: Perl parsing error (interpreter rc=2) Contents of STDERR channel: - Can't locate GD.pm in @INC (you may need to install the GD module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl) at /tmp/wml.11796.tmp1 line 197. BEGIN failed--compilation aborted at /tmp/wml.11796.tmp1 line 197. -- From 3e2b75df84a1ff86118302000dbbef7faccaa177 Mon Sep 17 00:00:00 2001 From: Laura Arjona Reina Date: Fri, 14 Aug 2020 13:20:42 +0200 Subject: [PATCH] Install libgd-perl in www-master, needed to build /doc/devel-manuals in Debian 10 buster --- debian/control | 1 + 1 file changed, 1 insertion(+) diff --git a/debian/control b/debian/control index 15561ab..ec13686 100644 --- a/debian/control +++ b/debian/control @@ -281,6 +281,7 @@ Depends: debiandoc-sgml, latex-cjk-chinese, ldap-utils, libcgi-pm-perl, + libgd-perl, libemail-address-perl, libintl-perl, liblocale-codes-perl, -- 2.20.1 signature.asc Description: OpenPGP digital signature
Bug#924172: www.debian.org: differences under english/ between builds in stretch and buster
Hi all Sorry for the long delay to come back to this. I have tested the workaround proposed by Cyril: https://salsa.debian.org/webmaster-team/webwml/-/tree/pu/partial-workaround-924172 and arrived to the same conclusions: * It makes no difference (and thus no harm) when applied in stretch * In buster, it builds correctly the sitemaps, with no references to "../english" paths (I tested Spanish and English, and the Spanish translation seemed also to be complete). OTOH, now that wml 2.28.0 is packaged in testing (thanks Axel and Shlomi!), I have installed wml and slice from testing in my buster box, and tried to build, and found that sitemap.en.html cannot be built (See error below. But just for the curious, because I think our way to go is to integrate Cyril's workaround, and with the patch, the files build correctly with wml 2.28.0). So I think it's good to accept it and unblock this way the upgrade to buster of www-master. Later we can file bugs for the not-complete translations. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona --- Error when building sitemap.en.html in a buster machine, but with wml and slice 2.28.0 (from testing) -- Just for the record, because we'll use another workaround wml -q -D CUR_YEAR=2020 -o UNDEFuEN:sitemap.en.html@g+w -D CUR_LANG=English -D CUR_ISO_LANG=en -D CUR_LOCALE=en_US.UTF-8 -D CHARSET=utf-8 \ ../english/sitemap.wml ePerl:Error: Perl runtime error (interpreter rc=2) Contents of STDERR channel: - couldn't open ./../index.wml or /home/larjona/Documentos/debian/www/webwml/english/../index.wml: No such file or directory Died at /tmp/0uDhaUPMnJ/wml.tmp1 line 750. -- ** WML:Break: Error in Pass 3 (rc=1). Died at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 402. TheWML::Frontends::Wml::Runner::_run_pass(TheWML::Frontends::Wml::Runner=HASH(0x563974ead458), 3, SCALAR(0x56397544aaf0), REF(0x56397544aac0), REF(0x56397544aad8)) called at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 440 TheWML::Frontends::Wml::Runner::_passes_loop(TheWML::Frontends::Wml::Runner=HASH(0x563974ead458)) called at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 727 TheWML::Frontends::Wml::Runner::_output_and_cleanup(TheWML::Frontends::Wml::Runner=HASH(0x563974ead458)) called at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 932 TheWML::Frontends::Wml::Runner::run_with_ARGV(TheWML::Frontends::Wml::Runner=HASH(0x563974ead458), HASH(0x56397543aed0)) called at /usr/bin/wml line 47 make: *** [Makefile:56: sitemap.en.html] Error 2
Bug#924172: www.debian.org: differences under english/ between builds in stretch and buster
El 10/8/20 a las 22:47, Laura Arjona Reina escribió: > > So I think it's good to accept it and unblock this way the upgrade to > buster of www-master. Later we can file bugs for the not-complete > translations. > This has been done in MR #524: https://salsa.debian.org/webmaster-team/webwml/-/merge_requests/524 (main commit 83f7cae0178074e5e4f913168b4b42c7be90af13) Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#960835: Debian Jessie site lists only 4 archs as supported -- patch for stretch
Hi Holger El 21/7/20 a las 9:23, Holger Wansing escribió: > Hi, > > now that Stretch is under LTS (but there are no different point-release > version-numbers for lts-archs and non-lts-archs), I have applied the part > of the patch, needed to display both sets of supported archs (lts archs > and initially-releases archs) on the release page > (also already done for Jessie). > > > And: > To bring all this to an end, I will (if noone objects) apply the rest of the > patch as well (but commented-out), and do the same for Buster and Bullseye > as well. That way, the mechanism would be in place for all releases, to have > different point-release version-numbers during LTS period (as it is for > jessie). > Thank you very much! Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#963071: Debian RT - add redirects to some /international/ folders that we moved to lowercase
Dear DSA We have moved to lowercase some language folders under www.debian.org/international so theses languages are processed in the same way as the rest (in order to send mail to translators with the pending translations, see bug #963071 for more details). I'm attaching a patch to set up redirects in Apache to avoid broken links. Thanks! -- Laura Arjona Reina https://wiki.debian.org/LauraArjona >From c9638a6fc7323aecdd51bf5ad1720b8ed8f0c549 Mon Sep 17 00:00:00 2001 From: Laura Arjona Reina Date: Sun, 21 Jun 2020 14:34:36 +0200 Subject: [PATCH] add redirects for some /international/ folders that we moved to lowercase --- modules/roles/templates/apache-www.debian.org.erb | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/modules/roles/templates/apache-www.debian.org.erb b/modules/roles/templates/apache-www.debian.org.erb index 3d235ee9e..d1244d657 100644 --- a/modules/roles/templates/apache-www.debian.org.erb +++ b/modules/roles/templates/apache-www.debian.org.erb @@ -182,8 +182,8 @@ Redirect /doc/prospective-packages /devel/wnpp/ Redirect /devel/maintainer_contacts /intro/organization Redirect /devel/debian-installer/gtk-frontend https://wiki.debian.org/DebianInstaller/GUI - Redirect /zh/ /international/Chinese/ - Redirect /chinese/ /international/Chinese/ + Redirect /zh/ /international/chinese/ + Redirect /chinese/ /international/chinese/ Redirect /devel/help /devel/join/ Redirect /distrib/books /doc/books Redirect /distrib/floppyinst /distrib/netinst @@ -201,6 +201,9 @@ Redirect /misc/memberships /intro/organization#memberships Redirect /misc/merchandise /events/merchandise Redirect /intl /international + Redirect /international/Catalan /international/catalan + Redirect /international/Chinese /international/chinese + Redirect /international/German /international/german Redirect /ports/armel /ports/arm Redirect /ports/armhf /ports/arm Redirect /ports/arm64 /ports/arm -- 2.20.1
Bug#963071: daily errors in webwml/check_trans.pl (called by cron/scripts/check_trans.sh)
Package: www.debian.org User www.debian@packages.debian.org Usertag: scripts Severity: normal We are receiving daily errors about the check_trans.pl tool on top of the webwml folder, it seems Perl is not able to get the translator.db.pl files for each language. We have 2 types of error: 1.- L1024: require $db_file; fails, but the file is there. For example arabic: Can't locate arabic/international/arabic/translator.db.pl in @INC (@INC contains: /srv/www.debian.org/webwml/Perl /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at ./check_trans.pl line 1024. We didn't change the check_trans.pl recently, I guess maybe something changed in the Perl environment that we need to provide the full path to the file (and not only relative path) or load the file in other way, no idea. Any Perl expert around? 2.- L1024: require $db_file; fails because the file is in other folder, for example Chinese: File `chinese/international/chinese/translator.db.pl' doesn't exist! I need my DBs to send mails. Please read the comments in the script and try again (The translator.db.pl is in the chinese/international/Chinese/translator.db.pl path). This issue (translator.db.pl in a diferent path) happens for 3 languages only: ./catalan/international/Catalan/translator.db.pl ./chinese/international/Chinese/translator.db.pl ./german/international/German/translator.db.pl I guess we need to: A.- move the translator.db.pl file to the corresponding folder with lower case letters or B.- add logic to the check_trans.pl to try the folder with capital letter if the usual path fails I tend to the A proposal because it's the one that I can do, but if there is anybody who can provide B, that's more elegant I guess :-) Kind regards, Laura Arjona Reina https://www.debian.org/LauraArjona
Bug#959755: Bug #959755: Package pages for source/buster-backports gets 500 error
retitle 959755 Package pages for source/buster-backports gets 500 error thanks Hello I still can reproduce this error, and also today webmaster@ received a report about some more URLs failing. URL for existing packages in stable-backports report a HTTP 500 error at the time of writing (Thu, 18 Jun 2020 10:25:41 +0200). For instance: https://packages.debian.org/source/stable-backports/linux https://packages.debian.org/source/stable-backports/apt-cacher-ng do not work (HTTP 500) URL for non-existing packages do return a page (HTTP 200) For instance https://packages.debian.org/source/stable-backports/foobar I have checked them too, and I can reproduce the error, so it's not limited to openldap package. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#959474: Issues with Chinese language (all variants) when building some pages in buster
Hi El 7/6/20 a las 16:02, Axel Beckert escribió: > Just ot be sure: I should still provide a stable update for buster, > right? > I don't know if the type of bug qualifies for a stable update. For www.debian.org, we'll be using the -O1 workaround for building the Chinese pages, and that's about optimization, we don't lose any functionality, so I think we can wait for bullseye. Boyuan, please correct me if I am wrong... Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#924172: www.debian.org: differences under english/ between builds in stretch and buster
Hello all, Thanks Cyril for your work here. We're trying to fix all the issues so the migration of www-master to buster can be done as soon as possible. I'll comment on the issues you found: 1. Changes related to canonicalization(?) of the URL The files affected are: 1.1.- */News/news.*.rdf (all languages) All those files are built using /english/News/news.rdf.in which includes this line: it seems that the variable $(HOME) is interpreted differently by the make or wml commands in buster. I have played with the "-D HOME~." line in /english/.wmlrc but it does not solve the issue. The file is built (in english and all the other languages except Chinese) by lines 36-37 of the /english/News/Makefile: $(WML) $(shell egrep '^-D (CUR_|CHAR)' ../.wmlrc) \ $(ENGLISHDIR)/News/news.rdf.in If I change that to $(WML) $(shell egrep '^-D (CUR_|CHAR)' ../.wmlrc) news.rdf.in then the English file is built with correct URL to the CSS, but the other languages fail. I don't know how to solve this, except using an absolute reference to the CSS file in the /english/News/news.rdf.in instead of the $(HOME) variable. 1.2. */sitemap.*.html (all languages) I guess it's the same problem (that the $(HOME) variable is used and interpreted wrongly with the new make or wml), but this file and how it is built is more cryptic for me so I wouldn't know how to start. The sitemap would be completely broken until this issue is fixed, if we migrate www-master to buster :/ Help needed! 2. Changes in mail address representation I confirm this happens but it's indeed random changes in the addresses obfuscation, so I don't consider this an issue. 3. Changes in a log file Not important (and probably we shouldn't provide the card there, maybe in the debian-flyers repo?) 4. Changes in ordering of coordinators 5. Changes in ordering under wnpp 6. Changes in order under l10n 8. More ordering changes (architectures, DSAs) Thanks for reporting, and for the work towards reproducibility. I think these are not blockers for the migration to buster of www-master.debian.org Maybe we could open a specific bug about these "reproducibility issues" and see if somebody is willing/able to work on it? 7. Changes related to image width/height attributes This is indeed as Julien commented, a bug in wml which is fixed in buster. Thanks -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#959474: Issues with Chinese language (all variants) when building some pages in buster
Hi all As a workaround for the Debian website, until wml 2.12.2~ds1-3 or higher arrives to stable, I have added the option "-O1" to the options passed to wml for Chinese, in the /chinese/Make.lang file: +# Add "-O1" to wml to be passed to htmlstrip, to avoid malformed UTF-8 +# see bug #959474 +# This option needs to be kept in Chinese until wml 2.12.2~ds1-3 or higher +# arrives to Debian stable + +WMLOPTIONSZH = -O1 WMLOUTPUT = -o UNDEFuZH@uCNuCNHKuCNTW:$(*F).zh-cn.html.tmp@g+w \ -o UNDEFuZH@uHKuCNHKuHKTWuTWHK:$(*F).zh-hk.html.tmp@g+w \ @@ -54,7 +60,7 @@ WMLPROLOG = --prolog=$(FORMAT_ZH) # Remove initial blank line due "[ZH::]" in $(TEMPLDIR)/common_tags.wml, # an unfortunate but necessary workaround of a bug in slice < 1.3.9 WMLEPILOG = --epilog=$(STRIP_INITIAL_BLANK_LINE) -WML = wml $(WMLOPTIONS) $(WMLOUTPUT) $(WMLPROLOG) $(WMLEPILOG) +WML = wml $(WMLOPTIONS) $(WMLOPTIONSZH) $(WMLOUTPUT) $(WMLPROLOG) $(WMLEPILOG) I have compared the results of builds in stretch and buster both with and without the option, and there are no changes in stretch, and the UTF-8 issues are fixed in buster with the option (by the way, thanks Boyuan for the additional fixes you did to mitigate the error). So, I think that Bug#959474 can be closed, but I'll leave it open until we effectively migrate to Buster and see the results in www.debian.org "live" :-) Thanks everybody for your work! Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#960835: Debian Jessie site lists only 4 archs as supported
Hi Thanks Holger for caring about this issue. A related problem with jessie is that we have 8.11.0 images for all the arches, but 8.11.1 images only for the LTS arches. see https://cdimage.debian.org/cdimage/archive/8.11.0/ and https://cdimage.debian.org/cdimage/archive/8.11.1/ So right now many links of the page https://www.debian.org/releases/jessie/debian-installer/ provide errors. I've had a look at your proposal and I agree (thanks!). In addition to the changes you propose, I think we need to figure out how to show the info in the debian-installer page so every link works: the ones that should point to the (unsupported) 8.11.0 images, and the ones pointing to the 8.11.1 images. We probably need custom tags for jessie for its arches and release_info templates. I'm sorry I couldn't put more time on this, for now. Right now it's something that happens with jessie, but I guess in the future we'll have similar issues in newer releases for which LTS only covers part of the initial architectures. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#959474: Issues with Chinese language (all variants) when building some pages in buster
Package: www.debian.org Severity: normal User: www.debian@packages.debian.org Usertags: scripts X-Debbugs-CC: debian-l10n-chin...@lists.debian.org X-Debbugs-CC: debian-i...@lists.debian.org Hi all, TL;DR There are some issues with some Chinese pages when they are built in a buster machine. We need to fix those issues (at least the "Malformed UTF-8 character [...] at ../../bin/tocn.pl [...]" ones) so DSA can upgrade the www-master machine to buster. See the summary of the log at the bottom to know which files produce this error. I have no idea of how to fix the issues, so any help from the Chinese team or web team mates is greatly appreciated.. Additional issues may arise (e.g. I still didn't test the release-notes or doc-manual), any help testing is welcome too, please create bug reports for each different issue or update the existing ones. Thanks! LONG VERSION I've done a test build of the /english and /chinese subdirs in a buster machine, and I have noticed some warnings/errors related to the Chinese pages (some, not all of them). It would be desirable to upgrade www-master machine to buster as soon as possible, so any help with this (from website or Chinese team members) is very appreciated. Below you can find an extract of the build log, including only the the files for which I got some error or warning message. After the build, I have compared the problematic HTML files of a build in stretch and a build in buster with a diff tool, to see if there were significant changes in the html output due to these issues. Here are my results: * For the messages of the type ", [zh_TW]Invalid UTF8: " when building, I couldn't note any difference between the output of a stretch build and the output of a buster build. I would say this is not a blocker for the buster upgrade of www-master. * For the messages of the type "Malformed UTF-8 character [...] at ../../bin/tocn.pl [...]" I have seen important changes in the HTML diff, I think the output in the stretch build is totally broken (fortunately, there are not many files in that situation). I would say this is a blocker for the buster upgrade of www-master, but I would prefer somebody of the Chinese team to confirm (try to build those files in a buster machine, and review the output). Additional notes: * I have only tested the wml build, not the rest of the cron scripts that run on www-master. I will try to do it in the following days, but if you already know any that works well (e.g. release-notes, doc-manuals...) just tell so I can skip them. * When I build files in my machines, there is something wrong in my environment that I don't get the .po files integrated every time, so for example the Chinese pages I build show the menus and footnote in English. Therefore, if there is any issue with the encoding of the .po files themselves, I guess I cannot detect it until I fix my particular issue :/ * The local build that I make uses the SAMPLE_FILES that are needed in some folders; so additional issues may arise when we use the actual files that are generated at runtime in the often and lessoften cron jobs. That's all for now, I think. Thanks for your patience reading and for your help! Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona --- extract of the build log file /chinese Processing donations.wml: [zh_CN]Invalid UTF8: ïŒç¹å»âæ·»å å°èŽç©èœŠâïŒç¶åå®æå©äœè¿çšã , [zh_TW]Invalid UTF8: ïŒç¹å»âæ·»å å°èŽç©èœŠâïŒç¶åå®æå©äœè¿çšã , [zh_HK]Invalid UTF8: ïŒç¹å»âæ·»å å°èŽç©èœŠâïŒç¶åå®æå©äœè¿çšã . make[1]: Entering directory '/webwml/chinese/Bugs' Processing Reporting.wml: [zh_CN]Invalid UTF8: °äžæ¬¡ç€ºäŸäŒè¯çè¿çšã , [zh_TW]Invalid UTF8: °äžæ¬¡ç€ºäŸäŒè¯çè¿çšã , [zh_HK]Invalid UTF8: °äžæ¬¡ç€ºäŸäŒè¯çè¿çšã . make[2]: Entering directory '/webwml/chinese/News/2000' Processing 2815.wml: [zh_CN]Invalid UTF8: µ·å€æåçéŒååå©ïŒå æ¬ïŒ , [zh_TW]Invalid UTF8: µ·å€æåçéŒååå©ïŒå æ¬ïŒ , [zh_HK]Invalid UTF8: µ·å€æåçéŒååå©ïŒå æ¬ïŒ . make[2]: Entering directory '/webwml/chinese/News/2009' Processing 20090214.wml: [zh_CN]Invalid UTF8: Sun SPARC (sparc)ã , [zh_TW]Invalid UTF8: Sun SPARC (sparc)ã , [zh_HK]Invalid UTF8: Sun SPARC (sparc)ã . make[2]: Entering directory '/webwml/chinese/News/weekly' copying index.zh-cn.html to ../../../../www/News/weekly/./2002/48 Processing index.wml: [zh_CN]Malformed UTF-8 character (unexpected end of string) in substitution (s///) at ../../bin/tocn.pl line 13, <> line 146. Malformed UTF-8 character (unexpected end of string) in substitution (s///) at ../../bin/tocn.pl line 15, <> line 146. panic: do_trans_simple_utf8 line 362 at ../../bin/tocn.pl line 20, <> line 146. , [zh_TW]Invalid UTF8: å , [zh_HK]Invalid UTF8: å . copying index.zh-cn.html to ../../../../www/News/weekly/./2002/49 copying
Bug#818927: side not found
Thanks, Holger! El 12 de abril de 2020 14:45:25 CEST, Holger Wansing escribió: >Hi, > >Holger Wansing wrote: >> While diffing the results of the original and the changed 7doc script, I >> found >> that there were several more files suffering from this problem: >> >> network-services.es.html >> sect.administration-interfaces.es.html >> sect.aptosid.id.html >> sect.automatic-upgrades.es.html >> sect.common-procedures.es.html >> sect.dist-upgrade.de.html >> sect.office-suites.es.html >> sect.other-derivatives.es.html >> sect.regular-upgrades.es.html >> sect.rtc-services.es.html >> sect.searching-packages.es.html >> sect.user-group-databases.es.html >> unix-services.es.html > >After the need to fix another issue first, all the above now work correctly. > > >Holger > -- Laura Arjona Reina https://wiki.debian.org/LauraArjona Sent with K-9 mail
Bug#922553: Bug #922553: Link to latest launch point announcement on each launch's index page, in multiple languages.
Applied, thanks! Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#922553: Bug #922553: Link to latest launch point announcement on each launch's index page, in multiple languages.
Hi jukav
El 29/3/20 a las 21:33, jukav escribió:
> Hi there
> We continue to help correct the error.
> Patches are attached for the home pages that use these tags, in some of
> the languages.
> Thank you!
> Applied, thanks!
The commit for czech/releases/etch/index.wml included a typo, which I
have fixed in a later commit (see below).
Kind regards,
--
Laura Arjona Reina
https://wiki.debian.org/LauraArjona
commit a8a50aead06e356748f2436bd6691513b13c043b
Author: Laura Arjona Reina
Date: Sun Mar 29 21:46:17 2020 +0200
[Czech] Fix typo in tag (etchX -> etch)
diff --git a/czech/releases/etch/index.wml b/czech/releases/etch/index.wml
index 12aa6ffc104..07669f1ff59 100644
--- a/czech/releases/etch/index.wml
+++ b/czech/releases/etch/index.wml
@@ -6,7 +6,7 @@
Debian GNU/Linux byl vydán
-.
+.
Debian 4.0 byl původně vydán <:=spokendate('2007-04-08'):>.
Tato nová verze zahrnuje mnoho významných změn popsaných
vtiskové zprávě
Bug#922553: Bug #922553: Make link to the last release point announcement in the index page of each release, fix 2
Applied, thanks! I have added (empty) tags for bullseye and bookworm releases, so we remember to update them when we publish those releases :-) Now, I think the only remaining thing is to sync translations. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#922553: Bug #922553: Make link to the last release point announcement in the index page of each release
Hi jukav, Thanks for your contribution! I just applied the patch you provided. Now it would be needed to include the new tags in the corresponding english/releases/XXX/index.wml so the date actually links to the announcements. I know you're working on it, so thanks in advance, I'll review and apply the next patch as soon as I can :-) Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#954931: 10gen-material-unstable probably needs adaptation to new Perl libraries (buster/bullseye)
Package: debian-i18n X-Debbugs-CC: debian-l10n-de...@alioth-lists.debian.net X-Debbugs-CC: debian-i...@lists.debian.org Hi After upgrading tye.debian.org to buster, we're getting these warnings after the daily cron scripts: /srv/i18n.debian.org/etc/cron.d//10gen-material-unstable: Locale::Language will be removed from the Perl core distribution in the next major release. Please install the separate liblocale-codes-perl package. It is being used at /srv/i18n.debian.org//dl10n/git/dl10n-check, line 22. Locale::Codes will be removed from the Perl core distribution in the next major release. Please install the separate liblocale-codes-perl package. It is being used at /usr/share/perl/5.28/Locale/Language.pm, line 22. Locale::Country will be removed from the Perl core distribution in the next major release. Please install the separate liblocale-codes-perl package. It is being used at /srv/i18n.debian.org//dl10n/git/dl10n-check, line 23. Somebody probably needs to have a look at the code, make it use the new libraries, and then ask DSA to install the liblocale-codes-perl package. The code is here: https://salsa.debian.org/l10n-team/dl10n It's maybe an easy thing, but I'm afraid I cannot look at the code these days, my main machine is still in stretch and anything related to buster/bullseye is difficult for me these days. If you need somebody with permissions in tye to try/deploy something or somebody to send the ticket to DSA, I can do those. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#952826: [www.debian.org] partners: convert svg graphics into png to make tidy happy
Hi The issue is due to a bug in wml which is solved in the buster package, so when we upgrade www-master.debian.org to buster, it will be fixed and we can use svg images without validation errors. I'll try to review the possible blockers to the buster upgrade in the following days. Kind regards El 29 de febrero de 2020 23:33:51 CET, Holger Wansing escribió: >Package: www.debian.org > >As tidy constantly complains about > >*** /srv/www.debian.org/www/partners/2018/index.en.html >line 159 column 3 - Warning: attribute "width" has invalid value >"height=" >line 255 column 3 - Warning: attribute "width" has invalid value >"height=" >*** /srv/www.debian.org/www/partners/2019/index.en.html >line 75 column 3 - Warning: attribute "width" has invalid value "height=" >line 159 column 3 - Warning: attribute "width" has invalid value >"height=" >line 255 column 3 - Warning: attribute "width" has invalid value >"height=" >*** /srv/www.debian.org/www/partners/2020/index.en.html >line 75 column 3 - Warning: attribute "width" has invalid value "height=" >line 159 column 3 - Warning: attribute "width" has invalid value >"height=" >line 255 column 3 - Warning: attribute "width" has invalid value >"height=" >*** /srv/www.debian.org/www/partners/index.en.html >line 77 column 3 - Warning: attribute "width" has invalid value "height=" >line 161 column 3 - Warning: attribute "width" has invalid value >"height=" >line 257 column 3 - Warning: attribute "width" has invalid value >"height=" > >which is all about width/height information in svg graphics: > >what about converting the relevant images (google.svg and >stackpack-logo-reversed.svg) >into some other format, like png? > >Please excuse my ignorance, I have no detailed knowledge on vector graphics: >maybe there is a reason why we should use svg there. >However, png is widely used in the partners section... > >I have attached png variants of the relevant images. > > >Holger > -- Laura Arjona Reina https://wiki.debian.org/LauraArjona Sent with K-9 mail
Bug#952593: FTBFS in buster: liblocale-codes-perl package required for building /english/doc/devel-manuals
Package: www.debian.org Severity: normal User: www.debian@packages.debian.org Usertags: scripts Hi, I have tried to build /english/doc/devel-manuals in a buster machine and got this error: wml -q -D CUR_YEAR=2020 -o UNDEFuEN:devel-manuals.en.html@g+w devel-manuals.wml ePerl:Error: Perl runtime error (interpreter rc=0) Contents of STDERR channel: - Locale::Codes will be removed from the Perl core distribution in the next major release. Please install the separate liblocale-codes-perl package. It is being used at /usr/share/perl/5.28/Locale/Language.pm, line 22. -- ** WML:Break: Error in Pass 3 (rc=1). Died at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 403. TheWML::Frontends::Wml::Runner::_run_pass(TheWML::Frontends::Wml::Runner=HASH(0x5648034e0458), 3, SCALAR(0x564803a629a0), SCALAR(0x564803a62970), SCALAR(0x564803a62988)) called at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 441 TheWML::Frontends::Wml::Runner::_passes_loop(TheWML::Frontends::Wml::Runner=HASH(0x5648034e0458)) called at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 726 TheWML::Frontends::Wml::Runner::_output_and_cleanup(TheWML::Frontends::Wml::Runner=HASH(0x5648034e0458)) called at /usr/share/wml/TheWML/Frontends/Wml/Runner.pm line 930 TheWML::Frontends::Wml::Runner::run_with_ARGV(TheWML::Frontends::Wml::Runner=HASH(0x5648034e0458), HASH(0x5648036c0c50)) called at /usr/bin/wml line 47 make: *** [../../Makefile.common:123: devel-manuals.en.html] Error 2 Installing liblocale-codes-perl solved the issue for me. I have checked https://salsa.debian.org/dsa-team/mirror/debian.org/blob/master/debian/control and I cannot see such package in the recipe for www-master. I have checked the www-master machine (wolkenstein.debian.org) and it's not installed there (but that machine is running Debian 9 stretch currently). I'm not sure if the package will be installed automatically with the upgrade to buster, or in a clean install as a dependency of other Perl package that is in the recipe in debian/control. Just opening this bug to not forget to check after the upgrade if it's needed to install manually and thus update the debian/control recipe. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#948969: malformed URI in the wnpp pages produces "Tidy validation failed" messages
Hi El 23 de febrero de 2020 10:30:22 CET, Holger Wansing escribió: >Hi, > >Holger Wansing wrote: >> Laura Arjona Reina wrote: >> > I'm not sure how to solve this. Things that come to mind: >> > 1.- asking the maintainer to file a RFH bug per package. >> > 2.- somebody to improve wnpp.pl script to take care about these things >> > (sorry, I >> > have no spoons/skills for that). >> > 3.- Any other idea? >> >> Exclude devel/wnpp from tidy processing for now? > >Any objection? > Not from my part. I was trying to find the time to look at how to add such exclusion but couldn't, so if it's clear for you, please go ahead. Just mention this bug report as a comment near the exclusion code for the future. Thanks! -- Laura Arjona Reina https://wiki.debian.org/LauraArjona Sent with K-9 mail
Bug#949736: enigmail: uninstallable in stretch (since thunderbird was upgraded to version 68 due to security upgrade)
Package: enigmail Version: 2:2.0.8-5~deb9u1 Justification: renders package unusable Severity: grave Tags: stretch Dear Maintainer, Current version of Thunderbird in Debian stretch is 68, which is incompatible with the enigmail currently packaged in stretch. The issue was fixed in Debian buster and Debian jessie by upgrading the version of enigmail, but this has not been done in stretch yet. Then, * for new installs, enigmail cannot be installed, * the computers that were already running stretch need to choose between upgrading Thunderbird to get the security updates (and then enigmail will be uninstalled), or keeping the old version of Thunderbird with a working enigmail (but having unpatched security vulnerabilities). There will be a release point for stretch soon and it would be great if it carries a new version of enigmail solving this issue for stretch. Thanks! -- Laura Arjona https://wiki.debian.org/LauraArjona -- System Information: Debian Release: 9.11 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-11-amd64 (SMP w/1 CPU core) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages enigmail depends on: ii gnupg 2.1.18-8~deb9u4 ii gnupg-agent2.1.18-8~deb9u4 ii icedove1:68.4.1-1~deb9u1 ii thunderbird [icedove] 1:68.4.1-1~deb9u1 Versions of packages enigmail recommends: ii pinentry-gnome3 [pinentry-x11] 1.0.0-2 enigmail suggests no packages. -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#948969: malformed URI in the wnpp pages produces "Tidy validation failed" messages
Package: www.debian.org User: www.debian@packages.debian.org Usertags: design Severity: normal Dear all When the website builds */devel/wnpp folder, there is a RFH bug that generates a malformed URI, and thus producing several "Tidy validation failed" messages each day, of the type: *** /srv/www.debian.org/www/devel/wnpp/help_requested.sv.html line 182 column 136 - Warning: escaping malformed URI reference The HTML code generated by the english/devel/wnpp/wnpp.pl script is like this one: --- https://bugs.debian.org/945468;>pgq, pgqd, pgq-node, python-pgq, python-skytools, londiste: Queuing for PostgreSQL, (https://packages.debian.org/src:pgq, pgqd, pgq-node, python-pgq, python-skytools, londiste">package info), requested 50 days ago. --- Such info is extracted from the RFH bug report #945468, with subject: RFH: pgq, pgqd, pgq-node, python-pgq, python-skytools, londiste -- Queuing for PostgreSQL I guess the issue is that the 'name' of the package extracted from the bug contains blanks and semicolons. I'm not sure how to solve this. Things that come to mind: 1.- asking the maintainer to file a RFH bug per package. 2.- somebody to improve wnpp.pl script to take care about these things (sorry, I have no spoons/skills for that). 3.- Any other idea? For now, I'm filing this bug report so the issue is registered and we can point translators/web team members to this info if they ask about the Tidy validation failed messages. Kind regards, -- Laura Arjona https://wiki.debian.org/LauraArjona
Bug#930846: New development of how to build the installation-guide for the website [ Re: Bug#930846: partman-auto-lvm: debconf show guided_size during auto install ]
Hello El 10/1/20 a las 20:55, Holger Wansing escribió: > Hi Laura, > > Laura Arjona Reina wrote: >> Hi >> >> El 9/1/20 a las 20:49, Holger Wansing escribió: >>> >>> To make a new build happen, manual intervention is >>> needed now ( because there is no new source package >>> version available for installation-guide since the last build, no new build >>> is trigered). >>> One need to go to >>> /srv/www.debian.org/cron/log/ig-stable-built.txt >>> and change that file (for example just change into an >>> empty file). >>> This is documented in the 1installation-guide script in >>> lessoften (cron git-repo). >>> That will trigger a new build at the next day. >> >> I've just done this (copied /srv/www.debian.org/cron/log/ig-stable-built.txt >> to >> /srv/www.debian.org/cron/log/ig-stable-built.txt.old and then changed >> ig-stable-built.txt to be an empty file). > > Hrr, this did not work. Sorry > > The variant with the empty file was my first idea, but that did not work. > So I changed that, now the file has to be removed. > > May I bother you again, to remove the file instead? > (Also, there is no need to keep the old file. You can remove it too.) > I have just updated the documentation in the 1installation-guide lessoften > script accordingly. > No problem. I have removed the file, unfortunately I couldn't do it before today's lessoften script run, so we need to wait until tomorrow to see if that worked. Cheers -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#930846: New development of how to build the installation-guide for the website [ Re: Bug#930846: partman-auto-lvm: debconf show guided_size during auto install ]
Hi El 9/1/20 a las 20:49, Holger Wansing escribió: > > To make a new build happen, manual intervention is > needed now ( because there is no new source package > version available for installation-guide since the last build, no new build > is trigered). > One need to go to > /srv/www.debian.org/cron/log/ig-stable-built.txt > and change that file (for example just change into an > empty file). > This is documented in the 1installation-guide script in > lessoften (cron git-repo). > That will trigger a new build at the next day. I've just done this (copied /srv/www.debian.org/cron/log/ig-stable-built.txt to /srv/www.debian.org/cron/log/ig-stable-built.txt.old and then changed ig-stable-built.txt to be an empty file). Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#930846: New development of how to build the installation-guide for the website [ Re: Bug#930846: partman-auto-lvm: debconf show guided_size during auto install ]
Hello El 7/1/20 a las 19:56, Adam D. Barratt escribió: > On Sun, 2020-01-05 at 17:46 +0100, Holger Wansing wrote: >> Hi, >> >> Holger Wansing wrote: > [...] >>> We could ask DSA to install 'fonts-nanum' and 'fonts-nanum-coding' >>> at wolkenstein, >>> to get that build successful again. >>> Would that be an option? >> >> Patch (from git format-patch) again DSA's debian.org repo is >> attached. > > I'm happy to do that, but I'd prefer an ACK from a member of the > webmaster group for completeness - Laura? > Sorry for the delay. I have reviewed this thread and the proposed solution looks good to me. So, please count my ACK to apply the patch adding fonts-nanum and fonts-nanum-coding. Thanks for the work! Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#930846: New development of how to build the installation-guide for the website [ Re: Bug#930846: partman-auto-lvm: debconf show guided_size during auto install ]
Hi The cron job will do the 'git pull' on wolkenstein the next time it runs. Kind regards El 1 de enero de 2020 14:45:21 CET, Holger Wansing escribió: >Hi, > >Samuel Thibault wrote: >> Samuel Thibault, le dim. 29 déc. 2019 22:15:59 +0100, a ecrit: >> > Holger Wansing, le dim. 29 déc. 2019 21:59:02 +0100, a ecrit: >> > > do you it would be possible for you to do another upload for the >> > > installation-guide some day? >> > >> > Ah, sure, I'm on it, then. >> >> Done! > >Thanks for the quick upload! > >However, I noticed that this does not fix the problem in #930846. >And while looking at the details, I came (again) to the longstanding problem >with the built of installation-guide for the website. > >Therefore, I have changed the 1installation-guide script in cron's >lessoften part (see >https://salsa.debian.org/webmaster-team/cron/commit/eb181b214009878967197a673a3488821d1c2258 > ) > >It changes the way of building the installation-guide: >instead of hardcoding release codenames and always pulling the latest package >version from the archive, it now parses the release codenames from the webwml >repo, and package version is determined via rmadison. > > >@Laura: could you see, if there is something needed on wolkenstein, to make >this >going live? (I assume a simply "git pull"?) > > >Thanks >Holger > > -- Laura Arjona Reina https://wiki.debian.org/LauraArjona Sent with K-9 mail
Bug#947357: Bug #947357: votebar template fails at parsing some translated files
user www.debian@packages.debian.org usertags 947357 scripts retitle 947357 votebar template fails at parsing some translated files thanks I have noticed that the files not added in the Spanish index were the ones with the translation-check header in the first line. I have moved the translation-check header line below, so the first line is the pagetitle and the second line the status, and then the file is parsed correctly by the votebar template and thus, added to the index. So, I see 2 ways of solving the issue: * Fixing the Perl code in /english/template/debian/votebar.wml so it parses the title and status line wherever they are * Finding a list of the translated files not having the pagetitle and status lines as the first two lines in the file, and fixing them as I did with the Spanish ones, and adding a note to translators in future voting files so they move the translation-check header below (note that copypage.pl places this line at the top of the file). Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#947357: Some translations of www.d.o/vote/index not updated
I have checked all the translations and the ones with issues are: French, Spanish, Japanese, Portuguese The rest are ok. Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona Sent with K-9 mail
Bug#947357: www.d.o/vote/index.en reflects voting open but translations not
Package: www.debian.org Severity: normal The www.debian.org/vote/index page includes a navigation bar listing all the elections, ordered by status. The current election is in status "Voting open" and the English version reflects that, but the translations not. I've checked the Spanish translations and the last election reflected is the DPL elections for 2018. In the French translation it reflects up to 2008. Those pages are built recently without errors, though, so there must be something wrong or overseen in the Makefiles or other auxiliary files. I open this bug so it's not forgotten and for the case somebody can have a look. I think I won't be able to act on this until some weeks later. Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona Sent with K-9 mail
Bug#944301: Bug #944301: WIP: [new-homepage] add icons from font-fork-awesome (except security which is from material.io)
Hi all I've committed a change in the English version of the new homepage, changing the icons to svg files taken from font-fork-awesome and material.io. See the commit below, and you can see the result in https://debian-newhomepage.larjona.net/index.en.html Some comments: 0.- all the icons used are from fork-awesome set of icons (CC-By 3.0/OFL-1.1/Expat), except "security" which is taken from material design icons from Google ( Apache License Version 2.0. ) https://salsa.debian.org/fonts-team/fonts-fork-awesome https://material.io/design/iconography/ https://github.com/google/material-design-icons/ 1.- fonts-fork-awesome is packaged in Debian and I have installed locally but I don't know how to make it work. When I install the package in my local computer, the corresponding CSS is installed in: /usr/share/fonts-fork-awesome/css/fork-awesome.css but I don't know how to reference it from the webwml tree. I tried to copy the css file to /webwml/english and update /english/template/basic.wml to reference it, but I don't see the icons, just a square with the Unicode code. Upstream documentation says to put the whole fork-awesome folder in the web tree, but I don't know if, having the Debian package around, there is a better way. So, for now, what I have done is to copy the SVG files (from the salsa fonts-fork-awesome repo, or the material.io in the /english/Pics folder), and add them as usual images to the index.wml file. This is the reason why I didn't sync the translations: if we find out how to use the CSS and the notation, I think that would be the best. 2.- When I copied the svg files from the source repos, I found out that the image was cropped because in some icons, it was bigger the image than the document size. So I edited all the svg files with Inkscape (in Debian buster) and set a paper size of 540 px width per 406,3 px height, and resized all the images to have 400,000 mm height (their proportional width), and aligned it centering it vertically and horizontally. 3.- I didn't change anything in the CSS so maybe an adjustement of columns/divs height/width is needed. 4.- I'm not very confident about using the "trophy" icon for "why Debian", nor the "shield" icon for "security". On one side, I would like to use all the icons from Fork-Awesome package, but I couldn't find anything suitable for "why debian" there, only the trophy, and for "security" (only a wrench, but even less confident). On the other side, in material.io I like the shield that is used for security now, and the "loyalty tag" for "why Debian": https://material.io/resources/icons/?icon=loyalty=baseline 5.- there are two packages for material icons in Debian, but I couldn't find the svg files in their salsa repos. I installed and I can add icons as "special characters" in LibreOffice, for example, but I don't know how it would be to make them work from the web. https://salsa.debian.org/openstack-team/third-party/fonts-materialdesignicons-webfont https://salsa.debian.org/hmc-guest/fonts-material-design-icons-iconfont/ In addition to this, I could find the shield icon there, but not the "loyalty" icon (I guess it's from a new version upstream and thus, not packaged yet). This is what I've could done for now. Opinions and help welcome. Kind regards Mensaje reenviado Asunto: [Git][webmaster-team/webwml][new-homepage] add icons from font-fork-awesome (except security which is from material.io) - WIP Bug #944301 Fecha: Thu, 12 Dec 2019 12:51:11 + De: Laura Arjona Reina Responder a:nore...@salsa.debian.org Para: dispatch+www.debian.org_...@tracker.debian.org GitLab Laura Arjona Reina pushed to branch new-homepage at Debian Webmaster Team / webwml <https://salsa.debian.org/webmaster-team/webwml> Commits: * *41f124fc <https://salsa.debian.org/webmaster-team/webwml/commit/41f124fc72ae111dcd33b98955393a284b94dcc9>* by Laura Arjona Reina /at 2019-12-12T12:36:04Z/ add icons from font-fork-awesome (except security which is from material.io) - WIP Bug #944301 8 changed files: * + english/Pics/heartbeat.svg <#2019f920a78d4f74e335db2a163a0a1366b08163> * + english/Pics/life-ring.svg <#3af0908fe718ff70cc0c45fbadaa93871fbf2a45> * + english/Pics/list.svg <#816dc4a7f6409066cfd85c15b2a06f4eb2b4ce9b> * + english/Pics/security.svg <#4a8d5b4627f2ff7e7a797c0e71cf78bbba486796> * + english/Pics/trophy.svg <#bc4bc735b2c032944b5efd4632cb8d8b6eec9d7c> * + english/Pics/user-plus.svg <#ea1d23980f0ee11b2ee0a1169612b7cab20947fb> * + english/Pics/users.svg <#c2b355beceddb33571e707fdcc589b708700d632> * english/index.wml <#dd196063e7cb2523baa15610bbb33e61f8099ad1>
Bug#896678: Bug #896678: l10n-rrd cron jobs fail with "llegal attempt to update using time X when last update time is X (minimum one second step)"
Hi, I've been doing some tests trying to fix other issue in the scripts, and this is what I found out about this bug: * The error is caused when "rrdtool update" is called with a date value that is not different than the one used when we called "rrdtool create" * The specific code that causes the error is: https://salsa.debian.org/l10n-team/dl10n/blob/master/dl10n-rrd/manpages-rrd.pl Line 100-102: use POSIX qw(strftime); $date = strftime "%s", localtime; $date = (int($date / $step)+1)*$step https://salsa.debian.org/l10n-team/dl10n/blob/master/dl10n-rrd/dl10n-rrd Line 244-246 use POSIX qw(strftime); $date = strftime "%s", localtime; $date = (int($date / $step)+1)*$step However, I'm not seeing that error for some time. I'll keep an eye on the reports to see if it happens again. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#944345: Migration to buster + python3 of micronews: feedgenerator, feedparser
Package: press Severity: normal X-Debbugs-CC: debian-public...@lists.debian.org Dear all dillon.debian.org, the Debian machine that provides bits.debian.org and micronews.debian.org (among other services) has been migrated to Debian 10 buster. Now, when trying to build micronews (make mpublish), I get an error: File "./create_extra_feeds.py", line 10, in from feedgenerator import Atom1Feed ImportError: No module named feedgenerator I see that python3-feedgenerator is installed, but python-feedgenerator is not. In my local machine with buster I have both packages installed and I can build micronews; I have checked that if I remove python-feedgenerator I can reproduce the issue. So one temporary solution to this is to ask python-feedgenerator to be installed in dillon. OTOH, we should try to migrate our services to python3 (see mail about this in [1]). [1] https://lists.debian.org/debian-services-admin/2019/10/msg0.html I think that python2 is only used in the create_extra_feeds.py file in micronews, and that file uses both feedgenerator (only python3 version installed in dillon, currently) and feedparse (only python2 version installed in dillon, currently). So other solution could be to migrate the script to python3, and then ask to install python3-feedparser in dillon. Once this is done, we would not need python-feedgenerator anymore. Do you think the migration is easy, or should I ask for the temporary solution for now? Note: I see that python-feedparser is installed because it's listed as dependency for bits.debian.org service: https://salsa.debian.org/dsa-team/mirror/debian.org/blob/master/debian/control#L1070 I didn't find a micronews entry in that file. We probably need to review also bits.debian.org python2/python3 usage, and update the control file accordingly (for both services). Kind regards, -- Laura Arjona https://wiki.debian.org/LauraArjona
Bug#944301: New homepage: use free (libre) icons
Package: www.debian.org User: www.debian@packages.debian.org Usertag: design Severity: normal X-Debbugs-CC: design-de...@alioth-lists.debian.net Hi all For the new homepage (a preview is visible at https://debian-newhomepage.larjona.net/ ), we have added some icons to the main links: * People * Our Philosophy * Get Involved, Contribute * Why Debian * User Support * Security Updates * More The current icons have been added in the /logos folder in these commits: https://salsa.debian.org/webmaster-team/webwml/commit/1884d59866f64f362925424fe848e1bb38d80e27 https://salsa.debian.org/webmaster-team/webwml/commit/b650c48fe04a19d5942b74c853d3833eb3a6cb66 https://salsa.debian.org/webmaster-team/webwml/commit/0a2b0a22c65d29d138591b0734d7bb86074d82a1 AFAIK the images themselves have been taken from https://www.flaticon.com/free-icon/security_102649 Several concerns have been raised about this (about the license and about the "ying/yang" icon, that can be perceived as controversial), so I'm proposing to change them and use other icons that are distributed under a free license, and trying to avoid controversial images. My proposal, for now, is to use icons from the "Fork Awesome" [1] or "Material" [2] fonts. Both have free/open source license and are packaged in Debian [3] [4]. [1] https://forkaweso.me/ [2] https://material.io/resources/icons/ [3] https://packages.debian.org/search?keywords=fonts-materialdesignicons-webfont [4] https://packages.debian.org/search?keywords=fonts-fork-awesome However, I don't know if the Debian packages include the icons we particularly want. I've done some proposals for new icons in: https://deb.li/ideasnewweb if you can comment or help us, we can figure out the ones we all like best and then see if we can use the Debian package or download the individual images from the newer upstream repo. I'm not sure about how to actually include and show the icons (fonts) in the website either, but I guess other people know, and if not, I would have a look at the documentation. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Bug#890447: Reorganise /News/index page, and add info about other news channels (bits, micronews...)
Hi all
As Paul Wise had suggested, I removed the mention of the external social
network.
I have committed the change below to the repo, and I think this bug can be
closed.
Thanks all
--
Laura Arjona Reina
https://wiki.debian.org/LauraArjona
Commits:
77025fd1 by Laura Arjona Reina at 2019-11-04T13:44:32Z
Reorder the paragraph of the news section. Add mention to the Debian blog and
micronews. Closes: #890447
- - - - -
1 changed file:
- english/News/index.wml
Changes:
=
english/News/index.wml
=
@@ -14,18 +14,17 @@ archives for our https://lists.debian.org/debian-announce/;>
debian-announce and
https://lists.debian.org/debian-news/;>
debian-news mailing lists.
-
-The press team of the Debian project can best be reached via mail
-to mailto:pr...@debian.org;>pr...@debian.org. Requests
-for interviews will be routed to the proper person within the Debian
-project. Please note that due to language barriers and timezone
-differences using mail is preferred over phone calls.
-
+
Those seeking information about current events and development
progress in the Debian community may be interested in the Debian Project News.
+href="project/">Debian Project News,
+the official Debian blog https://bits.debian.org;>Bits from
Debian,
+or the https://micronews.debian.org;>Debian micronews.
+
# don't wonder if there's no "project" folder; in fact it's just a symlink wo
the weekly-folder
+We're also tracking Debian's press coverage.
+
Debian, the distribution and the web site, has won awards, you can
find out which ones on the awards page.
@@ -35,7 +34,11 @@ find out which ones on the awards
page.
-We're also tracking Debian's press coverage.
+The press team of the Debian project can best be reached via mail
+to mailto:pr...@debian.org;>pr...@debian.org. Requests
+for interviews will be routed to the proper person within the Debian
+project. Please note that due to language barriers and timezone
+differences using mail is preferred over phone calls.
{#rss#:
https://salsa.debian.org/webmaster-team/webwml/commit/77025fd10675dec538e8d4d76d7a3320d2009e55
Bug#943470: webext-ublock-origin: Version in stable not working after [DSA 4549-1] firefox-esr security update
Package: webext-ublock-origin Version: 1.18.4+dfsg-2 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? After updating Firefox in Debian stable ([DSA 4549-1] firefox-esr security update), I can use Firefox but the ublock origin extension disappeared. * What exactly did you do (or not do) that was effective (or ineffective)? With a new profile, I still cannot see the extension. I have tried to remove and reinstall the package (from stable, version 1.18.4+dfsg-2) but it didn't solve the issue. I have tried to remove the folder storage/default/moz-extension+++whatever as suggested in 931640, with no luck. I have installed the version in testing (1.22.2+dfsg-1), and the problem was solved for new firefox profiles (although it appears disabled). Then, I have removed the folder "browser-extension-data" of my old profile, and then ublock origin also appeared in my old profile (and enabled). I have then tried to remove the testing version (1.22.2+dfsg-1) and reinstall the stable version (1.18.4+dfsg-2) but the extension disappeared again. Thanks -- Laura Arjona https://wiki.debian.org/LauraArjona -- System Information: Debian Release: 10.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled webext-ublock-origin depends on no packages. Versions of packages webext-ublock-origin recommends: ii chromium 76.0.3809.100-1~deb10u1 ii firefox-esr 68.2.0esr-1~deb10u1 Versions of packages webext-ublock-origin suggests: pn ublock-origin-doc -- no debconf information
Bug#932811: example page without "To report a problem with the web site..." footer
Hi
This is what I have figured out:
The footer template prints or not the fineprint "To report a problem with the
website..." depending on a variable NOCOMMENTS. If it's set to "", the fineprint
is shown:
https://salsa.debian.org/webmaster-team/webwml/blob/master/english/template/debian/footer.wml#L159
to L162
The value of the variable is set in other templates, or individual wml files. I
have searched for "NOCOMMENTS" in the english subfolder on the website and tried
to figure out the reasoning behind hiding the "fineprint" in those pages.
Looking at the list of pages:
template/debian/cdimage.wml:99:#use wml::debian::basic LINK="#8c4939"
VLINK="#45241c" ALINK="#ff2600" NOCOMMENTS=true
template/debian/projectnews/header.wml:7:#use wml::debian::template
title=" - <:=('$(PUBDATE)'):>$(PAGENAME)"
NOHOMELINK="yes" BARETITLE="yes" NOCOMMENTS="yes" SUMMARY="$(SUMMARY)"
template/debian/weeklynews/header.wml:5:#use wml::debian::template
title=" - <:=('$(PUBDATE)'):>$(PAGENAME)"
NOHOMELINK="yes" BARETITLE="yes" NOCOMMENTS="yes" SUMMARY="$(SUMMARY)"
contact.wml:1:#use wml::debian::template title="Getting in Contact with Us"
NOCOMMENTS="yes"
template/debian/consultant.wml:12:#use wml::debian::basic SUMMARY="$(SUMMARY)"
title="" NOCOMMENTS="yes" NOCOPYRIGHT="yes"
consultants/index.wml:1:#use wml::debian::template title="Consultants"
NOCOMMENTS="yes" GENTIME="yes"
legal/privacy.wml:1:#use wml::debian::template title="Privacy Policy"
NOCOMMENTS="yes"
I guess the general fineprint has been removed in the pages using a template
that provides another "contact" info, to avoid people contacting debian-www@
mailing list with CD/DVD issues, or publicity topics, etc.
We could solve this bug, then, removing the NOCOMMENTS="yes" and the
NOCOMMENTS=true in the wml files (and template files) where they are present.
I'm not sure about other people's opinion about showing the fineprint in *every
page*, so I'm attaching a patch for others to review and comment.
If there are no objections, I would apply the patch in one week or so.
Kind regards,
--
Laura Arjona Reina
https://wiki.debian.org/LauraArjona
>From 03a374ee0a28128f6df8b02c64b975353a55f4ef Mon Sep 17 00:00:00 2001
From: Laura Arjona Reina
Date: Wed, 16 Oct 2019 14:41:04 +0200
Subject: [PATCH] remove NOCOMMENTS="yes", so the fineprint "To report a
problem with the website..." is shown in every page
---
english/consultants/index.wml | 2 +-
english/contact.wml| 2 +-
english/legal/privacy.wml | 2 +-
english/template/debian/cdimage.wml| 2 +-
english/template/debian/consultant.wml | 2 +-
english/template/debian/projectnews/header.wml | 2 +-
english/template/debian/weeklynews/header.wml | 2 +-
7 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/english/consultants/index.wml b/english/consultants/index.wml
index 74a363803a5..b5d9ed0c383 100644
--- a/english/consultants/index.wml
+++ b/english/consultants/index.wml
@@ -1,4 +1,4 @@
-#use wml::debian::template title="Consultants" NOCOMMENTS="yes" GENTIME="yes"
+#use wml::debian::template title="Consultants" GENTIME="yes"
Debian is free software and offers free help through
mailing lists. Some people either don't
diff --git a/english/contact.wml b/english/contact.wml
index 5bf07b283e9..a420323faa1 100644
--- a/english/contact.wml
+++ b/english/contact.wml
@@ -1,4 +1,4 @@
-#use wml::debian::template title="Getting in Contact with Us" NOCOMMENTS="yes"
+#use wml::debian::template title="Getting in Contact with Us"
Debian is a large organization and there are a lot of ways to contact it.
This page will summarize the often requested means of contacting; it is by
diff --git a/english/legal/privacy.wml b/english/legal/privacy.wml
index 68cff042a11..bf300efad0e 100644
--- a/english/legal/privacy.wml
+++ b/english/legal/privacy.wml
@@ -1,4 +1,4 @@
-#use wml::debian::template title="Privacy Policy" NOCOMMENTS="yes"
+#use wml::debian::template title="Privacy Policy"
## Translators may want to add a note stating that the translation
## is only informative and has no legal value, and people
diff --git a/english/template/debian/cdimage.wml b/english/template/debian/cdimage.wml
index eebfecaaf0a..36cf15e213f 100644
--- a/english/template/debian/cdimage.wml
+++ b/english/template/debian/cdimage.wml
@@ -96,7 +96,7 @@
# for now, use the English pictures
en
-#use wml::debian::basic LINK="#8c4939" VLINK="#45241c" ALINK="#ff2600" NOCOMMENTS=true
Bug#924888: Debian RT - Add redirections for www.debian.org/misc/ pages, and group all of them
Hello DSA We're finishing the process of removing the /misc folder in www.debian.org. Attached you can find a patch for dsa-puppet adding a redirection to avoid broken links and to guide people to the new place of each content. More details about this in bug #924888 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924888 Thanks -- Laura Arjona Reina https://wiki.debian.org/LauraArjona >From d57d5f39f82f5d0d241d4059598c9322516bf567 Mon Sep 17 00:00:00 2001 From: Laura Arjona Reina Date: Thu, 18 Jul 2019 13:10:43 +0200 Subject: [PATCH] Add redirects for all the /misc section, and group all the redirects related to /misc --- modules/roles/templates/apache-www.debian.org.erb | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/modules/roles/templates/apache-www.debian.org.erb b/modules/roles/templates/apache-www.debian.org.erb index e0fb2c65..f97aab76 100644 --- a/modules/roles/templates/apache-www.debian.org.erb +++ b/modules/roles/templates/apache-www.debian.org.erb @@ -144,8 +144,6 @@ RedirectPermanent /SPI https://www.spi-inc.org # RedirectPermanent /OpenHardware http://www.openhardware.org RedirectPermanent /OpenSource https://opensource.org - RedirectPermanent /misc/bsd.license https://opensource.org/licenses/BSD-3-Clause - RedirectPermanent /Bugs/db/ix/pseudopackages.html /Bugs/pseudo-packages RewriteEngine on RewriteRule ^/Bugs/db/pa/l([^/]+).html$ https://bugs.debian.org/$1 @@ -178,6 +176,11 @@ RedirectPermanent /ports/laptops /misc/laptops/ RedirectPermanent /misc/README.mirrors /mirror/list RedirectPermanent /misc/README.non-US /mirror/list.non-US + RedirectPermanent /misc/awards /News/awards + RedirectPermanent /misc/bsd.license https://opensource.org/licenses/BSD-3-Clause + RedirectPermanent /misc/laptops https://wiki.debian.org/InstallingDebianOn + RedirectPermanent /misc/memberships /intro/organization#memberships + RedirectPermanent /misc/merchandise /events/merchandise RedirectPermanent /intl /international RedirectPermanent /ports/armel /ports/arm RedirectPermanent /ports/armhf /ports/arm -- 2.20.1
Bug#930846: partman-auto-lvm: debconf show guided_size during auto install
Hi all El 15/7/19 a las 12:36, Holger Wansing escribió: Hi, Steve McIntyre wrote: On Sat, Jun 22, 2019 at 01:05:01PM +0200, Baptiste BEAUPLAT wrote: Tags: patch Added patch: https://salsa.debian.org/installer-team/installation-guide/merge_requests/7 Merged, thanks for your contribution! This has been fixed in the installation-guide package, version 20190622 (currently in stable) has the fix. However, https://www.debian.org/releases/buster/example-preseed.txt still does not have it. So CC'ing debian-www for assistance I've had a look at the www-master.debian.org I see that the installation guide has been generated on 20190623 but the example-preseed.txt file has date 20190324. I guess something went wrong with that file, and since there has not been changes in the installation guide since then, the build has not been retried. In our cron job, I've temporarily removed the part where it checks if we need to build or not the guide, to force a rebuild today, and thus have logs to see what happens to that file. I'll have a look later today to the logs and will update the bug. Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
