Send n libk
Lähetetty Huawei-matkapuhelimestani
Bug#859122: about 500 DLAs missing from the website
On Mon, Feb 11, 2019 at 03:56:41PM -0500, Antoine Beaupré wrote: > It's true there's a lot of junk in there... I suspect most of the `.pl` > scripts in there could actually be symlink to the main secteam scripts, > because they are basically the same. > > I also suspect most of the stuff is unused, even from the secteam's > point of view. For example, `check-cve-refs.pl` assumes there's a > `security/data` directory in the website, which is not the case > (anymore?). I'll also leave that to the security/www teams considerations ;) > I would suggest removing those from at least the LTS > section and have done so in the following MR: > https://salsa.debian.org/webmaster-team/webwml/merge_requests/55 I've reviewed, merged and pushed this now. Thank you! > > * This new /lts section of the website is not referenced yet in other > > places of the Debian website. I'm not sure if it should be referenced in > > /security, in /releases/, or in both. There is also the temptation > > of creating a link in the homepage but there is also the suggestion of > > reducing the links in the homepage, so... For now, I'll try to add it to > > the sitemap and see how many references to the LTS wiki page we have > > currently, to see if any of them can be replaced with link to this > > section in the website. But I'll wait some days to do it because it's > > not clear for me if you want to populate the section to cover all the > > aspects of LTS, or keep it only/mainly for security stuff. > I would avoid putting the LTS work too proeminently on the website at > this point, to be honest. The goal of publishing those advisories there, > for me, is coherence: they were already partly present and I wanted to > have them *all* available *somewhere* with a predictable URL and RSS > feeds (as opposed to, say the mailing list). agreed. > We shouldn't get into the slippery debate of how much we want LTS > content on the website, in my opinion. at least for here and now! :) -- tschau, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Bug#922246: www/lts: if DLA-1234-1 and DLA-1234-2 exist, only that last one shows up in indexes
package: www.debian.org x-debbugs-cc: debian-...@lists.debian.org Hi, this is a bug to track fixing this small glitch in the new /lts/security/ area: On Mon, Feb 11, 2019 at 04:26:38PM -0500, Antoine Beaupré wrote: > > On Sat, Feb 09, 2019 at 03:55:44AM +0100, Laura Arjona Reina wrote: > >> * The /lts/security//index.*.html files show the last advisory for > >> the cases where there are several files with the same beginning (e.g. > >> for DSA- and DSA--2, both html files are generated, but the > >> index only points to the -2 file). If this is not the intended > >> behaviour, changes in index.wml and Makefiles are needed. > > I think we want the other DLAs linked from the indexes as well. > > shall we file a bug to not forget this? > I looked into this, and couldn't figure it out. > Please do file a bug for now, I have no idea how to fix this... done :) -- tschau, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Bug#859122: about 500 DLAs missing from the website
Hi, On Mon, Feb 11, 2019 at 04:26:38PM -0500, Antoine Beaupré wrote: > > I think we want the other DLAs linked from the indexes as well. > > shall we file a bug to not forget this? > I looked into this, and couldn't figure it out. > Please do file a bug for now, I have no idea how to fix this... ok, will do. > >> that sets the redirect from > >> https://www.debian.org/security/any_year/dla-whatever to > >> https://www.debian.org/security/lts/any_year/dla-whatever > > right. shall we file a bug to not forget this? > Filed the patch here: > https://salsa.debian.org/anarcat/dsa-puppet/merge_requests/1 cool, thank you. > Reviews welcome. I'm particularly doubtful of the dla-map thing - it's > not in the source repo, but can I assume it's present on the website > deployment? I cannot comment on that dla-map, the rest looks good to me. (And simpler than I expected.) > >> * Adaptation in the security tracker so the new URL paths are used from > >> now on is also needed. > > right. shall we file a bug to not forget this? ok, will do. -- tschau, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Bug#922222: adapt 7doc_manuals cron script to use the multiple git repos in Salsa
Package: www.debian.org Severity: normal Hello I am opening a bug so this is not forgotten. Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona Mensaje reenviado Asunto: Re: 7doc_manuals cron script fails (trying to access svn repo in Alioth) Resent-Date: Wed, 21 Nov 2018 15:20:02 + (UTC) Resent-From: debian-...@lists.debian.org Fecha: Wed, 21 Nov 2018 15:51:35 +0100 De: Laura Arjona Reina Para: debian-...@lists.debian.org CC: debian-www Hello web and documentation teams, El 31/5/18 a las 23:57, Laura Arjona Reina escribió: Hello Debian Documentation team: One of the scripts that we use to build the Debian website (www.debian.org), 7doc_manuals, does not work anymore. Source code: https://salsa.debian.org/webmaster-team/cron/blob/master/parts/7doc_manuals It tries to access svn repo(s) in alioth: svn export --force svn://svn.debian.org/svn/ddp/manuals . > svn.log 2>&1 and they are not available anymore. Can you update it to access the corresponding repo in salsa? (or give us a hint about what to do). I've been looking at the code of the 7doc_manuals script: https://salsa.debian.org/webmaster-team/cron/blob/master/parts/7doc_manuals and the current organisation of the ddp repos in Salsa. I've listed all the manuals that were built from the original SVN "manuals" repo, reviewed case by case, and this is my proposal: 1.- The following manuals show "Obsolete documentation" in their first page of the content, and also are hosted now under https://salsa.debian.org/ddp-team/attic: apt-howto book-suggestions ddp-policy -> would close #147164 www.debian.org: DDP: DDP policy is too out of date dictionary debian-euro-support meta network-administrator programmer repository-howto system-administrator tutorial user users-guide so I propose remove them from the "7doc_manuals" build script and remove the manuals from the Debian website. Then, in the pages where we link to them, change the link to point to the corresponding attic repo and add a note about "obsolete documentation" (if it's not there yet). The person wanting to get the obsolete manuals, can download the repo and build themselves. 2.- The following manuals don't include the text "Obsolete documentation", but they are hosted in https://salsa.debian.org/ddp-team/attic, so I'm not sure what to do: debian-bugs (in attic) distribute-deb (in attic) dselect-beginner (in attic) fr/debian-fr-howto intro-i18n For now, I propose to remove them from the build script and keep the copy built in May 2018 in the Debian website. Maybe add a README file in the webwml repo in english/doc explaining where are the repos for the case it's needed to build them again. 3.- The following manuals are current, so I (if nobody beats me to it) will adapt the script to get the last changes from the current git repo, and build: https://salsa.debian.org/ddp-team/hamradio-handbook.git https://salsa.debian.org/ddp-team/java-faq.git 4.- The following manuals are current, but the current "make" command in the 7doc_manuals script would not work even if we get the git repos. I appreciate help to adapt the 7doc_manuals script for these: https://salsa.debian.org/ddp-team/project-history.git make -C project-history publish PUBLISHDIR=/srv/www.debian.org/www/doc/manuals install_file="install -p -m 664" install_dir="install -d -m 2775" make: *** No rule to make target 'publish'. Stop. https://salsa.debian.org/ddp-team/securing-debian-manual.git make -C securing-howto publish PUBLISHDIR=/srv/www.debian.org/www/doc/manuals install_file="install -p -m 664" install_dir="install -d -m 2775" make: *** No rule to make target 'publish'. Stop. Comments welcome. Kind regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
