* repo corrupted?
@ 2023-12-30 21:52 T.V Raman
2023-12-30 22:25 ` Stefan Kangas
2023-12-31 9:48 ` Sean Allred
0 siblings, 2 replies; 6+ messages in thread
From: T.V Raman @ 2023-12-30 21:52 UTC (permalink / raw)
To: emacs-devel
Git says
remote: Counting objects: 393, done.
remote: fatal: Out of memory, malloc failed (tried to allocate 205121 bytes)
remote: aborting due to possible repository corruption on the remote side.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: repo corrupted?
2023-12-30 21:52 repo corrupted? T.V Raman
@ 2023-12-30 22:25 ` Stefan Kangas
2023-12-31 3:14 ` T.V Raman
2023-12-31 9:48 ` Sean Allred
1 sibling, 1 reply; 6+ messages in thread
From: Stefan Kangas @ 2023-12-30 22:25 UTC (permalink / raw)
To: T.V Raman, emacs-devel
"T.V Raman" <raman@google.com> writes:
> Git says
> remote: Counting objects: 393, done.
> remote: fatal: Out of memory, malloc failed (tried to allocate 205121 bytes)
> remote: aborting due to possible repository corruption on the remote side.
> fatal: protocol error: bad pack header
> 13:51:42 gnu-emacs $
I just pulled from and pushed to master, and I'm getting:
Pushing to git.sv.gnu.org:/srv/git/emacs.git
Writing objects: 100% (4/4), 399 bytes | 399.00 KiB/s, done.
Total 4 (delta 3), reused 0 (delta 0), pack-reused 0
To git.sv.gnu.org:/srv/git/emacs.git
1d278dc786c..82f6367ee24 master -> master
updating local tracking ref 'refs/remotes/origin/master'
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: repo corrupted?
2023-12-30 22:25 ` Stefan Kangas
@ 2023-12-31 3:14 ` T.V Raman
0 siblings, 0 replies; 6+ messages in thread
From: T.V Raman @ 2023-12-31 3:14 UTC (permalink / raw)
To: Stefan Kangas; +Cc: emacs-devel
Stefan Kangas <stefankangas@gmail.com> writes:
likely transient issue, now appears to be working.> "T.V Raman" <raman@google.com> writes:
>
>> Git says
>> remote: Counting objects: 393, done.
>> remote: fatal: Out of memory, malloc failed (tried to allocate 205121 bytes)
>> remote: aborting due to possible repository corruption on the remote side.
>> fatal: protocol error: bad pack header
>> 13:51:42 gnu-emacs $
>
> I just pulled from and pushed to master, and I'm getting:
>
> Pushing to git.sv.gnu.org:/srv/git/emacs.git
> Writing objects: 100% (4/4), 399 bytes | 399.00 KiB/s, done.
> Total 4 (delta 3), reused 0 (delta 0), pack-reused 0
> To git.sv.gnu.org:/srv/git/emacs.git
> 1d278dc786c..82f6367ee24 master -> master
> updating local tracking ref 'refs/remotes/origin/master'
--
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: repo corrupted?
2023-12-30 21:52 repo corrupted? T.V Raman
2023-12-30 22:25 ` Stefan Kangas
@ 2023-12-31 9:48 ` Sean Allred
2023-12-31 11:03 ` Andreas Schwab
1 sibling, 1 reply; 6+ messages in thread
From: Sean Allred @ 2023-12-31 9:48 UTC (permalink / raw)
To: T.V Raman; +Cc: emacs-devel
"T.V Raman" <raman@google.com> writes:
> Git says
> remote: Counting objects: 393, done.
> remote: fatal: Out of memory, malloc failed (tried to allocate 205121 bytes)
> remote: aborting due to possible repository corruption on the remote side.
> fatal: protocol error: bad pack header
> 13:51:42 gnu-emacs $
No problem on this end fetching from either of these remotes:
https://git.savannah.gnu.org/git/emacs.git
git@github.com:emacs-mirror/emacs.git
The repository is not corrupted. The issue is right there in the error
message:
fatal: Out of memory, malloc failed (tried to allocate 205121 bytes)
It does admittedly go on to say there's 'possible repository
corruption', but this is just catch-all messaging. Git only asked for
200K of memory (like it says in the error) -- seems reasonable to me.
Whatever server you were fetching from was having problems. Try again.
--
Sean Allred
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: repo corrupted?
2023-12-31 9:48 ` Sean Allred
@ 2023-12-31 11:03 ` Andreas Schwab
2023-12-31 15:26 ` T.V Raman
0 siblings, 1 reply; 6+ messages in thread
From: Andreas Schwab @ 2023-12-31 11:03 UTC (permalink / raw)
To: Sean Allred; +Cc: T.V Raman, emacs-devel
The savannah server probably had a transient resource shortage (which
can happen if too many clients try to access it at the same time).
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: repo corrupted?
2023-12-31 11:03 ` Andreas Schwab
@ 2023-12-31 15:26 ` T.V Raman
0 siblings, 0 replies; 6+ messages in thread
From: T.V Raman @ 2023-12-31 15:26 UTC (permalink / raw)
To: Andreas Schwab; +Cc: Sean Allred, emacs-devel
I think you are right, the problem disappeared when I tried a few hours
later.
--
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2023-12-31 15:26 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-12-30 21:52 repo corrupted? T.V Raman
2023-12-30 22:25 ` Stefan Kangas
2023-12-31 3:14 ` T.V Raman
2023-12-31 9:48 ` Sean Allred
2023-12-31 11:03 ` Andreas Schwab
2023-12-31 15:26 ` T.V Raman
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).