I placed the library in maven central, and, accordingly, signed it as it should, and did all the necessary steps. The last time I posted the updated version a long time ago (a few months ago), there were mostly minor updates (and rarely) that went only to the githab. Now there is a need to rebuild one old project that uses this library - I don’t want to connect it as a local dependency, because it’s not so convenient (the maven is used). I used to use one feature - if I make changes on my computer, I use one of the maven tasks ( install , if my memory doesn’t change my memory), then the changes go to the local repository, and after that, without adding them to the maven repository in pom.xml add even a new version of the project, which is only locally, and everything will work.

It was a prehistory, now the question is: I changed a laptop a few months ago, and all the main actions took place on it, including the generation of gpg keys and that's it. Now an error occurs when trying to mvn install :

gpg: signing failed: Inappropriate ioctl for device

As I understand it, the error appears because my key does not match the one that was previously (I just generated it).

Are there any ways to solve this problem? There is no access to the old laptop, and everything was cleared before the sale and os was reinstalled, so I wouldn’t get access to the old data anyway, but I completely forgot about it.

Or maybe a mistake in something else? I will be grateful.

    1 answer 1

    The problem is solved (at least for the local repository), quite simply:

    Add to ~ / .gnupg / gpg.conf :

     use-agent pinentry-mode loopback 

    Add to ~ / .gnupg / gpg-agent.conf :

    allow-loopback-pinentry

    Then restart: echo RELOADAGENT | gpg-connect-agent echo RELOADAGENT | gpg-connect-agent

    Fair for linux and osx.


    Asked a question before using google.
    I did not see a similar question, so I left the answer.
    Source of