Re: [VOTE] Release Lucene 9.4.2 RC1

2022-11-18 Thread Michael Sokolov 
(I don't really believe the .asc files are broken; probably a local
gpg problem I don't understand)

SUCCESS! [0:44:08.338731]
+1 from me

On Fri, Nov 18, 2022 at 10:18 AM Uwe Schindler  wrote:
>
> Hi,
>
> the second build succeeded. I really think it was another job running at same 
> time that also tried to communicate with GPG and used another home dir.
>
> Log: https://jenkins.thetaphi.de/job/Lucene-Release-Tester/25/console
>
> SUCCESS! [1:43:46.817984]
> Finished: SUCCESS
>
> After jenkins finished the job it killed all child processes and all agents 
> are gone.
>
> In the meantime I also did some manual checks: Running Luke from windows with 
> whitespace in dir worked and I was able to open my test index. I also started 
> with Java 19 and --enable-preview and the Luke log showed that it uses the 
> new MMapDire impl.
>
> I correct my previous vote: ++1 to release. 
>
> Uwe
>
> Am 18.11.2022 um 16:06 schrieb Uwe Schindler:
>
> I had also seen this message. My guess: Another build was running in Jenkins 
> that also spawned an agent with different home dir! I think Robert already 
> talked about this. We should kill the agents before/after we have used them.
>
> Uwe
>
> Am 18.11.2022 um 15:47 schrieb Adrien Grand:
>
> Reading Uwe's error message more carefully, I had first assumed that the GPG 
> failure was due to the lack of an ultimately trusted signature, but it seems 
> like it's due to "can't connect to the agent: IPC connect call failed" 
> actually, which suggests an issue with the GPG agent?
>
> On Fri, Nov 18, 2022 at 3:00 PM Michael Sokolov  wrote:
>>
>> I got this message when initially downloading the artifacts:
>>
>> Downloading 
>> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db/lucene/lucene-9.4.2-src.tgz.asc
>> File: 
>> /tmp/smoke_lucene_9.4.2_858d9b437047a577fa9457089afff43eefa461db/lucene.lucene-9.4.2-src.tgz.gpg.verify.log
>> verify trust
>>   GPG: gpg: WARNING: This key is not certified with a trusted signature!
>>
>> is it related?
>>
>> On Fri, Nov 18, 2022 at 8:43 AM Uwe Schindler  wrote:
>> >
>> > The problem is: it is working like this since years - the 9.4.1 release 
>> > worked fine. No change!
>> >
>> > And I can't configure this because GPG uses its own home directory setup 
>> > by smoke tester (see paths below). So it should not look anywhere else? In 
>> > addition "gpg: no ultimately trusted keys found" is just a warning, it 
>> > should not cause gpg to exit.
>> >
>> > Also why does it only happens at the time of Maven? It checks signatures 
>> > before, too. This is why I restarted the build: 
>> > https://jenkins.thetaphi.de/job/Lucene-Release-Tester/25/console (still 
>> > running)
>> >
>> > Uwe
>> >
>> > Am 18.11.2022 um 14:21 schrieb Adrien Grand:
>> >
>> > Uwe, the error message suggests that Policeman Jenkins is not ultimately 
>> > trusting any of the keys. Does it work if you configure it to ultimately 
>> > trust your "Uwe Schindler (CODE SIGNING KEY) " key 
>> > (which I assume you would be ok with)?
>> >
>> > On Fri, Nov 18, 2022 at 2:18 PM Uwe Schindler  wrote:
>> >>
>> >> I am restarting the build, maybe it was some hickup. Interestingly it 
>> >> only failed for the Maven dependencies. P.S.: Why does it import the key 
>> >> file over and over? It would be enough to do this once at beginning of 
>> >> smoker.
>> >>
>> >> Uwe
>> >>
>> >> Am 18.11.2022 um 14:12 schrieb Uwe Schindler:
>> >>
>> >> Hi,
>> >>
>> >> I get a failure because your key is somehow rejected by GPG (Ubuntu 
>> >> 22.04):
>> >>
>> >> https://jenkins.thetaphi.de/job/Lucene-Release-Tester/24/console
>> >>
>> >> verify maven artifact sigs command "gpg --homedir 
>> >> /home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg 
>> >> --import /home/jenkins/workspace/Lucene-Release-Tester/smoketmp/KEYS" 
>> >> failed: gpg: keybox 
>> >> '/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/pubring.kbx'
>> >>  created gpg: 
>> >> /home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/trustdb.gpg:
>> >>  trustdb created gpg: key B83EA82A0AFCEE7C: public key "Yonik Seeley 
>> >> " imported gpg: can't connect to the agent: IPC connect 
>> >> call failed gpg: key E48025ED13E57FFC: public key "Upayavira 
>> >> " imported [...] gpg: key 051A0FAF76BC6507: public key 
>> >> "Adrien Grand (CODE SIGNING KEY) " imported [...] 
>> >> gpg: key 32423B0E264B5CBA: public key "Julie Tibshirani (New code signing 
>> >> key) " imported gpg: Total number processed: 62 
>> >> gpg: imported: 62 gpg: no ultimately trusted keys found
>> >> It looks like for others it succeeds? No idea why. Maybe Ubuntu 22.04 has 
>> >> a too-new GPG or it needs to use gpg2?
>> >>
>> >> -1 to release until this is sorted out.
>> >>
>> >> Uwe
>> >>
>> >> Am 17.11.2022 um 15:18 schrieb Adrien Grand:
>> >>
>> >> Please vote for release candidate 1 for Lucene 9.4.2
>> >>
>> >> The artifacts can be downloaded from:
>> >>

Re: [GitHub] [lucene] rmuir commented on pull request #11946: add similarity threshold for hnsw

2022-11-18 Thread Michael Sokolov 
What I have in mind would be to implement entirely in the
KnnVectorQuery. Since results are sorted by score, they can easily be
post-filtered there: no need to implement anything at the codec layer
I think.

On Thu, Nov 17, 2022 at 10:10 AM GitBox  wrote:
>
>
> rmuir commented on PR #11946:
> URL: https://github.com/apache/lucene/pull/11946#issuecomment-1318777402
>
>i'm also concerned about committing to providing this API for the future. 
> eventually, we'll move away from HNSW to something that actually scales, and 
> it may not support this thresholding?
>
>
> --
> This is an automated message from the Apache Git Service.
> To respond to the message, please log on to GitHub and use the
> URL above to go to the specific comment.
>
> To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
>
> For queries about this service, please contact Infrastructure at:
> us...@infra.apache.org
>
>
> -
> To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
> For additional commands, e-mail: issues-h...@lucene.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: [VOTE] Release Lucene 9.4.2 RC1

2022-11-18 Thread Uwe Schindler 

Hi,

the second build succeeded. I really think it was another job running at 
same time that also tried to communicate with GPG and used another home dir.


Log: https://jenkins.thetaphi.de/job/Lucene-Release-Tester/25/console

SUCCESS! [1:43:46.817984]
Finished: SUCCESS

After jenkins finished the job it killed all child processes and all 
agents are gone.


In the meantime I also did some manual checks: Running Luke from windows 
with whitespace in dir worked and I was able to open my test index. I 
also started with Java 19 and --enable-preview and the Luke log showed 
that it uses the new MMapDire impl.


I correct my previous vote: ++1 to release. 

Uwe

Am 18.11.2022 um 16:06 schrieb Uwe Schindler:


I had also seen this message. My guess: Another build was running in 
Jenkins that also spawned an agent with different home dir! I think 
Robert already talked about this. We should kill the agents 
before/after we have used them.


Uwe

Am 18.11.2022 um 15:47 schrieb Adrien Grand:
Reading Uwe's error message more carefully, I had first assumed that 
the GPG failure was due to the lack of an ultimately trusted 
signature, but it seems like it's due to "can't connect to the agent: 
IPC connect call failed" actually, which suggests an issue with the 
GPG agent?


On Fri, Nov 18, 2022 at 3:00 PM Michael Sokolov  
wrote:


I got this message when initially downloading the artifacts:

Downloading

https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db/lucene/lucene-9.4.2-src.tgz.asc
File:

/tmp/smoke_lucene_9.4.2_858d9b437047a577fa9457089afff43eefa461db/lucene.lucene-9.4.2-src.tgz.gpg.verify.log
    verify trust
      GPG: gpg: WARNING: This key is not certified with a trusted
signature!

is it related?

On Fri, Nov 18, 2022 at 8:43 AM Uwe Schindler 
wrote:
>
> The problem is: it is working like this since years - the 9.4.1
release worked fine. No change!
>
> And I can't configure this because GPG uses its own home
directory setup by smoke tester (see paths below). So it should
not look anywhere else? In addition "gpg: no ultimately trusted
keys found" is just a warning, it should not cause gpg to exit.
>
> Also why does it only happens at the time of Maven? It checks
signatures before, too. This is why I restarted the build:
https://jenkins.thetaphi.de/job/Lucene-Release-Tester/25/console
(still running)
>
> Uwe
>
> Am 18.11.2022 um 14:21 schrieb Adrien Grand:
>
> Uwe, the error message suggests that Policeman Jenkins is not
ultimately trusting any of the keys. Does it work if you
configure it to ultimately trust your "Uwe Schindler (CODE
SIGNING KEY) " key (which I assume you
would be ok with)?
>
> On Fri, Nov 18, 2022 at 2:18 PM Uwe Schindler 
wrote:
>>
>> I am restarting the build, maybe it was some hickup.
Interestingly it only failed for the Maven dependencies. P.S.:
Why does it import the key file over and over? It would be enough
to do this once at beginning of smoker.
>>
>> Uwe
>>
>> Am 18.11.2022 um 14:12 schrieb Uwe Schindler:
>>
>> Hi,
>>
>> I get a failure because your key is somehow rejected by GPG
(Ubuntu 22.04):
>>
>> https://jenkins.thetaphi.de/job/Lucene-Release-Tester/24/console
>>
>> verify maven artifact sigs command "gpg --homedir
/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg
--import
/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/KEYS"
failed: gpg: keybox

'/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/pubring.kbx'
created gpg:

/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/trustdb.gpg:
trustdb created gpg: key B83EA82A0AFCEE7C: public key "Yonik
Seeley " imported gpg: can't connect to the
agent: IPC connect call failed gpg: key E48025ED13E57FFC: public
key "Upayavira " imported [...] gpg: key
051A0FAF76BC6507: public key "Adrien Grand (CODE SIGNING KEY)
" imported [...] gpg: key 32423B0E264B5CBA:
public key "Julie Tibshirani (New code signing key)
" imported gpg: Total number processed: 62
gpg: imported: 62 gpg: no ultimately trusted keys found
>> It looks like for others it succeeds? No idea why. Maybe
Ubuntu 22.04 has a too-new GPG or it needs to use gpg2?
>>
>> -1 to release until this is sorted out.
>>
>> Uwe
>>
>> Am 17.11.2022 um 15:18 schrieb Adrien Grand:
>>
>> Please vote for release candidate 1 for Lucene 9.4.2
>>
>> The artifacts can be downloaded from:
>>

https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db
>>
>> You can run the smoke tester directly with this command:
>>
>> python3 -u dev-tools/scripts/smokeTestRelease.py \
>>

Re: [VOTE] Release Lucene 9.4.2 RC1

2022-11-18 Thread Kevin Risden 
I haven't looked at Lucene smoketester code but I would assume its
similar to Solr - SOLR-16132 (
https://github.com/apache/solr/commit/0cfef740617cc40585e3121e0b41e5cc8002471f)
fixed some of the gpg-agent stuff recently.

Kevin Risden


On Fri, Nov 18, 2022 at 10:07 AM Uwe Schindler  wrote:

> I had also seen this message. My guess: Another build was running in
> Jenkins that also spawned an agent with different home dir! I think Robert
> already talked about this. We should kill the agents before/after we have
> used them.
>
> Uwe
> Am 18.11.2022 um 15:47 schrieb Adrien Grand:
>
> Reading Uwe's error message more carefully, I had first assumed that the
> GPG failure was due to the lack of an ultimately trusted signature, but it
> seems like it's due to "can't connect to the agent: IPC connect call
> failed" actually, which suggests an issue with the GPG agent?
>
> On Fri, Nov 18, 2022 at 3:00 PM Michael Sokolov 
> wrote:
>
>> I got this message when initially downloading the artifacts:
>>
>> Downloading
>> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db/lucene/lucene-9.4.2-src.tgz.asc
>> File:
>> /tmp/smoke_lucene_9.4.2_858d9b437047a577fa9457089afff43eefa461db/lucene.lucene-9.4.2-src.tgz.gpg.verify.log
>> verify trust
>>   GPG: gpg: WARNING: This key is not certified with a trusted
>> signature!
>>
>> is it related?
>>
>> On Fri, Nov 18, 2022 at 8:43 AM Uwe Schindler  wrote:
>> >
>> > The problem is: it is working like this since years - the 9.4.1 release
>> worked fine. No change!
>> >
>> > And I can't configure this because GPG uses its own home directory
>> setup by smoke tester (see paths below). So it should not look anywhere
>> else? In addition "gpg: no ultimately trusted keys found" is just a
>> warning, it should not cause gpg to exit.
>> >
>> > Also why does it only happens at the time of Maven? It checks
>> signatures before, too. This is why I restarted the build:
>> https://jenkins.thetaphi.de/job/Lucene-Release-Tester/25/console (still
>> running)
>> >
>> > Uwe
>> >
>> > Am 18.11.2022 um 14:21 schrieb Adrien Grand:
>> >
>> > Uwe, the error message suggests that Policeman Jenkins is not
>> ultimately trusting any of the keys. Does it work if you configure it to
>> ultimately trust your "Uwe Schindler (CODE SIGNING KEY) <
>> uschind...@apache.org>" key (which I assume you would be ok with)?
>> >
>> > On Fri, Nov 18, 2022 at 2:18 PM Uwe Schindler  wrote:
>> >>
>> >> I am restarting the build, maybe it was some hickup. Interestingly it
>> only failed for the Maven dependencies. P.S.: Why does it import the key
>> file over and over? It would be enough to do this once at beginning of
>> smoker.
>> >>
>> >> Uwe
>> >>
>> >> Am 18.11.2022 um 14:12 schrieb Uwe Schindler:
>> >>
>> >> Hi,
>> >>
>> >> I get a failure because your key is somehow rejected by GPG (Ubuntu
>> 22.04):
>> >>
>> >> https://jenkins.thetaphi.de/job/Lucene-Release-Tester/24/console
>> >>
>> >> verify maven artifact sigs command "gpg --homedir
>> /home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg --import
>> /home/jenkins/workspace/Lucene-Release-Tester/smoketmp/KEYS" failed: gpg:
>> keybox
>> '/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/pubring.kbx'
>> created gpg:
>> /home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/trustdb.gpg:
>> trustdb created gpg: key B83EA82A0AFCEE7C: public key "Yonik Seeley <
>> yo...@apache.org>" imported gpg: can't connect to the agent: IPC connect
>> call failed gpg: key E48025ED13E57FFC: public key "Upayavira <
>> u...@odoko.co.uk>" imported [...] gpg: key 051A0FAF76BC6507: public key
>> "Adrien Grand (CODE SIGNING KEY) " imported [...]
>> gpg: key 32423B0E264B5CBA: public key "Julie Tibshirani (New code signing
>> key) " imported gpg: Total number processed: 62
>> gpg: imported: 62 gpg: no ultimately trusted keys found
>> >> It looks like for others it succeeds? No idea why. Maybe Ubuntu 22.04
>> has a too-new GPG or it needs to use gpg2?
>> >>
>> >> -1 to release until this is sorted out.
>> >>
>> >> Uwe
>> >>
>> >> Am 17.11.2022 um 15:18 schrieb Adrien Grand:
>> >>
>> >> Please vote for release candidate 1 for Lucene 9.4.2
>> >>
>> >> The artifacts can be downloaded from:
>> >>
>> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db
>> >>
>> >> You can run the smoke tester directly with this command:
>> >>
>> >> python3 -u dev-tools/scripts/smokeTestRelease.py \
>> >>
>> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db
>> >>
>> >> The vote will be open for at least 72 hours i.e. until 2022-11-20
>> 15:00 UTC.
>> >>
>> >> [ ] +1  approve
>> >> [ ] +0  no opinion
>> >> [ ] -1  disapprove (and reason why)
>> >>
>> >> Here is my +1.
>> >>
>> >> --
>> >> Adrien
>> >>
>> >> --
>> >> Uwe Schindler
>> >> Achterdiek 19, D-28357 Bremen
>> >> https://www.thetaphi.de
>> >>

Re: [VOTE] Release Lucene 9.4.2 RC1

2022-11-18 Thread Uwe Schindler 
I had also seen this message. My guess: Another build was running in 
Jenkins that also spawned an agent with different home dir! I think 
Robert already talked about this. We should kill the agents before/after 
we have used them.


Uwe

Am 18.11.2022 um 15:47 schrieb Adrien Grand:
Reading Uwe's error message more carefully, I had first assumed that 
the GPG failure was due to the lack of an ultimately trusted 
signature, but it seems like it's due to "can't connect to the agent: 
IPC connect call failed" actually, which suggests an issue with the 
GPG agent?


On Fri, Nov 18, 2022 at 3:00 PM Michael Sokolov  
wrote:


I got this message when initially downloading the artifacts:

Downloading

https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db/lucene/lucene-9.4.2-src.tgz.asc
File:

/tmp/smoke_lucene_9.4.2_858d9b437047a577fa9457089afff43eefa461db/lucene.lucene-9.4.2-src.tgz.gpg.verify.log
    verify trust
      GPG: gpg: WARNING: This key is not certified with a trusted
signature!

is it related?

On Fri, Nov 18, 2022 at 8:43 AM Uwe Schindler  wrote:
>
> The problem is: it is working like this since years - the 9.4.1
release worked fine. No change!
>
> And I can't configure this because GPG uses its own home
directory setup by smoke tester (see paths below). So it should
not look anywhere else? In addition "gpg: no ultimately trusted
keys found" is just a warning, it should not cause gpg to exit.
>
> Also why does it only happens at the time of Maven? It checks
signatures before, too. This is why I restarted the build:
https://jenkins.thetaphi.de/job/Lucene-Release-Tester/25/console
(still running)
>
> Uwe
>
> Am 18.11.2022 um 14:21 schrieb Adrien Grand:
>
> Uwe, the error message suggests that Policeman Jenkins is not
ultimately trusting any of the keys. Does it work if you configure
it to ultimately trust your "Uwe Schindler (CODE SIGNING KEY)
" key (which I assume you would be ok with)?
>
> On Fri, Nov 18, 2022 at 2:18 PM Uwe Schindler 
wrote:
>>
>> I am restarting the build, maybe it was some hickup.
Interestingly it only failed for the Maven dependencies. P.S.: Why
does it import the key file over and over? It would be enough to
do this once at beginning of smoker.
>>
>> Uwe
>>
>> Am 18.11.2022 um 14:12 schrieb Uwe Schindler:
>>
>> Hi,
>>
>> I get a failure because your key is somehow rejected by GPG
(Ubuntu 22.04):
>>
>> https://jenkins.thetaphi.de/job/Lucene-Release-Tester/24/console
>>
>> verify maven artifact sigs command "gpg --homedir
/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg
--import
/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/KEYS"
failed: gpg: keybox

'/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/pubring.kbx'
created gpg:

/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/trustdb.gpg:
trustdb created gpg: key B83EA82A0AFCEE7C: public key "Yonik
Seeley " imported gpg: can't connect to the
agent: IPC connect call failed gpg: key E48025ED13E57FFC: public
key "Upayavira " imported [...] gpg: key
051A0FAF76BC6507: public key "Adrien Grand (CODE SIGNING KEY)
" imported [...] gpg: key 32423B0E264B5CBA:
public key "Julie Tibshirani (New code signing key)
" imported gpg: Total number processed: 62
gpg: imported: 62 gpg: no ultimately trusted keys found
>> It looks like for others it succeeds? No idea why. Maybe Ubuntu
22.04 has a too-new GPG or it needs to use gpg2?
>>
>> -1 to release until this is sorted out.
>>
>> Uwe
>>
>> Am 17.11.2022 um 15:18 schrieb Adrien Grand:
>>
>> Please vote for release candidate 1 for Lucene 9.4.2
>>
>> The artifacts can be downloaded from:
>>

https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db
>>
>> You can run the smoke tester directly with this command:
>>
>> python3 -u dev-tools/scripts/smokeTestRelease.py \
>>

https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db
>>
>> The vote will be open for at least 72 hours i.e. until
2022-11-20 15:00 UTC.
>>
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>>
>> Here is my +1.
>>
>> --
>> Adrien
>>
>> --
>> Uwe Schindler
>> Achterdiek 19, D-28357 Bremen
>> https://www.thetaphi.de
>> eMail: u...@thetaphi.de
>>
>> --
>> Uwe Schindler
>> Achterdiek 19, D-28357 Bremen
>> https://www.thetaphi.de
>> eMail: u...@thetaphi.de
>
>
>
> --
> Adrien
>
> --
> Uwe Schindler
> Achterdiek 19,

Re: [VOTE] Release Lucene 9.4.2 RC1

2022-11-18 Thread Robert Muir 
I think he is running this from jenkins job. I suspect agents have
"stacked up" over time take a look with "ps". Every time i run the
smoketester, it "leaks" at least an agent or two.

On Fri, Nov 18, 2022 at 9:48 AM Adrien Grand  wrote:
>
> Reading Uwe's error message more carefully, I had first assumed that the GPG 
> failure was due to the lack of an ultimately trusted signature, but it seems 
> like it's due to "can't connect to the agent: IPC connect call failed" 
> actually, which suggests an issue with the GPG agent?
>
> On Fri, Nov 18, 2022 at 3:00 PM Michael Sokolov  wrote:
>>
>> I got this message when initially downloading the artifacts:
>>
>> Downloading 
>> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db/lucene/lucene-9.4.2-src.tgz.asc
>> File: 
>> /tmp/smoke_lucene_9.4.2_858d9b437047a577fa9457089afff43eefa461db/lucene.lucene-9.4.2-src.tgz.gpg.verify.log
>> verify trust
>>   GPG: gpg: WARNING: This key is not certified with a trusted signature!
>>
>> is it related?
>>
>> On Fri, Nov 18, 2022 at 8:43 AM Uwe Schindler  wrote:
>> >
>> > The problem is: it is working like this since years - the 9.4.1 release 
>> > worked fine. No change!
>> >
>> > And I can't configure this because GPG uses its own home directory setup 
>> > by smoke tester (see paths below). So it should not look anywhere else? In 
>> > addition "gpg: no ultimately trusted keys found" is just a warning, it 
>> > should not cause gpg to exit.
>> >
>> > Also why does it only happens at the time of Maven? It checks signatures 
>> > before, too. This is why I restarted the build: 
>> > https://jenkins.thetaphi.de/job/Lucene-Release-Tester/25/console (still 
>> > running)
>> >
>> > Uwe
>> >
>> > Am 18.11.2022 um 14:21 schrieb Adrien Grand:
>> >
>> > Uwe, the error message suggests that Policeman Jenkins is not ultimately 
>> > trusting any of the keys. Does it work if you configure it to ultimately 
>> > trust your "Uwe Schindler (CODE SIGNING KEY) " key 
>> > (which I assume you would be ok with)?
>> >
>> > On Fri, Nov 18, 2022 at 2:18 PM Uwe Schindler  wrote:
>> >>
>> >> I am restarting the build, maybe it was some hickup. Interestingly it 
>> >> only failed for the Maven dependencies. P.S.: Why does it import the key 
>> >> file over and over? It would be enough to do this once at beginning of 
>> >> smoker.
>> >>
>> >> Uwe
>> >>
>> >> Am 18.11.2022 um 14:12 schrieb Uwe Schindler:
>> >>
>> >> Hi,
>> >>
>> >> I get a failure because your key is somehow rejected by GPG (Ubuntu 
>> >> 22.04):
>> >>
>> >> https://jenkins.thetaphi.de/job/Lucene-Release-Tester/24/console
>> >>
>> >> verify maven artifact sigs command "gpg --homedir 
>> >> /home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg 
>> >> --import /home/jenkins/workspace/Lucene-Release-Tester/smoketmp/KEYS" 
>> >> failed: gpg: keybox 
>> >> '/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/pubring.kbx'
>> >>  created gpg: 
>> >> /home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/trustdb.gpg:
>> >>  trustdb created gpg: key B83EA82A0AFCEE7C: public key "Yonik Seeley 
>> >> " imported gpg: can't connect to the agent: IPC connect 
>> >> call failed gpg: key E48025ED13E57FFC: public key "Upayavira 
>> >> " imported [...] gpg: key 051A0FAF76BC6507: public key 
>> >> "Adrien Grand (CODE SIGNING KEY) " imported [...] 
>> >> gpg: key 32423B0E264B5CBA: public key "Julie Tibshirani (New code signing 
>> >> key) " imported gpg: Total number processed: 62 
>> >> gpg: imported: 62 gpg: no ultimately trusted keys found
>> >> It looks like for others it succeeds? No idea why. Maybe Ubuntu 22.04 has 
>> >> a too-new GPG or it needs to use gpg2?
>> >>
>> >> -1 to release until this is sorted out.
>> >>
>> >> Uwe
>> >>
>> >> Am 17.11.2022 um 15:18 schrieb Adrien Grand:
>> >>
>> >> Please vote for release candidate 1 for Lucene 9.4.2
>> >>
>> >> The artifacts can be downloaded from:
>> >> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db
>> >>
>> >> You can run the smoke tester directly with this command:
>> >>
>> >> python3 -u dev-tools/scripts/smokeTestRelease.py \
>> >> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db
>> >>
>> >> The vote will be open for at least 72 hours i.e. until 2022-11-20 15:00 
>> >> UTC.
>> >>
>> >> [ ] +1  approve
>> >> [ ] +0  no opinion
>> >> [ ] -1  disapprove (and reason why)
>> >>
>> >> Here is my +1.
>> >>
>> >> --
>> >> Adrien
>> >>
>> >> --
>> >> Uwe Schindler
>> >> Achterdiek 19, D-28357 Bremen
>> >> https://www.thetaphi.de
>> >> eMail: u...@thetaphi.de
>> >>
>> >> --
>> >> Uwe Schindler
>> >> Achterdiek 19, D-28357 Bremen
>> >> https://www.thetaphi.de
>> >> eMail: u...@thetaphi.de
>> >
>> >
>> >
>> > --
>> > Adrien
>> >
>> > --
>> > Uwe Schindler
>> > Achterdiek 19, D-28357 Bremen
>> > https://www.thetaphi.de
>> > eMail:

Re: [VOTE] Release Lucene 9.4.2 RC1

2022-11-18 Thread Adrien Grand 
Reading Uwe's error message more carefully, I had first assumed that the
GPG failure was due to the lack of an ultimately trusted signature, but it
seems like it's due to "can't connect to the agent: IPC connect call
failed" actually, which suggests an issue with the GPG agent?

On Fri, Nov 18, 2022 at 3:00 PM Michael Sokolov  wrote:

> I got this message when initially downloading the artifacts:
>
> Downloading
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db/lucene/lucene-9.4.2-src.tgz.asc
> File:
> /tmp/smoke_lucene_9.4.2_858d9b437047a577fa9457089afff43eefa461db/lucene.lucene-9.4.2-src.tgz.gpg.verify.log
> verify trust
>   GPG: gpg: WARNING: This key is not certified with a trusted
> signature!
>
> is it related?
>
> On Fri, Nov 18, 2022 at 8:43 AM Uwe Schindler  wrote:
> >
> > The problem is: it is working like this since years - the 9.4.1 release
> worked fine. No change!
> >
> > And I can't configure this because GPG uses its own home directory setup
> by smoke tester (see paths below). So it should not look anywhere else? In
> addition "gpg: no ultimately trusted keys found" is just a warning, it
> should not cause gpg to exit.
> >
> > Also why does it only happens at the time of Maven? It checks signatures
> before, too. This is why I restarted the build:
> https://jenkins.thetaphi.de/job/Lucene-Release-Tester/25/console (still
> running)
> >
> > Uwe
> >
> > Am 18.11.2022 um 14:21 schrieb Adrien Grand:
> >
> > Uwe, the error message suggests that Policeman Jenkins is not ultimately
> trusting any of the keys. Does it work if you configure it to ultimately
> trust your "Uwe Schindler (CODE SIGNING KEY) " key
> (which I assume you would be ok with)?
> >
> > On Fri, Nov 18, 2022 at 2:18 PM Uwe Schindler  wrote:
> >>
> >> I am restarting the build, maybe it was some hickup. Interestingly it
> only failed for the Maven dependencies. P.S.: Why does it import the key
> file over and over? It would be enough to do this once at beginning of
> smoker.
> >>
> >> Uwe
> >>
> >> Am 18.11.2022 um 14:12 schrieb Uwe Schindler:
> >>
> >> Hi,
> >>
> >> I get a failure because your key is somehow rejected by GPG (Ubuntu
> 22.04):
> >>
> >> https://jenkins.thetaphi.de/job/Lucene-Release-Tester/24/console
> >>
> >> verify maven artifact sigs command "gpg --homedir
> /home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg --import
> /home/jenkins/workspace/Lucene-Release-Tester/smoketmp/KEYS" failed: gpg:
> keybox
> '/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/pubring.kbx'
> created gpg:
> /home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/trustdb.gpg:
> trustdb created gpg: key B83EA82A0AFCEE7C: public key "Yonik Seeley <
> yo...@apache.org>" imported gpg: can't connect to the agent: IPC connect
> call failed gpg: key E48025ED13E57FFC: public key "Upayavira <
> u...@odoko.co.uk>" imported [...] gpg: key 051A0FAF76BC6507: public key
> "Adrien Grand (CODE SIGNING KEY) " imported [...]
> gpg: key 32423B0E264B5CBA: public key "Julie Tibshirani (New code signing
> key) " imported gpg: Total number processed: 62
> gpg: imported: 62 gpg: no ultimately trusted keys found
> >> It looks like for others it succeeds? No idea why. Maybe Ubuntu 22.04
> has a too-new GPG or it needs to use gpg2?
> >>
> >> -1 to release until this is sorted out.
> >>
> >> Uwe
> >>
> >> Am 17.11.2022 um 15:18 schrieb Adrien Grand:
> >>
> >> Please vote for release candidate 1 for Lucene 9.4.2
> >>
> >> The artifacts can be downloaded from:
> >>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db
> >>
> >> You can run the smoke tester directly with this command:
> >>
> >> python3 -u dev-tools/scripts/smokeTestRelease.py \
> >>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db
> >>
> >> The vote will be open for at least 72 hours i.e. until 2022-11-20 15:00
> UTC.
> >>
> >> [ ] +1  approve
> >> [ ] +0  no opinion
> >> [ ] -1  disapprove (and reason why)
> >>
> >> Here is my +1.
> >>
> >> --
> >> Adrien
> >>
> >> --
> >> Uwe Schindler
> >> Achterdiek 19, D-28357 Bremen
> >> https://www.thetaphi.de
> >> eMail: u...@thetaphi.de
> >>
> >> --
> >> Uwe Schindler
> >> Achterdiek 19, D-28357 Bremen
> >> https://www.thetaphi.de
> >> eMail: u...@thetaphi.de
> >
> >
> >
> > --
> > Adrien
> >
> > --
> > Uwe Schindler
> > Achterdiek 19, D-28357 Bremen
> > https://www.thetaphi.de
> > eMail: u...@thetaphi.de
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

-- 
Adrien

Re: [VOTE] Release Lucene 9.4.2 RC1

2022-11-18 Thread Michael Sokolov 
I got this message when initially downloading the artifacts:

Downloading 
https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db/lucene/lucene-9.4.2-src.tgz.asc
File: 
/tmp/smoke_lucene_9.4.2_858d9b437047a577fa9457089afff43eefa461db/lucene.lucene-9.4.2-src.tgz.gpg.verify.log
verify trust
  GPG: gpg: WARNING: This key is not certified with a trusted signature!

is it related?

On Fri, Nov 18, 2022 at 8:43 AM Uwe Schindler  wrote:
>
> The problem is: it is working like this since years - the 9.4.1 release 
> worked fine. No change!
>
> And I can't configure this because GPG uses its own home directory setup by 
> smoke tester (see paths below). So it should not look anywhere else? In 
> addition "gpg: no ultimately trusted keys found" is just a warning, it should 
> not cause gpg to exit.
>
> Also why does it only happens at the time of Maven? It checks signatures 
> before, too. This is why I restarted the build: 
> https://jenkins.thetaphi.de/job/Lucene-Release-Tester/25/console (still 
> running)
>
> Uwe
>
> Am 18.11.2022 um 14:21 schrieb Adrien Grand:
>
> Uwe, the error message suggests that Policeman Jenkins is not ultimately 
> trusting any of the keys. Does it work if you configure it to ultimately 
> trust your "Uwe Schindler (CODE SIGNING KEY) " key 
> (which I assume you would be ok with)?
>
> On Fri, Nov 18, 2022 at 2:18 PM Uwe Schindler  wrote:
>>
>> I am restarting the build, maybe it was some hickup. Interestingly it only 
>> failed for the Maven dependencies. P.S.: Why does it import the key file 
>> over and over? It would be enough to do this once at beginning of smoker.
>>
>> Uwe
>>
>> Am 18.11.2022 um 14:12 schrieb Uwe Schindler:
>>
>> Hi,
>>
>> I get a failure because your key is somehow rejected by GPG (Ubuntu 22.04):
>>
>> https://jenkins.thetaphi.de/job/Lucene-Release-Tester/24/console
>>
>> verify maven artifact sigs command "gpg --homedir 
>> /home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg --import 
>> /home/jenkins/workspace/Lucene-Release-Tester/smoketmp/KEYS" failed: gpg: 
>> keybox 
>> '/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/pubring.kbx'
>>  created gpg: 
>> /home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/trustdb.gpg:
>>  trustdb created gpg: key B83EA82A0AFCEE7C: public key "Yonik Seeley 
>> " imported gpg: can't connect to the agent: IPC connect 
>> call failed gpg: key E48025ED13E57FFC: public key "Upayavira 
>> " imported [...] gpg: key 051A0FAF76BC6507: public key 
>> "Adrien Grand (CODE SIGNING KEY) " imported [...] gpg: 
>> key 32423B0E264B5CBA: public key "Julie Tibshirani (New code signing key) 
>> " imported gpg: Total number processed: 62 gpg: 
>> imported: 62 gpg: no ultimately trusted keys found
>> It looks like for others it succeeds? No idea why. Maybe Ubuntu 22.04 has a 
>> too-new GPG or it needs to use gpg2?
>>
>> -1 to release until this is sorted out.
>>
>> Uwe
>>
>> Am 17.11.2022 um 15:18 schrieb Adrien Grand:
>>
>> Please vote for release candidate 1 for Lucene 9.4.2
>>
>> The artifacts can be downloaded from:
>> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db
>>
>> You can run the smoke tester directly with this command:
>>
>> python3 -u dev-tools/scripts/smokeTestRelease.py \
>> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db
>>
>> The vote will be open for at least 72 hours i.e. until 2022-11-20 15:00 UTC.
>>
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>>
>> Here is my +1.
>>
>> --
>> Adrien
>>
>> --
>> Uwe Schindler
>> Achterdiek 19, D-28357 Bremen
>> https://www.thetaphi.de
>> eMail: u...@thetaphi.de
>>
>> --
>> Uwe Schindler
>> Achterdiek 19, D-28357 Bremen
>> https://www.thetaphi.de
>> eMail: u...@thetaphi.de
>
>
>
> --
> Adrien
>
> --
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> https://www.thetaphi.de
> eMail: u...@thetaphi.de

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: [VOTE] Release Lucene 9.4.2 RC1

2022-11-18 Thread Uwe Schindler 
The problem is: it is working like this since years - the 9.4.1 release 
worked fine. No change!


And I can't configure this because GPG uses its own home directory setup 
by smoke tester (see paths below). So it should not look anywhere else? 
In addition "gpg: no ultimately trusted keys found" is just a warning, 
it should not cause gpg to exit.


Also why does it only happens at the time of Maven? It checks signatures 
before, too. This is why I restarted the build: 
https://jenkins.thetaphi.de/job/Lucene-Release-Tester/25/console (still 
running)


Uwe

Am 18.11.2022 um 14:21 schrieb Adrien Grand:
Uwe, the error message suggests that Policeman Jenkins is not 
ultimately trusting any of the keys. Does it work if you configure it 
to ultimately trust your "Uwe Schindler (CODE SIGNING KEY) 
" key (which I assume you would be ok with)?


On Fri, Nov 18, 2022 at 2:18 PM Uwe Schindler  wrote:

I am restarting the build, maybe it was some hickup. Interestingly
it only failed for the Maven dependencies. P.S.: Why does it
import the key file over and over? It would be enough to do this
once at beginning of smoker.

Uwe

Am 18.11.2022 um 14:12 schrieb Uwe Schindler:


Hi,

I get a failure because your key is somehow rejected by GPG
(Ubuntu 22.04):

https://jenkins.thetaphi.de/job/Lucene-Release-Tester/24/console

verify maven artifact sigs command "gpg --homedir
/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg
--import
/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/KEYS"
failed: gpg: keybox

'/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/pubring.kbx'
created gpg:

/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/trustdb.gpg:
trustdb created gpg: key B83EA82A0AFCEE7C: public key "Yonik
Seeley  " imported
gpg: can't connect to the agent: IPC connect call failed gpg: key
E48025ED13E57FFC: public key "Upayavira 
" imported [...] gpg: key
051A0FAF76BC6507: public key "Adrien Grand (CODE SIGNING KEY)
 " imported [...]
gpg: key 32423B0E264B5CBA: public key "Julie Tibshirani (New code
signing key) 
" imported gpg: Total number
processed: 62 gpg: imported: 62 gpg: no ultimately trusted keys
found
It looks like for others it succeeds? No idea why. Maybe Ubuntu
22.04 has a too-new GPG or it needs to use gpg2?

-1 to release until this is sorted out.

Uwe

Am 17.11.2022 um 15:18 schrieb Adrien Grand:

Please vote for release candidate 1 for Lucene 9.4.2

The artifacts can be downloaded from:

https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db

You can run the smoke tester directly with this command:

python3 -u dev-tools/scripts/smokeTestRelease.py \

https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db

The vote will be open for at least 72 hours i.e. until
2022-11-20 15:00 UTC.

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Here is my +1.

-- 
Adrien
-- 
Uwe Schindler

Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail:u...@thetaphi.de


-- 
Uwe Schindler

Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail:u...@thetaphi.de



--
Adrien


--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail:u...@thetaphi.de

Re: [VOTE] Release Lucene 9.4.2 RC1

2022-11-18 Thread Adrien Grand 
Uwe, the error message suggests that Policeman Jenkins is not ultimately
trusting any of the keys. Does it work if you configure it to ultimately
trust your "Uwe Schindler (CODE SIGNING KEY) " key
(which I assume you would be ok with)?

On Fri, Nov 18, 2022 at 2:18 PM Uwe Schindler  wrote:

> I am restarting the build, maybe it was some hickup. Interestingly it only
> failed for the Maven dependencies. P.S.: Why does it import the key file
> over and over? It would be enough to do this once at beginning of smoker.
>
> Uwe
> Am 18.11.2022 um 14:12 schrieb Uwe Schindler:
>
> Hi,
>
> I get a failure because your key is somehow rejected by GPG (Ubuntu 22.04):
>
> https://jenkins.thetaphi.de/job/Lucene-Release-Tester/24/console
>
> verify maven artifact sigs command "gpg --homedir
> /home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg --import
> /home/jenkins/workspace/Lucene-Release-Tester/smoketmp/KEYS" failed: gpg:
> keybox
> '/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/pubring.kbx'
> created gpg:
> /home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/trustdb.gpg:
> trustdb created gpg: key B83EA82A0AFCEE7C: public key "Yonik Seeley
>  " imported gpg: can't connect to the
> agent: IPC connect call failed gpg: key E48025ED13E57FFC: public key
> "Upayavira  " imported [...] gpg: key
> 051A0FAF76BC6507: public key "Adrien Grand (CODE SIGNING KEY)
>  " imported [...] gpg: key
> 32423B0E264B5CBA: public key "Julie Tibshirani (New code signing key)
>  " imported gpg: Total number
> processed: 62 gpg: imported: 62 gpg: no ultimately trusted keys found
> It looks like for others it succeeds? No idea why. Maybe Ubuntu 22.04 has
> a too-new GPG or it needs to use gpg2?
>
> -1 to release until this is sorted out.
>
> Uwe
> Am 17.11.2022 um 15:18 schrieb Adrien Grand:
>
> Please vote for release candidate 1 for Lucene 9.4.2
>
> The artifacts can be downloaded from:
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db
>
> You can run the smoke tester directly with this command:
>
> python3 -u dev-tools/scripts/smokeTestRelease.py \
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db
>
> The vote will be open for at least 72 hours i.e. until 2022-11-20 15:00
> UTC.
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Here is my +1.
>
> --
> Adrien
>
> --
> Uwe Schindler
> Achterdiek 19, D-28357 Bremenhttps://www.thetaphi.de
> eMail: u...@thetaphi.de
>
> --
> Uwe Schindler
> Achterdiek 19, D-28357 Bremenhttps://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>

-- 
Adrien

Re: [VOTE] Release Lucene 9.4.2 RC1

2022-11-18 Thread Uwe Schindler 
I am restarting the build, maybe it was some hickup. Interestingly it 
only failed for the Maven dependencies. P.S.: Why does it import the key 
file over and over? It would be enough to do this once at beginning of 
smoker.


Uwe

Am 18.11.2022 um 14:12 schrieb Uwe Schindler:


Hi,

I get a failure because your key is somehow rejected by GPG (Ubuntu 
22.04):


https://jenkins.thetaphi.de/job/Lucene-Release-Tester/24/console

verify maven artifact sigs command "gpg --homedir 
/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg 
--import /home/jenkins/workspace/Lucene-Release-Tester/smoketmp/KEYS" 
failed: gpg: keybox 
'/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/pubring.kbx' 
created gpg: 
/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/trustdb.gpg: 
trustdb created gpg: key B83EA82A0AFCEE7C: public key "Yonik Seeley 
" imported gpg: can't connect to the agent: IPC 
connect call failed gpg: key E48025ED13E57FFC: public key "Upayavira 
" imported [...] gpg: key 051A0FAF76BC6507: public key 
"Adrien Grand (CODE SIGNING KEY) " imported [...] 
gpg: key 32423B0E264B5CBA: public key "Julie Tibshirani (New code 
signing key) " imported gpg: Total number 
processed: 62 gpg: imported: 62 gpg: no ultimately trusted keys found
It looks like for others it succeeds? No idea why. Maybe Ubuntu 22.04 
has a too-new GPG or it needs to use gpg2?


-1 to release until this is sorted out.

Uwe

Am 17.11.2022 um 15:18 schrieb Adrien Grand:

Please vote for release candidate 1 for Lucene 9.4.2

The artifacts can be downloaded from:
https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db

You can run the smoke tester directly with this command:

python3 -u dev-tools/scripts/smokeTestRelease.py \
https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db

The vote will be open for at least 72 hours i.e. until 2022-11-20 
15:00 UTC.


[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Here is my +1.

--
Adrien

--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail:u...@thetaphi.de


--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail:u...@thetaphi.de

Re: [VOTE] Release Lucene 9.4.2 RC1

2022-11-18 Thread Uwe Schindler 

Hi,

I get a failure because your key is somehow rejected by GPG (Ubuntu 22.04):

https://jenkins.thetaphi.de/job/Lucene-Release-Tester/24/console

verify maven artifact sigs command "gpg --homedir 
/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg 
--import /home/jenkins/workspace/Lucene-Release-Tester/smoketmp/KEYS" 
failed: gpg: keybox 
'/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/pubring.kbx' 
created gpg: 
/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/trustdb.gpg: 
trustdb created gpg: key B83EA82A0AFCEE7C: public key "Yonik Seeley 
" imported gpg: can't connect to the agent: IPC 
connect call failed gpg: key E48025ED13E57FFC: public key "Upayavira 
" imported [...] gpg: key 051A0FAF76BC6507: public key 
"Adrien Grand (CODE SIGNING KEY) " imported [...] 
gpg: key 32423B0E264B5CBA: public key "Julie Tibshirani (New code 
signing key) " imported gpg: Total number 
processed: 62 gpg: imported: 62 gpg: no ultimately trusted keys found
It looks like for others it succeeds? No idea why. Maybe Ubuntu 22.04 
has a too-new GPG or it needs to use gpg2?


-1 to release until this is sorted out.

Uwe

Am 17.11.2022 um 15:18 schrieb Adrien Grand:

Please vote for release candidate 1 for Lucene 9.4.2

The artifacts can be downloaded from:
https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db

You can run the smoke tester directly with this command:

python3 -u dev-tools/scripts/smokeTestRelease.py \
https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db

The vote will be open for at least 72 hours i.e. until 2022-11-20 
15:00 UTC.


[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Here is my +1.

--
Adrien


--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail:u...@thetaphi.de

[Vector Based Search Dev] Let's use the Github label

2022-11-18 Thread Alessandro Benedetti 
Hi all,
there's a label on our Github 'vector-based-search' (
https://github.com/apache/lucene/issues?q=label%3Avector-based-search+is%3Aclosed
).
I just gave it a pass and tagged most of the issues I believe are related.

If we all do this little extra effort of tagging when creating the issue,
it would be much easier in the future to quickly find the latest happening
in the field(being an area that is super active).
Being involved in this area, I find it super useful!

Thanks for helping!

Cheers
--
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PMC Member*

e-mail: a.benede...@sease.io


*Sease* - Information Retrieval Applied
Consulting | Training | Open Source

Website: Sease.io 
LinkedIn  | Twitter
 | Youtube
 | Github

Re: Maven artifacts and releases

2022-11-18 Thread Dawid Weiss 
> I think, if smoke tester knows the version, it could just check the staging 
> repo, too. It is just another URL!?

Yes, it's an URL.

> If the staging repository on nexus has a hash inside (I think they have), 
> maybe the release wizard places some file with the URL of the actual staging 
> repo into the folder?

I spent some time digging. I am no longer convinced direct Nexus
staging would be a good thing to do because you can have multiple
staging repos (from multiple rcs) and accidentally release the wrong
one - a step from which there's no recovery...

The staging API for Nexus is quite simple - Solr's upload-maven.sh has
almost all of it covered (the exception being profile ID retrieval).
Unsurprisingly, Nexus API is documented in a terrible way and lacks
the documentation
for the key staging method (deployByRepositoryId)...

https://oss.sonatype.org/nexus-staging-plugin/default/docs/index.html

I'll write that nexus-pushing script, no problem there. I'm just
looking at options other than bash + curl because this seems rather
crude. All the pieces are in place though, it's downhill now.


Dawid

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Maven artifacts and releases

2022-11-18 Thread Uwe Schindler 
I think, if smoke tester knows the version, it could just check the 
staging repo, too. It is just another URL!? If the staging repository on 
nexus has a hash inside (I think they have), maybe the release wizard 
places some file with the URL of the actual staging repo into the folder?


Uwe

Am 17.11.2022 um 14:37 schrieb Adrien Grand:
I remember another proposal which consisted of using the Gradle build 
to rebuild Maven artifacts at the type of uploading to Nexus, which I 
liked less because it involved re-building, and who knows what may 
happen that could produce slightly different binaries. I like your new 
proposal better.


> Those are browsable and artifacts can be downloaded from there 
before voting (although I'm not sure if anybody inspects those maven 
artifacts)


I suspect you know this, but the smoke tester does download these 
artifacts and runs some checks.




On Thu, Nov 17, 2022 at 2:31 PM Dawid Weiss  wrote:


Yeah, I thought so. I'd love to help improve this as part of the
next release - it should really be simple. I know the old way was
to have maven artifacts separately (to agree/vote upon) but in my
opinion it wouldn't change much if the release manager pointed to
release artifacts + maven artifact (staging) repository uploaded
to Apache Nexus. Those are browsable and artifacts can be
downloaded from there before voting (although I'm not sure if
anybody inspects those maven artifacts). Also, the staging
repository can "hang" unreleased until the voting is closed. This
would make the build side of things much easier and wound't
require any extra infrastructure/ steps.

Dawid

On Thu, Nov 17, 2022 at 2:08 PM Adrien Grand 
wrote:

I remember using a 8.x build to do that for the 9.0 release.

On Thu, Nov 17, 2022 at 1:54 PM Dawid Weiss
 wrote:


I looked at an old issue related to maven artifact
publishing and I noticed the release wizard still gives
instructions to use the ant-based script (which isn't
there anymore?):

ant clean stage-maven-artifacts

I'm sorry to ask but how did release managers stage maven
artifacts so far on 9x?

Dawid



-- 
Adrien




--
Adrien


--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail:u...@thetaphi.de