FYI,

looks like this:



 

I also tried to compile, test and assemble. All works. Only the src.tgz can’t 
be built from itsself, because the extracted folder is no git repository 😊:

 

> Task :checkWorkingCopyClean

WARNING: Directory is not a valid git checkout (won't check dirty files): 
C:\Users\Uwe Schindler\Desktop\lucene-9.0.0

 

> Task :lucene:distribution:assembleSourceTgz FAILED

fatal: not a git repository (or any of the parent directories): .git

 

So all fine, unless you really, really want to have an infinite recursion 
building src.tgz from itsself. 😊

 

Uwe

 

-----

Uwe Schindler

Achterdiek 19, D-28357 Bremen

https://www.thetaphi.de

eMail: [email protected]

 

From: Uwe Schindler <[email protected]> 
Sent: Sunday, November 28, 2021 10:51 PM
To: Robert Muir <[email protected]>
Cc: [email protected]
Subject: Re: [VOTE] Release Lucene 9.0.0 RC3

 

The pax file is only in the root of the tar file next to the folder named 
"lucene-9.0.0/".

This is why I have seen it. You open the tar file and it shows up next to the 
root folder, so it was impossible to ignore. Same after extraction.

Am 28. November 2021 20:58:52 UTC schrieb Robert Muir <[email protected] 
<mailto:[email protected]> >:

On Sun, Nov 28, 2021 at 11:12 AM Uwe Schindler <[email protected] 
<mailto:[email protected]> > wrote:


 Thanks Robert!

 This is of course not a problem, but 7zip is the defacto unzipper used on 
windows nowadays, so we should be prepared because of questions.

 It's not an issue at all, the hidden file contains useful information (commit 
hash), so I don't care. I was more wondering why it was created from beginning, 
as the binary artifact doesn't have it. Dawid explained it (we create the 
archive with "git archive" command). All fine!

 πŸ‘


Yeah, I'm curious if we can 7-unzip the artifacts and compile them and
stuff?  Does it cause conflicts/problems like it does for other
projects? E.G. if you extract it with 7zip, does it build and work? Is
that how you tested the RC?

If our minimal use of pax features just create an "unnecessary file",
then it is nothing to worry about. I really do like the "git" approach
because the previous ant build had complicated logic to basically
reproduce what git "already knows".

--
Uwe Schindler
Achterdiek 19, 28357 Bremen
https://www.thetaphi.de

Reply via email to