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: [log4j] `2.23.1` reproducibility failure (Was: [VOTE] Release Apache Log4j 2.23.1)
And thank you Volkan for walking me through fixing my local issue. Gary On 2024/03/06 16:22:50 Gary Gregory wrote: > The build was completed successfully. > > Gary > > On Wed, Mar 6, 2024 at 11:02 AM Gary Gregory wrote: > > > > I nuked the whole thing (rm -rf ~/.m2/repository/) for good measure > > (I'll do that once a month from now on). > > > > Building (and downloading the world)... > > > > It's made it past log4j-bom so we might be looking good... > > > > TY! > > Gary > > > > On Wed, Mar 6, 2024 at 10:33 AM Volkan Yazıcı wrote: > > > > > > Could you do `rm -rf ~/.m2/repository/org/apache/commons` and retry, > > > please? (If you compare `target/bom.xml`s you can see that your local > > > `commons-*` clones have different hashes.) > > > > > > On Wed, Mar 6, 2024 at 4:00 PM Gary Gregory > > > wrote: > > > > > > > On Wed, Mar 6, 2024 at 9:54 AM Volkan Yazıcı wrote: > > > > > > > > > > Could you share the `target/bom.xml` and > > > > > > > > https://paste.apache.org/za0k3 > > > > > > > > > `target/log4j-bom-2.23.1.buildinfo` files too, please? > > > > > > > > https://paste.apache.org/1403q > > > > > > > > Gary > > > > > > > > > > > > > > On Wed, Mar 6, 2024 at 3:35 PM Gary Gregory > > > > wrote: > > > > > > > > > > > rm -rf ~/.m2/repository/org/apache/logging/log4j/*/2.23.1* > > > > > > export NEXUS_REPO= > > > > > > > > > > https://repository.apache.org/content/repositories/orgapachelogging-1261 > > > > > > sh mvnw -Prelease verify artifact:compare > > > > > > -Dreference.repo=$NEXUS_REPO > > > > > > > > > > > > Gary > > > > > > > > > > > > On Wed, Mar 6, 2024 at 9:33 AM Volkan Yazıcı wrote: > > > > > > > > > > > > > > Which command are you exactly running? > > > > > > > > > > > > > > Could you share the `target/bom.xml` and > > > > > > `target/log4j-bom-2.23.1.buildinfo` files too, please? > > > > > > > > > > > > > > On Wed, Mar 6, 2024 at 3:28 PM Gary Gregory > > > > > > > > > > > > > wrote: > > > > > > >> > > > > > > >> Same :-( > > > > > > >> > > > > > > >> [INFO] --- bnd-baseline:7.0.0:baseline (check-api-compat) @ > > > > log4j-bom > > > > > > --- > > > > > > >> [INFO] skip project with packaging=pom > > > > > > >> [INFO] > > > > > > >> [INFO] --- artifact:3.5.0:compare (default-cli) @ log4j-bom --- > > > > > > >> [ERROR] project.build.outputTimestamp property should not be > > > > inherited > > > > > > >> but defined in POM > > > > /Users/garydgregory/rc/log4j/src/.flattened-pom.xml > > > > > > >> Downloading from reference: > > > > > > >> > > > > > > > > > > https://repository.apache.org/content/repositories/orgapachelogging-1261/org/apache/logging/log4j/log4j-bom/2.23.1/log4j-bom-2.23.1.buildinfo > > > > > > >> [INFO] Reference buildinfo file not found: it will be generated > > > > > > >> from > > > > > > >> downloaded reference artifacts > > > > > > >> Downloading from reference: > > > > > > >> > > > > > > > > > > https://repository.apache.org/content/repositories/orgapachelogging-1261/org/apache/logging/log4j/log4j-bom/2.23.1/log4j-bom-2.23.1.pom > > > > > > >> Downloaded from reference: > > > > > > >> > > > > > > > > > > https://repository.apache.org/content/repositories/orgapachelogging-1261/org/apache/logging/log4j/log4j-bom/2.23.1/log4j-bom-2.23.1.pom > > > > > > >> (12 kB at 77 kB/s) > > > > > > >> Downloading from reference: > > > > > > >> > > > > > > > > > > https://repository.apache.org/content/repositories/orgapachelogging-1261/org/apache/logging/log4j/log4j-bom/2.23.1/log4j-bom-2.23.1-cyclonedx.xml > > > > > > >> Downloaded from reference: > > > > > > >> > > > > > > > > > > https://repository.apache.org/content/repositories/orgapachelogging-1261/org/apache/logging/log4j/log4j-bom/2.23.1/log4j-bom-2.23.1-cyclonedx.xml > > > > > > >> (704 kB at 914 kB/s) > > > > > > >> [INFO] Minimal buildinfo generated from downloaded artifacts: > > > > > > >> > > > > > > > > > > /Users/garydgregory/rc/log4j/src/target/reference/log4j-bom-2.23.1.buildinfo > > > > > > >> [ERROR] sha512 mismatch log4j-bom-2.23.1-cyclonedx.xml: > > > > > > >> investigate > > > > > > >> with diffoscope > > > > > > >> > > > > target/reference/org.apache.logging.log4j/log4j-bom-2.23.1-cyclonedx.xml > > > > > > >> target/bom.xml > > > > > > >> [ERROR] Reproducible Build output summary: 1 files ok, 1 > > > > > > >> different > > > > > > >> [ERROR] see diff target/reference/log4j-bom-2.23.1.buildinfo > > > > > > >> target/log4j-bom-2.23.1.buildinfo > > > > > > >> [ERROR] see also > > > > > > >> https://maven.apache.org/guides/mini/guide-reproducible-builds.html > > > > > > >> [INFO] Reproducible Build output comparison saved to > > > > > > >> > > > > /Users/garydgregory/rc/log4j/src/target/log4j-bom-2.23.1.buildcompare > > > > > > >> [INFO] Aggregate buildcompare copied to > > > > > > >> > > > > /Users/garydgregory/rc/log4j/src/target/log4j-bom-2.23.1.buildcompare > > > > > > >> [INFO] > > > > > > > > > > > > > > > > >> [INFO] Reactor Summ
Re: [VOTE] Release Apache Log4net 2.0.16
I've failed to build probably because the machine I am doing this on is DNS locked down for security and can only access certain sites. I was able to install install-dotnet-core-sdk-1.1.ps1 but not install-net-framework-sdk-3.5.ps1 (Error 0x800F0954 in a dialog that points to https://learn.microsoft.com/en-US/troubleshoot/windows-client/application-management/dotnet-framework-35-installation-error) but I also don't know if how if this machine has enough already on top of Microsoft Windows [Version 10.0.19045.4046] My results: https://paste.apache.org/jj3c8 I rebooted and tried again with the same results. Gary On 2024/03/07 03:11:22 Robert Middleton wrote: > +1 > > Verified the following: > * apache-log4net-source-2.0.16.zip and associated sha/signature > * apache-log4net-binaries-2.0.16.zip and associated sha/signature > > It looks all good to me. > > -Robert Middleton > > On Tue, Mar 5, 2024 at 1:20 AM Ralph Goers wrote: > > > > +1 > > > > Verified signatures > > Verified hashes > > Verified License and Notice files. > > > > Note - the copyright year should be the first year the code was created. > > You can update it to include “-(currentYear}” but that is not strictly > > necessary. > > > > Ralph > > > > > On Mar 4, 2024, at 10:48 AM, Jan Friedrich wrote: > > > > > > +1 > > > > > > Unit tests on my machine were successful. > > > We integrated the new version into our test environment and all manual > > > tests were successful. > > > > > > Jan > > > > > >> +1 > > > > > >> Verified signatures. > > >> Verified hashes. > > > > > >> `NOTICE` contains 2022 as the copyright year, but I don't find it a > > >> blocker. (I have fixed it in `master`.) > > > > > >> On Fri, Mar 1, 2024 at 2:19 PM Davyd McColl wrote: > > > > > >>> 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 > > >>> > > >>> Distribution: I'm not sure - > > >>> https://dist.apache.org/repos/dist/dev/logging/log4net should have > > >>> 2.0.16 binaries and source (I've added via SVN), but I'm not seeing > > >>> them. Any help appreciated. > > >>> > > >>> > > >>> > > >>> Please have a look at the staging site & artifacts and test (if you can > > >>> - clone, `npm i`, `npm test`) > > >>> > > >>> [ ] +1, release the artifacts > > >>> > > >>> [ ] -1, don't release, because > > >>> > > >>> > > >>> (thanks Piotr: I copied most of your last VOTE mail!) > > >>> > > >>> > > >>> -d > > >>> > > >>> > > > > > >
Re: [VOTE] Release Apache Log4net 2.0.16
Hello Gary, the errors are in the examples project for .net compact framework (which is no longer supported by microsoft): C:\Users\ggregory\rc\apache-log4net-source-2.0.16\examples\netcf\1.0\Tutorials\ConsoleApp\cs\src\ConsoleApp.csdproj(23,1): error MSB4075: The project file "C:\Users\ggregory\rc\apache-log4net-source-2.0.16\examples\netcf\1.0\Tutorials\ConsoleApp\cs\src\ConsoleApp.csdproj" must be opened in the Visual Studio IDE and converted to the latest version before it can be built by MSBuild. -> This project file can only be opened by VS 2003. In the next release we will drop support for those exotic frameworks and delete the corresponding examples. I've already updated all the examples in my feature branch for this. Regards. Jan Thursday, March 7, 2024, 10:28:40 PM, you wrote: > I've failed to build probably because the machine I am doing this on is DNS > locked down for security and can only access certain sites. > I was able to install install-dotnet-core-sdk-1.1.ps1 but not > install-net-framework-sdk-3.5.ps1 (Error 0x800F0954 in a dialog that points > to > https://learn.microsoft.com/en-US/troubleshoot/windows-client/application-management/dotnet-framework-35-installation-error) > but I also don't know if how if this machine has enough already on top of > Microsoft Windows [Version 10.0.19045.4046] > My results: https://paste.apache.org/jj3c8 > I rebooted and tried again with the same results. > Gary > On 2024/03/07 03:11:22 Robert Middleton wrote: >> +1 >> Verified the following: >> * apache-log4net-source-2.0.16.zip and associated sha/signature >> * apache-log4net-binaries-2.0.16.zip and associated sha/signature >> It looks all good to me. >> -Robert Middleton >> On Tue, Mar 5, 2024 at 1:20 AM Ralph Goers >> wrote: >>> +1 >>> Verified signatures >>> Verified hashes >>> Verified License and Notice files. >>> Note - the copyright year should be the first year the code was created. >>> You can update it to include “-(currentYear}” but that is not strictly >>> necessary. >>> Ralph On Mar 4, 2024, at 10:48 AM, Jan Friedrich wrote: +1 Unit tests on my machine were successful. We integrated the new version into our test environment and all manual tests were successful. Jan > +1 > Verified signatures. > Verified hashes. > `NOTICE` contains 2022 as the copyright year, but I don't find it a > blocker. (I have fixed it in `master`.) > On Fri, Mar 1, 2024 at 2:19 PM Davyd McColl wrote: >> 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 >> Distribution: I'm not sure - >> https://dist.apache.org/repos/dist/dev/logging/log4net should have >> 2.0.16 binaries and source (I've added via SVN), but I'm not seeing >> them. Any help appreciated. >> Please have a look at the staging site & artifacts and test (if you can >> - clone, `npm i`, `npm test`) >> [ ] +1, release the artifacts >> [ ] -1, don't release, because >> (thanks Piotr: I copied most of your last VOTE mail!) >> -d
Re: [VOTE] Release Apache Log4net 2.0.16
Thanks for trying, Gary. I need to update the docs, I think, because I dropped client profile framework targets with the last release (iirc) because of that exact problem - can't install like that any more. You really just need the latest dotnet ask (8) and .net from windows features (including the option for 3.5 which says it also brings in 2) -d On 07 March 2024 23:29:08 "Gary D. Gregory" wrote: I've failed to build probably because the machine I am doing this on is DNS locked down for security and can only access certain sites. I was able to install install-dotnet-core-sdk-1.1.ps1 but not install-net-framework-sdk-3.5.ps1 (Error 0x800F0954 in a dialog that points to https://learn.microsoft.com/en-US/troubleshoot/windows-client/application-management/dotnet-framework-35-installation-error) but I also don't know if how if this machine has enough already on top of Microsoft Windows [Version 10.0.19045.4046] My results: https://paste.apache.org/jj3c8 I rebooted and tried again with the same results. Gary On 2024/03/07 03:11:22 Robert Middleton wrote: +1 Verified the following: * apache-log4net-source-2.0.16.zip and associated sha/signature * apache-log4net-binaries-2.0.16.zip and associated sha/signature It looks all good to me. -Robert Middleton On Tue, Mar 5, 2024 at 1:20 AM Ralph Goers wrote: > > +1 > > Verified signatures > Verified hashes > Verified License and Notice files. > > Note - the copyright year should be the first year the code was created. You can update it to include “-(currentYear}” but that is not strictly necessary. > > Ralph > > > On Mar 4, 2024, at 10:48 AM, Jan Friedrich wrote: > > > > +1 > > > > Unit tests on my machine were successful. > > We integrated the new version into our test environment and all manual tests were successful. > > > > Jan > > > >> +1 > > > >> Verified signatures. > >> Verified hashes. > > > >> `NOTICE` contains 2022 as the copyright year, but I don't find it a > >> blocker. (I have fixed it in `master`.) > > > >> On Fri, Mar 1, 2024 at 2:19 PM Davyd McColl wrote: > > > >>> 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 > >>> > >>> Distribution: I'm not sure - > >>> https://dist.apache.org/repos/dist/dev/logging/log4net should have > >>> 2.0.16 binaries and source (I've added via SVN), but I'm not seeing > >>> them. Any help appreciated. > >>> > >>> > >>> > >>> Please have a look at the staging site & artifacts and test (if you can > >>> - clone, `npm i`, `npm test`) > >>> > >>> [ ] +1, release the artifacts > >>> > >>> [ ] -1, don't release, because > >>> > >>> > >>> (thanks Piotr: I copied most of your last VOTE mail!) > >>> > >>> > >>> -d > >>> > >>> > > >
