Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Git not committing, gpg stuck in database_open waiting for lock

When I attempt to commit in Git through R, I continuously get revoked access.

The error is:

gpg: Note: database_open 134217901 waiting for lock (held by 9857) ..

  1. I have pushed.
  2. I have pulled.
  3. I have set a new token.
  4. I have cloned the project.

I'm expecting the commit to send but I'm getting the full error:

gpg: Note: database_open 134217901 waiting for lock (held by 9857) ... [GNUPG:] FAILURE sign 134250628 gpg: signing failed: Operation timed out

I'm attempting to commit a R script to GitHub through R. When I use the commit option through the panel, it will not push. I have tried to reset my credentials, put a new personal token on, and other tactics. It is not working. Not sure where to go from here. I'm expecting for the code to enter the repo and it is not.

I am stuck in a loop:

--list-keys
gpg: Note: database_open 134217901 waiting for lock (held by 9857) ...
gpg: Note: database_open 134217901 waiting for lock (held by 9857) ...
gpg: Note: database_open 134217901 waiting for lock (held by 9857) ...
gpg: Note: database_open 134217901 waiting for lock (held by 9857) ...
gpg: Note: database_open 134217901 waiting for lock (held by 9857) ...
like image 202
Will Avatar asked Nov 24 '25 09:11

Will


1 Answers

Actually the solution above cannot be the solution, as it simply deactivates the gpg signing flag.

In my case what worked was this: https://gist.github.com/bahadiraraz/f2fb15b07e0fce92d8d5a86ab33469f7

the error was "simply" due to a freezing during the git commit. removing the lock file, solved it immediately.

like image 156
Tonio Avatar answered Nov 27 '25 01:11

Tonio



Donate For Us

If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!