Bug#863647: marked as done (use LDAP to generate www.debian.org/intro/organization page (or at least, part of it))
Your message dated Wed, 24 Apr 2024 22:26:59 +0200
with message-id <26153.27411.53763.690...@cs.uni-koeln.de>
and subject line closing
has caused the Debian Bug report #863647,
regarding use LDAP to generate www.debian.org/intro/organization page (or at
least, part of it)
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.)
--
863647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: www.debian.org
Severity: wishlist
We have some info stored in the Debian LDAP, about people belonging to
groups, that could be used to generate (and keep updated
automatically) the /intro/organization page.
Adapting a script written by Paul Wise (thanks!), and running it from
a debian.org machine (e.g. people.debian.org), I can obtain the list
of, for example, Publicity Team delegates (see attached script
ldap_dump.py)..
We would need to know the gid or supplementaryGid of each of the teams
that we want to generate.
Then we would need to compare the list of groups/people that we can
obtain from LDAP, with the current list that we have in
/intro/organization. To take into account: some teams have no
corresponding LDAP group, e.g. Technical Committee.
Then, adapt the current organization.data file to insert the
corresponding scripting parts for the data that we obtain via LDAP
(not sure if we can insert Python scripts in the wml files, but
probably we can write similar code in Perl).
Leaving this here for now, I may return to advance this later in the
year, if nobody beats me to it.
Cheers
--
Laura Arjona Reina
https://wiki.debian.org/LauraArjona
#!/usr/bin/python
# Author: Paul Wise
# Author: Laura Arjona Reina
# License: MIT/Expat
import os
import sys
import ldap
aliases = []
l = ldap.initialize('ldaps://db.debian.org')
r = l.search_s('dc=debian,dc=org',ldap.SCOPE_SUBTREE,'(supplementaryGid=publicity)',['gecos'])
aliases.append('Publicity Team')
for dn,e in r:
aliases.append(' Member: %s' % e['gecos'][0])
del l, r
with open(os.path.expanduser('./debian-teams'), 'w') as f:
f.write('\n'.join(aliases))
--- End Message ---
--- Begin Message ---
Obtaining the data from LDAP does not help, because also the LDAP data
is not up to date. We often have inactive members belonging to some
team/LDAP group for years after they went inactive.
Paul mentioned in another bug that some team members (I think it was
the wiki team) were not added to the wiki contact mail alias. So
having them in a list makes no sense.
--
regards Thomas--- End Message ---
Bug#821096: marked as done (filenames of generated by parse-advisory.pl and parse-dls.pl files should include the revision number)
Your message dated Wed, 24 Apr 2024 22:18:06 +0200 with message-id <26153.26878.499420.858...@cs.uni-koeln.de> and subject line closing has caused the Debian Bug report #821096, regarding filenames of generated by parse-advisory.pl and parse-dls.pl files should include the revision number 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.) -- 821096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: www.debian.org Severity: normal Dear Maintainer, Security Team issues revisions of DSAs, e. g. DSA-3485-1 and DSA-3485-2, but currently parse-advisory cannot handle revisions file-wise. That is, it creates dsa-3485.wml for the original DSA, but it is not so easy to create a revision when the latter is issued, because file dsa-3485.wml already exists. So, someone needs to, say, rename dsa-3485.wml, use parse-advisory to create a source page for the revision, then rename both wml files: the original DSA and its revision. To avoid that parse-advisory should add the revision number to filename of generated wml file. Sometimes (like in dsa-3485-1 and dsa-3485-2 case) it is not so easy to change the text of dsa-3485 in such a way that it would include both the original DSA and its revision, so it's better to store them in separate files. Cheers! Lev Lamberov -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- These scripts are not used any more. -- regards Thomas--- End Message ---
Bug#583781: marked as done (Please provide only one item by DPN issue for News/weekly RSS)
Your message dated Wed, 24 Apr 2024 22:16:54 +0200 with message-id <26153.26806.525741.717...@cs.uni-koeln.de> and subject line closing has caused the Debian Bug report #583781, regarding Please provide only one item by DPN issue for News/weekly RSS 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.) -- 583781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: www.debian.org Severity: wishlist Heya, it would be great to have a RSS and/or Atom feed for the news section of the Debian homepage (and possibly a different one for the advisories listed there too). I know it's stuff one can already follow via mailing list(s), but a lot of people these days uses feeds directly, I think we can offer a service to more users offering both. Now, I've written before helpers that generate RSS, and I'm willing to contribute one for this specific case. Nevertheless the README files under News/ are a bit scary in stating that only press/webmasters should fiddle with them, so I'm looking for advice. Where can a script that generates RSS/Atom (and commits it?) can be hooked at in the process of maintaining the HTML listing of news on the website homepage? An alternative less invasive solution would be to have a separate script elsewhere checking out periodically from CVS the News/ directory, generate the RSS feed, and have it referenced from the homepage. That would work, wouldn't be that much at stake with feed technology (which does pull anyhow), but somehow doesn't feel "right". Any hint? Thanks for maintaining www.d.o! -- System Information: Debian Release: squeeze/sid 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.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- Just closing this very old wishlist. We only had discussion about it, but noone worked on this. -- regards Thomas--- End Message ---
Bug#905422: marked as done (Avoid hard-coding the version numbers of FHS)
Your message dated Wed, 24 Apr 2024 22:05:51 +0200 with message-id <26153.26143.765941.208...@cs.uni-koeln.de> and subject line closing has caused the Debian Bug report #905422, regarding Avoid hard-coding the version numbers of FHS 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.) -- 905422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: www.debian.org Severity: normal Dear debian website developers, New Debian Policy has updated Debian's FHS version from v2.3 to v3.0. The corresponding FHS version under www.debian.org needs to be updated too. https://www.debian.org/doc/devel-manuals#policy -- Regards, Boyuan Yang -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE=zh_CN:zh (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- The current FHS version is only used once in this document. I see no problem in not using a variable for that. -- regards Thomas--- End Message ---
Bug#612274: marked as done (www.debian.org: RSS feed for News contains same timestamp for multiple entries posted on the same day)
Your message dated Wed, 24 Apr 2024 21:56:00 +0200 with message-id <26153.25552.726089.531...@cs.uni-koeln.de> and subject line closing has caused the Debian Bug report #612274, regarding www.debian.org: RSS feed for News contains same timestamp for multiple entries posted on the same day 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.) -- 612274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612274 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: www.debian.org Severity: normal The RSS feed at http://www.debian.org/News/news contains the same timestamp for 2 news posted the same day. This is somewhat annoying for tools like feed2omb which rely on the timestamp of the last article they forwarded to decide whether something needs to be forwarded or not. They will forward the first one and then consider the second one to not be newer (this is because I don't allow feed2omb to post 2 articles in the same run). It would thus be nice to use different timestamps. Just increment the timestamp arbitrarily in this situation. Cheers, -- System Information: Debian Release: 6.0 APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'stable'), (150, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- This bug has no activity since many years. It seems that it's not a problem for anyone these days. -- regards Thomas--- End Message ---
Bug#872944: marked as done (www.debian.org: Remove JavaScript from Policy Manual published on web mirrors)
Your message dated Wed, 24 Apr 2024 21:52:17 +0200 with message-id <26153.25329.121588.795...@cs.uni-koeln.de> and subject line closing has caused the Debian Bug report #872944, regarding www.debian.org: Remove JavaScript from Policy Manual published on web mirrors 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.) -- 872944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: www.debian.org Severity: important Hello webmasters, The Debian Policy Manual just changed its HTML output and while the HTML has published, the CSS and included images have not. Looking at [1], the CSS and included images should have been published because they're still installed to /usr/share/doc/debian-policy/policy.html/. So I think this is a problem on your end rather than ours. Please do reassign this bug if I'm wrong about that, and thanks in advance for your help. [1] https://anonscm.debian.org/cgit/debwww/cron.git/tree/parts/7doc -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Sean Whitton signature.asc Description: PGP signature --- End Message --- --- Begin Message --- This bug is about removing JS from the policy manual. This is not needed, therefore closing. If you like to discuss if a single page version is needed, please reopen #877337. -- viele Grüße Thomas--- End Message ---
Re: upgrade procedure instructs users to run “apt update” but neglects upgrading
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
Processed: reassign 1069758 to release-notes
Processing commands for cont...@bugs.debian.org: > # www.debian.org/.../release-notes/... > reassign 1069758 release-notes Bug #1069758 [www.debian.org] www.debian.org: upgrade procedure instructs users to run “apt update” but neglects upgrading Bug reassigned from package 'www.debian.org' to 'release-notes'. Ignoring request to alter found versions of bug #1069758 to the same values previously set Ignoring request to alter fixed versions of bug #1069758 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1069758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#863579: marked as done (www.debian.org: include wiki team in /intro/organization)
Your message dated Wed, 24 Apr 2024 16:18:58 +0200 with message-id <26153.5330.271446.253...@cs.uni-koeln.de> and subject line closing has caused the Debian Bug report #863579, regarding www.debian.org: include wiki team in /intro/organization 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.) -- 863579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: www.debian.org Severity: normal It would be nice to include the wiki team members in /intro/organization, as well as the mail contact. Nor https://wiki.debian.org/DebianWiki/Contact nor https://wiki.debian.org/Teams/DebianWiki list people names, so people in the wiki team should say if they want to appear there and provide the list of names, positions, and mail addresses to list. -- System Information: Debian Release: 8.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- IMO it's not needed and the discussion also shows that the LDAP information is not up to date. So having a list of people which are not receiving the emails makes no sense. And my experiences clearly shows that updating such a list is not done. This is similar to experiences with lists in /intro/organisation Therefore closing. -- regards Thomas--- End Message ---
webwml failed
/srv/www.debian.org/cron/log/wml_run.log-make -C 2022 install /srv/www.debian.org/cron/log/wml_run.log-make[3]: Entering directory '/srv/www.debian.org/webwml/dutch/vote/2022' /srv/www.debian.org/cron/log/wml_run.log-make -C platforms install /srv/www.debian.org/cron/log/wml_run.log-make[4]: Entering directory '/srv/www.debian.org/webwml/dutch/vote/2022/platforms' /srv/www.debian.org/cron/log/wml_run.log-make[4]: Leaving directory '/srv/www.debian.org/webwml/dutch/vote/2022/platforms' /srv/www.debian.org/cron/log/wml_run.log-make[3]: Leaving directory '/srv/www.debian.org/webwml/dutch/vote/2022' /srv/www.debian.org/cron/log/wml_run.log-make -C 2023 install /srv/www.debian.org/cron/log/wml_run.log-make[3]: Entering directory '/srv/www.debian.org/webwml/dutch/vote/2023' /srv/www.debian.org/cron/log/wml_run.log-make -C platforms install /srv/www.debian.org/cron/log/wml_run.log-make[4]: Entering directory '/srv/www.debian.org/webwml/dutch/vote/2023/platforms' /srv/www.debian.org/cron/log/wml_run.log-make[4]: Leaving directory '/srv/www.debian.org/webwml/dutch/vote/2023/platforms' /srv/www.debian.org/cron/log/wml_run.log-make[3]: Leaving directory '/srv/www.debian.org/webwml/dutch/vote/2023' /srv/www.debian.org/cron/log/wml_run.log-make -C 2024 install /srv/www.debian.org/cron/log/wml_run.log-make[3]: Entering directory '/srv/www.debian.org/webwml/dutch/vote/2024' /srv/www.debian.org/cron/log/wml_run.log-wml -q -D CUR_YEAR=2024 -o UNDEFuNL:vote_001.nl.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.nl.html] Error 1 /srv/www.debian.org/cron/log/wml_run.log-make[3]: Leaving directory '/srv/www.debian.org/webwml/dutch/vote/2024' /srv/www.debian.org/cron/log/wml_run.log:make[2]: [../../Makefile.common:84: 2024-install] Error 2 (ignored) /srv/www.debian.org/cron/log/wml_run.log-make[2]: Leaving directory '/srv/www.debian.org/webwml/dutch/vote' /srv/www.debian.org/cron/log/wml_run.log-make -C women install /srv/www.debian.org/cron/log/wml_run.log-make[2]: Entering directory '/srv/www.debian.org/webwml/dutch/women' /srv/www.debian.org/cron/log/wml_run.log-make -C profiles install
webwml failed
/srv/www.debian.org/cron/log/wml_run.log-make -C 2022 install /srv/www.debian.org/cron/log/wml_run.log-make[3]: Entering directory '/srv/www.debian.org/webwml/dutch/vote/2022' /srv/www.debian.org/cron/log/wml_run.log-make -C platforms install /srv/www.debian.org/cron/log/wml_run.log-make[4]: Entering directory '/srv/www.debian.org/webwml/dutch/vote/2022/platforms' /srv/www.debian.org/cron/log/wml_run.log-make[4]: Leaving directory '/srv/www.debian.org/webwml/dutch/vote/2022/platforms' /srv/www.debian.org/cron/log/wml_run.log-make[3]: Leaving directory '/srv/www.debian.org/webwml/dutch/vote/2022' /srv/www.debian.org/cron/log/wml_run.log-make -C 2023 install /srv/www.debian.org/cron/log/wml_run.log-make[3]: Entering directory '/srv/www.debian.org/webwml/dutch/vote/2023' /srv/www.debian.org/cron/log/wml_run.log-make -C platforms install /srv/www.debian.org/cron/log/wml_run.log-make[4]: Entering directory '/srv/www.debian.org/webwml/dutch/vote/2023/platforms' /srv/www.debian.org/cron/log/wml_run.log-make[4]: Leaving directory '/srv/www.debian.org/webwml/dutch/vote/2023/platforms' /srv/www.debian.org/cron/log/wml_run.log-make[3]: Leaving directory '/srv/www.debian.org/webwml/dutch/vote/2023' /srv/www.debian.org/cron/log/wml_run.log-make -C 2024 install /srv/www.debian.org/cron/log/wml_run.log-make[3]: Entering directory '/srv/www.debian.org/webwml/dutch/vote/2024' /srv/www.debian.org/cron/log/wml_run.log-wml -q -D CUR_YEAR=2024 -o UNDEFuNL:vote_001.nl.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.nl.html] Error 1 /srv/www.debian.org/cron/log/wml_run.log-make[3]: Leaving directory '/srv/www.debian.org/webwml/dutch/vote/2024' /srv/www.debian.org/cron/log/wml_run.log:make[2]: [../../Makefile.common:84: 2024-install] Error 2 (ignored) /srv/www.debian.org/cron/log/wml_run.log-make[2]: Leaving directory '/srv/www.debian.org/webwml/dutch/vote' /srv/www.debian.org/cron/log/wml_run.log-make -C women install /srv/www.debian.org/cron/log/wml_run.log-make[2]: Entering directory '/srv/www.debian.org/webwml/dutch/women' /srv/www.debian.org/cron/log/wml_run.log-make -C profiles install
Erwerb Ihrer Domain
Sehr geehrte Damen und Herren, Ich bin daran interessiert, die Domain www.briefly.de zu erwerben. Bei meiner Recherche bin ich auf Ihre Website gestoßen in der Hoffnung, dass Sie mir bei meinem Anliegen behilflich sein können und ggfs. bereit sind, mich diese käuflich erwerben zu lassen. Ich freue mich auf Ihre Rückmeldung. Herzliche Grüße Kilian Lamothe -- Telefon: 0175 70 61 752
