You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Paul Maier <sv...@web.de> on 2010/10/20 21:03:56 UTC
1.6.13: svn cleanup fails to cleanup
Hello!
I would be interested, if this problem is fixed in the
current 1.7 trunk.
svn cleanup should be able to repair and unlock the WC.
Unfortunately I am not able to build the trunk from source
myself.
Here is a reproduction script that produces a corrupt WC, and no
svn command can repair it, so the WC seems lost:
svnadmin create xx
svn co "file:///C:/[...]/xx" yy
cd yy
echo a > a
svn add a
svn ci -m ""
svn lock a
svn mkdir 1
mv a 1 # here "forgot" to type svn before the mv
svn ci -m ""
svn st -u
svn cleanup 1
svn cleanup .
svn st -u
The error message advises to use svn cleanup, but svn cleanup
fails to unlock the WC.
(Even though it would be possible:
touch a;
svn cleanup .
unlocks the WC.)
Console output follows:
-----------------------
>svnadmin create xx
>svn co "file:///C:/[...]/xx" yy
>cd yy
yy>echo a 1>a
yy>svn add a
yy>svn ci -m ""
yy>svn lock a
yy>svn mkdir 1
yy>mv a 1
yy>svn ci -m ""
Hinzufügen 1
svn: Übertragen erfolgreich, aber andere Fehler folgen:
svn: Fehler beim Weiterschalten der Revisionen nach der Übertragung (Details folgen):
svn: In Verzeichnis "[...]\yy"
svn: Fehler beim Bearbeiten des Befehls "committed" in "[...]\yy"
svn: Fehler beim Ermitteln der "letzten Änderungszeit" von "[...]\yy\a"
svn: Kann Status von "[...]\yy\a" nicht ermitteln: Das System kann die angegebene Datei nicht finden.
yy>svn st -u
! B 1 a
? 1\a
L 2 1
L 0 .
Status bezogen auf Revision: 2
yy>svn cleanup 1
yy>svn cleanup .
svn: In Verzeichnis "."
svn: Fehler beim Bearbeiten des Befehls "committed" in "."
svn: Fehler beim Ermitteln der "letzten Änderungszeit" von "a"
svn: Kann Status von "a" nicht ermitteln: Das System kann die angegebene Datei nicht finden.
yy>svn st -u
! B 1 a
? 1\a
L 0 .
Status bezogen auf Revision: 2
Thanks & Regards,
Paul
Re: 1.6.13: svn cleanup fails to cleanup
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Paul Maier wrote on Thu, Oct 21, 2010 at 21:28:43 +0200:
> > Could you please file an issue in our tracker, linking to this thread?
>
> To be honest, I have no idea about the meaning of all the necessary
> parameters like priority and DEFECT or ENHANCEMENT and target milestone,
> that I really would appreciate if someone could file that issue for me.
>
JFDI. If you mess up the fields, someone can correct them after the
issue is filed.
I'd call this one a DEFECT. There is no 'target milestone' field on the
'new issue' form (and appropriately so, since that field should be set
by the developers).
> Let's say, if nobody took over filing this issue till - say - weekend,
> I will then try to do it.
>
> Deal?
>
> @Daniel: Thanks for having tested this!
>
You're welcome, and thanks.
> Paul.
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: Daniel Shahaf [mailto:d.s@daniel.shahaf.name]
> > Gesendet: Donnerstag, 21. Oktober 2010 15:49
> > An: Paul Maier
> > Cc: users@subversion.apache.org
> > Betreff: Re: 1.6.13: svn cleanup fails to cleanup
> >
> > Paul Maier wrote on Wed, Oct 20, 2010 at 23:03:56 +0200:
> > > Hello!
> > >
> > > I would be interested, if this problem is fixed in the
> > > current 1.7 trunk.
> >
> > It's not fixed, see transcript below.
> >
> > Could you please file an issue in our tracker, linking to this thread?
> >
> > (You'll have to create a tigris.org account for that.)
> >
> > Thanks,
> >
> > Daniel
> >
> > > svn cleanup should be able to repair and unlock the WC.
> > > Unfortunately I am not able to build the trunk from source
> > > myself.
> > >
> > > Here is a reproduction script that produces a corrupt WC, and no
> > > svn command can repair it, so the WC seems lost:
> > >
> > > svnadmin create xx
> > > svn co "file:///C:/[...]/xx" yy
> > > cd yy
> > > echo a > a
> > > svn add a
> > > svn ci -m ""
> > > svn lock a
> > > svn mkdir 1
> > > mv a 1 # here "forgot" to type svn before the mv
> > > svn ci -m ""
> > > svn st -u
> > > svn cleanup 1
> > > svn cleanup .
> > > svn st -u
> > >
> > > The error message advises to use svn cleanup, but svn cleanup
> > > fails to unlock the WC.
> > > (Even though it would be possible:
> > > touch a;
> > > svn cleanup .
> > > unlocks the WC.)
> >
> > [[[
> > 0:% cat foo.sh
> > #!/bin/sh
> > $svnadmin create xx
> > $svn co file:///`pwd`/xx yy
> > cd yy
> > echo a > a
> > $svn add a
> > $svn ci -m ""
> > $svn lock a
> > $svn mkdir 1
> > mv a 1 # here "forgot" to type $svn before the mv
> > $svn ci -m ""
> > $svn st -u
> > $svn cleanup 1
> > $svn cleanup .
> > $svn st -u
> > touch a;
> > $svn cleanup .
> > 0:% sh -x ./foo.sh
> > + /home/daniel/src/svn/trunk/subversion/svnadmin/svnadmin create xx
> > ++ pwd
> > + /home/daniel/src/svn/trunk/subversion/svn/svn co
> > file:////tmp/svn/xx yy
> > Checked out revision 0.
> > + cd yy
> > + echo a
> > + /home/daniel/src/svn/trunk/subversion/svn/svn add a
> > A a
> > + /home/daniel/src/svn/trunk/subversion/svn/svn ci -m ''
> > Adding a
> > Transmitting file data .
> > Committed revision 1.
> > + /home/daniel/src/svn/trunk/subversion/svn/svn lock a
> > 'a' locked by user 'daniel'.
> > + /home/daniel/src/svn/trunk/subversion/svn/svn mkdir 1
> > A 1
> > + mv a 1
> > + /home/daniel/src/svn/trunk/subversion/svn/svn ci -m ''
> > Adding 1
> >
> > Committed revision 2.
> > subversion/svn/commit-cmd.c:156: (apr_err=200000)
> > subversion/libsvn_client/commit.c:855: (apr_err=200000)
> > svn: Commit succeeded, but other errors follow:
> > subversion/libsvn_client/commit.c:873: (apr_err=155009)
> > svn: Error bumping revisions post-commit (details follow):
> > subversion/libsvn_wc/adm_ops.c:510: (apr_err=155009)
> > subversion/libsvn_wc/workqueue.c:2282: (apr_err=155009)
> > subversion/libsvn_wc/workqueue.c:2217: (apr_err=155009)
> > subversion/libsvn_wc/workqueue.c:1311: (apr_err=155009)
> > svn: Error processing post-commit work for '/tmp/svn/yy/a'
> > subversion/libsvn_wc/workqueue.c:1134: (apr_err=2)
> > subversion/libsvn_wc/workqueue.c:880: (apr_err=2)
> > subversion/libsvn_subr/io.c:3630: (apr_err=2)
> > subversion/libsvn_subr/io.c:3561: (apr_err=2)
> > subversion/libsvn_subr/io.c:2764: (apr_err=2)
> > svn: Can't open file '/tmp/svn/yy/a': No such file or directory
> > + /home/daniel/src/svn/trunk/subversion/svn/svn st -u
> > subversion/svn/status-cmd.c:326: (apr_err=155037)
> > subversion/svn/util.c:959: (apr_err=155037)
> > subversion/libsvn_client/status.c:300: (apr_err=155037)
> > subversion/libsvn_wc/node.c:193: (apr_err=155037)
> > subversion/libsvn_wc/wc_db.c:4350: (apr_err=155037)
> > subversion/libsvn_wc/wc_db_pdh.c:540: (apr_err=155037)
> > subversion/libsvn_wc/wc_db_pdh.c:268: (apr_err=155037)
> > subversion/libsvn_wc/wc_db_pdh.c:101: (apr_err=155037)
> > svn: Previous operation was interrupted; run 'svn cleanup'
> > + /home/daniel/src/svn/trunk/subversion/svn/svn cleanup 1
> > subversion/svn/cleanup-cmd.c:82: (apr_err=155004)
> > subversion/libsvn_client/cleanup.c:64: (apr_err=155004)
> > subversion/libsvn_wc/cleanup.c:149: (apr_err=155004)
> > subversion/libsvn_wc/cleanup.c:92: (apr_err=155004)
> > subversion/libsvn_wc/wc_db.c:7409: (apr_err=155004)
> > subversion/libsvn_wc/wc_db.c:7409: (apr_err=155004)
> > svn: Working copy '/tmp/svn/yy/1' locked.
> > subversion/libsvn_wc/wc_db.c:7401: (apr_err=155004)
> > svn: '/tmp/svn/yy' is already locked.
> > svn: run 'svn cleanup' to remove locks (type 'svn help
> > cleanup' for details)
> > + /home/daniel/src/svn/trunk/subversion/svn/svn cleanup .
> > subversion/svn/cleanup-cmd.c:82: (apr_err=155009)
> > subversion/libsvn_client/cleanup.c:64: (apr_err=155009)
> > subversion/libsvn_wc/cleanup.c:149: (apr_err=155009)
> > subversion/libsvn_wc/cleanup.c:98: (apr_err=155009)
> > subversion/libsvn_wc/workqueue.c:2282: (apr_err=155009)
> > subversion/libsvn_wc/workqueue.c:2217: (apr_err=155009)
> > subversion/libsvn_wc/workqueue.c:1311: (apr_err=155009)
> > svn: Error processing post-commit work for '/tmp/svn/yy/a'
> > subversion/libsvn_wc/workqueue.c:1134: (apr_err=2)
> > subversion/libsvn_wc/workqueue.c:880: (apr_err=2)
> > subversion/libsvn_subr/io.c:3630: (apr_err=2)
> > subversion/libsvn_subr/io.c:3561: (apr_err=2)
> > subversion/libsvn_subr/io.c:2764: (apr_err=2)
> > svn: Can't open file '/tmp/svn/yy/a': No such file or directory
> > + /home/daniel/src/svn/trunk/subversion/svn/svn st -u
> > subversion/svn/status-cmd.c:326: (apr_err=155037)
> > subversion/svn/util.c:959: (apr_err=155037)
> > subversion/libsvn_client/status.c:300: (apr_err=155037)
> > subversion/libsvn_wc/node.c:193: (apr_err=155037)
> > subversion/libsvn_wc/wc_db.c:4350: (apr_err=155037)
> > subversion/libsvn_wc/wc_db_pdh.c:540: (apr_err=155037)
> > subversion/libsvn_wc/wc_db_pdh.c:268: (apr_err=155037)
> > subversion/libsvn_wc/wc_db_pdh.c:101: (apr_err=155037)
> > svn: Previous operation was interrupted; run 'svn cleanup'
> > + touch a
> > + /home/daniel/src/svn/trunk/subversion/svn/svn cleanup .
> > 0:%
> > ]]]
>
Re: 1.6.13: svn cleanup fails to cleanup
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Paul Maier wrote on Thu, Oct 21, 2010 at 21:28:43 +0200:
> > Could you please file an issue in our tracker, linking to this thread?
>
> To be honest, I have no idea about the meaning of all the necessary
> parameters like priority and DEFECT or ENHANCEMENT and target milestone,
> that I really would appreciate if someone could file that issue for me.
>
JFDI. If you mess up the fields, someone can correct them after the
issue is filed.
I'd call this one a DEFECT. There is no 'target milestone' field on the
'new issue' form (and appropriately so, since that field should be set
by the developers).
> Let's say, if nobody took over filing this issue till - say - weekend,
> I will then try to do it.
>
> Deal?
>
> @Daniel: Thanks for having tested this!
>
You're welcome, and thanks.
> Paul.
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: Daniel Shahaf [mailto:d.s@daniel.shahaf.name]
> > Gesendet: Donnerstag, 21. Oktober 2010 15:49
> > An: Paul Maier
> > Cc: users@subversion.apache.org
> > Betreff: Re: 1.6.13: svn cleanup fails to cleanup
> >
> > Paul Maier wrote on Wed, Oct 20, 2010 at 23:03:56 +0200:
> > > Hello!
> > >
> > > I would be interested, if this problem is fixed in the
> > > current 1.7 trunk.
> >
> > It's not fixed, see transcript below.
> >
> > Could you please file an issue in our tracker, linking to this thread?
> >
> > (You'll have to create a tigris.org account for that.)
> >
> > Thanks,
> >
> > Daniel
> >
> > > svn cleanup should be able to repair and unlock the WC.
> > > Unfortunately I am not able to build the trunk from source
> > > myself.
> > >
> > > Here is a reproduction script that produces a corrupt WC, and no
> > > svn command can repair it, so the WC seems lost:
> > >
> > > svnadmin create xx
> > > svn co "file:///C:/[...]/xx" yy
> > > cd yy
> > > echo a > a
> > > svn add a
> > > svn ci -m ""
> > > svn lock a
> > > svn mkdir 1
> > > mv a 1 # here "forgot" to type svn before the mv
> > > svn ci -m ""
> > > svn st -u
> > > svn cleanup 1
> > > svn cleanup .
> > > svn st -u
> > >
> > > The error message advises to use svn cleanup, but svn cleanup
> > > fails to unlock the WC.
> > > (Even though it would be possible:
> > > touch a;
> > > svn cleanup .
> > > unlocks the WC.)
> >
> > [[[
> > 0:% cat foo.sh
> > #!/bin/sh
> > $svnadmin create xx
> > $svn co file:///`pwd`/xx yy
> > cd yy
> > echo a > a
> > $svn add a
> > $svn ci -m ""
> > $svn lock a
> > $svn mkdir 1
> > mv a 1 # here "forgot" to type $svn before the mv
> > $svn ci -m ""
> > $svn st -u
> > $svn cleanup 1
> > $svn cleanup .
> > $svn st -u
> > touch a;
> > $svn cleanup .
> > 0:% sh -x ./foo.sh
> > + /home/daniel/src/svn/trunk/subversion/svnadmin/svnadmin create xx
> > ++ pwd
> > + /home/daniel/src/svn/trunk/subversion/svn/svn co
> > file:////tmp/svn/xx yy
> > Checked out revision 0.
> > + cd yy
> > + echo a
> > + /home/daniel/src/svn/trunk/subversion/svn/svn add a
> > A a
> > + /home/daniel/src/svn/trunk/subversion/svn/svn ci -m ''
> > Adding a
> > Transmitting file data .
> > Committed revision 1.
> > + /home/daniel/src/svn/trunk/subversion/svn/svn lock a
> > 'a' locked by user 'daniel'.
> > + /home/daniel/src/svn/trunk/subversion/svn/svn mkdir 1
> > A 1
> > + mv a 1
> > + /home/daniel/src/svn/trunk/subversion/svn/svn ci -m ''
> > Adding 1
> >
> > Committed revision 2.
> > subversion/svn/commit-cmd.c:156: (apr_err=200000)
> > subversion/libsvn_client/commit.c:855: (apr_err=200000)
> > svn: Commit succeeded, but other errors follow:
> > subversion/libsvn_client/commit.c:873: (apr_err=155009)
> > svn: Error bumping revisions post-commit (details follow):
> > subversion/libsvn_wc/adm_ops.c:510: (apr_err=155009)
> > subversion/libsvn_wc/workqueue.c:2282: (apr_err=155009)
> > subversion/libsvn_wc/workqueue.c:2217: (apr_err=155009)
> > subversion/libsvn_wc/workqueue.c:1311: (apr_err=155009)
> > svn: Error processing post-commit work for '/tmp/svn/yy/a'
> > subversion/libsvn_wc/workqueue.c:1134: (apr_err=2)
> > subversion/libsvn_wc/workqueue.c:880: (apr_err=2)
> > subversion/libsvn_subr/io.c:3630: (apr_err=2)
> > subversion/libsvn_subr/io.c:3561: (apr_err=2)
> > subversion/libsvn_subr/io.c:2764: (apr_err=2)
> > svn: Can't open file '/tmp/svn/yy/a': No such file or directory
> > + /home/daniel/src/svn/trunk/subversion/svn/svn st -u
> > subversion/svn/status-cmd.c:326: (apr_err=155037)
> > subversion/svn/util.c:959: (apr_err=155037)
> > subversion/libsvn_client/status.c:300: (apr_err=155037)
> > subversion/libsvn_wc/node.c:193: (apr_err=155037)
> > subversion/libsvn_wc/wc_db.c:4350: (apr_err=155037)
> > subversion/libsvn_wc/wc_db_pdh.c:540: (apr_err=155037)
> > subversion/libsvn_wc/wc_db_pdh.c:268: (apr_err=155037)
> > subversion/libsvn_wc/wc_db_pdh.c:101: (apr_err=155037)
> > svn: Previous operation was interrupted; run 'svn cleanup'
> > + /home/daniel/src/svn/trunk/subversion/svn/svn cleanup 1
> > subversion/svn/cleanup-cmd.c:82: (apr_err=155004)
> > subversion/libsvn_client/cleanup.c:64: (apr_err=155004)
> > subversion/libsvn_wc/cleanup.c:149: (apr_err=155004)
> > subversion/libsvn_wc/cleanup.c:92: (apr_err=155004)
> > subversion/libsvn_wc/wc_db.c:7409: (apr_err=155004)
> > subversion/libsvn_wc/wc_db.c:7409: (apr_err=155004)
> > svn: Working copy '/tmp/svn/yy/1' locked.
> > subversion/libsvn_wc/wc_db.c:7401: (apr_err=155004)
> > svn: '/tmp/svn/yy' is already locked.
> > svn: run 'svn cleanup' to remove locks (type 'svn help
> > cleanup' for details)
> > + /home/daniel/src/svn/trunk/subversion/svn/svn cleanup .
> > subversion/svn/cleanup-cmd.c:82: (apr_err=155009)
> > subversion/libsvn_client/cleanup.c:64: (apr_err=155009)
> > subversion/libsvn_wc/cleanup.c:149: (apr_err=155009)
> > subversion/libsvn_wc/cleanup.c:98: (apr_err=155009)
> > subversion/libsvn_wc/workqueue.c:2282: (apr_err=155009)
> > subversion/libsvn_wc/workqueue.c:2217: (apr_err=155009)
> > subversion/libsvn_wc/workqueue.c:1311: (apr_err=155009)
> > svn: Error processing post-commit work for '/tmp/svn/yy/a'
> > subversion/libsvn_wc/workqueue.c:1134: (apr_err=2)
> > subversion/libsvn_wc/workqueue.c:880: (apr_err=2)
> > subversion/libsvn_subr/io.c:3630: (apr_err=2)
> > subversion/libsvn_subr/io.c:3561: (apr_err=2)
> > subversion/libsvn_subr/io.c:2764: (apr_err=2)
> > svn: Can't open file '/tmp/svn/yy/a': No such file or directory
> > + /home/daniel/src/svn/trunk/subversion/svn/svn st -u
> > subversion/svn/status-cmd.c:326: (apr_err=155037)
> > subversion/svn/util.c:959: (apr_err=155037)
> > subversion/libsvn_client/status.c:300: (apr_err=155037)
> > subversion/libsvn_wc/node.c:193: (apr_err=155037)
> > subversion/libsvn_wc/wc_db.c:4350: (apr_err=155037)
> > subversion/libsvn_wc/wc_db_pdh.c:540: (apr_err=155037)
> > subversion/libsvn_wc/wc_db_pdh.c:268: (apr_err=155037)
> > subversion/libsvn_wc/wc_db_pdh.c:101: (apr_err=155037)
> > svn: Previous operation was interrupted; run 'svn cleanup'
> > + touch a
> > + /home/daniel/src/svn/trunk/subversion/svn/svn cleanup .
> > 0:%
> > ]]]
>
Re: 1.6.13: svn cleanup fails to cleanup
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Thanks, Paul.
I've tweaked the description to be slightly more verbose (we have
several 'svn cleanup' issues) and fixed the component (most probably
this is a bug in the library --- where the work is done --- not in the
thin layer that the cmdline client is).
Paul Maier wrote on Sat, Oct 23, 2010 at 01:35:25 +0200:
> filed Issue 3739
> http://subversion.tigris.org/issues/show_bug.cgi?id=3739
>
> Paul.
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: Stefan Sperling [mailto:stsp@elego.de]
> > Gesendet: Donnerstag, 21. Oktober 2010 22:13
> > An: Paul Maier
> > Cc: users@subversion.apache.org
> > Betreff: Re: 1.6.13: svn cleanup fails to cleanup
> >
> > On Thu, Oct 21, 2010 at 09:28:43PM +0200, Paul Maier wrote:
> > > Hi everybody,
> > >
> > > > Could you please file an issue in our tracker, linking to
> > this thread?
> > >
> > > To be honest, I have no idea about the meaning of all the necessary
> > > parameters like priority and DEFECT or ENHANCEMENT and
> > target milestone,
> > > that I really would appreciate if someone could file that
> > issue for me.
> >
> > The bugtracker shouldn't be asking this stuff from our users,
> > but unfortunately it does :(
> > Just pick something and we'll fix it later if it needs fixing.
> > It'll be fine.
> >
> > In this case I'd pick DEFECT, leave the priority at the default
> > and set the milestone to unscheduled. But that doesn't really matter.
> > The most important thing is that the issue gets filed in the tracker
> > so we don't forget about it.
> >
> > Your support with filing issues will be very much appreciated.
> > We all have things to do so if the person who reported an
> > issue also files it,
> > our community as a whole can save some valuable time.
> > See also
> > http://producingoss.com/en/managing-volunteers.html#delegation
> > which explains the deeper reasons for why we tend to ask
> > people to perform
> > tasks. (The short answer is that it's partly about spreading
> > the workload,
> > and partly about building community bonds).
> >
> > Thanks,
> > Stefan
>
Re: 1.6.13: svn cleanup fails to cleanup
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Thanks, Paul.
I've tweaked the description to be slightly more verbose (we have
several 'svn cleanup' issues) and fixed the component (most probably
this is a bug in the library --- where the work is done --- not in the
thin layer that the cmdline client is).
Paul Maier wrote on Sat, Oct 23, 2010 at 01:35:25 +0200:
> filed Issue 3739
> http://subversion.tigris.org/issues/show_bug.cgi?id=3739
>
> Paul.
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: Stefan Sperling [mailto:stsp@elego.de]
> > Gesendet: Donnerstag, 21. Oktober 2010 22:13
> > An: Paul Maier
> > Cc: users@subversion.apache.org
> > Betreff: Re: 1.6.13: svn cleanup fails to cleanup
> >
> > On Thu, Oct 21, 2010 at 09:28:43PM +0200, Paul Maier wrote:
> > > Hi everybody,
> > >
> > > > Could you please file an issue in our tracker, linking to
> > this thread?
> > >
> > > To be honest, I have no idea about the meaning of all the necessary
> > > parameters like priority and DEFECT or ENHANCEMENT and
> > target milestone,
> > > that I really would appreciate if someone could file that
> > issue for me.
> >
> > The bugtracker shouldn't be asking this stuff from our users,
> > but unfortunately it does :(
> > Just pick something and we'll fix it later if it needs fixing.
> > It'll be fine.
> >
> > In this case I'd pick DEFECT, leave the priority at the default
> > and set the milestone to unscheduled. But that doesn't really matter.
> > The most important thing is that the issue gets filed in the tracker
> > so we don't forget about it.
> >
> > Your support with filing issues will be very much appreciated.
> > We all have things to do so if the person who reported an
> > issue also files it,
> > our community as a whole can save some valuable time.
> > See also
> > http://producingoss.com/en/managing-volunteers.html#delegation
> > which explains the deeper reasons for why we tend to ask
> > people to perform
> > tasks. (The short answer is that it's partly about spreading
> > the workload,
> > and partly about building community bonds).
> >
> > Thanks,
> > Stefan
>
AW: 1.6.13: svn cleanup fails to cleanup
Posted by Paul Maier <sv...@web.de>.
filed Issue 3739
http://subversion.tigris.org/issues/show_bug.cgi?id=3739
Paul.
> -----Ursprüngliche Nachricht-----
> Von: Stefan Sperling [mailto:stsp@elego.de]
> Gesendet: Donnerstag, 21. Oktober 2010 22:13
> An: Paul Maier
> Cc: users@subversion.apache.org
> Betreff: Re: 1.6.13: svn cleanup fails to cleanup
>
> On Thu, Oct 21, 2010 at 09:28:43PM +0200, Paul Maier wrote:
> > Hi everybody,
> >
> > > Could you please file an issue in our tracker, linking to
> this thread?
> >
> > To be honest, I have no idea about the meaning of all the necessary
> > parameters like priority and DEFECT or ENHANCEMENT and
> target milestone,
> > that I really would appreciate if someone could file that
> issue for me.
>
> The bugtracker shouldn't be asking this stuff from our users,
> but unfortunately it does :(
> Just pick something and we'll fix it later if it needs fixing.
> It'll be fine.
>
> In this case I'd pick DEFECT, leave the priority at the default
> and set the milestone to unscheduled. But that doesn't really matter.
> The most important thing is that the issue gets filed in the tracker
> so we don't forget about it.
>
> Your support with filing issues will be very much appreciated.
> We all have things to do so if the person who reported an
> issue also files it,
> our community as a whole can save some valuable time.
> See also
> http://producingoss.com/en/managing-volunteers.html#delegation
> which explains the deeper reasons for why we tend to ask
> people to perform
> tasks. (The short answer is that it's partly about spreading
> the workload,
> and partly about building community bonds).
>
> Thanks,
> Stefan
Re: 1.6.13: svn cleanup fails to cleanup
Posted by Stefan Sperling <st...@elego.de>.
On Thu, Oct 21, 2010 at 09:28:43PM +0200, Paul Maier wrote:
> Hi everybody,
>
> > Could you please file an issue in our tracker, linking to this thread?
>
> To be honest, I have no idea about the meaning of all the necessary
> parameters like priority and DEFECT or ENHANCEMENT and target milestone,
> that I really would appreciate if someone could file that issue for me.
The bugtracker shouldn't be asking this stuff from our users,
but unfortunately it does :(
Just pick something and we'll fix it later if it needs fixing.
It'll be fine.
In this case I'd pick DEFECT, leave the priority at the default
and set the milestone to unscheduled. But that doesn't really matter.
The most important thing is that the issue gets filed in the tracker
so we don't forget about it.
Your support with filing issues will be very much appreciated.
We all have things to do so if the person who reported an issue also files it,
our community as a whole can save some valuable time.
See also http://producingoss.com/en/managing-volunteers.html#delegation
which explains the deeper reasons for why we tend to ask people to perform
tasks. (The short answer is that it's partly about spreading the workload,
and partly about building community bonds).
Thanks,
Stefan
AW: 1.6.13: svn cleanup fails to cleanup
Posted by Paul Maier <sv...@web.de>.
Hi everybody,
> Could you please file an issue in our tracker, linking to this thread?
To be honest, I have no idea about the meaning of all the necessary
parameters like priority and DEFECT or ENHANCEMENT and target milestone,
that I really would appreciate if someone could file that issue for me.
Let's say, if nobody took over filing this issue till - say - weekend,
I will then try to do it.
Deal?
@Daniel: Thanks for having tested this!
Paul.
> -----Ursprüngliche Nachricht-----
> Von: Daniel Shahaf [mailto:d.s@daniel.shahaf.name]
> Gesendet: Donnerstag, 21. Oktober 2010 15:49
> An: Paul Maier
> Cc: users@subversion.apache.org
> Betreff: Re: 1.6.13: svn cleanup fails to cleanup
>
> Paul Maier wrote on Wed, Oct 20, 2010 at 23:03:56 +0200:
> > Hello!
> >
> > I would be interested, if this problem is fixed in the
> > current 1.7 trunk.
>
> It's not fixed, see transcript below.
>
> Could you please file an issue in our tracker, linking to this thread?
>
> (You'll have to create a tigris.org account for that.)
>
> Thanks,
>
> Daniel
>
> > svn cleanup should be able to repair and unlock the WC.
> > Unfortunately I am not able to build the trunk from source
> > myself.
> >
> > Here is a reproduction script that produces a corrupt WC, and no
> > svn command can repair it, so the WC seems lost:
> >
> > svnadmin create xx
> > svn co "file:///C:/[...]/xx" yy
> > cd yy
> > echo a > a
> > svn add a
> > svn ci -m ""
> > svn lock a
> > svn mkdir 1
> > mv a 1 # here "forgot" to type svn before the mv
> > svn ci -m ""
> > svn st -u
> > svn cleanup 1
> > svn cleanup .
> > svn st -u
> >
> > The error message advises to use svn cleanup, but svn cleanup
> > fails to unlock the WC.
> > (Even though it would be possible:
> > touch a;
> > svn cleanup .
> > unlocks the WC.)
>
> [[[
> 0:% cat foo.sh
> #!/bin/sh
> $svnadmin create xx
> $svn co file:///`pwd`/xx yy
> cd yy
> echo a > a
> $svn add a
> $svn ci -m ""
> $svn lock a
> $svn mkdir 1
> mv a 1 # here "forgot" to type $svn before the mv
> $svn ci -m ""
> $svn st -u
> $svn cleanup 1
> $svn cleanup .
> $svn st -u
> touch a;
> $svn cleanup .
> 0:% sh -x ./foo.sh
> + /home/daniel/src/svn/trunk/subversion/svnadmin/svnadmin create xx
> ++ pwd
> + /home/daniel/src/svn/trunk/subversion/svn/svn co
> file:////tmp/svn/xx yy
> Checked out revision 0.
> + cd yy
> + echo a
> + /home/daniel/src/svn/trunk/subversion/svn/svn add a
> A a
> + /home/daniel/src/svn/trunk/subversion/svn/svn ci -m ''
> Adding a
> Transmitting file data .
> Committed revision 1.
> + /home/daniel/src/svn/trunk/subversion/svn/svn lock a
> 'a' locked by user 'daniel'.
> + /home/daniel/src/svn/trunk/subversion/svn/svn mkdir 1
> A 1
> + mv a 1
> + /home/daniel/src/svn/trunk/subversion/svn/svn ci -m ''
> Adding 1
>
> Committed revision 2.
> subversion/svn/commit-cmd.c:156: (apr_err=200000)
> subversion/libsvn_client/commit.c:855: (apr_err=200000)
> svn: Commit succeeded, but other errors follow:
> subversion/libsvn_client/commit.c:873: (apr_err=155009)
> svn: Error bumping revisions post-commit (details follow):
> subversion/libsvn_wc/adm_ops.c:510: (apr_err=155009)
> subversion/libsvn_wc/workqueue.c:2282: (apr_err=155009)
> subversion/libsvn_wc/workqueue.c:2217: (apr_err=155009)
> subversion/libsvn_wc/workqueue.c:1311: (apr_err=155009)
> svn: Error processing post-commit work for '/tmp/svn/yy/a'
> subversion/libsvn_wc/workqueue.c:1134: (apr_err=2)
> subversion/libsvn_wc/workqueue.c:880: (apr_err=2)
> subversion/libsvn_subr/io.c:3630: (apr_err=2)
> subversion/libsvn_subr/io.c:3561: (apr_err=2)
> subversion/libsvn_subr/io.c:2764: (apr_err=2)
> svn: Can't open file '/tmp/svn/yy/a': No such file or directory
> + /home/daniel/src/svn/trunk/subversion/svn/svn st -u
> subversion/svn/status-cmd.c:326: (apr_err=155037)
> subversion/svn/util.c:959: (apr_err=155037)
> subversion/libsvn_client/status.c:300: (apr_err=155037)
> subversion/libsvn_wc/node.c:193: (apr_err=155037)
> subversion/libsvn_wc/wc_db.c:4350: (apr_err=155037)
> subversion/libsvn_wc/wc_db_pdh.c:540: (apr_err=155037)
> subversion/libsvn_wc/wc_db_pdh.c:268: (apr_err=155037)
> subversion/libsvn_wc/wc_db_pdh.c:101: (apr_err=155037)
> svn: Previous operation was interrupted; run 'svn cleanup'
> + /home/daniel/src/svn/trunk/subversion/svn/svn cleanup 1
> subversion/svn/cleanup-cmd.c:82: (apr_err=155004)
> subversion/libsvn_client/cleanup.c:64: (apr_err=155004)
> subversion/libsvn_wc/cleanup.c:149: (apr_err=155004)
> subversion/libsvn_wc/cleanup.c:92: (apr_err=155004)
> subversion/libsvn_wc/wc_db.c:7409: (apr_err=155004)
> subversion/libsvn_wc/wc_db.c:7409: (apr_err=155004)
> svn: Working copy '/tmp/svn/yy/1' locked.
> subversion/libsvn_wc/wc_db.c:7401: (apr_err=155004)
> svn: '/tmp/svn/yy' is already locked.
> svn: run 'svn cleanup' to remove locks (type 'svn help
> cleanup' for details)
> + /home/daniel/src/svn/trunk/subversion/svn/svn cleanup .
> subversion/svn/cleanup-cmd.c:82: (apr_err=155009)
> subversion/libsvn_client/cleanup.c:64: (apr_err=155009)
> subversion/libsvn_wc/cleanup.c:149: (apr_err=155009)
> subversion/libsvn_wc/cleanup.c:98: (apr_err=155009)
> subversion/libsvn_wc/workqueue.c:2282: (apr_err=155009)
> subversion/libsvn_wc/workqueue.c:2217: (apr_err=155009)
> subversion/libsvn_wc/workqueue.c:1311: (apr_err=155009)
> svn: Error processing post-commit work for '/tmp/svn/yy/a'
> subversion/libsvn_wc/workqueue.c:1134: (apr_err=2)
> subversion/libsvn_wc/workqueue.c:880: (apr_err=2)
> subversion/libsvn_subr/io.c:3630: (apr_err=2)
> subversion/libsvn_subr/io.c:3561: (apr_err=2)
> subversion/libsvn_subr/io.c:2764: (apr_err=2)
> svn: Can't open file '/tmp/svn/yy/a': No such file or directory
> + /home/daniel/src/svn/trunk/subversion/svn/svn st -u
> subversion/svn/status-cmd.c:326: (apr_err=155037)
> subversion/svn/util.c:959: (apr_err=155037)
> subversion/libsvn_client/status.c:300: (apr_err=155037)
> subversion/libsvn_wc/node.c:193: (apr_err=155037)
> subversion/libsvn_wc/wc_db.c:4350: (apr_err=155037)
> subversion/libsvn_wc/wc_db_pdh.c:540: (apr_err=155037)
> subversion/libsvn_wc/wc_db_pdh.c:268: (apr_err=155037)
> subversion/libsvn_wc/wc_db_pdh.c:101: (apr_err=155037)
> svn: Previous operation was interrupted; run 'svn cleanup'
> + touch a
> + /home/daniel/src/svn/trunk/subversion/svn/svn cleanup .
> 0:%
> ]]]
Re: 1.6.13: svn cleanup fails to cleanup
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Paul Maier wrote on Wed, Oct 20, 2010 at 23:03:56 +0200:
> Hello!
>
> I would be interested, if this problem is fixed in the
> current 1.7 trunk.
It's not fixed, see transcript below.
Could you please file an issue in our tracker, linking to this thread?
(You'll have to create a tigris.org account for that.)
Thanks,
Daniel
> svn cleanup should be able to repair and unlock the WC.
> Unfortunately I am not able to build the trunk from source
> myself.
>
> Here is a reproduction script that produces a corrupt WC, and no
> svn command can repair it, so the WC seems lost:
>
> svnadmin create xx
> svn co "file:///C:/[...]/xx" yy
> cd yy
> echo a > a
> svn add a
> svn ci -m ""
> svn lock a
> svn mkdir 1
> mv a 1 # here "forgot" to type svn before the mv
> svn ci -m ""
> svn st -u
> svn cleanup 1
> svn cleanup .
> svn st -u
>
> The error message advises to use svn cleanup, but svn cleanup
> fails to unlock the WC.
> (Even though it would be possible:
> touch a;
> svn cleanup .
> unlocks the WC.)
[[[
0:% cat foo.sh
#!/bin/sh
$svnadmin create xx
$svn co file:///`pwd`/xx yy
cd yy
echo a > a
$svn add a
$svn ci -m ""
$svn lock a
$svn mkdir 1
mv a 1 # here "forgot" to type $svn before the mv
$svn ci -m ""
$svn st -u
$svn cleanup 1
$svn cleanup .
$svn st -u
touch a;
$svn cleanup .
0:% sh -x ./foo.sh
+ /home/daniel/src/svn/trunk/subversion/svnadmin/svnadmin create xx
++ pwd
+ /home/daniel/src/svn/trunk/subversion/svn/svn co file:////tmp/svn/xx yy
Checked out revision 0.
+ cd yy
+ echo a
+ /home/daniel/src/svn/trunk/subversion/svn/svn add a
A a
+ /home/daniel/src/svn/trunk/subversion/svn/svn ci -m ''
Adding a
Transmitting file data .
Committed revision 1.
+ /home/daniel/src/svn/trunk/subversion/svn/svn lock a
'a' locked by user 'daniel'.
+ /home/daniel/src/svn/trunk/subversion/svn/svn mkdir 1
A 1
+ mv a 1
+ /home/daniel/src/svn/trunk/subversion/svn/svn ci -m ''
Adding 1
Committed revision 2.
subversion/svn/commit-cmd.c:156: (apr_err=200000)
subversion/libsvn_client/commit.c:855: (apr_err=200000)
svn: Commit succeeded, but other errors follow:
subversion/libsvn_client/commit.c:873: (apr_err=155009)
svn: Error bumping revisions post-commit (details follow):
subversion/libsvn_wc/adm_ops.c:510: (apr_err=155009)
subversion/libsvn_wc/workqueue.c:2282: (apr_err=155009)
subversion/libsvn_wc/workqueue.c:2217: (apr_err=155009)
subversion/libsvn_wc/workqueue.c:1311: (apr_err=155009)
svn: Error processing post-commit work for '/tmp/svn/yy/a'
subversion/libsvn_wc/workqueue.c:1134: (apr_err=2)
subversion/libsvn_wc/workqueue.c:880: (apr_err=2)
subversion/libsvn_subr/io.c:3630: (apr_err=2)
subversion/libsvn_subr/io.c:3561: (apr_err=2)
subversion/libsvn_subr/io.c:2764: (apr_err=2)
svn: Can't open file '/tmp/svn/yy/a': No such file or directory
+ /home/daniel/src/svn/trunk/subversion/svn/svn st -u
subversion/svn/status-cmd.c:326: (apr_err=155037)
subversion/svn/util.c:959: (apr_err=155037)
subversion/libsvn_client/status.c:300: (apr_err=155037)
subversion/libsvn_wc/node.c:193: (apr_err=155037)
subversion/libsvn_wc/wc_db.c:4350: (apr_err=155037)
subversion/libsvn_wc/wc_db_pdh.c:540: (apr_err=155037)
subversion/libsvn_wc/wc_db_pdh.c:268: (apr_err=155037)
subversion/libsvn_wc/wc_db_pdh.c:101: (apr_err=155037)
svn: Previous operation was interrupted; run 'svn cleanup'
+ /home/daniel/src/svn/trunk/subversion/svn/svn cleanup 1
subversion/svn/cleanup-cmd.c:82: (apr_err=155004)
subversion/libsvn_client/cleanup.c:64: (apr_err=155004)
subversion/libsvn_wc/cleanup.c:149: (apr_err=155004)
subversion/libsvn_wc/cleanup.c:92: (apr_err=155004)
subversion/libsvn_wc/wc_db.c:7409: (apr_err=155004)
subversion/libsvn_wc/wc_db.c:7409: (apr_err=155004)
svn: Working copy '/tmp/svn/yy/1' locked.
subversion/libsvn_wc/wc_db.c:7401: (apr_err=155004)
svn: '/tmp/svn/yy' is already locked.
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
+ /home/daniel/src/svn/trunk/subversion/svn/svn cleanup .
subversion/svn/cleanup-cmd.c:82: (apr_err=155009)
subversion/libsvn_client/cleanup.c:64: (apr_err=155009)
subversion/libsvn_wc/cleanup.c:149: (apr_err=155009)
subversion/libsvn_wc/cleanup.c:98: (apr_err=155009)
subversion/libsvn_wc/workqueue.c:2282: (apr_err=155009)
subversion/libsvn_wc/workqueue.c:2217: (apr_err=155009)
subversion/libsvn_wc/workqueue.c:1311: (apr_err=155009)
svn: Error processing post-commit work for '/tmp/svn/yy/a'
subversion/libsvn_wc/workqueue.c:1134: (apr_err=2)
subversion/libsvn_wc/workqueue.c:880: (apr_err=2)
subversion/libsvn_subr/io.c:3630: (apr_err=2)
subversion/libsvn_subr/io.c:3561: (apr_err=2)
subversion/libsvn_subr/io.c:2764: (apr_err=2)
svn: Can't open file '/tmp/svn/yy/a': No such file or directory
+ /home/daniel/src/svn/trunk/subversion/svn/svn st -u
subversion/svn/status-cmd.c:326: (apr_err=155037)
subversion/svn/util.c:959: (apr_err=155037)
subversion/libsvn_client/status.c:300: (apr_err=155037)
subversion/libsvn_wc/node.c:193: (apr_err=155037)
subversion/libsvn_wc/wc_db.c:4350: (apr_err=155037)
subversion/libsvn_wc/wc_db_pdh.c:540: (apr_err=155037)
subversion/libsvn_wc/wc_db_pdh.c:268: (apr_err=155037)
subversion/libsvn_wc/wc_db_pdh.c:101: (apr_err=155037)
svn: Previous operation was interrupted; run 'svn cleanup'
+ touch a
+ /home/daniel/src/svn/trunk/subversion/svn/svn cleanup .
0:%
]]]