Re: Auto-repo-repair

2012-11-22 Thread Enrico Weigelt
Hi, > I still think that it would make the most sense to do the following > (if you insist on some sort of automated repair): > (1) Fetch a "good" clone (or clones) into a temporary directory; > (2) Cannibalize the objects from it (them); > (3) Re-run git fsck and check for still-missing / unreach

Re: Auto-repo-repair

2012-11-20 Thread Drew Northup
On Mon, Nov 19, 2012 at 5:35 PM, Enrico Weigelt wrote: > >> >> How would the broken repository be sure of what it is missing to >> >> request it from the other side? >> > >> > fsck will find missing objects. >> >> And what about the objects referred to by objects that are missing? > > Will be fetc

Re: Auto-repo-repair

2012-11-19 Thread Enrico Weigelt
> >> How would the broken repository be sure of what it is missing to > >> request it from the other side? > > > > fsck will find missing objects. > > And what about the objects referred to by objects that are missing? Will be fetched after multiple iterations. We could even introduce some 'fsck

Re: Auto-repo-repair

2012-11-18 Thread Drew Northup
On Sun, Nov 18, 2012 at 11:55 AM, Enrico Weigelt wrote: > >> How would the broken repository be sure of what it is missing to >> request it from the other side? > > fsck will find missing objects. And what about the objects referred to by objects that are missing? Jeff's solution doesn't suffer f

Re: Auto-repo-repair

2012-11-18 Thread Enrico Weigelt
> How would the broken repository be sure of what it is missing to > request it from the other side? fsck will find missing objects. > > -- > -Drew Northup > -- > "As opposed to vegetable or mineral error?" > -John Pescatore, SANS New

Re: Auto-repo-repair

2012-11-18 Thread Drew Northup
On Sat, Nov 17, 2012 at 4:21 AM, Enrico Weigelt wrote: > Hi, > >> You can't reliably just grab the broken objects, because most >> transports >> don't support grabbing arbitrary objects (you can do it if you have >> shell access to a known-good repository, but it's not automated). > > can we intro

Re: Auto-repo-repair

2012-11-17 Thread Enrico Weigelt
Hi, > You can't reliably just grab the broken objects, because most > transports > don't support grabbing arbitrary objects (you can do it if you have > shell access to a known-good repository, but it's not automated). can we introduce a new or extend existing transports to support that ? cu --

Re: Auto-repo-repair

2012-11-16 Thread Jeff King
On Fri, Nov 16, 2012 at 06:51:45PM +0100, Enrico Weigelt wrote: > I've broken some repo (missing objects), eg by messing something up > w/ alternates, broken filesystem, or whatever. And I've got a bunch > of remotes which (together) contain all of the lost objects. > > Now I'd like to run some $

Auto-repo-repair

2012-11-16 Thread Enrico Weigelt
Hi folks, suppose the following scenario: I've broken some repo (missing objects), eg by messing something up w/ alternates, broken filesystem, or whatever. And I've got a bunch of remotes which (together) contain all of the lost objects. Now I'd like to run some $magic_command which automatical