Fwd: WARN: invalid asfext:pmc 'https://logging.apache.org/log4j/2.x/' in https://logging.apache.org/log4j/2.x/doap_log4j.rdf

2018-04-10 Thread sebb
As the subject says: the asfext:pmc value is incorrect; it must point to a PMC not a release. -- Forwarded message -- From: Projects Date: 10 April 2018 at 03:00 Subject: WARN: invalid asfext:pmc 'https://logging.apache.org/log4j/2.x/' in https://logging.apache.org/log4j/2.x/doap

Fwd: WARN: invalid asfext:pmc 'https://logging.apache.org/log4j/2.x/' in https://logging.apache.org/log4j/2.x/doap_log4j.rdf

2018-04-12 Thread sebb
Please fix this. -- Forwarded message -- From: Projects Date: 12 April 2018 at 03:00 Subject: WARN: invalid asfext:pmc 'https://logging.apache.org/log4j/2.x/' in https://logging.apache.org/log4j/2.x/doap_log4j.rdf To: Site Development WARN: invalid asfext:pmc 'https://logging.

Re: [ANNOUNCE] Apache Log4j-Audit 1.0.1 released

2018-12-13 Thread sebb
On Thu, 13 Dec 2018 at 18:55, Ralph Goers wrote: > > The Apache Log4j Audit team is pleased to announce the Log4j Audit 1.0.1 > release! > > Apache Log4j Audit is a framework for performing audit logging using a > predefined catalog of audit events. It provides a tool to create and edit > audit

Fwd: Cannot find doap file: https://logging.apache.org/log4j/2.x/doap_log4j.rdf

2021-12-15 Thread sebb
FYI -- Forwarded message - From: Projects Date: Wed, 15 Dec 2021 at 02:00 Subject: Cannot find doap file: https://logging.apache.org/log4j/2.x/doap_log4j.rdf To: Site Development URL: https://logging.apache.org/log4j/2.x/doap_log4j.rdf HTTP Error 404: Not Found Source: https://

URGENT: download page has wrong links for 2.3

2021-12-15 Thread sebb
The links for the previous release (2.3) actually point to 2.12.1 They should ideally use sha256 or sha512 and not md5 Sebb

Re: URGENT: download page has wrong links for 2.3

2021-12-15 Thread sebb
Also the section for 2.12.1 should now be removed; presumably no-one should be using it going forward? On Wed, 15 Dec 2021 at 12:30, sebb wrote: > > The links for the previous release (2.3) actually point to 2.12.1 > > They should ideally use sha256 or sha512 and not md5 > > Sebb

Re: Dropping old folders from https://dist.apache.org/repos/dist/release/logging/log4j/

2021-12-15 Thread sebb
On Wed, 15 Dec 2021 at 14:17, Gary Gregory wrote: > > It seems to me we should drop: > - 2.12.1 BTW, this is referenced from: https://logging.apache.org/log4j/log4j-2.12.2/download.html which redirects to https://logging.apache.org/log4j/log4j-2.12.1/download.html That page anyway needs an urge

Re: URGENT: download page has wrong links for 2.3

2021-12-15 Thread sebb
2 site and change > 2.12.1 back to its original state. > > Ralph > > > > On Dec 15, 2021, at 6:20 AM, sebb wrote: > > > > Also the section for 2.12.1 should now be removed; presumably no-one > > should be using it going forward? > > > > On Wed, 1

Re: Cannot find doap file: https://logging.apache.org/log4j/2.x/doap_log4j.rdf

2021-12-15 Thread sebb
OK, in the meantime please update projects.xml to remove the link On Wed, 15 Dec 2021 at 16:09, Matt Sicker wrote: > > There’s a bug in the doap plugin on certain architectures. We’ll have to look > into this to re-enable the plugin. > > — > Matt Sicker > > > On D

Multiple KEYS files

2021-12-19 Thread sebb
The logging project currently has 3 KEYS files under https://dist.apache.org/repos/dist/release/logging KEYS log4net/KEYS log4php/KEYS Ideally these should be combined at the top level and redirects added. Sebb

Re: Multiple KEYS files

2021-12-19 Thread sebb
stead. KEYS files are still needed for dormant (and archived) components. Entries in KEYS files should not be dropped once they have been used to sign a release. Sebb. [I suppose if a key is revoked, it might make sense to drop the entry, but I would check this with Infra first] > -- > Ma

Re: [RESULT][VOTE] Move apache/log4j1 Git repo to apache/logging-log4j1 Git repo

2021-12-24 Thread sebb
On Fri, 24 Dec 2021 at 17:03, Carter Kozak wrote: > > You can find the PMC list here: > https://people.apache.org/phonebook.html?pmc=logging AFAIK that uses the LDAP group. The official list is derived from committee-info.txt as shown by Whimsy: https://whimsy.apache.org/roster/committee/loggin

Re: [RESULT][VOTE] Move apache/log4j1 Git repo to apache/logging-log4j1 Git repo

2021-12-24 Thread sebb
On Fri, 24 Dec 2021 at 17:57, Vladimir Sitnikov wrote: > > 1) I stand corrected, I misinterpreted the phonebook (I watched on bold > records only), so your calculation was correct. Sorry for that. Entries in bold are ASF members. > > which was only started 19 hours ago > > "vote count != consens

Please update Flume DOAP

2024-03-07 Thread sebb
https://github.com/apache/logging-flume/blob/trunk/doap_Flume.rdf still shows the PMC as Flume; please update to show PMC Logging. Thanks, Sebb

Re: Please update Flume DOAP

2024-03-14 Thread sebb
Ping? On Thu, 7 Mar 2024 at 11:42, sebb wrote: > > https://github.com/apache/logging-flume/blob/trunk/doap_Flume.rdf > still shows the PMC as Flume; please update to show PMC Logging. > > Thanks, > Sebb

Re: Please update Flume DOAP

2024-03-14 Thread sebb
Note: this is the line that needs to be fixed: https://github.com/apache/logging-flume/blob/trunk/doap_Flume.rdf#L29 On Thu, 14 Mar 2024 at 08:57, sebb wrote: > > Ping? > > On Thu, 7 Mar 2024 at 11:42, sebb wrote: > > > > https://github.com/apache/logging-flume/b

Re: Please update Flume DOAP

2024-03-19 Thread sebb
PING - still needs to be fixed. On Fri, 15 Mar 2024 at 00:42, sebb wrote: > > Note: this is the line that needs to be fixed: > > https://github.com/apache/logging-flume/blob/trunk/doap_Flume.rdf#L29 > > On Thu, 14 Mar 2024 at 08:57, sebb wrote: > > > > Ping? >

Re: Please update Flume DOAP

2024-03-19 Thread sebb
On Tue, 19 Mar 2024 at 20:40, Jan Friedrich wrote: > > Hi Sebb, > > is this what you want? > > https://github.com/apache/logging-flume/pull/421 That is what needs to be done so that projects.a.o works properly for Flume. [It is not something that I personally want]