Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TPM Update returns "failed to store -25299" #288

Open
Cyberlane opened this issue Jun 5, 2024 · 4 comments
Open

TPM Update returns "failed to store -25299" #288

Cyberlane opened this issue Jun 5, 2024 · 4 comments

Comments

@Cyberlane
Copy link

Computer information:

Apple M2 Max
macOS: Sonoma 14.4.1
Tmux: 3.4

When I tell TPM to update all my packages, I get the following:

Updating all plugins!

  "tpm" update success
    | Already up to date.
  "tmux-autoreload" update success
  "nord-tmux" update success
  "tmux-sensible" update success
    | Already up to date.
    | Already up to date.
    | failed to store: -25299
    | Already up to date.
  "tmux-pain-control" update success
    | failed to store: -25299
    | Already up to date.
  "tmux-yank" update success
    | Already up to date.

TMUX environment reloaded.

Done, press ENTER to continue.

I am concerned over all the instances of failed to store -25299. I have no idea what that could be, any suggestions would be appreciated.

@RossBarnie
Copy link

Do you get a similar error when you clone those repos or try to update them manually?

@RossBarnie
Copy link

I looked up the error and came across this thread which claims that the error is caused by a regression in git 2.45.0, so this is not a tmux bug. Your workaround for now should be to manually update them by navigating to their directories and running git pull.

@mikedfunk
Copy link

mikedfunk commented Jun 27, 2024

Hm, still not fixed in git 2.45.2.

Easier workaround than git pull in each directory is brew uninstall git then <Prefix><c-u> then brew install git

@c0nspiracy
Copy link

I believe this issue has been fixed in git 2.46.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants