| Commit message (Collapse) | Author | Age |
... | |
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
git cat-file -p cannot be relied on to tell when an object is corrupt.
If it fails, the fsck may not find all bad objects -- but as long as fsck
exits nonzero, it will return a failing fsckresult, and so recovery will
run.
In recovery, the objects get unpacked. This allows the improved findMissing
to find all corrupt loose objects when fsck is run again as part of the
recovery.
Removed the repack / prune-packed workaround that I added earlier to find
corrupt loose objects that fsck wasn't finding. That was slow, and we want
to keep all loose objects, so that findMissing will work. And, it's
unncessary, now that findMissing is fixed.
Also, fixed some places where unreadable files would crash recovery.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
It turned out to be broken, and led to failures.
6d67245728bbbc07ad1eeaf5b3c49f64c6bbcd11 was a better fix for the problem
that code tried to fix.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Sometimes git fsck outputs no shas even with --verbose, but fails, due to
badly corrupt objects. The best thing to do in this situation is to try to
pull and rsync from remotes, hoping that the bad objects will be
overwritten.
|
| |
| |
| |
| | |
treat the repository as a git repo.
|
| | |
|
| | |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
[dgit (5.10~bpo9+1) quilt-fixup]
|
| |
|
|
|
|
| |
[dgit (3.12) quilt-fixup]
|
| |
|
|
|
|
|
|
| |
* Package 1.20151215-1
[dgit import unpatched git-repair 1.20151215-1]
|
|
[dgit import orig git-repair_1.20151215.orig.tar.xz]
|