Re: Please update Flume DOAP

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]

Re: Please update Flume DOAP

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

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

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

Please update Flume DOAP

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: [RESULT][VOTE] Move apache/log4j1 Git repo to apache/logging-log4j1 Git repo

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 !=

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

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:

Re: Multiple KEYS files

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] > -

Multiple KEYS files

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: Cannot find doap file: https://logging.apache.org/log4j/2.x/doap_log4j.rdf

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

Re: URGENT: download page has wrong links for 2.3

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: Dropping old folders from https://dist.apache.org/repos/dist/release/logging/log4j/

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

Re: URGENT: download page has wrong links for 2.3

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

URGENT: download page has wrong links for 2.3

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

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

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:

Re: [ANNOUNCE] Apache Log4j-Audit 1.0.1 released

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 >

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

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

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

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

[jira] [Commented] (LOGCXX-481) Podling is documented as graduated

[ https://issues.apache.org/jira/browse/LOGCXX-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15258086#comment-15258086 ] Sebb commented on LOGCXX-481: - I'm not sure graduation will resolve it; there will then be two podling names

[jira] [Commented] (LOGCXX-480) SVN should be migrated from incubator area

[ https://issues.apache.org/jira/browse/LOGCXX-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15257402#comment-15257402 ] Sebb commented on LOGCXX-480: - http://incubator.apache.org/projects/log4cxx.html and http

[jira] [Created] (LOGCXX-480) SVN should be migrated from incubator area

Sebb created LOGCXX-480: --- Summary: SVN should be migrated from incubator area Key: LOGCXX-480 URL: https://issues.apache.org/jira/browse/LOGCXX-480 Project: Log4cxx Issue Type: Bug

Re: [NOTICE] people.apache.org web space is moving to home.apache.org

) Is there a way to fix this? On 26 November 2015 at 19:42, sebb <seb...@gmail.com> wrote: > I was able to use sftp to copy a small site: > > http://home.apache.org/~sebb/commons-build-plugin-1.5-RC1/ > > I used the "put -r" interactive command to do so. > >

Re: [NOTICE] people.apache.org web space is moving to home.apache.org

On 6 December 2015 at 02:01, Roman Shaposhnik <ro...@shaposhnik.org> wrote: > On Sat, Dec 5, 2015 at 1:32 PM, sebb <seb...@gmail.com> wrote: >> However, I have just discovered that although SFTP has a recursive put >> command, it does not have a recursive delete.

Re: [NOTICE] people.apache.org web space is moving to home.apache.org

I was able to use sftp to copy a small site: http://home.apache.org/~sebb/commons-build-plugin-1.5-RC1/ I used the "put -r" interactive command to do so. It takes quite a while as each file is sent separately. I've not tried uploading a very large site, so I don't know if that i

[jira] [Commented] (LOG4J2-456) Please delete old releases from mirroring system

[ https://issues.apache.org/jira/browse/LOG4J2-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13847593#comment-13847593 ] Sebb commented on LOG4J2-456: - PING Please delete old releases from mirroring system

[jira] [Commented] (LOG4J2-456) Please delete old releases from mirroring system

[ https://issues.apache.org/jira/browse/LOG4J2-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13847691#comment-13847691 ] Sebb commented on LOG4J2-456: - Logging is using svnpubsub, so it's just a question of tidying

[jira] [Resolved] (LOG4J2-456) Please delete old releases from mirroring system

[ https://issues.apache.org/jira/browse/LOG4J2-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved LOG4J2-456. - Resolution: Fixed Please delete old releases from mirroring system

[jira] [Created] (LOG4J2-456) Please delete old releases from mirroring system

Sebb created LOG4J2-456: --- Summary: Please delete old releases from mirroring system Key: LOG4J2-456 URL: https://issues.apache.org/jira/browse/LOG4J2-456 Project: Log4j 2 Issue Type: Bug

[jira] [Created] (LOG4NET-410) Please delete old releases from mirroring system

Sebb created LOG4NET-410: Summary: Please delete old releases from mirroring system Key: LOG4NET-410 URL: https://issues.apache.org/jira/browse/LOG4NET-410 Project: Log4net Issue Type: Bug

[jira] [Created] (LOG4PHP-212) Please delete old releases from mirroring system

Sebb created LOG4PHP-212: Summary: Please delete old releases from mirroring system Key: LOG4PHP-212 URL: https://issues.apache.org/jira/browse/LOG4PHP-212 Project: Log4php Issue Type: Bug

[jira] [Closed] (LOG4PHP-212) Please delete old releases from mirroring system

[ https://issues.apache.org/jira/browse/LOG4PHP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb closed LOG4PHP-212. Very prompt, thanks! Please delete old releases from mirroring system

[jira] [Commented] (LOG4J2-309) Duplicate LICENSE NOTICE files

[ https://issues.apache.org/jira/browse/LOG4J2-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13714676#comment-13714676 ] Sebb commented on LOG4J2-309: - AFAIK it's the remote-resources plugin that causes the problem

[jira] [Updated] (LOG4J2-309) Duplicate LICENSE NOTICE files

[ https://issues.apache.org/jira/browse/LOG4J2-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated LOG4J2-309: Description: The source archive apache-log4j-2.0-beta8-src.zip contains at the top-level: LICENSE LICENSE.txt

[jira] [Comment Edited] (LOG4J2-309) Duplicate LICENSE NOTICE files

[ https://issues.apache.org/jira/browse/LOG4J2-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13714676#comment-13714676 ] Sebb edited comment on LOG4J2-309 at 7/21/13 11:15 AM: --- AFAIK it's

[jira] [Created] (LOG4J2-309) Duplicate LICENSE NOTICE files

Sebb created LOG4J2-309: --- Summary: Duplicate LICENSE NOTICE files Key: LOG4J2-309 URL: https://issues.apache.org/jira/browse/LOG4J2-309 Project: Log4j 2 Issue Type: Bug Reporter: Sebb

[jira] Commented: (LOG4NET-278) Type 'Common.Logging.Log4Net.Log4NetLogger' in Assembly 'Common.Logging.Log4Net, Version=1.2.0.2, Culture=neutral, PublicKeyToken=af08829b84f0328e' is not marked as ser

[ https://issues.apache.org/jira/browse/LOG4NET-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12932996#action_12932996 ] Sebb commented on LOG4NET-278: -- This was not a Commons Logging issue - so moved to Log4Net