+1 SUCCESS! [0:47:41.351723]

On Fri, Sep 5, 2025 at 10:24 AM Ignacio Vera <[email protected]> wrote:

> +1 (binding)
>
> SUCCESS! [1:13:08.487251]
>
> On Fri, Sep 5, 2025 at 1:25 AM Ankit Jain <[email protected]> wrote:
>
>> Okay, I could finally get it to work. Let's go!!
>>
>> +1 (non binding)
>>
>> SUCCESS! [1:13:59.906562]
>>
>> On Thu, Sep 4, 2025 at 11:06 AM Michael Sokolov <[email protected]>
>> wrote:
>>
>>> I managed to get python 3.12 installed (using pyenv) and re-ran, but
>>> now I'm also seeing problems related to missing keys.  I will try
>>> again tomorrow
>>>
>>> On Thu, Sep 4, 2025 at 1:26 PM Vigya Sharma <[email protected]>
>>> wrote:
>>> >
>>> > Oh no! My key wasn't in the KEYS file so I had to manually add it on
>>> my machine to do the build. I used the following command:
>>> >
>>> > { MYKEY=4FB8850B; echo; gpg --list-public-keys $MYKEY; gpg --export -a
>>> --export-options no-export-attributes,export-minimal $MYKEY; } >> KEYS
>>> >
>>> > Then the release steps succeeded and it uploaded the artifacts. But I
>>> don't think it uploads the KEYS file? Do I need to do something to
>>> separately push the new KEYS file with my key added?
>>> >
>>> > Vigya
>>> >
>>> > On Thu, Sep 4, 2025 at 9:58 AM Ankit Jain <[email protected]>
>>> wrote:
>>> >>
>>> >> Probably, it takes some time for the key to sync. Still running into
>>> the same issue with ("gpg: Can't check signature: No public key")
>>> >>
>>> >> On Thu, Sep 4, 2025 at 9:46 AM Adrien Grand <[email protected]>
>>> wrote:
>>> >>>
>>> >>> I added Vigya's key to the KEYS file, hopefully this fixes the
>>> problem (once archive.apache.org syncs).
>>> >>>
>>> >>> On Thu, Sep 4, 2025 at 6:22 PM Adrien Grand <[email protected]>
>>> wrote:
>>> >>>>
>>> >>>> I'm running with Python 3.12.1 and don't get this error.
>>> >>>>
>>> >>>> However GPG complains about the signature. ("gpg: Can't check
>>> signature: No public key") I believe that this is due to the fact that
>>> Vigya's key is not in Lucene's KEYS file? (
>>> https://archive.apache.org/dist/lucene/KEYS)
>>> >>>>
>>> >>>> On Thu, Sep 4, 2025 at 4:58 PM Michael Sokolov <[email protected]>
>>> wrote:
>>> >>>>>
>>> >>>>> does the smokeTester require fancy new python now? It seems to fail
>>> >>>>> for me with python 3.9:
>>> >>>>>
>>> >>>>> sokolovm@sok➜~/workspace/lucene(branch_10_3)» python3 -u
>>> >>>>> dev-tools/scripts/smokeTestRelease.py \
>>> >>>>>       [14:56:23]
>>> >>>>>
>>> https://dist.apache.org/repos/dist/dev/lucene/lucene-10.3.0-RC1-rev-878a3db9c2d029020b0fcb2b00de314940cced96
>>> >>>>> Traceback (most recent call last):
>>> >>>>>   File
>>> "/local/home/sokolovm/workspace/lucene/dev-tools/scripts/smokeTestRelease.py",
>>> >>>>> line 40, in <module>
>>> >>>>>     import scriptutil
>>> >>>>>   File
>>> "/local/home/sokolovm/workspace/lucene/dev-tools/scripts/scriptutil.py",
>>> >>>>> line 26, in <module>
>>> >>>>>     from typing import Self, override
>>> >>>>> ImportError: cannot import name 'Self' from 'typing'
>>> >>>>> (/apollo/env/EnvImprovement/python3.9/lib/python3.9/typing.py)
>>> >>>>>
>>> >>>>> On Thu, Sep 4, 2025 at 2:58 AM Vigya Sharma <[email protected]>
>>> wrote:
>>> >>>>> >
>>> >>>>> > Please vote for release candidate 1 for Lucene 10.3.0
>>> >>>>> >
>>> >>>>> > The artifacts can be downloaded from:
>>> >>>>> >
>>> https://dist.apache.org/repos/dist/dev/lucene/lucene-10.3.0-RC1-rev-878a3db9c2d029020b0fcb2b00de314940cced96
>>> >>>>> >
>>> >>>>> > 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-10.3.0-RC1-rev-878a3db9c2d029020b0fcb2b00de314940cced96
>>> >>>>> >
>>> >>>>> > The vote will be open for at least 72 hours i.e. until
>>> 2025-09-08 07:00 UTC.
>>> >>>>> >
>>> >>>>> > [ ] +1  approve
>>> >>>>> > [ ] +0  no opinion
>>> >>>>> > [ ] -1  disapprove (and reason why)
>>> >>>>> >
>>> >>>>> > Here is my +1
>>> >>>>> > ----
>>> >>>>>
>>> >>>>>
>>> ---------------------------------------------------------------------
>>> >>>>> To unsubscribe, e-mail: [email protected]
>>> >>>>> For additional commands, e-mail: [email protected]
>>> >>>>>
>>> >>>>
>>> >>>>
>>> >>>> --
>>> >>>> Adrien
>>> >>>
>>> >>>
>>> >>>
>>> >>> --
>>> >>> Adrien
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>>

-- 
Adrien

Reply via email to