Handle fetch from contrib/replicant-next/ instead of replicant/

Using '..' enables repo to use URL relative to the location it
was fetched from. This is really handy as we can enable
multiple protocol with the same git repository:
- http:// is useful for potential caching on a network
- https:// is probably more secure and privacy friendly
  and is typically not blocked by restrictive network
  policies.
- git:// is probably secure, privacy friendly and more
  efficient and sometimes blocked by restrictive network
  policies.

However the side effect is that it makes the fetch relative
to the URL it is cloned from, which can create issues if the
depth level is changed. This works around such issue for
repositories not yet in the main namespace.

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

1 files changed, 2 insertions, 2 deletions

diff --git a/replicant/remotes.xml b/replicant/remotes.xml
index 6152dae..bff0c69 100644
--- a/replicant/remotes.xml
+++ b/replicant/remotes.xml
@@ -2,8 +2,8 @@
 <manifest>
   <remote  name="replicant-next"
            revision="replicant-next"
-           fetch=".." />
+           fetch="../.." />
 
   <remote  name="replicant-mirrors"
-           fetch="../mirrors" />
+           fetch="../../mirrors" />
 </manifest>