* binutils-gdb.git corruption?
@ 2021-02-22 17:56 Jan Kratochvil
2021-02-22 18:14 ` Frank Ch. Eigler
0 siblings, 1 reply; 5+ messages in thread
From: Jan Kratochvil @ 2021-02-22 17:56 UTC (permalink / raw)
To: overseers
$ git clone git://sourceware.org/git/binutils-gdb.git;cd binutils-gdb;git annotate gdb/gdbtypes.h
Cloning into 'binutils-gdb'...
remote: Enumerating objects: 39072, done.
remote: Counting objects: 100% (39072/39072), done.
remote: Compressing objects: 100% (37617/37617), done.
remote: Total 1043884 (delta 4326), reused 1884 (delta 1424), pack-reused 1004812
Receiving objects: 100% (1043884/1043884), 373.19 MiB | 1.79 MiB/s, done.
Resolving deltas: 100% (861546/861546), done.
Updating files: 100% (35799/35799), done.
fatal: invalid object name: b9c1b51e45b845debb76d8658edabca70ca56079
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: binutils-gdb.git corruption?
2021-02-22 17:56 binutils-gdb.git corruption? Jan Kratochvil
@ 2021-02-22 18:14 ` Frank Ch. Eigler
2021-02-22 18:29 ` Jan Kratochvil
0 siblings, 1 reply; 5+ messages in thread
From: Frank Ch. Eigler @ 2021-02-22 18:14 UTC (permalink / raw)
To: Overseers mailing list; +Cc: Jan Kratochvil
Hi -
> $ git clone git://sourceware.org/git/binutils-gdb.git;cd binutils-gdb;git annotate gdb/gdbtypes.h
> Cloning into 'binutils-gdb'...
> [...]
> fatal: invalid object name: b9c1b51e45b845debb76d8658edabca70ca56079
Ran a git fsck on binutils-gdb on sourceware; no problems except for some
dangling commits. Maybe this object only existed on your local repo?
- FChE
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: binutils-gdb.git corruption?
2021-02-22 18:14 ` Frank Ch. Eigler
@ 2021-02-22 18:29 ` Jan Kratochvil
2021-02-22 19:08 ` Frank Ch. Eigler
0 siblings, 1 reply; 5+ messages in thread
From: Jan Kratochvil @ 2021-02-22 18:29 UTC (permalink / raw)
To: Overseers mailing list
On Mon, 22 Feb 2021 19:14:31 +0100, Frank Ch. Eigler via Overseers wrote:
> > $ git clone git://sourceware.org/git/binutils-gdb.git;cd binutils-gdb;git annotate gdb/gdbtypes.h
> > Cloning into 'binutils-gdb'...
> > [...]
> > fatal: invalid object name: b9c1b51e45b845debb76d8658edabca70ca56079
>
> Ran a git fsck on binutils-gdb on sourceware; no problems except for some
> dangling commits.
I also ran fsck and it does not find any problem:
$ Checking object directories: 100% (256/256), done.
Checking objects: 100% (1091413/1091413), done.
Checking connectivity: 1052132, done.
dangling blob fd32115773133421ad67491a33a8701885833424
dangling commit 233d1485ae80f31da1f794ef47dd3797b2c52514
dangling blob b71c57bffbe42a67ccdf8a0b4766ccde51859a66
dangling blob 880cf124e27f5221ce99f34b7ba43c41b726b14c
dangling blob 66bdb13f31f47d074c7f32ca0e9f45b6fb80dec7
dangling blob fedbbe4f1bda044f28bdb2c7ae7b5f5b1fdc3dc6
I do not know what really happens there but it is FYI, I do not mind.
> Maybe this object only existed on your local repo?
As you can see above the reproducer makes a new repo.
Jan
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2021-02-22 19:24 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-02-22 17:56 binutils-gdb.git corruption? Jan Kratochvil
2021-02-22 18:14 ` Frank Ch. Eigler
2021-02-22 18:29 ` Jan Kratochvil
2021-02-22 19:08 ` Frank Ch. Eigler
2021-02-22 19:24 ` Jan Kratochvil
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).