[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn+dokuwiki Problem !

From: svn stuff <svn.stuff_at_gmail.com>
Date: 2007-01-16 22:15:00 CET

Thanks.
data is a working copy and the first method you supplied worked. (rm then
up).
But please tell me:
There's a way to delete or add "all" files in a folder right? What
"wildcharacter" should I use?
cause * doesn't seem to work.
These *.gz files get generated all the time, and the one difference before
the failing commit was that I used a script to remove files older than 30
days.
(sorry for the resend)

On 1/16/07, Ryan Schmidt <subversion-2007a@ryandesign.com> wrote:
>
> On Jan 16, 2007, at 14:29, svn stuff wrote:
>
> > I have been keeping a DokuWiki wiki under version control using
> > Subversion ( svn ) for a while
> > but the most recent commit Failed because:
> > svn: Commit failed (details follow):
> > svn: Working copy '/var/www/dokuwiki/data/attic' is missing or not
> > locked
> >
> > Note that the folder
> > /var/www/dokuwiki/data/attic
> > is full of *.gz (read binary) files that keep the history of the
> > dokuwiki pages.
> >
> > When I go to it and try "svn add * or a commit i get that "attic"
> > is not a working copy.
> > Even though , it's been a working copy from the start, and has its
> > own .svn folder.
> >
> > What to do to resolve this? Thanks.
>
> Sounds like Subversion doesn't think it's a working copy anymore.
> Somehow it broke. I don't know how, but it doesn't much matter.
>
> Is /var/www/docuwiki/data a working copy? If so, you can fix the
> attic directory by removing it, then updating the data directory.
>
> cd /var/www/docuwiki/data
> rm -rf attic
> svn up attic
>
> If /var/www/docuwiki/data is not a working copy, then you will want
> to check out a new attic:
>
> cd /var/www/docuwiki/data
> rm -rf attic
> svn checkout url://to/repo/attic
>
> Of course, in either scenario, if you had any uncommitted changes in
> attic, they will be irretrievably deleted by the rm -rf. So if this
> is the case, and you want to save those changes, you should instead
> move the broken attic out of the way, then update or checkout attic
> again (as above), then move the changed files over from the broken
> attic to the new working one, then commit the changes, then remove
> the broken attic.
>
>
> --
>
> To reply to the mailing list, please use your mailer's Reply To All
> function
>
>
>
Received on Tue Jan 16 22:15:55 2007

This is an archived mail posted to the Subversion Users mailing list.