Re: Bug#1072496: download file forbidden

2024-06-02 Thread Martin Zobel-Helas
Hi,

Please check  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646897

qcad is not distributable and therefore can not be downloaded from 
snapshot.d.o. 

This is why you see the http 403.

Best regards,
Martin

> Am 02.06.2024 um 23:24 schrieb Boyuan Yang :
> 
> Package: snapshot.debian.org
> Severity: normal
> 
> Hi,
> 
> 在 2024-06-02星期日的 22:49 +0200,jiri ht写道:
>> 
>> Good morning
>> I tried to download  qcad 
>> 
>> https://snapshot.debian.org/archive/debian/20060824T00Z/pool/main/q/qcad/qcad_2.0.5.0-1-2_amd64.deb
>> 
>> and this was answer:
>> Forbidden
>> You don't have permission to access this resource.
>> 
>> Apache Server at snapshot.debian.org Port 80
>> 
>> 
>> 
>> 
>> 
>> This file and too source and diff files cannot be  downloaded.
>> 
>> I tried to download other files and this is working.
>> 
>> 
>> Can You answer me  or repair it  please ?
> 
> You are reaching the debian-www mailing list, which is not in charge of the 
> maintenance
> of snapshot.debian.org.
> 
> The bottom of snapshot.debian.org website says: "Please report bugs against 
> the snapshot.debian.org package."
> I am doing you a favor to forward your report to a standalone bug report for 
> snapshot.debian.org.
> Next time, please submit your bug report following the instructions on
> https://www.debian.org/Bugs/Reporting .
> 
> Thanks,
> Boyuan Yang
> 


Re: download file forbidden

2024-06-02 Thread Boyuan Yang
Package: snapshot.debian.org
Severity: normal

Hi,

在 2024-06-02星期日的 22:49 +0200,jiri ht写道:
> 
> Good morning
> I tried to download  qcad 
> 
> https://snapshot.debian.org/archive/debian/20060824T00Z/pool/main/q/qcad/qcad_2.0.5.0-1-2_amd64.deb
> 
> and this was answer:
> Forbidden
> You don't have permission to access this resource.
> 
> Apache Server at snapshot.debian.org Port 80
> 
> 
> 
> 
> 
> This file and too source and diff files cannot be  downloaded.
> 
> I tried to download other files and this is working.
> 
> 
> Can You answer me  or repair it  please ?

You are reaching the debian-www mailing list, which is not in charge of the 
maintenance
of snapshot.debian.org.

The bottom of snapshot.debian.org website says: "Please report bugs against the 
snapshot.debian.org package."
I am doing you a favor to forward your report to a standalone bug report for 
snapshot.debian.org.
Next time, please submit your bug report following the instructions on
https://www.debian.org/Bugs/Reporting .

Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part


Re: Typo in download link for Debian 32-bit DVD ISO

2024-05-23 Thread Thomas Lange
Thanks for reporting. It has been fixed, but the rebuild of the web
pages is still needed. It will happen in a few hours.


> On Thu, 23 May 2024 09:08:41 +0200, Stefano Pigozzi  said:

> This page seems to be listing an invalid download link for the 32-bit PC 
DVD-1 iso.
> This link:

> 
https://cdimage.debian.org/debian-cd/current/i386/iso-cd/debian-12.5.0-i386-DVD-1.iso

> Should instead be:

> 
https://cdimage.debian.org/debian-cd/current/i386/iso-dvd/debian-12.5.0-i386-DVD-1.iso

-- 
best regards Thomas



Bug#608400: marked as done (re-organize how to contribute documentation "per-profile")

2024-05-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 May 2024 19:02:39 +0200
with message-id <26187.33327.681454.731...@cs.uni-koeln.de>
and subject line closing
has caused the Debian Bug report #608400,
regarding re-organize how to contribute documentation "per-profile"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
608400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: www.debian.org
Severity: normal

Out of curiosity in response to various DPL inquiries about "how can I help
Debian?", I've reviewed a bit the various pieces of documentation on the
subject and compared it with what other distros do.  A remarkable difference
seems to be a "per-profile" organization of the available material,
i.e. organizing the "how to contribute" page with a top-level distinction
among, say: developers, translators, bug triager, artists, donors, etc.

I believe there is some value in such a distinction, simply because the users
interested into helping out usually knows pretty well what they are able and
willing to do.  I hence suggest to reorganize the content of
http://www.debian.org/intro/help according to the various profiles.

Just for reference, here a few links to what others (random sampling, not
necessarily representative) have been doing in that respect:

- Fedora: http://fedoraproject.org/en/join-fedora (scrolling a bit down)
- Ubuntu: http://www.ubuntu.com/community
- OpenSUSE: http://en.opensuse.org/Portal:How_to_participate

Thanks a lot for maintaining www.d.o,
Cheers.

-- System Information:
Debian Release: 6.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


--- End Message ---
--- Begin Message ---

This was never implemented, so closing.
Since we restructred this page a lot the proposed change is obsolete.
-- 
regards Thomas--- End Message ---


Re: 我们需要linux-headers-6.1.0-21-amd64

2024-05-17 Thread Boyuan Yang
Hi,

On Fri, 2024-05-17 at 22:06 +, mmmg 高老师 wrote:
> CHINESE
> 由于官方未更新导致无法安装nvidia驱动 。这给我带来很多困扰 并且我无法找到debian11/10的ios在中国镜像站
> 请快速解决 谢谢 我非常急
> 谢谢
> ENGLISH
> Due to the lack of official updates, it is not possible to install the NVIDIA 
> driver. This has caused me a lot of trouble and I am unable to find the iOS 
> of Debian11/10 on the Chinese mirror site.
> Please resolve it quickly. I am very urgent
> thanks.

You have reached the debian-www mailing list, which is for discussion on
Debian website only and is not meant for user suport. For discussion
and user support in (Simplified) Chinese, please use the debian-chinese-gb
mailing list.
See https://lists.debian.org/debian-chinese-gb/ .

Thanks,
Boyuan Yang

您正在向 debian-www 发信,该邮件列表专用于讨论 Debian 网站相关事项,
不应用于获取用户支持。如您希望使用简体中文讨论并获取使用支持,请考虑
在 debian-chinese-gb 邮件列表中发信。详情请见
https://lists.debian.org/debian-chinese-gb/ 页面。

(另:仅以中文来看,您的问题描述难以理解。请考虑重新组织一下语言。
debian-chinese-gb 列表中有许多中国大陆和海外的用户和开发者,可以进一步帮助您。)

谢谢,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part


Re: Broken page link for buster installation

2024-05-17 Thread Thomas Lange
> On Fri, 17 May 2024 17:14:19 +0200, Holger Wansing  
> said:

> The buster release page says "To obtain and install Debian, see the 
installation 
> information page ..." but such page is not existant.
I removed this sentence.

-- 
regards Thomas



Processed: Re: Bug#1071157: www.debian.org: securing debian manual: broken links

2024-05-17 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 harden-doc
Bug #1071157 [www.debian.org] www.debian.org: securing debian manual: broken 
links
Bug reassigned from package 'www.debian.org' to 'harden-doc'.
Ignoring request to alter found versions of bug #1071157 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1071157 to the same values 
previously set

-- 
1071157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Re: Broken page link for buster installation

2024-05-17 Thread Holger Wansing
Hi,

Am 17. Mai 2024 16:27:28 MESZ schrieb Thomas Lange :
>Having LTS support does not mean that we recommend to install new
>systems using the outdated release. Therefore I've removed the link.
>
>And where is the page (which) mentioned?

The buster release page says "To obtain and install Debian, see the 
installation 
information page ..." but such page is not existant.


>
>> Editing the page like this is not professional (mentioning a page,
>> which is not there anymore).
>> Buster is still under LTS support, so not archived strictly.
>

Holger

-- 
Sent from /e/ OS on Fairphone3



Re: Broken page link for buster installation

2024-05-17 Thread Thomas Lange
Having LTS support does not mean that we recommend to install new
systems using the outdated release. Therefore I've removed the link.

And where is the page (which) mentioned?


> Editing the page like this is not professional (mentioning a page,
> which is not there anymore).
> Buster is still under LTS support, so not archived strictly.

-- 
regards Thomas



Re: Broken page link for buster installation

2024-05-17 Thread Holger Wansing
Hi,

Am 17. Mai 2024 15:12:55 MESZ schrieb Thomas Lange :
>Yes, it's correct that this link is not working any more. You can find
>the installer ISO here:
>  https://cdimage.debian.org/mirror/cdimage/archive/10.13.0/amd64/iso-cd/
>
>> On Thu, 16 May 2024 17:49:46 +, Heidi Fehr  said:
>
>> Hello!
>> I recently went to go look for an installer for Debian Buster v10 but it 
> appears that the page link is no longer working.
>> https://www.debian.org/releases/buster/debian-installer/

So, why was that page removed then?
Or at least add a link pointing to above archive URL?
Editing the page like this is not professional (mentioning a page,
which is not there anymore).
Buster is still under LTS support, so not archived strictly.


Holger


-- 
Sent from /e/ OS on Fairphone3



Re: Broken page link for buster installation

2024-05-17 Thread Thomas Lange
Yes, it's correct that this link is not working any more. You can find
the installer ISO here:
  https://cdimage.debian.org/mirror/cdimage/archive/10.13.0/amd64/iso-cd/

> On Thu, 16 May 2024 17:49:46 +, Heidi Fehr  said:

> Hello!
> I recently went to go look for an installer for Debian Buster v10 but it 
appears that the page link is no longer working.
> https://www.debian.org/releases/buster/debian-installer/

-- 
viele Grüße Thomas



Re: webml tidy warnings fixes

2024-05-09 Thread Boyuan Yang
Hi,

On Wed, 2024-05-08 at 22:48 +0500, Danila Shkerin wrote:
> Hi,
> 
> I've looked up tidy log for Russian language and fixed some warnigs,
> and 
> also fixed same (if has) in English language.
> 
> Patch in attachment.

Thanks, the changes are applied in
https://salsa.debian.org/webmaster-team/webwml/-/commit/34422e94132789c2bcd0f6d41dc8680b49c7f3ab
.

Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part


Re: The problem with security newsletters and newsletters on the security center

2024-05-08 Thread Тимур Казбеков
Thanks.
Is it ever possible to trust these sources, and what do you not want to do,
and you cannot manage them?
https://salsa.debian.org/security-tracker-team/security-tracker/-/raw/master/data/DSA/list
https://salsa.debian.org/security-tracker-team/security-tracker/-/raw/master/data/DLA/list

ср, 8 мая 2024 г. в 17:10, Thomas Lange :

> Hi,
>
> DSA-5248-1 is about php-twig - security update. This is correct in the
> security tracker https://security-tracker.debian.org/tracker/DSA-5248-1
>
> Unfortunally the email that was send about this security fix
> https://lists.debian.org/debian-security-announce/2022/msg00217.html
> had the wrong DSA number in the subject line and the mail itself.
>
> In our web pages, we can fix this, so the security entry links to the
> right email. This means www.debian.org/security/DSA-5248-1 will link
> to the correct email, but this email includes a wrong DSA number.
> Sorry for this confusion, but we cannot change the email afterwards.
>
> Here's the file of rewrites/fixes we use to link to the correct emails:
>
> https://salsa.debian.org/webmaster-team/webwml/-/blob/master/english/security/data/dsa.fixes?ref_type=heads
>
> --
> regards Thomas
>


Re: The problem with security newsletters and newsletters on the security center

2024-05-08 Thread Thomas Lange
> On Wed, 8 May 2024 17:44:01 +0600, Тимур Казбеков  
> said:

> Thanks.
> Is it ever possible to trust these sources, and what do you not want to 
do, and you cannot manage them?
> 
https://salsa.debian.org/security-tracker-team/security-tracker/-/raw/master/data/DSA/list
> 
https://salsa.debian.org/security-tracker-team/security-tracker/-/raw/master/data/DLA/list
These sources are the original ones, managed by the security team.
If there's some error in it, they can fix it.
You can file a bug report or send the security team an email about
errors in these files.
-- 
regards Thomas



Re: The problem with security newsletters and newsletters on the security center

2024-05-08 Thread Thomas Lange
Hi,

DSA-5248-1 is about php-twig - security update. This is correct in the
security tracker https://security-tracker.debian.org/tracker/DSA-5248-1

Unfortunally the email that was send about this security fix
https://lists.debian.org/debian-security-announce/2022/msg00217.html
had the wrong DSA number in the subject line and the mail itself.

In our web pages, we can fix this, so the security entry links to the
right email. This means www.debian.org/security/DSA-5248-1 will link
to the correct email, but this email includes a wrong DSA number.
Sorry for this confusion, but we cannot change the email afterwards.

Here's the file of rewrites/fixes we use to link to the correct emails:
https://salsa.debian.org/webmaster-team/webwml/-/blob/master/english/security/data/dsa.fixes?ref_type=heads

-- 
regards Thomas



Re: The problem with security newsletters and newsletters on the security center

2024-05-08 Thread Emilio Pozuelo Monfort

Hi,

On 08/05/2024 08:53, Тимур Казбеков wrote:

Hi!
We noticed that you have discrepancies in the mailing list and the
information provided on https://security-tracker.debian.org/tracker/
Example:
DSA-5248-1 link to the message
https://www.debian.org/security/2022/dsa-5248?ref=cve.news redirect to DSA
5246-1, but there is https://security-tracker.debian.org/tracker/DSA-5248-1
on the tracker, and unfortunately it is not clear why it overwrites the DSA
5246-1 in the mailing list, although they are completely different.
Here is a list of newsletters where there is a discrepancy between the
tracker and the newsletter:
DSA-5248-1 php-twig -- security update
DSA-4986-1 tomcat9 -- security update
DSA-4727-1 tomcat9 -- security update
DSA-4342-1 chromium-browser -- security update
DSA-3941-1 iortcw -- security update
DSA-3931-1 ruby-rack-cors -- security update
DSA-3768-1 openjpeg2 -- security update
DSA-3529-1 redmine -- security update
DSA-3525-1 pixman -- security update
DSA-3383-1 wordpress -- security update
DSA-3265-1 zendframework -- security update
DSA-3249-1 jqueryui -- security update
DLA-3177-1 python-django -- LTS security update
DLA-2941-1 linux-4.19 -- LTS security update
DLA-2887-1 lighttpd -- LTS security update
DLA-2785-1 linux-4.19 -- LTS security update
DLA-2714-1 linux-4.19 -- LTS security update
DLA-2690-1 linux-4.19 -- LTS security update
DLA-2652-1 unbound1.9 -- LTS security update
DLA-2610-1 linux-4.19 -- LTS security update
DLA-2594-1 tomcat8 -- LTS security update
DLA-2557-1 linux-4.19 -- LTS security update
DLA-2556-1 unbound1.9 -- LTS security update
DLA-2483-1 linux-4.19 -- LTS security update
DLA-2417-1 linux-4.19 -- LTS security update
DLA-2385-1 linux-4.19 -- LTS security update
DLA-2323-1 linux-4.19 -- LTS new package
DLA-2066-1 gthumb -- LTS security update
DLA-1709-1 waagent -- LTS security update
DLA-1543-1 gnulib -- LTS security update
DLA-1541-1 jekyll -- LTS security update
DLA-1540-1 net-snmp -- LTS security update
DLA-1539-1 samba -- LTS security update
DLA-1538-1 tinc -- LTS security update
DLA-1537-1 php-horde-kronolith -- LTS security update
DLA-1536-1 php-horde-core -- LTS security update
DLA-1535-1 php-horde -- LTS security update
DLA-1533-1 git -- LTS security update

Could you tell us or improve the experience of using newsletters?


This looks like a bug in the website redirections. I'm cc'ing debian-www.

Cheers,
Emilio



Re: Proposal: Refresh list of category in https://lists.debian.org/

2024-05-05 Thread Thomas Lange
Hi,

splitting developers and users is a good idea in my oppinion.
In the webwml repository
g...@salsa.debian.org:webmaster-team/webwml.git
there's the directory english/MailingLists/desc which includes
description, but I'm not sure if they are used for creating the web
page lists.debian.org. The listmaster team should know better.

-- 
regards Thomas



Re: Proposal: Refresh list of category in https://lists.debian.org/

2024-05-05 Thread Kentaro Hayashi
Hi,

I've proposed refresh list of category in
https://lists.debian.org before. [1]
There is a few feedbacks, but they are not negative ones.
[2][3]

So I want to make this idea forward, but not familiar way
to do it.

First, to raise an attention to the team, I've filed as a bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065647

Then I've seen https://wiki.debian.org/Teams/ListMaster, so
I've tried to contact the team directly.

As far as I know, content of repository is not public so
the only way to do is asking the team members to update ones, doesn't it?

[1]
Proposal: Refresh list of category in https://lists.debian.org/
https://lists.debian.org/debian-www/2024/03/msg00046.html

[2] https://lists.debian.org/debian-www/2024/03/msg00048.html
[3] https://lists.debian.org/debian-www/2024/04/msg1.html

Regards,

2024年3月30日(土) 19:53 Kentaro Hayashi :
>
> Hi,
>
> It seems that some of category in lists.debian.org
> may be too comprehensive,
> so I think that revisit updating list of category may be better.
>
> I've filed as a bug [1] especially the following 2 cases.
>
> * Case 1) "Users" category is too comprehensive, let's split it.
> * Case 2) "Developers" category is too comprehensive, let's split it.
>
> [1] https://bugs.debian.org/1065647
>
> Case 1) "Users" category is too comprehensive, let's split it.
>
> Split Users into "Users" and "Local Community and Users".
> Merit of this one is making it easy to distinct local/regional community.
>
>  Before:
>
>* Users (English)
> * debian-announce
> * debian-backports
> ...
> * debian-user
> ...
> * debian-chinese
> * debian-chinese-big5
> * debian-chinese-gb
> * debian-esperanto
> ...
>
>
>   After:
>
>* Users (English)
> * debian-announce
> * debian-backports
> ...
> * debian-user
> ...
>
>* Local Community and Users
>
> * debian-chinese
> * debian-chinese-big5
> * debian-chinese-gb
> * debian-esperanto
> * debian-french
> * debian-italian
> * debian-japanese
> * debian-user-catalan
> * debian-user-danish
> ...
>
> Case 2) Developers category is too comprehensive, let's split it.
>
> Extract some mailing-list into new "Maintenance of Programming
> Languages" from Developers category.
>
>   Before:
>
>* Developers
>
> * debian-academy
> ...
>
>   After:
>
>* Developers
>
> * debian-academy
> ...
>
>* Maintenance of Programming Languages
>
> * debian-ada
> * debian-clojure
> * debian-common-lisp
> * debian-go
> * debian-haskell
> * debian-js
> * debian-ocaml-maint
> * debian-perl
> * debian-python
> * debian-r
> * debian-ruby
> * debian-rust
> * debian-scheme
>
> Any thought?
>
> Regards,
>
>
>
> --
> Kentaro Hayashi 



-- 
Kentaro Hayashi 



Re: Re: Errors building /releases/buster folder in several languages (Re: webwml failed)

2024-05-01 Thread Thomas Lange


If I'm not wrong the current build errors come from these lines in 
Makefile.common:

151 ifneq "$(LANGUAGE)" "en"
152 #Ensure that MO files do exist
153 #Translators have to run make under webwml//po if they
154 #want it updated, it cannot be automatically performed.
155 $(LOCALEDESTFILES): $(LOCALEDIR)/%.mo: $(WMLBASE)/po/%.$(LANGUAGE).po
156 $(MAKE) -C $(WMLBASE)/po install-$*.mo


I wonder if this really because of a change in releases/
It looks more like the build in l10n/po fails.
-- 
regards Thomas



Re: Errors building /releases/buster folder in several languages (Re: webwml failed)

2024-05-01 Thread Holger Wansing



Am 30. April 2024 15:26:29 MESZ schrieb Laura Arjona Reina 
:.
>
>I don't know if there is another solution that does not involve manually 
>deleting files in www-master, to be taken into account for the future.

Simply wipe out the whole tree?


Holger

-- 
Sent from /e/ OS on Fairphone3



Re: Errors building /releases/buster folder in several languages (Re: webwml failed)

2024-04-30 Thread Thomas Lange
Thanks for helping. I already saw this error but didn't knew how to fix it.

> On Tue, 30 Apr 2024 15:26:29 +0200, Laura Arjona Reina 
>  said:

> I have logged in www-master and I am manually deleting those 
> files/folders so the /releases/ folder for the language matches the 
> structure of the git repo, and "make" only tries to build what it's 
> really needed.


-- 
regards Thomas



Errors building /releases/buster folder in several languages (Re: webwml failed)

2024-04-30 Thread Laura Arjona Reina

Hello

We are receiving build errors in the /releases/buster folder for several 
languages (see log below).


That folder has been removed in the git repo, but in www-master machine 
it is still there for several languages, due to the existence of .forced 
files (these are created sometimes by the touch_translation.pl script, I 
didn't look at the details) or the existence of an empty 
debian-installer subfolder.


I have logged in www-master and I am manually deleting those 
files/folders so the /releases/ folder for the language matches the 
structure of the git repo, and "make" only tries to build what it's 
really needed.


I don't know if there is another solution that does not involve manually 
deleting files in www-master, to be taken into account for the future.


Kind regards

--
Laura Arjona Reina
https://wiki.debian.org/LauraArjona

El 30/4/24 a las 13:53, Debian Webmaster escribió:

/srv/www.debian.org/cron/log/wml_run.log-make -C ports install
/srv/www.debian.org/cron/log/wml_run.log-make[2]: Entering directory 
'/srv/www.debian.org/webwml/bulgarian/ports'
/srv/www.debian.org/cron/log/wml_run.log-make -C amd64 install
/srv/www.debian.org/cron/log/wml_run.log-make[3]: Entering directory 
'/srv/www.debian.org/webwml/bulgarian/ports/amd64'
/srv/www.debian.org/cron/log/wml_run.log-make[3]: Leaving directory 
'/srv/www.debian.org/webwml/bulgarian/ports/amd64'
/srv/www.debian.org/cron/log/wml_run.log-make -C i386 install
/srv/www.debian.org/cron/log/wml_run.log-make[3]: Entering directory 
'/srv/www.debian.org/webwml/bulgarian/ports/i386'
/srv/www.debian.org/cron/log/wml_run.log-make[3]: Leaving directory 
'/srv/www.debian.org/webwml/bulgarian/ports/i386'
/srv/www.debian.org/cron/log/wml_run.log-make[2]: Leaving directory 
'/srv/www.debian.org/webwml/bulgarian/ports'
/srv/www.debian.org/cron/log/wml_run.log-make -C releases install
/srv/www.debian.org/cron/log/wml_run.log-make[2]: Entering directory 
'/srv/www.debian.org/webwml/bulgarian/releases'
/srv/www.debian.org/cron/log/wml_run.log-make -C buster install
/srv/www.debian.org/cron/log/wml_run.log-make[3]: Entering directory 
'/srv/www.debian.org/webwml/bulgarian/releases/buster'
/srv/www.debian.org/cron/log/wml_run.log-make[3]: *** No rule to make target 
'install'.  Stop.
/srv/www.debian.org/cron/log/wml_run.log-make[3]: Leaving directory 
'/srv/www.debian.org/webwml/bulgarian/releases/buster'
/srv/www.debian.org/cron/log/wml_run.log:make[2]: [../../Makefile.common:84: 
buster-install] Error 2 (ignored)
/srv/www.debian.org/cron/log/wml_run.log-make -C sid install
/srv/www.debian.org/cron/log/wml_run.log-make[3]: Entering directory 
'/srv/www.debian.org/webwml/bulgarian/releases/sid'
/srv/www.debian.org/cron/log/wml_run.log-make[3]: Leaving directory 
'/srv/www.debian.org/webwml/bulgarian/releases/sid'
/srv/www.debian.org/cron/log/wml_run.log-make[2]: Leaving directory 
'/srv/www.debian.org/webwml/bulgarian/releases'
--
/srv/www.debian.org/cron/log/wml_run.log-make[3]: Entering directory 
'/srv/www.debian.org/webwml/chinese/releases/bookworm'
/srv/www.debian.org/cron/log/wml_run.log-make -C debian-installer install
/srv/www.debian.org/cron/log/wml_run.log-make[4]: Entering directory 
'/srv/www.debian.org/webwml/chinese/releases/bookworm/debian-installer'
/srv/www.debian.org/cron/log/wml_run.log-make[4]: Leaving directory 
'/srv/www.debian.org/webwml/chinese/releases/bookworm/debian-installer'
/srv/www.debian.org/cron/log/wml_run.log-make[3]: Leaving directory 
'/srv/www.debian.org/webwml/chinese/releases/bookworm'
/srv/www.debian.org/cron/log/wml_run.log-make -C bullseye install
/srv/www.debian.org/cron/log/wml_run.log-make[3]: Entering directory 
'/srv/www.debian.org/webwml/chinese/releases/bullseye'
/srv/www.debian.org/cron/log/wml_run.log-make -C debian-installer install
/srv/www.debian.org/cron/log/wml_run.log-make[4]: Entering directory 
'/srv/www.debian.org/webwml/chinese/releases/bullseye/debian-installer'
/srv/www.debian.org/cron/log/wml_run.log-make[4]: Leaving directory 
'/srv/www.debian.org/webwml/chinese/releases/bullseye/debian-installer'
/srv/www.debian.org/cron/log/wml_run.log-make[3]: Leaving directory 
'/srv/www.debian.org/webwml/chinese/releases/bullseye'
/srv/www.debian.org/cron/log/wml_run.log-make -C buster install
/srv/www.debian.org/cron/log/wml_run.log-make[3]: Entering directory 
'/srv/www.debian.org/webwml/chinese/releases/buster'
/srv/www.debian.org/cron/log/wml_run.log-make[3]: *** No rule to make target 
'install'.  Stop.
/srv/www.debian.org/cron/log/wml_run.log-make[3]: Leaving directory 
'/srv/www.debian.org/webwml/chinese/releases/buster'
/srv/www.debian.org/cron/log/wml_run.log:make[2]: [../../Makefile.common:84: 
buster-install] Error 2 (ignored)
/srv/www.debian.org/cron/log/wml_run.log-make -C sid install
/srv/www.debian.org/cron/log/wml_run.log-make[3]: Entering directory 
'/srv/www.debian.org/webwml/chinese/releases/sid'
/srv/www.debian.org/cron/log/wml_run.log-make[3]: Leaving directory 

Re: Website Privacy Policy

2024-04-28 Thread Ceppo
You may want to read . It does not
mention Debian's website explicitly, but the last paragraph reads as follows.

> Service related logging
>
> In addition to the explicitly listed services above the Debian infrastructure
> logs details about system accesses for the purposes of ensuring service
> availability and reliability, and to enable debugging and diagnosis of issues
> when they arise. This logging includes details of mails sent/received through
> Debian infrastructure, web page access requests sent to Debian infrastructure,
>^^
> and login information for Debian systems (such as SSH logins to project
> machines). None of this information is used for any purposes other than
> operational requirements and it is only stored for 15 days in the case of web
> server logs, 10 days in the case of mail log and 4 weeks in the case of
> authentication/ssh logs.

It is not GDPR-compliant, but someone raised the issue in the campaign for the
latest DPL election [1] and it looks like it won't be addressed in the
foreseeable future. [2]


[1] https://lists.debian.org/debian-vote/2024/04/msg00024.html
[2] https://lists.debian.org/debian-vote/2024/04/msg00037.html


--
Ceppo



Re: upgrade procedure instructs users to run “apt update” but neglects upgrading

2024-04-24 Thread Holger Wansing
You have reported this already some days ago, and this issue has been fixed.
You have been informed about this.

Sorry, why report again?
You don't get anything by reporting the same issue  multiple times.

Closing.





-- 
Sent from /e/ OS on Fairphone3



Re: desbloqueo de ip publica

2024-04-22 Thread Steve McIntyre
Hi Francisco,

On Mon, Apr 22, 2024 at 12:26:41PM +0200, Francisco Lara wrote:
>Buenos dias mi ip publica es 84.122.1.218 y esta bloqueada para el acceso a la
>wiki de debian le agradeceria desbloquearan esta ip y se me permitiera el
>acceso soy usuario total de debian y me resulta muy util para consulta y
>resolucion de problemas.
>
>Atentamenta un saludo  espero su respuesta.

Unblocked for you now.

-- 
Steve McIntyre93...@debian.org
Debian wiki admin - wiki.debian.orgw...@debian.org



Re: finding unsused scripts, add comment into scripts that are still used

2024-04-19 Thread Thomas Lange
> On Fri, 19 Apr 2024 18:32:02 -0300, Matías Bellone 
>  said:

> In my experience, a better comment would be where and/or why the script 
is used so that in 2030 anyone that reads the comment can know where to start 
searching to verify if it is still
> being used.

Great idea, but please also add the current year.
-- 
best regards Thomas



Re: finding unsused scripts, add comment into scripts that are still used

2024-04-19 Thread Matías Bellone
On Fri, Apr 19, 2024 at 6:14 PM Thomas Lange  wrote:

> Hi all,
>
> I like to find scripts in the webwml repo that are not used any more
> but were not removed from the git repo.
> Therefore I suggest to add a comment to those scripts, that are still
> used anyone like translators or by our cron jobs.
>
> I did this already for some script as you can see in
> git show 89df02f8989c7a72150aac9ac05801f487ed226e
>
> Please check the scripts that you are using and add the comment
> "# This script is still used in 2024"
>

In my experience, a better comment would be where and/or why the script is
used so that in 2030 anyone that reads the comment can know where to start
searching to verify if it is still being used.

Regards,
Toote


Re: Bug#987943: www.debian.org: Developers Reference: Sphinx search non-functional: searchindex.js missing

2024-04-09 Thread Holger Wansing
Hi,

Holger Wansing  wrote (Mon, 8 Apr 2024 00:35:46 +0200):
> Everything works fine there as far a I see (with a desktop firefox and brave
> browser, as well as with the mobile versions of those browsers on my 
> smartphone).
> Feel free to test with more browsers/platforms/whatever.
> 
> I guess I will need to trim the 7doc script once again - h ...

This is done now.
debian-policy on debian.org/doc is fine as it is now.

See commits 3462a061, a2262ec9 and ae8aa074 on
https://salsa.debian.org/webmaster-team/cron/-/commits/master/parts/7doc?ref_type=heads

So, we know now what is needed, to get it this far (aka: get the search
function working and make the html theme work on big (desktop pcs) and
small (smartphone) screens:

We need javascript functionality from the packages libjs-sphinxdoc and 
libjs-jquery. Without these, the above funtions will not work.
I brought it this far, to make sure of this fact.

I will close this bug now.

Whether javascript will stay active on debian.org website will need to be
decided. I will follow up regarding this topic on 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872944


Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Re: webwml failed

2024-04-09 Thread Thomas Vincent

Hello,

Le 09/04/2024 à 05:53, Debian Webmaster a écrit :

/srv/www.debian.org/cron/log/wml_run.log-make[3]: Entering directory 
'/srv/www.debian.org/webwml/portuguese/vote/2024'
/srv/www.debian.org/cron/log/wml_run.log-wml -q -D CUR_YEAR=2024 -o 
UNDEFuPT:vote_001.pt.html@g+w   vote_001.wml
/srv/www.debian.org/cron/log/wml_run.log:** WML:Error: file not found: 
vote_001_quorum.txt
/srv/www.debian.org/cron/log/wml_run.log:make[3]: *** 
[/srv/www.debian.org/webwml/english/vote/2024/Makefile:18: vote_001.pt.html] 
Error 1
/srv/www.debian.org/cron/log/wml_run.log-make[3]: Leaving directory 
'/srv/www.debian.org/webwml/portuguese/vote/2024'
/srv/www.debian.org/cron/log/wml_run.log:make[2]: [../../Makefile.common:84: 
2024-install] Error 2 (ignored)


vote_001.wml was trying to include files that do not exist yet.
Hopefully I fixed it.

Cheers,
Thomas



OpenPGP_signature.asc
Description: OpenPGP digital signature


Re: Bug#1053549: Create a Debian theme for documentation based in Sphinx (reStructuredText)

2024-04-07 Thread Holger Wansing
Hi,

Laura Arjona Reina  wrote (Fri, 6 Oct 2023 09:35:09 +0200):
> 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.

Thanks to Stéphane Blondon, we have a nice Debian theme for Sphinx now, and
I managed to get it to the website in the end so far, currently visible at
debian-policy:
https://www.debian.org/doc/debian-policy/index.html

I had to deal with some missing javascript files as well, to make the 
sidebar appear/disappear on small screens like smartphones, but that works
now.

The only thing which is not working currently, is the search functionality,
but since that's not theme-specific I guess (please correct me, if I'm 
wrong), I close this bug.

Javascript leaves some open issues, but for those I will follow-up on some 
existing javascript bugs, we already have for the website/manuals.


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Re: issue with Debian-style html theme for sphinx-based documents

2024-04-05 Thread Sean Whitton
Hello,

On Fri 05 Apr 2024 at 02:07pm +02, Holger Wansing wrote:

> Hi,
>
> Holger Wansing  wrote (Tue, 2 Apr 2024 14:47:12 +0200):
>> We need a separate copy of 3 packages in our www build tree on
>> wolkenstein and all www static mirrors (simply let DSA install those
>> packages on the machines will not work).
>> And every sphinx-based manual needs relative symlinks in its tree, pointing
>> to the above packages' content.
>> The 1ftpfiles and 7doc scripts, which need to be adapted for that, and
>> also the situation on the www mirrors is getting more complex, so I'm unsure
>> if we want this.
>> See my patch.
>>
>> On the other side, I don't see any other solution apart from developing
>> a new theme.
>
> Since there were no objections, I pushed that yesterday (+ one additional
> change was needed), and that works now.

Thank you very much again.

-- 
Sean Whitton


signature.asc
Description: PGP signature


Re: issue with Debian-style html theme for sphinx-based documents

2024-04-05 Thread Holger Wansing
Hi,

Holger Wansing  wrote (Tue, 2 Apr 2024 14:47:12 +0200):
> We need a separate copy of 3 packages in our www build tree on
> wolkenstein and all www static mirrors (simply let DSA install those
> packages on the machines will not work).
> And every sphinx-based manual needs relative symlinks in its tree, pointing
> to the above packages' content.
> The 1ftpfiles and 7doc scripts, which need to be adapted for that, and
> also the situation on the www mirrors is getting more complex, so I'm unsure 
> if we want this.
> See my patch.
> 
> On the other side, I don't see any other solution apart from developing
> a new theme.

Since there were no objections, I pushed that yesterday (+ one additional
change was needed), and that works now.


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Re: issue with Debian-style html theme for sphinx-based documents

2024-04-03 Thread Thomas Lange
Hi Holger,

even if things get more complex, this is a working solution. I'm very
happy for that and there's no need for spending more time into looking
for a perfect solution.
>From my side you get a thank you very much and a GO for applying this patch.

> On Tue, 2 Apr 2024 14:47:12 +0200, Holger Wansing  
> said:

> The 1ftpfiles and 7doc scripts, which need to be adapted for that, and
> also the situation on the www mirrors is getting more complex, so I'm 
unsure 
> if we want this.
> See my patch.

> On the other side, I don't see any other solution apart from developing
> a new theme.

-- 
regards Thomas



Re: Translation of DSA

2024-04-01 Thread Thomas Lange
Hi Giuseppe,

the DSA are untranslatable on our web page, yes. We did that on
purpose. First, these announcements are very technical information,
not intended for end users. End users just want to upgrade their
system and know if all packages are up to date. That's why we think
most people that are interested in these security information
understand english. Second, there are automatic translation services, that can
easily translate those pages.

Adding PO support may be possible (you have to change the perl
script), but I will not spend time into it, because IMO there are
more important parts on the web page I like to improve.

-- 
best regards Thomas



Re: Proposal: Refresh list of category in https://lists.debian.org/

2024-04-01 Thread Giuseppe Sacco
Hello,

Il giorno sab, 30/03/2024 alle 13.52 +0100, Tomas Pospisek ha scritto:
> On 30.03.24 11:53, Kentaro Hayashi wrote:
> > Hi,
> > 
> > It seems that some of category in lists.debian.org
> > may be too comprehensive,
> > so I think that revisit updating list of category may be better.
> > 
> > I've filed as a bug [1] especially the following 2 cases.
> > 
> > * Case 1) "Users" category is too comprehensive, let's split it.
> > * Case 2) "Developers" category is too comprehensive, let's split it.
> > 
> > [1] https://bugs.debian.org/1065647
> > 
> > Case 1) "Users" category is too comprehensive, let's split it.
[...]
> > Any thought?
> 
> +1
> *t

I agree, as well.

Giuseppe



Re: Proposal: Refresh list of category in https://lists.debian.org/

2024-03-30 Thread Tomas Pospisek

On 30.03.24 11:53, Kentaro Hayashi wrote:

Hi,

It seems that some of category in lists.debian.org
may be too comprehensive,
so I think that revisit updating list of category may be better.

I've filed as a bug [1] especially the following 2 cases.

* Case 1) "Users" category is too comprehensive, let's split it.
* Case 2) "Developers" category is too comprehensive, let's split it.

[1] https://bugs.debian.org/1065647

Case 1) "Users" category is too comprehensive, let's split it.

Split Users into "Users" and "Local Community and Users".
Merit of this one is making it easy to distinct local/regional community.

  Before:

* Users (English)
 * debian-announce
 * debian-backports
 ...
 * debian-user
 ...
 * debian-chinese
 * debian-chinese-big5
 * debian-chinese-gb
 * debian-esperanto
 ...


   After:

* Users (English)
 * debian-announce
 * debian-backports
 ...
 * debian-user
 ...

* Local Community and Users

 * debian-chinese
 * debian-chinese-big5
 * debian-chinese-gb
 * debian-esperanto
 * debian-french
 * debian-italian
 * debian-japanese
 * debian-user-catalan
 * debian-user-danish
 ...

Case 2) Developers category is too comprehensive, let's split it.

Extract some mailing-list into new "Maintenance of Programming
Languages" from Developers category.

   Before:

* Developers

 * debian-academy
 ...

   After:

* Developers

 * debian-academy
 ...

* Maintenance of Programming Languages

 * debian-ada
 * debian-clojure
 * debian-common-lisp
 * debian-go
 * debian-haskell
 * debian-js
 * debian-ocaml-maint
 * debian-perl
 * debian-python
 * debian-r
 * debian-ruby
 * debian-rust
 * debian-scheme

Any thought?


+1
*t



Re: Upcoming stable point release (12.6)

2024-03-29 Thread Adam D. Barratt
On Fri, 2024-02-16 at 17:35 +, Jonathan Wiltshire wrote:
> The next point release for "bookworm" (12.6) is scheduled for
> Saturday, April 6th. Processing of new uploads into bookworm-
> proposed-updates will be frozen during the preceeding weekend.

Due to recent events, the point release has been postponed. A new date
will be announced when possible.

Regards,

Adam



Re: Bug#1067949: www.debian.org: No language selection on "www.debian.org/doc/manuals/maint-guide/"

2024-03-29 Thread c.buhtz
Dear Holger,

Thanks for work on that ticket.

But this does not solve the problem that this language links are
missing.

Having this links directly in the footer of such pages would increase
the usability.

Kind,
Christian



Re: Bug#1067949: www.debian.org: No language selection on "www.debian.org/doc/manuals/maint-guide/"

2024-03-29 Thread Holger Wansing



Am 29. März 2024 12:22:29 MEZ schrieb Christian Buhtz :

>
>There is no option to select the language of that document. I always see the
>translated version (in my case German). But I want to see the original of
>course.

For the manuals we have overview pages with links per language and format
on .

See 
and 

Closing this bug



Holger





-- 
Sent from /e/ OS on Fairphone3



Re: Bug#1067671: unable to run "make pot" due to missing english/template/debian/legal.wml

2024-03-25 Thread Holger Wansing
Hi,

Wenbin Lv  wrote (Mon, 25 Mar 2024 19:21:16 +0800):
> Package: www.debian.org
> 
> Hi,
> 
> I noticed some .pot files are out of date when translating the web pages,
> but can't update them by running "make pot" under english/po. The errors
> are:
> 
> ../../english/po/wmlxgettext.pl legal
> ../../english/template/debian/legal.wml
> ../../english/template/debian/legal_tags.wml > ../../english/po/legal.pot
> Unable to open ../../english/template/debian/legal.wml
> make[1]: *** [Makefile:140: ../../english/po/legal.pot] Error 2
> make[1]: Leaving directory '/home/lwb/sources/webwml/english/po'
> make: *** [Makefile:184: pot] Error 2
> 
> This file was deleted in commit 4e6f84e3b617a3ef6f7fb3c7b7d4e75ef302968c.

I seems it has been forgotten to remove the reference for legal.pot from 
./english/po/Makefile.
Doing that, lead to similar errors for other files, that have also been
removed shortly:
./english/security/dsa.rdf.in
./english/security/make-ref-table.pl
./english/security/index.include


Fixed in 
https://salsa.debian.org/webmaster-team/webwml/-/commit/a4735ef7b64ae00322ecd0796aa7513d9909


Closing this bug

Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Re: distribution archives became unusable

2024-03-06 Thread Jonathan Dowland
I'm replying to debian-www@lists.debian.org, as I think that is probably
the best place to raise the question.

On Wed Mar 6, 2024 at 8:09 AM GMT, Harald Dunkel wrote:
> Hi folks,
>
> the repositories listed on https://www.debian.org/distrib/archive have
> been signed using expired keys. Unfortunately this page doesn't deal
> with this problem.
>
> Do you think this could be improved?
>
>
> Regards
> Harri




-- 
Please do not CC me for listmail.

  Jonathan Dowland
✎j...@debian.org
   https://jmtd.net



Re: Who's using Debian?

2024-03-02 Thread Paulo Henrique de Lima Santana

Hi Ewa,

Thank you for your message!

I added your page now, and It will published soon here:

https://www.debian.org/users/com/mazzani

Best regards,

Em 14/02/2024 09:13, Ewa Piasecka escreveu:

Mazzani Sp. zo.o. Design Studio, Warsaw, Poland

Type of organization: Commercial

Website: www.mazzani.pl 

Mazzani Sp. zo.o. Design Studio in Warsaw, Poland, utilizes the Debian 
operating system on its workstations and servers. The office comprises a 
total of 25 workstations where employees use graphic design software, 
including interior design tools such as AutoCAD, SketchUp, and Adobe 
Creative Suite. Additionally, the studio has 5 servers that handle the 
storage of project data and provide access to network resources. Debian 
was chosen for its stability, security, and the availability of a wide 
range of graphic tools and applications in its repositories. 
Furthermore, the studio values openness and free software, making Debian 
a perfect fit for their operational philosophy.


--
Paulo Henrique de Lima Santana (phls)
Belo Horizonte - Brasil
Debian Developer
Site: http://phls.com.br
GPG ID: 0443C450


OpenPGP_signature.asc
Description: OpenPGP digital signature


Re: broken images on https://www.debian.org/partners/2024/

2024-02-21 Thread Laura Arjona Reina

Hello

El 21/2/24 a las 16:46, Filipozzi, Luca escribió:

Hi,

Please note that image URLs such as 
https://www.debian.org/partners/2024/images/1und1.png are returning 404.


Thanks for the repo, Luca.

My fault, the Makefile of the different "image" folders was not updated 
to the corresponding year.


I have fixed it in the repo in commit:

https://salsa.debian.org/webmaster-team/webwml/-/commit/6528dd25619743661321aefdf0cdaaff0c045bcd

and I'm running "update-parts partners" in www-master.d.o so the change 
will visible online in few minutes.


Kind regards,

--
Laura Arjona Reina
https://wiki.debian.org/LauraArjona



Re: URL update 32 bit from 11 to 12

2024-02-15 Thread dadadortda-darmst...@yahoo.com
 Thank You
The problem is
on Your homepage
debian.org
is the update10 to 11.
That is the reason I did ask You.
Thank You
Sophie



Am Mittwoch, 14. Februar 2024 um 17:50:58 MEZ hat Holger Wansing 
 Folgendes geschrieben:  
 
 Hi Sophie,

Am 14. Februar 2024 16:41:49 MEZ schrieb "dadadortda-darmst...@yahoo.com" 
:
>Good afternoonPlease send me the URLfor the instructionsto update Debian 11 to 
>12 32 bit LXDEIm newbie

this is the wrong list for user support questions, sorry.
Please ask at debian-u...@lists.debian.org
(or debian-user-ger...@lists.debian.org, if you would prefer German).


Moreover, 

is what you want...


Holger


-- 
Sent from /e/ OS on Fairphone3
  

Re: URL update 32 bit from 11 to 12

2024-02-15 Thread Holger Wansing
Hi,

Am 15. Februar 2024 12:19:35 MEZ schrieb "dadadortda-darmst...@yahoo.com" 
:
> Thank You
>The problem is
>on Your homepage
>debian.org
>is the update10 to 11.
>That is the reason I did ask You.

Which URL?


Holger

>Thank You
>Sophie
>
>
>
>Am Mittwoch, 14. Februar 2024 um 17:50:58 MEZ hat Holger Wansing 
>  Folgendes geschrieben:  
> 
> Hi Sophie,
>
>Am 14. Februar 2024 16:41:49 MEZ schrieb "dadadortda-darmst...@yahoo.com" 
>:
>>Good afternoonPlease send me the URLfor the instructionsto update Debian 11 
>>to 12 32 bit LXDEIm newbie
>
>this is the wrong list for user support questions, sorry.
>Please ask at debian-u...@lists.debian.org
>(or debian-user-ger...@lists.debian.org, if you would prefer German).
>
>
>Moreover, 
>
>is what you want...
>
>
>Holger
>
>

-- 
Sent from /e/ OS on Fairphone3



Re: URL update 32 bit from 11 to 12

2024-02-14 Thread Holger Wansing



Am 14. Februar 2024 17:50:51 MEZ schrieb Holger Wansing 
>Moreover, 
>
>is what you want...

Uups, you explicitly asked for 32bit, so that would be



-- 
Sent from /e/ OS on Fairphone3



Re: URL update 32 bit from 11 to 12

2024-02-14 Thread Holger Wansing
Hi Sophie,

Am 14. Februar 2024 16:41:49 MEZ schrieb "dadadortda-darmst...@yahoo.com" 
:
>Good afternoonPlease send me the URLfor the instructionsto update Debian 11 to 
>12 32 bit LXDEIm newbie

this is the wrong list for user support questions, sorry.
Please ask at debian-u...@lists.debian.org
(or debian-user-ger...@lists.debian.org, if you would prefer German).


Moreover, 

is what you want...


Holger


-- 
Sent from /e/ OS on Fairphone3



Re: Upcoming stable point release (12.5)

2024-02-08 Thread Holger Wansing
Hi,

Thomas Lange  wrote (Thu, 8 Feb 2024 12:10:33 +0100):
> > On Thu, 8 Feb 2024 11:25:22 +0100, Holger Wansing 
> >  said:
> 
> > Now leaving out the year from above link like
> > https://www.debian.org/security/dsa-5612
> > also redirects to the same announcement.
> 
> > @Thomas: is this the intended behaviour (both variants are supported
> > and it stays this way) ?
> > In that case nothing needs to be done in the point release 
> announcements...
> 
> Yes, it's intended to work with and without the year. The security
> team knows about this and will change to links without the year in the future.
> 
> I prefer without the year, because people do not care about the year
> when looking for a DSA/DLA, and it's hard to guess the year if you
> don't know it but only the number.

Sounds fair.
So the proper long-term solution would be to apply changings like in the
patch I proposed anyway...


Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Re: Upcoming stable point release (12.5)

2024-02-08 Thread Thomas Lange
> On Thu, 8 Feb 2024 11:25:22 +0100, Holger Wansing  
> said:

> Now leaving out the year from above link like
> https://www.debian.org/security/dsa-5612
> also redirects to the same announcement.

> @Thomas: is this the intended behaviour (both variants are supported
> and it stays this way) ?
> In that case nothing needs to be done in the point release 
announcements...

Yes, it's intended to work with and without the year. The security
team knows about this and will change to links without the year in the future.

I prefer without the year, because people do not care about the year
when looking for a DSA/DLA, and it's hard to guess the year if you
don't know it but only the number.
-- 
regards Thomas



Re: Upcoming stable point release (12.5)

2024-02-08 Thread Holger Wansing
Hi,

Holger Wansing  wrote (Thu, 8 Feb 2024 10:47:21 +0100):
> Hi,
> 
> Jean-Pierre Giraud  wrote (Thu, 08 Feb 2024 
> 09:49:00 +0100):
> > Le jeudi 08 février 2024 à 08:28 +0100, Thomas Lange a écrit :
> > > It's now easier than before. You don't need the year in the URL any more.
> > > This should be used instead:
> > > https://www.debian.org/security/dsa-5551
> 
> @Jean-Pierre:
> Good catch noticing this. Thanks for the heads-up!
> 
> 
> Changings like in attached patch should do it.

On the other hand, I wonder if the above ("You don't need the year in the URL 
any more") is strictly correct:

Looking at the security tracker for instance at
https://security-tracker.debian.org/tracker/source-package/chromium
then choosing a CVE like
https://security-tracker.debian.org/tracker/CVE-2024-1077
and then at the referenced DSA at
https://security-tracker.debian.org/tracker/DSA-5612-1
there is a link to the DSA at debian.org (the link is just named "Debian")
that points to 
https://www.debian.org/security/2024/dsa-5612
and that works: it gets redirected to the correct DSA announcement at
https://lists.debian.org/debian-security-announce/2024/msg00019.html

Now leaving out the year from above link like
https://www.debian.org/security/dsa-5612
also redirects to the same announcement.


@Thomas: is this the intended behaviour (both variants are supported
and it stays this way) ?
In that case nothing needs to be done in the point release announcements...



Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Re: Upcoming stable point release (12.5)

2024-02-08 Thread Holger Wansing
Hi,

Jean-Pierre Giraud  wrote (Thu, 08 Feb 2024 09:49:00 
+0100):
> Le jeudi 08 février 2024 à 08:28 +0100, Thomas Lange a écrit :
> > It's now easier than before. You don't need the year in the URL any more.
> > This should be used instead:
> > https://www.debian.org/security/dsa-5551

@Jean-Pierre:
Good catch noticing this. Thanks for the heads-up!


Changings like in attached patch should do it.


Holger

-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076
--- 20240210.wml	2024-02-08 10:38:13.344483185 +0100
+++ 20240210-fix-dsa-links.wml	2024-02-08 10:41:00.640002849 +0100
@@ -8,10 +8,10 @@
 12.5
 
 
-DSA-%1
+DSA-%0
 <:
 my @p = ();
-for my $p (split (/,\s*/, "%2")) {
+for my $p (split (/,\s*/, "%1")) {
 	push (@p, sprintf ('https://packages.debian.org/src:%s;>%s', $p, $p));
 }
 print join (", ", @p);
@@ -139,48 +139,48 @@
 
 
 Advisory ID  Package
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
 
 
 


Re: Upcoming stable point release (12.5)

2024-02-08 Thread Jean-Pierre Giraud
Hi Thomas,
Le jeudi 08 février 2024 à 08:28 +0100, Thomas Lange a écrit :
> > > > > > On Thu, 08 Feb 2024 06:32:33 +, "Adam D. Barratt"
> > > > > >  said:
> 
>     > There's a map in the www.d.o Apache config, so existing URLs should
>     > still work afaik.
> 
>     > https://www.debian.org/security/2023/dsa-5551 , for instance, from
> the
>     > 12.4 announcement at https://www.debian.org/News/2023/20231210 still
>     > provides a means of accessing DSA 5551.
> 
> It's now easier than before. You don't need the year in the URL any more.
> This should be used instead:
> https://www.debian.org/security/dsa-5551
> 
It' a good news, but could you have look to the paragraph concerning the DSA
in the announcement and the section listing them : lines 10 to 19 and 140 to
184 in the file
https://salsa.debian.org/publicity-team/announcements/-/blob/master/en/2024/20240210.wml?ref_type=heads
and eventually make the necessary changes.

Regards

Jean-Pierre


signature.asc
Description: This is a digitally signed message part


Re: Upcoming stable point release (12.5)

2024-02-07 Thread Thomas Lange
> On Thu, 08 Feb 2024 06:32:33 +, "Adam D. Barratt" 
>  said:

> There's a map in the www.d.o Apache config, so existing URLs should
> still work afaik.

> https://www.debian.org/security/2023/dsa-5551 , for instance, from the
> 12.4 announcement at https://www.debian.org/News/2023/20231210 still
> provides a means of accessing DSA 5551.

It's now easier than before. You don't need the year in the URL any more.
This should be used instead:
https://www.debian.org/security/dsa-5551

-- 
regards Thomas



Re: Upcoming stable point release (12.5)

2024-02-07 Thread Adam D. Barratt
On Thu, 2024-02-08 at 01:54 +0100, Jean-Pierre Giraud wrote:
> had a look at the text of the upcoming point releases, and I think
> there
> will be a problem for the building of the announcement page because
> security
> advisories have been removed from the security directory. 
> Now, the current list of security advisories
> (https://www.debian.org/security/index.en.html) is build by a new
> script
> mapping directly to URL on the mailing list archive (security/mk-dsa-
> dla-
> list). I suppose the current announcement page need some edits to
> work
> correclty.

There's a map in the www.d.o Apache config, so existing URLs should
still work afaik.

https://www.debian.org/security/2023/dsa-5551 , for instance, from the
12.4 announcement at https://www.debian.org/News/2023/20231210 still
provides a means of accessing DSA 5551.

Does the build script need more than that? If so, what? The WML itself
just builds URLs of the form I mentioned.

Regards,

Adam



Re: Upcoming stable point release (12.5)

2024-02-07 Thread Jean-Pierre Giraud
Hi,
Le mercredi 24 janvier 2024 à 18:20 +, Adam D. Barratt a écrit :
> Hi,
> 
> The next point release for "bookworm" (12.5) is scheduled for Saturday,
> February 10th. Processing of new uploads into bookworm-proposed-updates
> will be frozen during the preceding weekend.
> 
> Regards,
> 
> Adam
I had a look at the text of the upcoming point releases, and I think there
will be a problem for the building of the announcement page because security
advisories have been removed from the security directory. 
Now, the current list of security advisories
(https://www.debian.org/security/index.en.html) is build by a new script
mapping directly to URL on the mailing list archive (security/mk-dsa-dla-
list). I suppose the current announcement page need some edits to work
correclty.

Regards,

Jean-Pierre Giraud (jipege)


signature.asc
Description: This is a digitally signed message part


Re: Removed pages under /releases/

2024-01-25 Thread Hans Fredrik Nordhaug
I'm top-posting since the message has become very long:

1) Removing translations (in general) without discussion is very
demotivating. It makes you think why bother translating debian.org at
all. You can always use the integrated translator in your browser.
(Maybe we should stop doing this and rather link to the preferred
translation service, but that is a different discussion.)

2) Removing translations, but keeping the English content is even more
demotivating. In this particular case, I don't mind removing the
release notes, but I think the release information should have be
preserved - for example in Norwegian:
https://web.archive.org/web/20230404193832/https://www.debian.org/releases/jessie/index.nb.html
This is something we could have discussed.

3) Regarding search: I don't see how the search improves very much by
removing old translated pages. If someone searches for "Debian Release
information", they don't get any hits for translated pages - for
example "Debian utgivelsesinformasjon".

Finally, I think translators focus on the main content without someone
removing old stuff :-)

I'm not angry or upset, and I don't need to discuss my points above -
it's just my opinion.

And, Thomas, I do appreciate the work you do to clean up the scripts
and the website.

Regards, Hans - who does a lousy job translating debian.org to Norwegian

ons. 24. jan. 2024 kl. 13:05 skrev Andreas Ronnquist :
>
> On Wed, 24 Jan 2024 09:45:46 +0100,
> Thomas Lange wrote:
>
> (First, no need to CC me, I read the list) -
>
> >Hi Andreas,
> >
> >another reason that I forgot was that we had too many versions of the
> >installmanual and the release notes. For many old releases we've kept
> >them in 14 languages for every architecture (around 10) for each old release.
> >E.g.:
> >https://web.archive.org/web/20230625201750/https://www.debian.org/releases/jessie/releasenotes
> >https://web.archive.org/web/20230625201754/https://www.debian.org/releases/jessie/installmanual
[cut]



Re: Removed pages under /releases/

2024-01-24 Thread Andreas Ronnquist
On Wed, 24 Jan 2024 09:45:46 +0100,
Thomas Lange wrote:

(First, no need to CC me, I read the list) - 

>Hi Andreas,
>
>another reason that I forgot was that we had too many versions of the
>installmanual and the release notes. For many old releases we've kept
>them in 14 languages for every architecture (around 10) for each old release.
>E.g.:
>https://web.archive.org/web/20230625201750/https://www.debian.org/releases/jessie/releasenotes
>https://web.archive.org/web/20230625201754/https://www.debian.org/releases/jessie/installmanual
>
>
>That made our own search engine produce very bad results, because
>often if shows results for old releases instead on hits from the
>newest installation manual. Our search engine cannot sort the result
>by date btw. Someone said we should fix this problem,
>but as noone worked on this I tried to produce better results by
>removing old content. I don't think that many people need the old
>version of the installation manual of releases, that are not supported
>by Debian or even by the LTS people any more. Do you think that people
>need the release notes because they want to install Debian jessie
>nowadays? We always have archive.org or softwareheritage for thoses
>information.

Ah, that is a very much better explanation to why the content has been
removed, yes. That indeed answers my questions. Of course I don't think
that it is wrong, IF it has a good reason (which I've got here). Thank
you!

But, with that said - communication could probably have been better.
As you probably have seen, some of the translators have re-added the
translations after you have removed them, which obviously shouldn't be
done.

(I won't of course re-add the Swedish ones now, after your explanation).

>
>In the past we've built every release note for two (or was it three?)
>releases 6 times a days regardless if the sources of the release notes
>had changed or not. I improved the build time a lot by adding code
>that only build them (for all languages and architectures) if
>something changed. Maybe you remember this improvement.

I do, and I thank you for it.

>
>I try to have the point of view from the user of our web pages. If
>they look or search for information on our web pages and get old and
>outdated search results, then our web page is useless for them. The
>ratio of old to new content on our webpages was very bad in the
>past. That's why I try to remove old content.
>

Thanks for the explanation - I appreciate it.

-- Andreas Rönnquist
mailingli...@gusnan.se
andr...@ronnquist.net



Re: Removed pages under /releases/

2024-01-24 Thread Thomas Lange
Hi Andreas,

another reason that I forgot was that we had too many versions of the
installmanual and the release notes. For many old releases we've kept
them in 14 languages for every architecture (around 10) for each old release.
E.g.:
https://web.archive.org/web/20230625201750/https://www.debian.org/releases/jessie/releasenotes
https://web.archive.org/web/20230625201754/https://www.debian.org/releases/jessie/installmanual


That made our own search engine produce very bad results, because
often if shows results for old releases instead on hits from the
newest installation manual. Our search engine cannot sort the result
by date btw. Someone said we should fix this problem,
but as noone worked on this I tried to produce better results by
removing old content. I don't think that many people need the old
version of the installation manual of releases, that are not supported
by Debian or even by the LTS people any more. Do you think that people
need the release notes because they want to install Debian jessie
nowadays? We always have archive.org or softwareheritage for thoses
information.

In the past we've built every release note for two (or was it three?)
releases 6 times a days regardless if the sources of the release notes
had changed or not. I improved the build time a lot by adding code
that only build them (for all languages and architectures) if
something changed. Maybe you remember this improvement.

I try to have the point of view from the user of our web pages. If
they look or search for information on our web pages and get old and
outdated search results, then our web page is useless for them. The
ratio of old to new content on our webpages was very bad in the
past. That's why I try to remove old content.

-- 
regards Thomas



Re: Removed pages under /releases/

2024-01-23 Thread Andreas Rönnquist
On Tue, 23 Jan 2024 18:36:42 +0100,
Thomas Lange wrote:

>Hi Andreas,
>
>I've removed those pages maily because they contain outdated obsolete
>content from very old releases and people put time into maintainig
>them, what I think is not worth it. I think it's sufficient to keep less
>information about these releases and only in english.
>
>I don't know if the translators missed the information.
>They may have a different opinion which information about old releases
>are usefull for our users.
>
>I don't think it's worth putting time into re-adding those pages or
>translating old web pages. In the past I saw multiple efforts of
>translators to work old security announcements for e.g.
>There are even efforts to translate voting web pages from 2010 and before.
>
>I would like to encourage translators to do work on more important
>(from my point of view) pages or topics. I think translators could do
>more review of content, and help finding outdated content, outdated
>manuals, broken links, obsolete listings off CD vendors, obsolete
>listings of vendors of pre-installed computers,

Well, I thought that the pages were deleted to make the build faster,
but now you say that is not case, but to make people work on "more
important" pages. 

I understand that point of view, but it seems pretty counter-intuitive
to remove translations for languages where there's 0 pages that are out
of date. If they were deleted to make the build
faster I would at least understand it.

Especially if the only reason is to make people translate more
important pages and not out of date stuff.

Deleting translations is a lousy motivator to get more pages translated.

(And yes, I do know that I can get the deleted files back from the git
repo, but as it is now I don't have much motivation to do so).

-- Andreas Rönnquist
mailingli...@gusnan.se
andr...@ronnquist.net
(please don't CC me, I read the list).



Re: Removed pages under /releases/

2024-01-23 Thread Thomas Lange
Hi Andreas,

I've removed those pages maily because they contain outdated obsolete
content from very old releases and people put time into maintainig
them, what I think is not worth it. I think it's sufficient to keep less
information about these releases and only in english.

I don't know if the translators missed the information.
They may have a different opinion which information about old releases
are usefull for our users.

I don't think it's worth putting time into re-adding those pages or
translating old web pages. In the past I saw multiple efforts of
translators to work old security announcements for e.g.
There are even efforts to translate voting web pages from 2010 and before.

I would like to encourage translators to do work on more important
(from my point of view) pages or topics. I think translators could do
more review of content, and help finding outdated content, outdated
manuals, broken links, obsolete listings off CD vendors, obsolete
listings of vendors of pre-installed computers,

-- 
regards Thomas


>>>>> On Tue, 23 Jan 2024 16:44:47 +0100, Andreas Rönnquist 
>>>>>  said:

> Hi -
> I have noticed that folders under the releases folder for several
> languages has been removed by Thomas Lange - and as I understand it, it
> is done on the quest to speed up the build of the webpages.

> That is fine by me, but now I see that several translators has started
> re-adding those removed files again for their languages - I thought
> that these where removed so that we should only have a english version
> of these as described above to speed up compilation.

> Is this just because these translators have missed the memo, or is it I
> who have missed some information?



Re: Who's using Debian

2024-01-21 Thread Paulo Henrique de Lima Santana

Hi,

Thank you for your message!

I added your page now, and It will published soon here:

https://www.debian.org/users/com/viralmood

Best regards,


Em 20/11/2023 10:05, Kontakt | ViralMood escreveu:

Hello,

We would like to add in user lists of debian.


1. ViralMood, Wroclaw, Poland

2. Commercial

3. https://viralmood.pl/

4. We are using Debian on five of our servers (64-bit versions), and on 
two of our workstations. Our servers are running applications written in 
PHP, database software (mysql, postgresql), and ftp.


We chose Debian because it is a stable and simple.



Thanks 

ViralMood



--
Paulo Henrique de Lima Santana (phls)
Belo Horizonte - Brasil
Debian Developer
Site: http://phls.com.br
GPG ID: 0443C450


OpenPGP_signature.asc
Description: OpenPGP digital signature


Re: Trixie installation guide links -> 404

2024-01-14 Thread Holger Wansing
Hi,

"d...@dougwebb.site"  wrote (Sun, 14 Jan 2024 19:44:47 
+0100):
> Hi there,
> 
> Just wanted to report that all of the guide links to install trixie on page:
> 
> https://www.debian.org/releases/trixie/installmanual
> 
> ...return 404 status codes (status code not presented to page viewer!)

That URL is not yet valid.
To install trixie (testing), see https://www.debian.org/devel/debian-installer/


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Re: Package link broken

2024-01-10 Thread Boyuan Yang
Hi,

在 2024-01-01星期一的 10:51 +0100,Bram Langen写道:
> Hi,
> 
> Below is my history looking for various packages to load.  You can see that 
> right after the first (bottom-most) hit I landed on the 'all' pages.  The 
> listing is in
> chronological order with the most recent hit on top.
> 
> So the initial redirection to the 'all' pages is from the 'all' link in the 
> section 'Download python3-colorama' under the header 'Architecture'.
> 
> For me this 'all/allpackages' page was very helpful to find the packages I 
> needed now that I am rebuilding a Raspberry Pi to the latest OS, and the 
> pip-method to load
> packages no longer works.
> 
> Hope this helps.

Thanks, this helps to narrow down the issue. The updated problem
description is filed in https://bugs.debian.org/1059780 .

Best,
Boyuan Yang


> https://packages.debian.org/bookworm/all/python3-serial/download
> https://packages.debian.org/bookworm/arm64/python/python3-serial
> https://packages.debian.org/bookworm/arm64/python/
> https://packages.debian.org/bookworm/arm64/
> https://packages.debian.org/bookworm/arm64/python3-rrdtool/download
> https://packages.debian.org/bookworm/python/python3-autobahn
> https://packages.debian.org/bookworm/python/
> https://packages.debian.org/bookworm/python/python3-rrdtool
> https://packages.debian.org/bookworm/
> https://packages.debian.org/bookworm/all/python3-rrdtool
> https://packages.debian.org/bookworm/all/allpackages
> https://packages.debian.org/bookworm/i386/python3-pytz-deprecation-shim
> https://www.google.com/url?sa=t=j==s=web==2ahUKEwisvP3P-beDAxUZ8gIHHTeOBrAQFnoECBEQAQ=https%3A%2F%2Fpackages.debian.org%2Fbookworm%2Fi386%2Fpython3-pytz-deprecation-shim=AOvVaw2Lo0PKVjMfjarsMYnY0_-O=89978449
> https://packages.debian.org/bookworm/all/python3-websocket/download
> https://packages.debian.org/bookworm/all/python3-websocket
> https://packages.debian.org/bookworm/all/python3-service-identity/download
> https://packages.debian.org/bookworm/armel/python3-service-identity
> https://www.google.com/url?sa=t=j==s=web==2ahUKEwis04GdgLWDAxUf7rsIHco9DhYQFnoECA8QAQ=https%3A%2F%2Fpackages.debian.org%2Fbookworm%2Farmel%2Fpython3-service-identity=AOvVaw1_PqRH9rizOCueN6cqkxSC=89978449
> https://packages.debian.org/bookworm/all/python3-autobahn/download
> https://packages.debian.org/bookworm/all/python3-autobahn
> https://packages.debian.org/bookworm/all/python3-twisted/download
> https://packages.debian.org/bookworm/all/python3-twisted
> https://packages.debian.org/bookworm/all/python3-schedule/download
> https://packages.debian.org/bookworm/all/python3-schedule
> https://packages.debian.org/bookworm/all/
> https://packages.debian.org/bookworm/all/python3-colorama/download
> https://packages.debian.org/bookworm/python3-colorama
> 
> On Mon, Jan 1, 2024 at 2:17 AM Boyuan Yang  wrote:
> > Hi,
> > 
> > 在 2023-12-31星期日的 14:26 +0100,Bram Langen写道:
> > > Hi,
> > > 
> > > The link to package "python3-rrdtool (1.7.2-4+b8)" from this page results 
> > > in the error message " Package not available in this suite." 
> > 
> > 
> > Could you provide an instruction on how did you browse the internet and
> > enter the page https://packages.debian.org/bookworm/all/allpackages ?
> > 
> > The webpage https://packages.debian.org/bookworm/all/allpackages , though 
> > it displays
> > package information, shall not exist from the very beginning.
> > 
> > I have submitted a corresponding bug report at 
> > https://bugs.debian.org/1059780 .
> > 
> > (PS: To Debian Webmasters: how can I contribute to fixing bugs of 
> > packages.debian.org ?
> > I have been looking for information since year 2019, but I am still 
> > clueless in 2024 today.
> > The most recent attempt is 
> > https://lists.debian.org/debian-www/2023/12/msg00029.html .
> > Any help would be appreciated.)
> > 
> > Thanks,
> > Boyuan Yang



signature.asc
Description: This is a digitally signed message part


Re: Dead links to "Introduction to i18n"

2024-01-10 Thread Boyuan Yang
Hi,

在 2024-01-09星期二的 12:21 +0100,jens@get2net.dk写道:
> https://wiki.debian.org/I18n has dead links.
> 
> "Introduction to i18n, Tomohiro KUBOTA" links to
> https://www.debian.org/doc/manuals/intro-i18n/ch-intro.en.html#s-intro-concepts
> 
> "Introduction to i18n" links to
> https://www.debian.org/doc/manuals/intro-i18n/


I have deleted the link to the disappeared webpage. The detailed analysis can
be found at https://wiki.debian.org/I18n?action=info .

Debian Wiki allows edit from everyone; next time please consider registering an
account and make the modification by yourself.

Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part


Re: po statistics

2024-01-06 Thread Holger Wansing
Hi,

Helge Kreutzmann  wrote (Fri, 17 Nov 2023 16:37:14 +):
> > > I'll just pick one:
> > > de_PY.nl.html is
> > > "Toestand van de PO-bestanden voor de taalcode: de_PY — German 
> > > @tmpl_lang@ndash; Paraguay"
> > > who needs this?
> 
[...]

> And maybe some German speaking community in Paraguay just happens to
> decide right now to do the work - then they could ramp up their
> efforts quickly, as the infrastructure is already there.

That was a bad example.
There is no such language team like de_PY (German in Paraguay).
'py' is a substitution for 'python' here; there is a German po file for
some python module at that page.

So I have removed de_PY, fr_PY, it_PY and zh_PY from the list.

As well as bin (which is a substitution for binary) and cli (as a short form
for Commandline Interface) and cut (there are no po files for 'cut' language
at that page; there are Danish, German and French po files at that page).


Greetings
Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Re: new redirects for www.d.o/security and www.d.o/lts/security

2024-01-05 Thread Salvatore Bonaccorso
Hi Thomas,

On Fri, Jan 05, 2024 at 12:06:58AM +0100, Thomas Lange wrote:
> Hi all,
> 
> we now redirect all DSA/DLA URLs under security and lts/security with
> or without having the year in the path and with or without a version
> to their announcement mail:
> Examples:
> /security/dsa-5576
> /security/2023/dsa-5576-2
> lts/security/2023/dla-3686-1
> lts/security/dla-3686
> 
> All URLs like dsa-5576-2 or dla-3686-1 are redirected to the specified
> versions of the DSA. A URL containing only a DSA/DLA number but no
> version currently redirect to version -1. In the future it may
> redirect to the most recent version.
> All redirects are not case sensitive.

Thanks a lot for your great work and invested time on this topic!

> @security-tracker admins:
> A page like https://security-tracker.debian.org/tracker/DSA-5576
> redirects to
> https://security-tracker.debian.org/tracker/DSA-5576-2
> On this page you have a link to the "Source  Debian" which is a link to
> https://www.debian.org/security/2023/dsa-5576.
> Currently this is a wrong link to dsa-5576-1.
> 
> The easiest way would be to make the "Source Debian" links always
> redirect to the announcement number including the version, but without
> the year. So for
> https://security-tracker.debian.org/tracker/DSA-5576-2
> change this link to
> https://www.debian.org/security/DSA-5576-2
> similar for the DLAs and so on.

Thanks, will look into it and see that we can align as well those and
make the adjusted reference in the tracker.

Regards,
Salvatore



Re: New script to strip out entries from languages list

2024-01-03 Thread Holger Wansing



Am 2. Januar 2024 23:23:05 MEZ schrieb Holger Wansing :
>While my first approach was, to call this new script in 
>webwml/english/international/l10n/po/Makefile after the gen-files.sh run, I 
>now realize that the correct way is, to call strip-langs.sh in webmaster's 
>cron repo in lessoften-parts/1l10n-data, where the data/langs file is 
>created. (I somehow was in the assumption, that the gen-files.sh creates
>data/langs, but today I saw I was wrong here.)
>While both approaches worked so far, it's the cleaner (and more obvious) way, 
>to call strip-langs.sh via the cron script 1l10n-data directly after creating
>data/langs. 
>Thus changing it that way. 
>
>See
>https://salsa.debian.org/webmaster-team/cron/-/commit/9fdc0e492fbb044f11c675fc92f660c13ab74616
>and
>https://salsa.debian.org/webmaster-team/webwml/-/commit/e59bdd1ee162d9d1eb2faca9b587eac151c478a4

Calling strip-langs.sh from cron script directly does not work 
as intended, so reverting back to my previos version.

Sorry for this forward-backward dance...


Holger



-- 
Sent from /e/ OS on Fairphone3



Re: New script to strip out entries from languages list

2024-01-02 Thread Holger Wansing
Hi again,

Holger Wansing  wrote (Tue, 02 Jan 2024 17:03:28 +0100):
> Am 2. Januar 2024 09:29:05 MEZ schrieb Thomas Lange :
> >Hi Holger,
> >
> >this script looks good to me. Thanks a lot for your work on this.
> >I think you can merge it.
> 
> Just merged.

While looking at the logs now, I see that I had to change that once more:

While my first approach was, to call this new script in 
webwml/english/international/l10n/po/Makefile after the gen-files.sh run, I 
now realize that the correct way is, to call strip-langs.sh in webmaster's 
cron repo in lessoften-parts/1l10n-data, where the data/langs file is 
created. (I somehow was in the assumption, that the gen-files.sh creates
data/langs, but today I saw I was wrong here.)
While both approaches worked so far, it's the cleaner (and more obvious) way, 
to call strip-langs.sh via the cron script 1l10n-data directly after creating
data/langs. 
Thus changing it that way. 

See
https://salsa.debian.org/webmaster-team/cron/-/commit/9fdc0e492fbb044f11c675fc92f660c13ab74616
and
https://salsa.debian.org/webmaster-team/webwml/-/commit/e59bdd1ee162d9d1eb2faca9b587eac151c478a4


Holger

-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Re: New script to strip out entries from languages list

2024-01-02 Thread Holger Wansing
Hi,

Am 2. Januar 2024 09:29:05 MEZ schrieb Thomas Lange :
>Hi Holger,
>
>this script looks good to me. Thanks a lot for your work on this.
>I think you can merge it.

Just merged.


>> On Mon, 1 Jan 2024 23:39:09 +0100, Holger Wansing  
>> said:
>
>
>> In additional steps, we could also remove entries like de_AT, de_CH, 
> de_DE
>> and only leave 'de', as mentioned by Thomas.
>> But that's another discussion.
>I guess we do not want to remove those languages, but merge the
>variants into de. But maybe this need to be done in a different
>script, maybe in gen-files.pl.

Hmm. That will be out of my skills...


Holger


-- 
Sent from /e/ OS on Fairphone3



Re: New script to strip out entries from languages list

2024-01-02 Thread Thomas Lange
Hi Holger,

this script looks good to me. Thanks a lot for your work on this.
I think you can merge it.

> On Mon, 1 Jan 2024 23:39:09 +0100, Holger Wansing  
> said:


> In additional steps, we could also remove entries like de_AT, de_CH, de_DE
> and only leave 'de', as mentioned by Thomas.
> But that's another discussion.
I guess we do not want to remove those languages, but merge the
variants into de. But maybe this need to be done in a different
script, maybe in gen-files.pl.

-- 
regards Thomas



Re: Package link broken

2024-01-01 Thread Bram Langen
Hi,

Below is my history looking for various packages to load.  You can see that
right after the first (bottom-most) hit I landed on the 'all' pages.  The
listing is in chronological order with the most recent hit on top.

So the initial redirection to the 'all' pages is from the 'all' link in the
section 'Download python3-colorama' under the header 'Architecture'.

For me this 'all/allpackages' page was very helpful to find the packages I
needed now that I am rebuilding a Raspberry Pi to the latest OS, and the
pip-method to load packages no longer works.

Hope this helps.

Thank you for your quick response.

Regards,

Bram Langen

https://packages.debian.org/bookworm/all/python3-serial/download
https://packages.debian.org/bookworm/arm64/python/python3-serial
https://packages.debian.org/bookworm/arm64/python/
https://packages.debian.org/bookworm/arm64/
https://packages.debian.org/bookworm/arm64/python3-rrdtool/download
https://packages.debian.org/bookworm/python/python3-autobahn
https://packages.debian.org/bookworm/python/
https://packages.debian.org/bookworm/python/python3-rrdtool
https://packages.debian.org/bookworm/
https://packages.debian.org/bookworm/all/python3-rrdtool
https://packages.debian.org/bookworm/all/allpackages
https://packages.debian.org/bookworm/i386/python3-pytz-deprecation-shim
https://www.google.com/url?sa=t=j==s=web==2ahUKEwisvP3P-beDAxUZ8gIHHTeOBrAQFnoECBEQAQ=https%3A%2F%2Fpackages.debian.org%2Fbookworm%2Fi386%2Fpython3-pytz-deprecation-shim=AOvVaw2Lo0PKVjMfjarsMYnY0_-O=89978449
https://packages.debian.org/bookworm/all/python3-websocket/download
https://packages.debian.org/bookworm/all/python3-websocket
https://packages.debian.org/bookworm/all/python3-service-identity/download
https://packages.debian.org/bookworm/armel/python3-service-identity
https://www.google.com/url?sa=t=j==s=web==2ahUKEwis04GdgLWDAxUf7rsIHco9DhYQFnoECA8QAQ=https%3A%2F%2Fpackages.debian.org%2Fbookworm%2Farmel%2Fpython3-service-identity=AOvVaw1_PqRH9rizOCueN6cqkxSC=89978449
https://packages.debian.org/bookworm/all/python3-autobahn/download
https://packages.debian.org/bookworm/all/python3-autobahn
https://packages.debian.org/bookworm/all/python3-twisted/download
https://packages.debian.org/bookworm/all/python3-twisted
https://packages.debian.org/bookworm/all/python3-schedule/download
https://packages.debian.org/bookworm/all/python3-schedule
https://packages.debian.org/bookworm/all/
https://packages.debian.org/bookworm/all/python3-colorama/download
https://packages.debian.org/bookworm/python3-colorama

On Mon, Jan 1, 2024 at 2:17 AM Boyuan Yang  wrote:

> Hi,
>
> 在 2023-12-31星期日的 14:26 +0100,Bram Langen写道:
> > Hi,
> >
> > The link to package "python3-rrdtool (1.7.2-4+b8)" from this page
> results in the error message " Package not available in this suite."
>
>
> Could you provide an instruction on how did you browse the internet and
> enter the page https://packages.debian.org/bookworm/all/allpackages ?
>
> The webpage https://packages.debian.org/bookworm/all/allpackages , though
> it displays
> package information, shall not exist from the very beginning.
>
> I have submitted a corresponding bug report at
> https://bugs.debian.org/1059780 .
>
> (PS: To Debian Webmasters: how can I contribute to fixing bugs of
> packages.debian.org ?
> I have been looking for information since year 2019, but I am still
> clueless in 2024 today.
> The most recent attempt is
> https://lists.debian.org/debian-www/2023/12/msg00029.html .
> Any help would be appreciated.)
>
> Thanks,
> Boyuan Yang
>


Re: Package link broken

2023-12-31 Thread Boyuan Yang
Hi,

在 2023-12-31星期日的 14:26 +0100,Bram Langen写道:
> Hi,
> 
> The link to package "python3-rrdtool (1.7.2-4+b8)" from this page results in 
> the error message " Package not available in this suite." 


Could you provide an instruction on how did you browse the internet and
enter the page https://packages.debian.org/bookworm/all/allpackages ?

The webpage https://packages.debian.org/bookworm/all/allpackages , though it 
displays
package information, shall not exist from the very beginning.

I have submitted a corresponding bug report at https://bugs.debian.org/1059780 .

(PS: To Debian Webmasters: how can I contribute to fixing bugs of 
packages.debian.org ?
I have been looking for information since year 2019, but I am still clueless in 
2024 today.
The most recent attempt is 
https://lists.debian.org/debian-www/2023/12/msg00029.html .
Any help would be appreciated.)

Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part


Re: website error report

2023-12-31 Thread Holger Wansing



Am 1. Januar 2024 01:43:33 MEZ schrieb zaknic :
>Hi,
>
>Clicked on this link and error message came up.
>
>https://packages.debian.org/jessie/x11vnc

Jessie has been superseded more than 5 years ago, according to


Please upgrade to a more recent Debian release


Holger

-- 
Sent from /e/ OS on Fairphone3



Re: website error report

2023-12-31 Thread Boyuan Yang
Hi,

在 2024-01-01星期一的 00:43 +,zaknic写道:
> 
> Hi, 
> 
> Clicked on this link and error message came up.
> 
> https://packages.debian.org/jessie/x11vnc

Could you provide with the web page that shows you this link?
This information would be very important to us.

Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part


Re: Translate pages

2023-12-29 Thread Holger Wansing
Hi,

Руслан Сёмченко  wrote (Fri, 29 Dec 2023 12:39:41 
+0300):
> Good afternoon, I would like to improve the translation or improve it. I
> know 3 languages Ukrainian Russian and English

See
https://www.debian.org/international/Russian
https://www.debian.org/international/Ukrainian

You will find contact addresses there, to get in touch with the translation
teams.


Holger

-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Re: upcoming changes of the web pages /security and /lts/security

2023-12-27 Thread Thomas Lange
> On Wed, 27 Dec 2023 16:37:57 +0100, Hans Fredrik Nordhaug 
>  said:

> Hi! 
> This looks great, but it would be nice if the list of "Recent Advisories" 
(dsa.list) was translated - maybe using PO files?
> Currently the entries are untranslated. Example:

> [24 Dec 2023] T  DSA-5588-1 putty security update

> It would be nice if the date was translated and the common categories 
like "security update".

Since 2015 we only use "security update" as a common category for
almost all advisories. Here are some numbers
- 1700 x security update, 6 other categories for the DSAs
- 2504 x LTS security update and 12 others for the DLAs

In the end we would have a localized date, but the interesting
information of the advisory itself would still be in english.
It's not worth spending time into this effort and it would make
many things much more complicated.

I also think that automatic translation software nowadays can
translate the date including the name of month easily and even
translating the advisory shouldn't be hard.

--
best regards Thomas



Re: upcoming changes of the web pages /security and /lts/security

2023-12-27 Thread Hans Fredrik Nordhaug
Hi!

This looks great, but it would be nice if the list of "Recent Advisories"
(dsa.list) was translated - maybe using PO files? Currently the entries are
untranslated. Example:

[*24 Dec 2023*] T DSA-5588-1 putty *security update*

It would be nice if the date was translated and the common categories like
"security update".

Regards, Hans

man. 25. des. 2023 kl. 22:33 skrev Thomas Lange :

> Hi all,
>
> as announced on Dec 7th, I have now removed the old index.wml files
> and renamed new.wml to index.wml in the webwml repository under
> security/ and lts/security/.
>
> =
> IMPORTANT
> =
> Now the security team and the LTS team do not need to manually prepare
> a .wml and .data file for each advisory.
> Please stop creating those files for new advisories.
> =
>
> For the translators:
> Please stop translating old advisories.
> We still have to adjust the translation headers because of the
> renaming from new.wml to index.wml.
>
> A hint for the languages which did not had a translation for new.wml
> until now. Here are some more infos, how I created the new.wml files:
>
>   english/security/new.wml is a copy of english/security/index.wml with
> some changes.
>   You will see the change history (including a rename from dsa.wml to
> new.wml) by
> $ git log -p --follow 3160b3931961~1.. index.wml
>
>   For lts/security/new.wml use
> $ git log -p --follow a1010f1cb6fd~1.. index.wml
>
>
>
> I still need to do some cleanup and check if everything works.
> The new index.wml files are not yet created yet but this will be done
> in the next hours.
>
> --
> best regards Thomas
>
>


Re: upcoming changes of the web pages /security and /lts/security

2023-12-26 Thread Salvatore Bonaccorso
Hi Thomas,

On Mon, Dec 25, 2023 at 09:14:51PM +0100, Thomas Lange wrote:
> Hi all,
> 
> as announced on Dec 7th, I have now removed the old index.wml files
> and renamed new.wml to index.wml in the webwml repository under
> security/ and lts/security/.
> 
> =
> IMPORTANT
> =
> Now the security team and the LTS team do not need to manually prepare
> a .wml and .data file for each advisory.
> Please stop creating those files for new advisories.
> =
> 
> For the translators:
> Please stop translating old advisories.
> We still have to adjust the translation headers because of the
> renaming from new.wml to index.wml.
> 
> A hint for the languages which did not had a translation for new.wml
> until now. Here are some more infos, how I created the new.wml files:
> 
>   english/security/new.wml is a copy of english/security/index.wml with some 
> changes.
>   You will see the change history (including a rename from dsa.wml to 
> new.wml) by
> $ git log -p --follow 3160b3931961~1.. index.wml
> 
>   For lts/security/new.wml use
> $ git log -p --follow a1010f1cb6fd~1.. index.wml
> 
> 
> 
> I still need to do some cleanup and check if everything works.
> The new index.wml files are not yet created yet but this will be done
> in the next hours.

Thanks for all your work on this front.

Regards,
Salvatore



Re: upcoming changes of the web pages /security and /lts/security

2023-12-26 Thread Sylvain Beucler

Hi,

On 26/12/2023 11:12, Holger Levsen wrote:

On Mon, Dec 25, 2023 at 10:56:56PM +0100, Thomas Lange wrote:

 > what do we need to do instead? :)
Nothing in the webwml repository.
The list of recent advisories on the web pages is now automatically
generated from the data from the security tracker.
It's important that the announcement mail is sent and that those lists
are updated:
https://salsa.debian.org/security-tracker-team/security-tracker/-/raw/master/data/DSA/list
https://salsa.debian.org/security-tracker-team/security-tracker/-/raw/master/data/DLA/list
That's all.


ah, very nice! & thanks for clarifying too!


https://lts-team.pages.debian.net/wiki/Development.html updated :)

Cheers!
Sylvain Beucler
Debian LTS Team



Re: upcoming changes of the web pages /security and /lts/security

2023-12-26 Thread Holger Levsen
On Mon, Dec 25, 2023 at 10:56:56PM +0100, Thomas Lange wrote:
> > what do we need to do instead? :)
> Nothing in the webwml repository.
> The list of recent advisories on the web pages is now automatically
> generated from the data from the security tracker.
> It's important that the announcement mail is sent and that those lists
> are updated:
> https://salsa.debian.org/security-tracker-team/security-tracker/-/raw/master/data/DSA/list
> https://salsa.debian.org/security-tracker-team/security-tracker/-/raw/master/data/DLA/list
> That's all.

ah, very nice! & thanks for clarifying too!


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

The devel is in the details.


signature.asc
Description: PGP signature


Re: upcoming changes of the web pages /security and /lts/security

2023-12-25 Thread Thomas Lange
> On Mon, 25 Dec 2023 21:24:19 +, Holger Levsen  
> said:

> On Mon, Dec 25, 2023 at 09:14:51PM +0100, Thomas Lange wrote:
>> Now the security team and the LTS team do not need to manually prepare
>> a .wml and .data file for each advisory.
>> Please stop creating those files for new advisories.

> what do we need to do instead? :)
Nothing in the webwml repository.
The list of recent advisories on the web pages is now automatically
generated from the data from the security tracker.
It's important that the announcement mail is sent and that those lists
are updated:

https://salsa.debian.org/security-tracker-team/security-tracker/-/raw/master/data/DSA/list
https://salsa.debian.org/security-tracker-team/security-tracker/-/raw/master/data/DLA/list

That's all.
-- 
regards Thomas



Re: upcoming changes of the web pages /security and /lts/security

2023-12-25 Thread Holger Levsen
On Mon, Dec 25, 2023 at 09:14:51PM +0100, Thomas Lange wrote:
> Now the security team and the LTS team do not need to manually prepare
> a .wml and .data file for each advisory.
> Please stop creating those files for new advisories.

what do we need to do instead? :)


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

Klimakatastrophe bedeutet kompletter sozialer Kollaps.


signature.asc
Description: PGP signature


Re: upcoming changes of the web pages /security and /lts/security

2023-12-25 Thread Thomas Lange
Hi all,

as announced on Dec 7th, I have now removed the old index.wml files
and renamed new.wml to index.wml in the webwml repository under
security/ and lts/security/.

=
IMPORTANT
=
Now the security team and the LTS team do not need to manually prepare
a .wml and .data file for each advisory.
Please stop creating those files for new advisories.
=

For the translators:
Please stop translating old advisories.
We still have to adjust the translation headers because of the
renaming from new.wml to index.wml.

A hint for the languages which did not had a translation for new.wml
until now. Here are some more infos, how I created the new.wml files:

  english/security/new.wml is a copy of english/security/index.wml with some 
changes.
  You will see the change history (including a rename from dsa.wml to new.wml) 
by
$ git log -p --follow 3160b3931961~1.. index.wml

  For lts/security/new.wml use
$ git log -p --follow a1010f1cb6fd~1.. index.wml



I still need to do some cleanup and check if everything works.
The new index.wml files are not yet created yet but this will be done
in the next hours.

-- 
best regards Thomas



Re: Continuous updates on linux kernel

2023-12-15 Thread Holger Wansing
Hi,

Am 15. Dezember 2023 19:39:31 MEZ schrieb Gianfranco 
:
>Good morning, today I downloaded the kernel update to 
>linux-image-6.1.0-16-amd64, a few days ago to inux-image-6.1.0-15-amd64 and a 
>short time before to inux-image-6.1.0-14-amd64 which was then also removed 
>from https://packages.debian.org/bookworm/kernel/
>
>Is there any problem? Something we should know about?

sorry, this mailinglist is for maintaining the website, not for user support.

See  instead.


Holger



-- 
Sent from /e/ OS on Fairphone3



Re: update entries of debian(ports) architectures on page

2023-12-13 Thread Boyuan Yang
Hi,

在 2023-08-26星期六的 12:22 +0800,Bo YU写道:
> Hi,
> 
> Maybe you have know the news loong64 has be added into debian-ports[0]
> but I noticed the page does not to be refreshed for loong64, like:
> https://packages.debian.org/unstable/cgit
> 
> So could you have a look at this?
> 
> BR,
> Bo
> 
> BTW,
> I am not sure this is right place to ask or not because I see
> 
> ```
> report bug of the site please send mail to debian-www@lists.debian.org
> ```
> [0]: https://lists.debian.org/debian-devel-announce/2023/08/msg0.html

Ping, anyone?

BTW, in the past 6 years I never really know how to get changes merged and 
deployed on
packages.debian.org. Anyone can help or point me to some guidance 
documentations?
I also have some submitted Merged Requests at
https://salsa.debian.org/webmaster-team/packages/-/merge_requests and no one is 
reviewing
them in the last 5 months.

Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part


Re: Main download button on Debian.org website returns 404

2023-12-10 Thread Holger Wansing
Hi,

Am 11. Dezember 2023 01:52:44 MEZ schrieb Davi Mello de Figueiredo 
:
>Hi,
>
>I believe this the tag `current-tiny-cd-release-filename` on the deployed
>website returns a wrong path for the main download button.
>
>```
>href="
>https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.2.0-amd64-netinst.iso;
>=> 404

Works now.
The website has been updated to reflect the point releases, that happened this 
weekend.


Holger

-- 
Sent from /e/ OS on Fairphone3



Re: upcoming changes of the web pages /security and /lts/security

2023-12-08 Thread Thomas Lange
> On Fri, 8 Dec 2023 10:27:24 -0500, Roberto C. Sánchez 
>  said:

> At what point should the LTS team stop generating these? Is that
> something that we should discontinue right away, or do wait for a formal
> announcement to let us know that these should no longer be generated
> when a DLA is released?
I will announce this to both security teams after I did the change. So
please continue preparing the .wml and .data files until you'll get
the "Stop" from me.

-- 
regards Thomas



Re: upcoming changes of the web pages /security and /lts/security

2023-12-08 Thread Roberto C . Sánchez
Hi Thomas,

[I changed lts-secur...@debian.org to debian-...@lists.debian.org since
lts-secur...@debian.org is meant only to reach members of the team
approved to deal with embargoed issues. It is not a public list like
debian-...@lists.debian.org.]

I read through this message and I am very excited about the coming
changes.

On Thu, Dec 07, 2023 at 08:38:05PM +0100, Thomas Lange wrote:
> Hi all,
> 
> in the past, all security related lists (like the N recent security
> advisories, crossreferences, RSS feeds, OVAL) were using the .wml and
> .data files which exists for each DSA and DLA. These two files are
> still created manually for each DSA and DLA.
> 
> After talking to the security team, my goal is to remove the need of
> this manuall work and generate all information automatically from the
> primary security sources from the Debian Security Tracker. This also
> makes the security information more early available to our users
> without waiting for someone to prepare the .wml and .data files.
> 
> 
> The changes will affect the webwml repository under /security/ and
> /lts/security/.
> 
Our workflow for LTS still includes manual generation of .wml and .data
files, as you note. As this is a step in the process which presents an
opportunity make mistakes, I am pleased that this is being automated.

At what point should the LTS team stop generating these? Is that
something that we should discontinue right away, or do wait for a formal
announcement to let us know that these should no longer be generated
when a DLA is released?

Regards,

-Roberto

-- 
Roberto C. Sánchez



Re: how to get more recent translations for important web pages

2023-12-08 Thread Thomas Lange
> On Thu, 7 Dec 2023 20:59:08 +0100, Holger Wansing  
> said:

> [Adding debian-www to the loop]
> Hi,

>> On the other hand, it occurred to me, if it's possible, to only change 
the
>> filename from let's say index.wml to index.wml.old instead of removing 
the 
>> file (assuming that the wml build process of the website ignores such
>> files; did not check that).
>> That would make it very easy for translators, to catch up with their 
work,
>> if they find time. 
>> Of course you might say "Hey, the file is not lost, we have a git repo
>> here! No need for such trick." 
>> That's of course correct, but translators might not be as familiar with
>> such advanced usage of git as DDs are.
>> So I think it would be worse it.
The only advantage I see, is that you see that there's an old
translation, for those were we will catch up with the renaming. In the
end the translators always have to use git. Having an .outdated file they need 
to use
$ git mv xxx.outdated 

I we delete the file they could use a simple 2-line shell script we
provide for them:

#! /bin/bash

hash=$(git log -- $1|head -1|awk '{print $2 "~1" }')
git checkout $hash -- $1

Let's call it undo-delete 

> I have tested this for ../german/releases/trixie/installmanual.wml,
> renamed that into installmanual.outdated and that works, the page gets
> removed from the web, and otherwise no errors on the webwml build.
> So, maybe that would be a possible "solution", instead of removing the
> translation files completely?
We still have the problem, that we might have to rename ALL deleted
files. Otherwise the translators could never rely on seeing a
.outdated file. What if there's no .outdated? Then they have to parse through 
the git
log and check if there's nevertheless an old deleted translation.

One more point: Does thi work for a complete deleted subdirectory, as I did
some time ago with tamil, albanian,...

I'm not against your solution and I think we should give it a try and
then after a year see if this helps to get more recent
translations. Then we can made a new decision if we want continue this workflow.

-- 
viele Grüße Thomas



Re: how to get more recent translations for important web pages

2023-12-07 Thread Holger Wansing
[Adding debian-www to the loop]

Hi,

Holger Wansing  wrote (Sun, 3 Dec 2023 00:08:21 +0100):
> I would not vote too strict against the removal of outdated translations,
> in fact I did that some years ago for German as well, due to lack of
> manpower in the German team.
> You don't get applause for such initiative, it's an unthankful job.
> 
> That being said, I could imagine a timeframe from ~6 months for this
> to be senseful?
> 
> On the other hand, it occurred to me, if it's possible, to only change the
> filename from let's say index.wml to index.wml.old instead of removing the 
> file (assuming that the wml build process of the website ignores such
> files; did not check that).
> That would make it very easy for translators, to catch up with their work,
> if they find time. 
> Of course you might say "Hey, the file is not lost, we have a git repo
> here! No need for such trick." 
> That's of course correct, but translators might not be as familiar with
> such advanced usage of git as DDs are.
> So I think it would be worse it.

I have tested this for ../german/releases/trixie/installmanual.wml,
renamed that into installmanual.outdated and that works, the page gets
removed from the web, and otherwise no errors on the webwml build.
So, maybe that would be a possible "solution", instead of removing the
translation files completely?


Holger

-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Overhaul of releases//index (Re: how to get more recent translations for important web pages)

2023-12-06 Thread Holger Wansing
[Adding debian-ww to the loop]

Hi,

Holger Wansing  wrote (Sun, 3 Dec 2023 00:08:21 +0100):
> And for usual changings:
> I think we need to much resources (on the English side as well as on
> translator's) for repeating tasks like pages under ../releases.
> Basically, the files under 
> ../releases/buster
> ../releases/bullseye
> ../releases/bookworm
> ../releases/trixie
> are nearly the same, but with small differences in codenames, release
> dates and such.
> But nevertheless all those pages need to be touched by translators
> many times over the release cycle (if translators want to keep their
> files up-to-date).
> Even pages for oldstable need translator's time to be up-to-date
> (I just spotted exactly this situation for Bullseye today!)
> And remember: if one changes a page in English, that might imply work for 
> dozens of translators!!!
> 
> 
> I can think about changing the whole mechanism behind these pages, to create
> a basis, which has content for all situations during the whole release
> lifetime, without any need to change that underway:
> 
> So, we would create such "template" for English, translators work on 
> translating the relevant parts and then they have their template for
> their language as well, and when a new release comes, we just run a
> sed script, which changes the codenames from the stable one to oldstable,
> testing to stable, and so on. The release dates need to be adjusted, 
> but with that most of the work should be done.
> Another relevant situation is when LTS period starts or ends for a
> release, but I imagine we can get this done be just changing an entity,
> which is used for all languages, and we are done.

I have a tested and working proposal ready now (here for 
../releases/bookworm/index).

It contains six sets of different content, which makes it possible, to
dynamically enable the needed content for the respective situations over
the whole release cycle.

That all is controlled via these six variables:

--
# Is -2 the current release ? (yes/no)


# Is -1 the current release ? (yes/no)


# Is  the current release ? (yes/no)


# Is +1 the current release ? (yes/no)


# Security updates discontinued for current release ? (yes/no)


# Has LTS period begun for current release ? (yes/no)

--

Apart from that, I have converted the hardcoded dates for "initial release
of Debian 12.0" and "security updates discontinued for Bookworm" into
tags defined in ./english/template/debian/release_info.wml, so no need to
change the index file, when the time for those change comes, just change
the tag.



I filed this as MR:
https://salsa.debian.org/webmaster-team/webwml/-/merge_requests/944


Holger

-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Re: plan to remove translations with only few pages

2023-11-28 Thread Thomas Lange
Hi,

as announced, I now have removed the web page translations for

Esperanto (eo)
Armenian (hy)
Hebrew (he)
Lithuanian (lt)
Slovene (sl)
Tamil (ta)
Albanian (sq)

because they had very few or no translation and no recent translation activity.
I've ignored changes like http -> https and similar.

> tor. 16. nov. 2023 kl. 05:00 skrev Thomas Lange :

> [cut]
> I suggest to have a bare minimum of pages translated, for e.g. the
> startpage and some pages on level 2 of the web hierarchy, maybe the
> download page should be mandatory.

I think the active members of the i18n list should decide on their own
what rules they like to propose for a new translation of the web pages
to make it into the web repository. See my ideas above.

In the past (from 2004 to 2008) we already had some rules that removed
outdated translations. Search in the git logs for
"Automatic purge of file outdated for six months"
I like this idea, but I think this is too fast, and it should depend
on how much content was changed on this web page.

-- 
regards Thomas



Re: Adding /home encryption by default

2023-11-27 Thread Shlomi Fish
hi,

On Mon, 27 Nov 2023 12:01:56 +
System Administrator  wrote:

> Good morning, everyone. 
> 
>  
> We would like to add support for /home encryption by default in the testing
> version of the next Debian.
>

-1. 

count me out:

https://www.shlomifish.org/philosophy/philosophy/putting-cards-on-the-table-2019-2020/indiv-nodes/fear-is-path-to-
dark-side.xhtml

> as we want to introduce more settings to the Gnome Control Center such as
> Biometric Login on the Users section, 2FA system, Recovery Section, Active
> Directory Section and other Enterprise features for Debian System 
> 
>  
> Anyone interested in joining our team?
> 
>  
>  
> Hirech Baghdad Belkheir 
> 
> Atlanexis Inc
> 
>  



-- 

Shlomi Fish   https://www.shlomifish.org/
Original Riddles - https://www.shlomifish.org/puzzles/

There are two types of command interfaces: good interfaces and user interfaces.
— https://en.wikiquote.org/wiki/Daniel_J._Bernstein

Please reply to list if it's a mailing list post - https://shlom.in/reply .



Re: Bug#932957: New theme for docs in reStructuredText (was: Re: Bug#932957: #932957 Please migrate Release Notes to reStructuredText)

2023-11-24 Thread Holger Wansing


Holger Wansing  wrote (Fri, 24 Nov 2023 22:49:47 +0100):
> I used the alabaster theme, which is the default theme in Sphinx, and 
> set some configuration options in conf.py, to adapt some details. That's all.
> 
> So no need to create a new theme IMO.
> 
> Just set the appropriate options in the manual, and build it.

I have switched trixie's release-notes to this new theme, and the result 
is now visible on www.debian.org/releases/trixie/release-notes.

I noticed, that the links to the previous and next chapter at the top
and the bottom of the pages are missing.

Some research showed, that the reason for this is the sphinx version on
www-master, which is a bullseye system.
Starting with the sphinx version in bookworm, those links are supported.
So this will start working, when wolkenstein will get updated to bookworm.

Moreover, I changed the Debian logo to include the document name (here:
"Release-Notes"), to have that information available on every page of the
release-notes (at the top).


Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Re: Bug#932957: New theme for docs in reStructuredText (was: Re: Bug#932957: #932957 Please migrate Release Notes to reStructuredText)

2023-11-24 Thread Holger Wansing
[ Re-sending message; first attempt from smartphone dropped some recipients, 
sorry ]


Am 24. November 2023 10:50:19 MEZ schrieb Laura Arjona Reina 
:
>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 used the alabaster theme, which is the default theme in Sphinx, and 
set some configuration options in conf.py, to adapt some details. That's all.

So no need to create a new theme IMO.

Just set the appropriate options in the manual, and build it.


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



New theme for docs in reStructuredText (was: Re: Bug#932957: #932957 Please migrate Release Notes to reStructuredText)

2023-11-24 Thread Laura Arjona Reina

Hello Holger


And since there has been a call for a Debian theme for Sphinx (see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053549), a proposal
for that can be found at
https://people.debian.org/~holgerw/sphinx-theme-for-debian/alabaster/release-notes/
(for those, who are uncomfortable with the greenish theme).


I've had a quick look at the theme 
inhttps://people.debian.org/~holgerw/sphinx-theme-for-debian/alabaster/release-notes/
  and looks very nice both in my computer and my phone, and I think it's a good 
improvement for the current theme. Thank you *very much*.

I don't know which is the better way forward, maybe add a repo for the theme in 
the ddp-team umbrella, and then file a bug for every documentation manual using 
Sphinx, suggesting including it?

I also know there are some other bugs related to Debian Documentation using 
Sphinx (search box, javascript-related issues) but it's hard for me to find an 
enough-long chunk of time to look at them, apologies.

Kind regards,
--

Laura Arjona Reina
https://wiki.debian.org/LauraArjona


Re: po statistics

2023-11-23 Thread Thomas Lange
Hi all,

thanks for all the feedback. It seems that there's more work to do
than I've expected. Currently I will not work on fixing the po
statistics, because I want to concentrate on the security pages.
So, if anyone else likes to work on this, feel free to do so.

-- 
regards Thomas



Re: Bug#932957: #932957 Please migrate Release Notes to reStructuredText

2023-11-22 Thread Holger Wansing
Hi again,

Holger Wansing  wrote (Mon, 13 Nov 2023 11:19:07 +0100):
> Time for a status update:
> Since the new release-notes itself are now being built on www-master (based
> on Sphinx), some changings were needed for the webpage (currently 
> www.debian.org/releases/testing/releasenotes), because we no longer have
> separate release-notes for the different release-archs.
> 
> I did that yesterday, let's say as a proposal.
> 
> Previously, there was some sort of black magic (or maybe it's perl), 
> which automatically creates a table with all architectures, languages,
> and output formats of the r-n.
> Changing this mechanism to leave out the architecture part is out of my
> skills, but I managed to copy (and adapt) the logic which is being used in 
> the debian.org/doc part of the website, to generate the list of available 
> languages and formats for the different manuals there.
> 
> It looks fine IMO, and it also works. However new languages are not 
> displayed automatically, so compared to the old mechanism there might
> be some handwork needed at some point (but rare I guess).
> 
> 
> @webmaster, @release-team, @ddp-team: what do you think? Would this
> proposal be acceptable to you for the new release-notes (trixie and later)?

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).


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Re: po statistics

2023-11-20 Thread Helge Kreutzmann
Hello,
On Mon, Nov 20, 2023 at 01:41:04PM +0100, Laura Arjona Reina wrote:
> El 20/11/23 a las 10:43, Thomas Lange escribió:
> > I'm still not sure which of the languages we need or which are just
> > bugs in packages. Or do we have bug in the scripts, that generat this
> > language list?
> > What about the AA_BB and AA@somestring languages?
> > 
> > For e.g. I wonder why we have international/l10n/po/man_DE
> > which links only to this po file:
> > https://i18n.debian.org/material/po/unstable/main/i/i2p/installer/resources/locale-man/i2p_0.9.48-1.1_man_de.po.gz
> > 
> > This po file cleary says
> > "Language: de\n"
> > Why is the language then called man_DE and not just "de"? Is this a
> > bug in our scripts?
> 
> I think this is a bug, because those po files are named man_ because they
> are translations of the manual pages, not because of the Mandingo language.
> 
> "Similar" thing happens with
> https://www.debian.org/international/l10n/po/bos_DE (and all other bos_XX
> links in https://www.debian.org/international/l10n/po/): they are
> translations files of the boswars package, having two translations
> templates, one named     boswars_version_xx.po.gz and another one named 
> boswars_version_bos_xx.po.gz, so that "bos" is misdetected as Bosnian
> language.

Ideally these would be fixed upstream, but 2nd best option would be to
filter them, i.e. if it is invalid combination (as shown) then simply
simply present it unter "DE" (in your example).

This, howeve, would require a list of all valid combination. I don't
know if such a list exists.

Greetings

Helge

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature


Re: po statistics

2023-11-20 Thread Laura Arjona Reina

Hello

El 20/11/23 a las 10:43, Thomas Lange escribió:

Hi

I'm still not sure which of the languages we need or which are just
bugs in packages. Or do we have bug in the scripts, that generat this
language list?
What about the AA_BB and AA@somestring languages?

For e.g. I wonder why we have international/l10n/po/man_DE
which links only to this po file:
https://i18n.debian.org/material/po/unstable/main/i/i2p/installer/resources/locale-man/i2p_0.9.48-1.1_man_de.po.gz

This po file cleary says
"Language: de\n"
Why is the language then called man_DE and not just "de"? Is this a
bug in our scripts?


I think this is a bug, because those po files are named man_ because 
they are translations of the manual pages, not because of the Mandingo 
language.


"Similar" thing happens with 
https://www.debian.org/international/l10n/po/bos_DE (and all other 
bos_XX links in https://www.debian.org/international/l10n/po/): they are 
translations files of the boswars package, having two translations 
templates, one named     boswars_version_xx.po.gz and another one named  
boswars_version_bos_xx.po.gz, so that "bos" is misdetected as Bosnian 
language.


I don't know *where* is the bug, though: it can be in the i2p package 
because of wrong structure or naming o files (sorry, I don't know the 
related policy), in the l10n scripts* that gather the material 
(https://salsa.debian.org/l10n-team/dl10n/) or in our code that process 
that data in webwml repo. Hence I'm CC'ing debian-i18n and 
debian-l10n-devel for the case anybody knows and it's easy to fix. If 
not, a quick workaround could be to exclude the problematic packages 
from our stats (exclude them from the dl10n scripts so no material is 
generated).


Kind regards,

--
Laura Arjona Reina
https://wiki.debian.org/LauraArjona


  1   2   3   4   5   6   7   8   9   10   >