Checksum of release 2.23.0 does not seem to be correct

Hi, I downloaded log4j 2.23.0 from https://logging.apache.org/log4j/2.x/download.html Specifically I downloaded https://www.apache.org/dyn/closer.lua/logging/log4j/2.23.0/apache-log4j-2.23.0-bin.zip The checksum file https://www.apache.org/dist/logging/log4j/2.23.0/apache-log4j-2.23.0-bin.zip.

Re: Checksum of release 2.23.0 does not seem to be correct

Hi Piers, On Fri, 1 Mar 2024 at 13:33, Piers Uso Walter wrote: > I downloaded log4j 2.23.0 from > https://logging.apache.org/log4j/2.x/download.html > Specifically I downloaded > https://www.apache.org/dyn/closer.lua/logging/log4j/2.23.0/apache-log4j-2.23.0-bin.zip > > The checksum file > http

Re: Checksum of release 2.23.0 does not seem to be correct

Hi Piotr, Thanks for the quick response. And yes, everything is OK on your side. I did indeed somehow manage to download the HTML file as the zip archive. That explains why the checksum was wrong. How embarrassing:-( With kind regards Piers > Am 01.03.2024 um 13:55 schrieb Piotr P. Karwasz :

[VOTE] Release Apache Log4net 2.0.16

Hi all This is the vote to release Apache log4net version 2.0.16 Website: https://logging.staged.apache.org/log4net/release/release-notes.html GitHub: https://github.com/apache/logging-log4net GitHub release (pre-release): https://github.com/apache/logging-log4net/releases/tag/2.0.16-rc1

Re: [VOTE] Release Apache Log4net 2.0.16

Davyd, I am afraid it cannot qualify an official vote if the [source] distribution artifacts are missing. This is the whole point of the ASF release ceremony. Binary artifacts, Website, GitHub, VCS, Nuget, etc. can be the most important mediums for you and/or the project, though they are irrelevant

Re: Checksum of release 2.23.0 does not seem to be correct

Hi Piers, On Fri, 1 Mar 2024 at 14:14, Piers Uso Walter wrote: > Thanks for the quick response. > And yes, everything is OK on your side. > > I did indeed somehow manage to download the HTML file as the zip archive. > That explains why the checksum was wrong. > > How embarrassing:-( I did the ex

Re: Checksum of release 2.23.0 does not seem to be correct

> On Mar 1, 2024, at 6:55 AM, Piotr P. Karwasz wrote: > > Hi Piers, > > On Fri, 1 Mar 2024 at 14:14, Piers Uso Walter wrote: >> Thanks for the quick response. >> And yes, everything is OK on your side. >> >> I did indeed somehow manage to download the HTML file as the zip archive. >> That e

Re: [VOTE] Release Apache Log4net 2.0.16

Hi Volkan That was my whole point with the question on my release vote: I have put things in svn, bit I'm not seeing them at the url you've posted. I assume I've done something wrong, but I don't know what and need someone to help. I must admit my svn-fu is rubbish so perhaps I just messed up

Re: Checksum of release 2.23.0 does not seem to be correct

Hi Ralph, On Fri, 1 Mar 2024 at 15:33, Ralph Goers wrote: > > Maybe we should replace the links on the web page? There are actually > > people (like me and probably you) that don't download everything > > through the browser. > > What do you think? > > Replace them with what? We are required to u

Uploading release distribution for review (Was: [VOTE] Release Apache Log4net 2.0.16)

Davyd, assuming you have `svn` in the command line, following should get the job done: # Checkout the `dev` distribution repository svn co https://dist.apache.org/repos/dist/dev/logging logging-dist-dev cd logging-dist-dev # Delete old distribution files svn rm log4net # Add the new distribution

Re: Uploading release distribution for review (Was: [VOTE] Release Apache Log4net 2.0.16)

Hi Volkan Thanks for taking the time to explain (: This is pretty-much what I did, as per step 16 of https://github.com/apache/logging-log4net/blob/master/doc/RELEASING.md - unless there's a typo I've made somewhere or something like that. That's why I'm confused as to why I can't see the a