blob: 34b52213c2294190fade75424c588cf8703f5d2f (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
|
### Please describe the problem.
When adding a new remote which is not accessible (hence still unsynced) git annex tries to connect to it at each remote operation, even if a specific other remote is given for the command.
### What steps will reproduce the problem?
<pre>
git init 1
cd 1
git annex init
touch file
git annex add file
git commit -m"a file"
git clone . ../2
git remote add 2 ../2
git annex sync 2
</pre>
At this point annex syncs with remote "2" and nothing else
But if adding a (currently) unaccessible remote
<pre>
git remote add bad nobody@offline.local:nothing
git annex sync 2
</pre>
gives
<pre>
ssh: Could not resolve hostname offline.local: Name or service not known
ssh: Could not resolve hostname offline.local: Name or service not known
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
commit ok
pull 2
ok
push 2
Everything up-to-date
ok
</pre>
so annex tries to sync with the "bad" remote, even though the command tells it to only sync from "2". I would expect it to only sync with remote "2" in this case.
### What version of git-annex are you using? On what operating system?
git-annex version: 5.20131221
Debian Sid
> Behaving as intended. [[done]] --[[Joey]]
|
