Lost Repository Was: Removing git-annex Repo

[Klaus Ethgen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hello Joey,

Am So den  4. Dez 2011 um  2:02 schrieb Joey Hess:
> > Am Fr den  2. Dez 2011 um 21:54 schrieb Klaus Ethgen:
> > > Not only that, also a "git annex fsck" will bring it back. But I wonder
> > > where it gets the description and ID of the old remote.
> > 
> > Now I have the same problem but only way around.
> > 
> > I did create a new git and annex. Filled it with annexed content and
> > pushed all to a second new created repository.
> > 
> > Now I cloned the first to an other machine and did git annex init Blafoo
> > inside. After push I was thinking that everything is ok. But it wasn't.
> > Every time I fsck or add new files or otherwise do annex stuff it trows
> > out the cloned repository from trust.log and uuid.log.
> > 
> > I use version 3.20111122 from Debian at the moment.
> 
> I don't entirely understand your description of the problem.
> I'd appreciate a proper bug report with full details; transcripts, etc.

At the moment I am not absolutely sure of the bug or not.

Lets make an example.

   > git annex status
   supported backends: SHA256 SHA1 SHA512 SHA224 SHA384 SHA256E SHA1E SHA512E SHA224E SHA384E WORM URL
   supported remote types: git S3 bup directory rsync web hook
   trusted repositories: 1
           xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -- Backup
   semitrusted repositories: 2
           00000000-0000-0000-0000-000000000001 -- web
           yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy -- here (Master)
   untrusted repositories: 1
           zzzzzzzz-zzzz-zzzz-zzzz-zzzzzzzzzzzz -- Clone
   local annex keys: 42
   local annex size: 1 gigabyte
   visible annex keys: 42
   visible annex size: 1 gigabyte
   backend usage: 
           SHA256: 42
   > git annex drop file/name
   drop file/name ok
   > git annex status
   supported backends: SHA256 SHA1 SHA512 SHA224 SHA384 SHA256E SHA1E SHA512E SHA224E SHA384E WORM URL
   supported remote types: git S3 bup directory rsync web hook
   trusted repositories: 1
           xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -- Backup
   semitrusted repositories: 2
           00000000-0000-0000-0000-000000000001 -- web
           yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy -- here (Master)
   untrusted repositories: 0
   local annex keys: 41
   local annex size: 1 gigabyte
   visible annex keys: 42
   visible annex size: 1 gigabyte
   backend usage: 
           SHA256: 42
   >

And no Clone repository anymore. But it is still a valid repository and
in this case it ist one of the repositories that still has the dropped
file!

I never before see that issue.

> > That leads me again to the question where annex do have its store what
> > it like and what not?
> 
> http://git-annex.branchable.com/internals/

Hmm.. That is more or less what I observed.

Regards
   Klaus
- -- 
Klaus Ethgen                              http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen <Klaus at Ethgen.de>
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQGcBAEBCgAGBQJO20ySAAoJEKZ8CrGAGfasf98MAKh///Uau9CYAqzOsrJGhrQS
wWi1yvGctu3KbPnXQrp1KsC1gBasx7/Bgk4pU+x6B5G+X6db2fCCzPiDfewjvJt7
f0p2P7upgS3XKZNE0Ku+7qQVdcbjQskwXZIQBi1/bpI+mkZN3X45WFVLVaLOWtxU
AocA0v3clh1TEsPscc+vvSinK414ERI5UD4/8IpNByvd1gGYvbCsGCLAev3s8rRs
pSyqxmHipovHBxgQ111QcmhKABxEsB4oAq21CJvesy65avbEMfpd0UuXBj85NY4u
4KXNijeucrMp/7yUN9jAdnpGHTP2Lu6mc19wA8ch4Ru0+6iYJDbSINDfOz7U7wmS
oF2RPLAiBr8r388Nve1oksDV9DV+lIljdElRR+nD8MWhGcqgOijdKBRq+jAco0RY
VsX6uDpa1y6die3KivxrUvFvSY109mL6qWNNluLoxSsX4CjM3Ul1PGyr5IOANYO3
7W9bubDFY0ocLd+pI4G1xBm3a/EluMtUoP2UjnnzHA==
=d2Zs
-----END PGP SIGNATURE-----