Issue 2566: clone crashes when target is on different file system - Darcs bug tracker

Title	clone crashes when target is on different file system
Priority	urgent	Status	resolved
Milestone		Resolved in
Superseder		Nosy List	bfrk
Assigned To		Topics

Created on 2018-02-18.11:14:52 by bfrk, last changed 2020-08-01.10:30:54 by bfrk.

Messages
msg19895 (view)	Author: bfrk	Date: 2018-02-18.11:14:50
What I did is > darcs clone . /tmp/blabla WARNING: creating a nested repository. Copying patches, to get lazy repository hit ctrl-C... darcs: ./darcs_new25356: renamePath:rename: unsupported operation (Invalid cross-device link) It seems darcs is trying to rename a file across a file system boundary.
msg19896 (view)	Author: bfrk	Date: 2018-02-18.11:31:14
Strangely, this only happens with clone . /tmp/blabla It works fine when I do cd /tmp clone ~/src/darcs/whatever blabla
msg19897 (view)	Author: bfrk	Date: 2018-02-18.13:09:56
I tracked it down to this patch: patch 94914596fe8fcfed224f45872aa8851b33d14fc9 Author: 'Ben Franksen <ben.franksen@online.de>' Date: Thu Oct 26 19:12:33 CEST 2017 * refactored creation of new repositories Will investigate.
msg19899 (view)	Author: bfrk	Date: 2018-02-18.16:50:24
We need a way to test commands involving operations between local repos in different file systems. I have no idea yet how to do that.
msg22351 (view)	Author: bfrk	Date: 2020-08-01.10:30:52
Resolved, I think by patch 94914596fe8fcfed224f45872aa8851b33d14fc9 Author: 'Ben Franksen <ben.franksen@online.de>' Date: Thu Oct 26 19:12:33 CEST 2017 * refactored creation of new repositories

History
Date	User	Action	Args
2018-02-18 11:14:52	bfrk	create
2018-02-18 11:31:15	bfrk	set	messages: + msg19896
2018-02-18 13:09:58	bfrk	set	messages: + msg19897
2018-02-18 16:50:26	bfrk	set	messages: + msg19899
2020-08-01 10:30:54	bfrk	set	status: unknown -> resolved messages: + msg22351