Re: How to recovery from a file accidentally committed twice?
Am Di den 17. Aug 2021 um 19:06 schrieb Marc Haber: > one second of not paying attention did it, and I accidentally committed > a file that is in one vcsh-repository, bin/foo to a second vcsh > repository. Now both repos are fighting about that file. vcsh bar rm > bin/foo just took the fight to another limit? > > How do I recover, telling the wrong repository to completely forget about the > file? vcsh bar rm --cached bin/foo Gruß Klaus -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C signature.asc Description: PGP signature ___ vcs-home mailing list vcs-home@lists.madduck.net https://lists.madduck.net/listinfo/vcs-home
Re: Managing git remotes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Am So den 6. Mär 2016 um 18:06 schrieb Christopher Baines: > just fixup?), so it does not really work. I also want 2 standard remotes > for most of the repositories, but that would require adding different > fixup lines to all of repository definitions. Well, Maybe not for the past, but why don't you use git url..insteadOf feature? That allows you to use kind of alias for your Repos and if they change, just change the alias. I used to have short alias for my main repositories. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQGcBAEBCgAGBQJW3VGfAAoJEKZ8CrGAGfasDSsL+wWV5qotEBQU1hOc98PeudcG UhJ/DXuTVVgnqeopyXFXffkwuxr97fLsVQk9MS8l6T7TigPCKUVDAqxjIKq8dsUB nXQzkU0Mo1s9NznGLnyyq8/CMQ6ZfuwR/weGaFpFMGOk30GPtJoZdMWL0Klu90R+ MlPl2aDtrU3WRsZcTlqoWafmlqv2jUJWYr6ANMnJvrfCxP8ebTswLXk3eCDZN3dT ZE4nM+X345+o6HQRyjoZJMy+/IEeL1a2bPKvjD9BNGGwEXBoZXKvPfLGC2XIUQoF sGzmAWdrn1x3l3DNKslRkyVrRkUsK+CuyQScAcQiA626UKI8JJN/ZFr+2P00dVHB zUyCqhK9FCLA2pi2dma1UXKN/cu9qtXmrOFg79QaGcA6ujMpb3rfhYRtDehJuacn rZJgyqu2MWal+gtE8MdIDPd38cvaWVVxmcTj4AS6HK2kLtBAgcFrElU3Re4rxFoY /Ng3K2HozlCe33j9AN2hdJyV8okoEn52ZjDzHvvsJQ== =m5eM -END PGP SIGNATURE- ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
Re: git-annex - documentation clarification - I've had data loss
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Just a hint to eventually get your data back: Am Mo den 10. Feb 2014 um 13:50 schrieb Matthew Hannigan: > Next I reformated the disk, and get a funny feeling that the copy went > a little too fast ... Try to use some forensic tools. If you just formated your disk and did not write any data to it, the change is high that you get back most of the files in case of mp3/video/images. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQGcBAEBCgAGBQJS+QJ0AAoJEKZ8CrGAGfasMQQL/RlnCSXinqIrJjSV1rI7Q4zi NGQk/w7qT+jJ8XXYyMDnoAv+himrvk+cMvVXjE/8CvwGutDKwvXvX2zxUaC8yBjo /H4hZAxQwVENDRtfiGo5+HxrYgUUbv0vpqK0r05ddXK5JZ7YYMuLFP8y2TAVzcQl VYyX3NkACmpLkTPYTSt4C1QYQjcuJV/vQ+LydXYA0nW+kuBHgo4q+F3EMw5K5HPi mlkfIzGZWh/+z5EFJcfxvLDiF4xSgO6B2cX7SUFMt/B5Qwp1TotTdG/dtR3KXo7B EM3P3qsyONDyjELXkBgOZIWgbbcZqXSJZOqY+BtoTmQc9F5pkI4DOLIqmqKLpIRC 4SnHtsDelAOH4Aribu8Puq6QSOgNgugOiTN+v3MxhvPMI4XSFZNCxu4n3z68Dwmp 1vkNHGWc3kaxVHhFvyOstySTElNx7Q/Q8Ap0Yg24Td6LfcgZ2OsJ2kHEdmUvSCz9 ZrtbSrjZAbnZCnC8YYTRKWSTkhQE1xnyAX5hS4FLTA== =2Mdb -END PGP SIGNATURE- ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
Re: more git-annex plumbing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, Am Mo den 16. Apr 2012 um 10:59 schrieb Thomas Koch: > I have a few things that I'd like to do with git-annex but that are hard > because git-annex does not expose internal plumbing commands. I intend to > start a list of such commands here with possible use cases: > > - calculate checksum of a file > - doesAnnexHasChecksum? > - doesAnnexHasFile? > > Useful to deduplicate files from many old CD backups > > - checksum to path > - move file into annex Especially the second last I was searching for many times. I did this with some pipe doing readlink and grep. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQGcBAEBCgAGBQJPjEZsAAoJEKZ8CrGAGfasz5UMAKobMuG8eVaqOdA/TDjsUg5E pTDnAcv91dgUDjLn/lPl6Si2uDpDqhyBX56qHShRaeQ5z17Wps1t6ij5srs2c1BY mX0kvKbrQyPB4czOrCX9fISjTivjCoxbBbgMe9IdH0Nbz4Ul9vB60IuhUnZ47Dlc 83X4sc+s9ODoPvCEMI+OKT6rr/ImRgeE9a/pglUasjNCukipolcB7V3RIaitnC3q xS4Cz62/oWoy4cIKbpSvNtiP6bRaZP6WtVxJxr526L+/WEuzXjbb8nSWnk4j81R/ A7PGANXZryrUkVbj3zCsZO37evfMtFQpf/FT8I1rkvpOpFzHqW+IFOt8QOUtcW9/ CWykqsO92Z8Q1YWtTbv7oRC59kAKhpMjz3SbDmI5GZyRAEHW14f99FRDQsLg5WkN oFsCmJbGkRXB0zTM1vuPGsooYzIHW1NUppijm233aAzlLMR17lHKhp9jzqgTdhbI 6hxvcWVjpBZwA/0X3ZYhy8TGvWNfwYu2NfZS+vBlSg== =2Yca -END PGP SIGNATURE- ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
Re: Spaces in remotes and git annex
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 NotDashEscaped: You need GnuPG to verify this message Hi joey, Am Do den 5. Jan 2012 um 19:38 schrieb Joey Hess: > > Today I cloned a remote git annexed repository that has a space in path. > > With git I have to use one backslash instead of three that are needed in > > scp. Now I tried to get a document from that repository and failed as > > git-annex seems to use scp and need all three backslashes. > > > > Is there any way to work around that problem? > > I've pushed a change that improves git-annex's support for weird urls > like this: > > url = ssh://localhost/home/joey/tmp/foo bar > url = localhost:tmp/foo bar > > Before, git-annex would seem to ignore the first of these (it actually > thought it was a local directory!), and complained the second was a > bad url, now both are supported and work in my tests. I'll give it a try. Thanks. :-) (Uhm.. first have to install ghc.) > Maybe this will fix your problem. If not, what kind of repository is it, > a git repository, or a special remote, and what does the url for it in > .git/config look like? Sure, it is a git repo. Regards Klaus -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQGcBAEBCgAGBQJPBfODAAoJEKZ8CrGAGfas1fQMALWgp8sxdOwk+0o/QqMCX9Co BPslBr08Na6z0lKK5TiQFqgzOrCpMuZf+HWaaDE5me6WJmdH80SpxXsvkVqiuG+D a2eJxSRuZh/dO/ln3qxJPTnFdn98b8/OMZN9gj4Y73ymHytOQ2JYGgb2Wc+uLnX+ IPpvEB1J9IMSHFxpNjPxTA2uwnK4YDbQUL9LUZHdmcHwAQxTaQ1Sz56WfJd+CMUk EEpUXzXGdKheKQTmmmbrqk7WgShboOA+Y+0N8KhpBPb4XnhKHf+9dv33K/IXQ8EO IjQmNHDdjdVCUyHr6A3XPNSAkGTwQAKF7q2DjLqtK6EPJ7xwkgjDi7rW4MXSrofD Du7TAcy+B1b4suvgD0pKhEUyDOHNS7XAjRKWIdrsqUj0s0URKdfJ3Maiosf3sW80 xkIKQAjOjN673ShBH20aENtKOqr3JoyjMIStgRvqZddraM1eTm62acnZwLzSbqZX 6J2t4X7TvlVrB6nBpiVAjFpTrI1CwtHU1chuqsXFcw== =bc9e -END PGP SIGNATURE- ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
Spaces in remotes and git annex
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 NotDashEscaped: You need GnuPG to verify this message Hi, I seems to be predestined to find strange problems. ;-) Today I cloned a remote git annexed repository that has a space in path. With git I have to use one backslash instead of three that are needed in scp. Now I tried to get a document from that repository and failed as git-annex seems to use scp and need all three backslashes. Is there any way to work around that problem? Regards Klaus -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQGcBAEBCgAGBQJPBdp3AAoJEKZ8CrGAGfasaa4L/iYWz+qRsa2RiVt0RRWIV4X2 ABm2tFFHJ0pyP/Zguea8omLPYvg5xf1qpIUiKZB1A3DerbxN6IdwgytfXfDX3aKz QSHU0VisgjS2JXxajPXygNqYex8Obomcjj/n/gR9abRInPDwOqllLpL6vVCMzDd+ /xDH53Yocckorvq+oIKUKl8JGZSsyY85hm+Jbveac91RYchTfvqajCBhO/zCVjXl JXwTiovtr3rNQPbf3rxh0XLejGVvPwNWfw3RAz1G8TgKmyzDP1IIQzuVcN5/le9z lq32ve5UaroWQwZHBwsXHVObBV42eQpktV+VPDSOCS8SnIoXNbpYvR4GhxF1Rz6x uuGCy128LxW6xjksxqbjlnFpYMDaiz7ZuKfK6IolU/LrQu0k3b5JJBp+1fJ3tCBB zX4D/TMjJJ0uf1dUfXCrGBG9zaYf4rH24R12WORz8rM6wHhkEEbYFXufD2TWnH6f X6ZH+HZXa/SSAKzd9J1WrR9TwamWHIC+vc7ni9Dw2w== =1f+I -END PGP SIGNATURE- ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
Re: syncing non-git trees with git-annex
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
NotDashEscaped: You need GnuPG to verify this message
Am Mi den 14. Dez 2011 um 14:15 schrieb Adam Spiers:
> > find -name \*.avi -exec git annex add {} \;
>
> That's substantially less performant, because it forks a whole new
> tree of git / git-annex processes per file.
>
> If we're getting picky, we should also worry about spaces in
> filenames:
>
> find -name \*.avi -print0 | xargs -0 git annex add
>
> but it was only an example, and to be honest, I didn't even use the
> xargs variant myself; I used zsh's recursive globbing:
>
> git annex add **/*.avi
Well, the zsh syntax is fine as long as the matches are not too much. If
the result gets to big your command line would get too big.
On the other hand you can use find as the following:
find -name \*.avi -exec git annex add {} +
This will not spawn new process for every file but will also work with
more files a command line can hold. And it is even a bit more performant
as the xargs version.
Regards
Klaus
--
Klaus Ethgen http://www.ethgen.ch/
pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen
Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
iQGcBAEBCgAGBQJO6NRaAAoJEKZ8CrGAGfassbYMAKZTTpHPsrtyOZWBE7V/FcFT
VacmPRHiKWEmA/ovHBXz+EQVo9M1BruYjVck5/WQIN+BCvkHywUQdVVDwuNwXRsD
Gd69+suQK+sPfdLtSkADR0Sgplf3bF4OhLQlAfmCfZEdMlLi8qVgXXA9J7r6EmjR
kTei6Pkf8t0L5fkj4vznJYfG++Xo58Jd/HMsjN1JxbN2/J3RLIEsLhjNjQGLwsKs
4HNj6L/vNyJ4FgvbKLB8117oo3l3cnNCL3hCNHKZZf2HHUHKZKee4+HPmuho14y5
thkGo5cLRZAy32VmO/sVC8b1680pMCzAdUEyNLHTJw376sAYp3ROWWkfaTI5/SL7
De5U+HDfqtje1AaPPCVuu9qFEzTn/jphkJG7GBTg8FDPrrZd2H23ATeMQajKm3hV
aZi2FomKBWg5RkEfioWYYUwsJQvTlu4eycj7IUeDquc2bDnEgmJd+Eeasz2yxXVI
vURUMqj91nXbGpkoKUTxfPUPUdpVk2NNvxMLzpfKCw==
=f0ez
-END PGP SIGNATURE-
___
vcs-home mailing list
vcs-home@lists.madduck.net
http://lists.madduck.net/listinfo/vcs-home
Re: Lost Repository Was: Removing git-annex Repo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Mo den 5. Dez 2011 um 17:19 schrieb Joey Hess: > Klaus Ethgen wrote: > > > Can you check out the git-annex branch and run git-log on uuid.log, > > > and see what the most recent change to it looked like? > > > > It is an update. After that I revert this update and the next time it > > will purged again. > > It sort of sounds as if you are checking out the git-annex branch, > manually editing and committing a file, and seeing git-annex revert > that change. Well, after the Bug happens several times I started to do the following after git-annex removed the occurrences: git checkout git-annex git cherry-pick # This id is the first time I fixed it by hand git add trust.log uuid.log git commit -m "Correcting update" git checkout master The patch looks somethink like: diff --git a/trust.log b/trust.log index xxx..xxx 100644 --- a/trust.log +++ b/trust.log @@ -1 +1,2 @@ ---- 1 timestamp=1322867090.765867s +---- 0 timestamp=1322867165.394761s diff --git a/uuid.log b/uuid.log index xxx..xxx 100644 --- a/uuid.log +++ b/uuid.log @@ -1,2 +1,3 @@ ----- Backup timestamp=1322866827.929813s ---- Master timestamp=1322866770.445515s +---- Backup timestamp=1322866827.929813s +---- Clone timestamp=1322867722.827595s Which is the revert of this two files. > That's expected behavior actually.. > http://git-annex.branchable.com/internals/ explains why. Sorry, no it don't. I do not want to modify the git-annex branch as I know it is internal. But the situation gives me no other choice than to revert it every and every time. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQGcBAEBCgAGBQJO3PVpAAoJEKZ8CrGAGfasAPcL/2G12mXQWQcNaDO6tEdL7hkJ CM5IA8xnxN4cOIWry3YbfDePwQ4Q3/rPnCEj/epGP7QIYB+tatPjJCCz+2ivprc7 GyZtih+C8cwYpad/T/QKEEAM2txMR2uy2kkGy43aFaCN2YRC/2KDmK5ePfxgcRTJ W+U5VyNu8Aury73WzNGc41e8R/Uple8QZz/r9fvP5c23MtNB83229cjMNBauw4Q6 IHuM0tBNDSY22rZ0MG7WRFgtzgPOZjGsShMVn1TJFpelTheOsCtc0GVjkbwVaGrF IND2Vo23kBFBlc6vy7g99lra7qAoAZxptfGbqZaMKEWXYVmAMiCB+KiBYE5CcH58 2e4sRbPj2xkVITD9RNlWrH7e/amBpf1w5a+i/gNmHMAGYvX0vYS2abwz+FdwqoQ2 ALhycZFig3kmYlDSw+64lS98j9TwAXdZ2IoBCwnJHRZrbrOLhcfBpmncZRW9TRa6 bW56MR5zZUzMpq8L4xtacmxKputo1WGsNhWXftpOGA== =uWye -END PGP SIGNATURE- ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
Re: Lost Repository Was: Removing git-annex Repo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Am So den 4. Dez 2011 um 22:17 schrieb Joey Hess: > It certianly looks like a bug. Ok. > I cannot even think of how it would be changing git-annex:uuid.log > when all you did is a drop, and particularly if there was no > auto-merge of another git-annex branch. There was, but tist is many commits ago now. > Can you check out the git-annex branch and run git-log on uuid.log, > and see what the most recent change to it looked like? It is an update. After that I revert this update and the next time it will purged again. > Do you have any clues how I can set up a repository that replicates this > behavior? I did nothing special. I'll try to create a demo. Gruß Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQGcBAEBCgAGBQJO3BDTAAoJEKZ8CrGAGfaslkcL/0YDTHI8JPYaK2Se9qDVIvXP 6B9Lrhn9tyyzneeQGTsmp4K50//hg0OydZvOFY7inO9JhBN4igHoo2A7n8djpNow d4EF+7w1rqqfRXiDxK29US1He9A59BXnG4TUFfSG/T90JRqs1ooUQ/P0QYkGCE9y eB/dr4J7x2e+WvPR7mz/XdiotidITS77fk1jHzgwTVXZtKmytYUm5CNZDkW3Zj4l YCHjkGOijFN4Fk+eA7td1zWJFc7ePQOPulCLuQ0xC6/T1KqUH8oCtjXr2eSdSzNe Nb+skk0qZfH34PDKibuprJVHmBysyUw+XTCuyLvl9lBHM7Ao3/EYVw5ztnwF+diT OFwuv0dyPuIL+hJzRoeaNP3cDM45HNMdbRfXdexmxNMg0H7xnv08p03wLx7TKm0I 1I5Ngn5SMLWPkEyQ77SotL4odpWyV18kS8+Xn06yRhGrKg5UfF3E6NYx/iFRMb48 PUpV6CE+4nxfeWgv8ZCqnKksOMyO1F/DMzzOSe47zQ== =akar -END PGP SIGNATURE- ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
Re: Lost Repository Was: Removing git-annex Repo
-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.2022 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 ---- -- Backup semitrusted repositories: 2 ----0001 -- web ---- -- here (Master) untrusted repositories: 1 ---- -- 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 ---- -- Backup semitrusted repositories: 2 ----0001 -- web ---- -- 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 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- ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
Lost Repository Was: Removing git-annex Repo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 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. That leads me again to the question where annex do have its store what it like and what not? I use version 3.2022 from Debian at the moment. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQGcBAEBCgAGBQJO2l6oAAoJEKZ8CrGAGfasmw4L/jdTf4IAYygQ82e/ODsBw3y4 mrctrVgzbOW6d3OCx7fVI52yzijVSMg7k7ghJ+lJxP93xFMcb8YGcBioRjZzyb/9 D45fZALG9kmNMBw1mjBi/XypnPTJRvt8XZRrlPTB4tqGrYSe+eYdjZzhByVEbL7z wx55jJjTCL0xHL1VIUWj64iO4P/36634eQVXMh13ZAABE4mcA0WmY/sVz8bsL8I1 Vyz5mhs/OM4mGxe9WxKcrJhYLUp+Z8CIJvwiwhQPlIlowUDgaznxkzcYht4rajMu nXOdo6YFNQB4VkwDvfvaYjJK7i5nMx+egJPoG3rQe/+jUSIUIIwgbATg77mJPCyd HkbuP0eCeZTxSzRyu7gkDhDcJB7TjuF0Dv2lI1qAi+7WuaWPzrV2TobCjGAEtCoX JNd0R0oPk/O/A8Uf57ROjenOKUuZuBp7GmbLonK6Xc7nQD0fnlv8RqDWwB4LG5PO YP/EOO3alKBFSekFSaj8yxSQY2JOh8M+89Q47FG9rA== =qCcI -END PGP SIGNATURE- ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
Re: Removing git-annex Repo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hiho, Am Fr den 2. Dez 2011 um 21:18 schrieb Joey Hess: > Klaus Ethgen wrote: > > is there a other way than "git checkout git-annex; sed -i -e > > '//d' **/*(.); git commit -a; git checkout master" to remove a > > repository completely from annex knowledge? > > Well, that doesn't actually work; I felt it. > if you do that and then pull a independantly changed git-annex branch > from a remote, the auto-union-merge will then add back all the lines > you removed. 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. > Marking the repository untrusted is the usual way. I red about. But I want to wipe out the whole repository and don't want to have inherited waste. And yes, I can do the cleanup on all remotes too. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQGcBAEBCgAGBQJO2TsMAAoJEKZ8CrGAGfasgcwL/2uwSDto2z2kOzfhrDq67812 2SsW3SM+3aFX2j7jCSCw2hm0Pk0Dx5J2vuOge8qu2fk9yStxVB/DpvwZZQLn73PW Pha993XxHCbPxj+IvQA+pYbFZJ5Chq7GQdhrlfLQp1/Y+Y04FVvsVfLZzNoBghSC HMSejI3vINaL1nyVkgJ0QDagUpNmcNeFsqoDJA/6wCne3EbypoItYZGXNJWWj6QH RXe1ioMynUYo8B5lt3e6PN11w8tU1qqhOIeVODe8oqmgU21dEer/wkxRXlpkmPsJ 0PoJvDWYSVhBdER54+mzculeqTO/NHXjMAb8H9J0VNylnUWyf2s1S27r+Vu22RlA IufcqGL5HuetkUgtZkXtIpk+zvLOF7yjxurX6unECFeJtZSYSRg+9b1SM5pFVJct 0glqEV9RK8iicCZmn3MmA+KUk1I6TI4wd6SjPbYHSBWlOT8fjjRa9+H/ouoJWBlI 6eKupbuzrAcDd5s8QE8hznAheuyRslz6+ofoX4D0dA== =6Fqo -END PGP SIGNATURE- ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
Removing git-annex Repo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi all, is there a other way than "git checkout git-annex; sed -i -e '//d' **/*(.); git commit -a; git checkout master" to remove a repository completely from annex knowledge? Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQGcBAEBCgAGBQJO2RUHAAoJEKZ8CrGAGfasWwIL/i35UgG7tAiAJxRRnqgRuAZh HuyA/B7eTGryRBfO8bHPBpShZhgkByuJU6FwEZtMpLaa6pIkQ9pOdD/vu+zrpJ2L 3Q2VHjtyCHsnsrKjH7qrA2PwQ88tG1X/8sBhUwwLWW9lUNAXdRZIEEelytHFj49c RR46/8s0KdkhFcsFUUqR6emf+JQDg4n8UguMUM2efO5JMzYVeMZs7EqlOHqjaasa yIS5+z+jHfZT4prpX6CI07+5QkJfdzGl+V2S0ex4KsB1DkvhmIGZ3Yi2CLIKs0A/ 1t2sCbyw/VhGMU+qxJCV2hiZ9LLi/oMy01IA+8x7j/2AU2axqiuMxify+cKz+F/s rHwYnoKE1BCaOkbsEynR1wpu5I8YoW4fWf4PUMiys8uBILeVW3ArK5VX6pQFg7oU dd3B1wrRd8OZA+z1b5PK+pmd5HsRS2ipl9gCtRqtlckzscdsBE8DMxgPMA8gwV5F dzxd4geKfXQDOUsPND75CXvkr3PR9S/v5ZQmd0Lhjg== =ErBb -END PGP SIGNATURE- ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
