https://bugzilla.novell.com/show_bug.cgi?id=690492 https://bugzilla.novell.com/show_bug.cgi?id=690492#c0 Summary: osc co/up corrupts working copy Classification: Internal Novell Products Product: openSUSE Build Service Version: master Platform: x86-64 OS/Version: Linux Status: NEW Severity: Critical Priority: P5 - None Component: osc AssignedTo: adrian@novell.com ReportedBy: ohering@novell.com QAContact: adrian@novell.com Found By: Outsourced Testing Blocker: --- This has already been reported (my connection problem was caused by the firewall in the dsl router, it just triggered the corruption) http://lists.opensuse.org/opensuse-buildservice/2010-04/msg00264.html I upgraded a SLES11SP1 osc to 0.130 and later to the 0.131 release (which calls itself 0.131git), and the issue got worse and not detectable anymore by wrapper scripts. My svn export script is supposed to run unattended by a cron job. But since the buildservice is unreliable the checkouts, updates, commits and even addremove do often fail. Whats usually left is a broken working copy. Manual intervention is required and that costs much of my time... Wouldnt it be good if osc checkout/update never leaves a mess behind if the process is interrupted in some way? With 0.125.5 as shipped with SLES11 and 11.2 it was possible to edit osc/_files and .osc/_packages and remove incomplete files. The next 'osc up' run will pull these files again and all is fine. This is now broken with 0.131. osc up and co should better arrange the update process in such a way that the working copy is never in an "inconsistent state" no matter what happens during the osc run. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.