[opensuse-buildservice] osc up impossible
cd ~/osc/devel:ARM:13.2:Contrib:Allwinner osc up Your working copy './kernel-default' is in an inconsistent state. Please run 'osc repairwc ./kernel-default' (Note this might _remove_ files from the .osc/ dir). Please check the state of the working copy afterwards (via 'osc status ./kernel-default') osc repairwc ./kernel-default done. Please check the state of the wc (via 'osc status ./kernel-default'). osc st kernel-default ? kernel-default/README.KSYMS ... osc up resuming broken update... failed to add file 'README.KSYMS' file/dir with the same name already exists osc up kernel-default resuming broken update... failed to add file 'README.KSYMS' file/dir with the same name already exists osc co kernel-default error: './kernel-default' is already an initialized osc working copy osc repairwc kernel-default osc: working copy 'kernel-default' is not inconsistent osc-0.151.2-11.1.noarch So osc can't fix it, check it out, or update it. How do I fix it? Is there any kind of test mode for osc up, so I can check how it proposes to wreck my local copy before actually doing so? The above problem likely resulted from hitting ^C on osc up because it insisted on downloading far more stuff then I needed at the time, at snail's pace when I was doing other work. Thanks, Volker -- Volker Kuhlmann http://volker.top.geek.nz/ Please do not CC list postings to me. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Volker Kuhlmann
How do I fix it?
Try removing the offending file. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thu 07 May 2015 19:16:14 NZST +1200, Andreas Schwab wrote:
Try removing the offending file.
Well I can, but then the same happens with the next file. Running repairwc doesn't see any problem. This means going through every file of all 200MB, or what ever portion of that has already been downloaded. That's a ridiculous waste of time and bandwidth, so I was looking for a better way. Thanks, Volker -- Volker Kuhlmann http://volker.top.geek.nz/ Please do not CC list postings to me. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 2015-05-07 19:46:25 +1200, Volker Kuhlmann wrote:
On Thu 07 May 2015 19:16:14 NZST +1200, Andreas Schwab wrote:
Try removing the offending file.
Well I can, but then the same happens with the next file. Running repairwc doesn't see any problem.
Yes, because the wc is not inconsistent.
This means going through every file of all 200MB, or what ever portion of that has already been downloaded.
Everything has been downloaded at this point.
That's a ridiculous waste of time and bandwidth, so I was looking for a better way.
Huh? You can also use "osc up -l <size>" to download only files with less than <size> bytes. Or use "osc less/cat" if you just want to view a particular file. Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (3)
-
Andreas Schwab
-
Marcus Hüwe
-
Volker Kuhlmann