I was actually able to check out at home last night, so it may be some
weird filtering rules at my company with their firewall.  I just tried
again at work and got the same error.  If you're able to confirm that
the file
''muse\samples\eclipse-osgi\osgi_manager\bundles\org.apache.muse.managem
ent.common\src\org\apache\muse\management\common\.svn\tmp\text-base\IMan
agedContainerHome.java.svn-base' actually exists in the muse subversion
repository, then I know the issue is on my end.  It looks like security
once again frees me from mundane things like getting work done ;)

-----Original Message-----
From: Chris Twiner [mailto:[email protected]] 
Sent: Wednesday, January 14, 2009 7:00 AM
To: [email protected]
Subject: Re: unable to checkout from trunk

it seems to be an .svn problem, not a muse one.  Browsing that link
directly for trunk doesn't show an .svn hidden dir (which would be a
problem).

If you try checking out from trunk into a completely new directory does
it work?

On 1/13/09, Lucente, Richard D <[email protected]> wrote:
> When I try to get the trunk, the following error occurs:
>
>  svn co http://svn.apache.org/repos/asf/webservices/muse/trunk/ muse
>
>  svn: Your .svn/tmp directory may be missing or corrupt; run 'svn
>  cleanup' and try again
>  svn: Can't open file
>
'muse\samples\eclipse-osgi\osgi_manager\bundles\org.apache.muse.manageme
>
nt.common\src\org\apache\muse\management\common\.svn\tmp\text-base\IMana
>  gedContainerHome.java.svn-base': The system cannot find the path
>  specified.
>
>  svn cleanup doesn't help.
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: [email protected]
>  For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to