Did you get errors?
On Tue, Oct 25, 2022 at 3:56 PM Ishan Chattopadhyaya <
ichattopadhy...@gmail.com> wrote:
> I waited at the right time and entered the passphrase. Seems like the GPG
> step succeeded? But, the artifact still didn't get generated :-(
>
> On Wed, Oct 26, 2022 at 1:01 AM Houston P
I waited at the right time and entered the passphrase. Seems like the GPG
step succeeded? But, the artifact still didn't get generated :-(
On Wed, Oct 26, 2022 at 1:01 AM Houston Putman wrote:
> If you look at the PR there is an initial step added to pre-cache your
> passphrase in the gpg agent.
If you look at the PR there is an initial step added to pre-cache your
passphrase in the gpg agent. If you run that yourself, you should be fine?
On Tue, Oct 25, 2022 at 3:02 PM Ishan Chattopadhyaya <
ichattopadhy...@gmail.com> wrote:
> Ah, there's a "gpg: signing failed: Timeout" thing shown the
Ah, there's a "gpg: signing failed: Timeout" thing shown there. I was out
on a walk, and not sure if I was late to intercept a prompt.
I'll re-run and see how it goes. This time I'll not be AFK at the right
time :-)
On Wed, Oct 26, 2022 at 12:30 AM Ishan Chattopadhyaya <
ichattopadhy...@gmail.com>
Alas, it failed again due to GPG. This time, I can't tell what went wrong,
except the non-zero exit.
Should I add my credentials in gradle.properties and try again?
On Tue, Oct 25, 2022 at 11:34 PM Ishan Chattopadhyaya <
ichattopadhy...@gmail.com> wrote:
> With your patch, Houston, the following
With your patch, Houston, the following command went quite a far bit
further than failing fast with GPG issues. I think it is worth trying out
(merging and rebuilding the RC1).
ishan@x1extreme ~/code/solr (branch_9_1) $ ./gradlew --no-daemon
assembleRelease -Dversion.release=9.1.0 -Psign --max-wor
Couldn't find a file by that name:
ishan@x1extreme ~/code/solr (branch_9_1) $ sudo find / -name gpg-agent.conf
Place your finger on the fingerprint reader
find: ‘/run/user/1000/doc’: Permission denied
find: ‘/run/user/1000/gvfs’: Permission denied
find: ‘/proc/3730/task/3730/net’: Invalid argument
I'm trying to locate the gpg-agent.conf. The ~/.gnupg dir is like this:
ishan@x1extreme ~/code/solr (branch_9_1) $ tree ~/.gnupg/
/home/ishan/.gnupg/
├── private-keys-v1.d
│ ├── 6B96929D18CF7343BCA9CB3D6E17F3D1F298AE08.key
│ └── EF99BCB6F0CE32A0D16C816E1C9BAE2980C54795.key
├── pubring.kbx
└──
Yes, I had tested it out. It works, as per the screenshots attached. The
second one shows the prompt (GNOME).
On Tue, Oct 25, 2022 at 11:23 PM Mike Drob wrote:
> From `gradlew helpPublishing`
>
> If you the following command fails with your GPG configuration, you can
> not use an external GP
>From `gradlew helpPublishing`
If you the following command fails with your GPG configuration, you can
not use an external GPG process with gradle:
echo foo | gpg --batch --no-tty --armor --detach-sign --use-agent
--local-user YOUR_KEY_NAME
Can you verify that command works for you? You m
Ok, I have a fix for this to start, it does require a commit:
https://github.com/apache/solr/pull/1125
For a more complete fix can you share your gpg agent conf
file: ~/.gnupg/gpg-agent.conf?
This will help me setup the release wizard for default setups.
On Tue, Oct 25, 2022 at 1:40 PM Ishan Cha
I tried putting the keyid and passphrase in the gradle.properties. But the
signing.secretKeyRingFile didn't work as, AFAICT, Fedora doesn't have a
secret key file lying around in the filesystem, I think it uses some secure
storage for it.
On Tue, 25 Oct, 2022, 10:32 pm Houston Putman, wrote:
> T
The GPG stuff has been tested and works, though with certain inputs. I can
get it to work with `-PuseGPG` and providing the following properties
`-Psigning.gnupg.keyName` (with the full fingerprint) and
`-Psigning.gnupg.passphrase`.
I think the problem is getting the passphrase to the GPG stuff th
Has the GPG signing ever been tested with Linux (or Fedora in particular)?
Any ideas on how to proceed?
On Tue, Oct 25, 2022 at 10:22 PM Ishan Chattopadhyaya <
ichattopadhy...@gmail.com> wrote:
> Here are the logs with external GPG.
>
> ishan@x1extreme ~/code/solr (branch_9_1) $ python3 -u
> dev
Here are the logs with external GPG.
ishan@x1extreme ~/code/solr (branch_9_1) $ python3 -u
dev-tools/scripts/buildAndPushRelease.py \
--logfile ~/.solr-releases/9.1.0/RC1/logs/buildAndPushRelease.log \
--push-local "~/.solr-releases/9.1.0/RC1/dist" \
--rc-num 1 \
--sign 2085660D9C1FCCACC4A479A3BF1
The "no configured signatory" seems to be the problem.
I tried adding the following to the gradle.properties:
signing.keyId=4992A24C
signing.password=
signing.secretKeyRingFile=
However, none of the files worked well. The problem could be that there
exists no such file on Fedora that qualifies as
Hi,
I'm having no luck with GPG signing on Fedora 34 (GNU/Linux).
This is the output with gradle based signing.
Please advise.
Thanks,
Ishan
>From the console:
ishan@x1extreme ~/code/solr (branch_9_1) $ python3 -u
dev-tools/scripts/buildAndPushRelease.py \
--logfile ~/.solr-releases/9.1.0/RC1/lo
Instructions on how to join the list is found on the website:
https://solr.apache.org/community.html#mailing-lists-chat
Jan
> 25. okt. 2022 kl. 06:22 skrev aditya deshpande <...>:
>
> Hi Team,
>
> Please subscribe me to the mailing list.
>
> Regards,
> Aditya Deshpande
--
Hi Team,
Please subscribe me to the mailing list.
Regards,
Aditya Deshpande
19 matches
Mail list logo
