[EMAIL PROTECTED] wrote:
Second, to create all the symlinks you only
need a simple command not a script: `ln -s ~/dotfiles/* ~/`.
That won't deal with dotfiles that are renamed or deleted.
I'm not entirely clear on why, in the examples I've seen, the -s option is
used to create symbolic
This is a problem I'm increasingly stuggling with as I have more and
more git repositories, that were converted from old subversion
repositories etc. How do I make sure I don't accidentially delete a
repository that has historical data I will want later? How do I know
which historical repository
Richard Hartmann wrote:
I would love to have variables supported in addition to absolute and
relative paths in .mrconfig. At the least, ~ should work and
$XDG_CONFIG_HOME (or other generic ones) would be even better.
It's not documented, so perhaps it's a bug, but you can already do this. Ie:
Dieter Plaetinck wrote:
@Joey: you mentioned you think inotify might be a better
backend/paradigm for this than fuse, so do you think implementing
git-annex in something like dvcs-autosync is feasible? and/or
preferable?
Feasable? Certianly. Preferable? I'm in the let a thousand flowers
bloom
Dieter Plaetinck wrote:
I think having support for this in git-annex would be very useful,
even if it's not that efficient: if this can be dealt with in
git-annex, individual higherlevel projects like sharebox and
dvcs-autosync have less headaches. Not to mention
sharebox/dvcs-autosync
Richard Hartmann wrote:
I know Joey pondered this as well, you will find some references on
git-annex' ikiwiki. This is needed for S3 in the medium term, anyway.
Basically, the plan is to encrypt the files with a symmetric key and
then allow access to that key via other keys. That way, you
micah anderson wrote:
But what if someone adds a new remote? Because I put things in the
.mrconfig as a 'post_checkout' the new remote will not be added to the
git repository. I could add the remotes twice, in a post_checkout (for
the new person who wants to get them all) and then also as a
Richard Hartmann wrote:
I would like to use mr to run `git gc` on all my git repos. While I
could add a gc, or repack, option to my configs, I am wondering if
there is a way for mr to only act on a certain type of repo.
The manpage seems to imply there no way to do this, but I figured
Richard Hartmann wrote:
is there any way to access command line parameters via the config? Setting
quiet = 1
jobs = 5
in my main .mrconfig does not yield the desired effect.
This is not currently supported, but I'd probably accept a reasonable
clean patch.
--
see shy jo
Richard Hartmann wrote:
If the attached qualifies, I can add support for verbose, quiet,
stats, and interactive and update the docs.
Lot of code bloat. This would probably be a good oportunity to move the
global config variables into a hash, which could then be queried and
also filled in by
micah anderson wrote:
[DEFAULT]
post_checkout = mr addremotes
pre_update = mr addremotes
Of course these run on all repos, like any mr command.
So, what's really needed is:
[DEFAULT]
post_checkout = mr -d $MR_REPO addremotes
pre_update = mr -d $MR_REPO addremotes
--
see shy jo
Richard Hartmann wrote:
Hi all (i.e. Joey),
git annex fsck
is a no-op in a bare repository. While I can understand that there is
no (easy) way to verify the symlinks, the annex objects are there
regardless.
Wouldn't it make sense to allow me to check repo integrity in bare
repos, as
, and only found
googles repo and Mike Pearce's show_status. I have dubbed the
latter clustergit and have been using it ever since.
Today a friend told me about Joey Hess' mr, that seems to be able to
do a lot of the things I need, but IMHO is comparatively difficult to
set up and is not covered
Richard Hartmann wrote:
* git annex status does not know about the global annex keys size
I think this could be fixed fairly easily using the existing code to
list the keys in a non-checked out git branch.
One thing I have been pondering is to create a local clone of the bare
repo and
Richard Hartmann wrote:
On Thu, Oct 27, 2011 at 18:31, Joey Hess j...@kitenet.net wrote:
I think this could be fixed fairly easily using the existing code to
list the keys in a non-checked out git branch.
Sounds good. Would that cover the other noted limitations, as well?
Unsure what
Richard Hartmann wrote:
The problem is that, afaik, I can't have it as a bare special remote.
It would be very weird to have a bup repository that is *not* bare.
The use case is that I built hosted a server for backups and backups
only. As origin, it's used to sync git state between all
Richard Hartmann wrote:
On Thu, Oct 27, 2011 at 21:21, Joey Hess j...@kitenet.net wrote:
It would be very weird to have a bup repository that is *not* bare.
True; what I meant was the merged bup annex, indeed.
As I said, it's probably possible to use a branch of the same repository
Richard Hartmann wrote:
fatal: ambiguous argument 'git-annex..refs/remotes/origin/git-annex':
unknown revision or path not in the working tree.
It seems your repository has lost the git-annex branch.
You might try running git fsck to get a better view of the damage,
but it's unlikely to fix
Adam Spiers wrote:
If I have multiple repository paths all similar but spread across
different .mrconfig files, e.g.
in ~/.mrconfig
[.config/mr]
checkout = ...
in ~/.config/mr/config.d/CLI:
[$HOME/.git-repos/zsh]
...
[$HOME/.git-repos/mutt]
...
and in
Adam Spiers wrote:
So far mr is clearly winning :-) However, cfgctl does have one or two
tricks up its sleeve:
- Config modules / packages / repositories / whatever you want to
call them are indexed by name within a unique namespace, rather
than by directory path, and packages
Richard Hartmann wrote:
No, the branch was still there. If you want the contents, I can send
them off-list.
Hmm, either the main git-annex branch or origin/git-annex seems to be
missing based on the error message, and I don't think it's the latter.
Sounds like a good idea. One question about
Richard Hartmann wrote:
On Fri, Oct 28, 2011 at 21:23, Joey Hess j...@kitenet.net wrote:
Hmm, either the main git-annex branch or origin/git-annex seems to be
missing based on the error message, and I don't think it's the latter.
Both are there.
git log git-annex..origin/git-annex fails
Adam Spiers wrote:
I already did this; in fact I *had* to, in order to support GNU stow,
which requires the stow package namespace to be the list of
directories under a single stow directory. If you look for
$STOW_PKG_PATH in the code I originally posted, you'll see:
Richard Hartmann wrote:
Is there any technical reason that would make
git annex init test --uuid=foo
impossible? That way, I could re-use the UUID when I _know_ it's OK to
reuse them.
There is no technical reason that could not be done, but copying the
.git/config has the same effect
Richard Hartmann wrote:
On Sat, Oct 29, 2011 at 18:58, Joey Hess j...@kitenet.net wrote:
There is no technical reason that could not be done, but copying the
.git/config has the same effect today.
OK, so git annex init, edit the UUID manually and then start to add
data? That would still
Adam Spiers wrote:
I notice that chaining to absolute paths does not work, e.g.:
[$HOME/foo/bar]
checkout = ...
chain = true
This is due to the way the chaining code checks for an .mrconfig in
the chained repository:
if ($parameter eq 'chain'
length
Adam Spiers wrote:
On Wed, Nov 02, 2011 at 05:02:13PM -0400, Joey Hess wrote:
Adam Spiers wrote:
I notice that chaining to absolute paths does not work, e.g.:
Is this a feature or a bug? I would have thought it would be useful
to chain to absolute paths.
Probably because nobody
Adam Spiers wrote:
- Do you track your mrconfig files with version control?
yes
How do you do that? Are they all in one repo? How do you get each
one into the right subdirectory of ~ ?
They're checked out by mr as part of the repositories that provide the
subdirectories they're
Svend Sorensen wrote:
I'm using mr to manage the repositories for the various software that I
track. However, I don't want to check out all the repos by default. (The
list is getting long). I also don't want to make a modification to the
.mrconfig each time I want to check out a repo. (E.g.
Svend Sorensen wrote:
How do I force mr to checkout a lazy repo? 'mr checkout' seems to ignore any
arguments, so 'mr checkout repo' skips repos that have 'skip = lazy'. If I
manually create the repo directory, mr thinks the repo is already checked out.
Yes, this is a use case for mr checkout
Joey Hess wrote:
Svend Sorensen wrote:
How do I force mr to checkout a lazy repo? 'mr checkout' seems to ignore any
arguments, so 'mr checkout repo' skips repos that have 'skip = lazy'. If I
manually create the repo directory, mr thinks the repo is already checked
out.
Yes
Adam Spiers wrote:
Thanks for the info, but I'm confused because that doesn't seem to
correspond exactly with the layout you gave earlier. For example, you
said that you have a ~/doc/.mrconfig, but you didn't say that there
was a repository tracking ~/doc itself - only that ~/doc had various
Thomas Koch wrote:
Hi,
I'm starting to learn git-annex and tried by creating one local git-annex
enabled repo on my laptop. Then I wanted to create another non-bare repo on
my
server to push to it.
I can not access my laptop from the server, since I'm sitting behind a NAT.
However
Adam Spiers wrote:
I've made a lot of progress since this last mail, and I'm conscious
that my branch is now approximately 50 commits ahead of the official
master branch, so I think it's time to work on convergence if
possible.
It would be helpful if you:
* separated the stow stuff into its
Adam Spiers wrote:
Thanks for the reply. Sure - I can syphon those commits off into a
stow branch. It bothered me too that they were non-contiguous. In
fact, I appreciate that just dumping a whole load of uncategorised
commits on your doorstep isn't particularly helpful, so maybe it's
Adam Spiers wrote:
OK. I'm not entirely sure I understand what you want though. How
would you define self-contained in this context?
Any patch that does not depend on any other patch.
IMHO it's an impossible task without color.
Scanning for a new paragraph (\n\n) is an impossible task?
--
Klaus Ethgen wrote:
is there a other way than git checkout git-annex; sed -i -e
'/hash/d' **/*(.); git commit -a; git checkout master to remove a
repository completely from annex knowledge?
Well, that doesn't actually work; if you do that and then pull a
independantly changed git-annex branch
Adam Spiers wrote:
$ git annex --help
No manual entry for git-annex
Is this issue related to the fact that I installed git-annex with cabal
install?
Yes, as far as I know, cabal does not have a way to handle man pages.
make install does install one, that git brings up when you run this
Adam Spiers wrote:
I set up two git annex repos on the local machine which point to each
other and then run git annex map, it chews up a load of CPU,
presumably trying to traverse the cyclic repository graph without ever
noticing there's a loop:
Fixed, it only happened when the repos referred
Adam Spiers wrote:
9c87f2352214175de307efedb8fd93889a26afbc
Can you give an example of when this is needed?
I can't remember but I definitely saw it happen at least once :-/
My worry is that, since that really shouldn't happen AFIACS, you
were actually seeing a bug. Either that or
Adam Spiers wrote:
This may be a good time to discuss the design of the `include'
parameter. When you were deciding what its value should be, I guess
there were at least three possibilities:
(1) a chunk of shell-code which returns the actual shell-code to
include
(2) a
Joey Hess wrote:
It could well not be. mr list -j 10 runs in the same time as mr list -j 1,
suggesting the overhead is in something else than actually running the
shell.
Whoops, bad benchmark, -j comes before action.
Anyway, yes, without any calls to system(), mr list takes just 0.35 seconds
Joey Hess wrote:
Moving the git_test etc into perl code would be one way to speed it up
for the common case. Adding a special case optimisation to avoid the shell
for true and false brings mr list down from 8.50 to 1.81 seconds.
The remaining time is here spent running skip tests, I have a lot
Sean Whitton wrote:
Currently reviewing my setup; switching from madduck’s vcsh to RichiH’s,
and from unison to git-annex for my ~/var/ directory of massive media
files and backups and the like. Liking it so far.
Have installed ghs using my distribution’s package (CRUX, it’s
source-based)
Adam Spiers wrote:
Firstly, I built a library of skip functions:
https://github.com/aspiers/mr-config/blob/master/lib/skippers
which lets me write things like:
[$HOME/.GIT/adamspiers.org/gnupg.sec]
skip = default_skipper || missing_exe gpg
I'm with you so far; this is how I
Sean Whitton wrote:
On my second machine, my laptop, I don’t seem to be able to push to the
centralised repository: I am getting the error one gets when one hasn’t
yet done a pull and done a merge, but I definitely have:
| ! [rejected]git-annex - git-annex (non-fast-forward)
You
Adam Spiers wrote:
Furthermore,
git annex whereis --not --in=
lists all files, not just the ones which aren't locally available.
joey@gnu:~/lib/soundgit annex whereis --not --in=
git-annex: no remote specified
If your mailer is eating trailing periods or something.. whereis
Adam Spiers wrote:
On Fri, Dec 23, 2011 at 5:13 PM, Joey Hess j...@kitenet.net wrote:
Adam Spiers wrote:
I don't get that error message.
version?
3.20111211
So, your git-annex version was, apparently, seeing --in= as in the
remote named '', and doing the expensive query of git
Adam Spiers wrote:
git annex add this_file_does_not_exist
does not result in a warning. This leads to confusing (lack of)
behaviour in certain cases, e.g.
generate_a_list_of_files_some_of_which_contain_spaces | xargs git annex
add
would silently fail to add the files
Richard Hartmann wrote:
On Thu, Dec 15, 2011 at 20:44, Richard Hartmann
richih.mailingl...@gmail.com wrote:
You need to run git annex merge before pushing and all will be well.
This seems to be a _very_ common problem for new users. I know it's a
message from git, not git-annex, but
Adam Spiers wrote:
there is a bigger cost - the risk of having a version of the completion
rules which does not match the version of mr installed.
This is, in practice, not a large problem, and can be dealt with by
distribution integrators.
There's also a converse argument. Completion
Richard Hartmann wrote:
On Sat, Dec 24, 2011 at 15:44, Joey Hess j...@kitenet.net wrote:
Since using git-ls-files is so convenient in most ways, all I can
think to do about this is document it.
--error-unmatch ?
Produces a strange error message if run on files that are already in
git
Klaus Ethgen wrote:
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
Sean Whitton wrote:
Thank you for your reply, and sorry for not thinking a little more before
e-mailing. Here is the output. I think that this may be a vcsh problem
rather than a mr problem after looking at this.
Looks to me like a mr version older than 1.09 being used with a mr
include file
Adam Spiers wrote:
I find some parts of the mr script quite hard to follow, and
consequently to write patches for. For example, loadconfig() has 221
lines, and is 8 levels of indentation deep at certain points. Would
you accept extract subroutine refactoring patches which do not
change the
Yaroslav Halchenko wrote:
so I could use the same mr configuration across boxes even where I do
not forward my ssh key, while leaving me an opportunity to push later on
happen I need that (not to mention that why to bother with ssh tunneling
for pulling if straight git: is available)
It also
Thomas Koch wrote:
It'd be of course wonderful if I could tell git-annex directly to import all
files of the disc. Duplicate files should symlink to the same file in the git-
annex backend, shouldn't they?
Yes. If you don't mind the overhead of copying all the files, simply
copying the whole
Thomas Koch wrote:
I'm thinking, how a simple web photo gallery setup could be possible with git-
annex, a static gallery generator like lazygal (Debian packaged) and some
scripting.
But to make this a viable alternative to facebook for my wife, I'd
additionally need (or like):
-
Paul Stodghill wrote:
1. Do something with symbolic links other than ignore them.
Note that this is a potentially difficult security situation.
One idea that has been floated is to keep the annexed files in a
different repo, in an ikiwiki underlay. It would be easier to make
ikiwiki skip
Thomas Koch wrote:
Hi,
still about photos and git-annex: When my wife edits photos prior to
uploading
them, it would be fine if she wouldn't need to know about git-annex. Hacking
git-annex support in every photo application is no option.
But is there any linux kernel or LD_PRELOAD
Thomas Koch wrote:
Hi,
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?
Adam Spiers wrote:
Looks to me like you got the order wrong - don't you need
to commit and push *before* the git annex copy? Otherwise
the meta-data for doc.2012.tar.gz isn't in the git-annex branch
when the annex copy is done and it will just copy the previous
contents of oldscm to
René Mayrhofer wrote:
No, I punted on it. The inotify managed directory will behave
differently/annoyingly when the user tries to modify files. This
certianly doesn't perfectly cover every use case, but I feel it's an
ok tradeoff, you can get used to that behavior.
There is some event
Sean Hammond wrote:
I think it worked. Git annex assistant did a lot of transferring,
and when it was eventually done the number of files and size of the
~/Annex/Music dir is exactly the same on both machines, and the
files look fine.
The ~/Annex/.git dirs are quite big though: 640M and
Sean Hammond wrote:
1. The total number of files in ~/Annex, not including .git, on A
and B is different:
ls -R1 ~/Annex | wc -l
21830
ls -R1 ~/Annex | wc -l
21845
2. git-annex status shows untracked and modified files on both
machines (different files on each machine).
These seem
Matthew Hannigan wrote:
Anyway, time passes, and I decide to move all this content over to a
different disk.
I just used drag and drop from a gui (not sure whether windows or
linux) and of course the select doesn't pick up the .git directory.
Next I reformated the disk, and get a funny
Lorenzo Cappelletti wrote:
Signed-off-by: Lorenzo Cappelletti lorenzo.cappelle...@gmail.com
---
mr | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mr b/mr
index ddc0738..ecd1c02 100755
--- a/mr
+++ b/mr
@@ -2076,7 +2076,7 @@ bzr_trusted_checkout = bzr
Edward Betts wrote:
The page http://vcs-home.branchable.com/recentchanges/ contains spam.
Reverting it meant deleting recentchanges.mdwn. How do I get my change
onto the wiki?
There's a bug in ikiwiki where refresh does not notice a deleted page
has exposed a page from the underlay. A
Seems to me that mr -m status is what you seek.
--
see shy jo
___
vcs-home mailing list
vcs-home@lists.madduck.net
http://lists.madduck.net/listinfo/vcs-home
69 matches
Mail list logo
