Yes, thanks for that info; what you said makes sense, although it's
not clear from the options. Just as you'd expect, my setup started
crashing again later on in the evening. Here's hoping for a Versions
with 1.6.6...
--Nicholas
On Nov 27, 7:37 pm, Quinn Taylor quinntay...@mac.com wrote:
It
Hey Tim,
I just noticed that this issue has been fixed in Subversion 1.6.6.
From the release notes:
* fix libsvn_ra_svn/marshal.c assertion failed (opt || cstr) (issue
#3485)
Or if you're interested in more details:
http://subversion.tigris.org/issues/show_bug.cgi?id=3485
We'll try to replace
Hey Dirk,
thanks for the update, I'm looking forward to that update!
Cheers,
tim
On Nov 27, 11:53 am, Dirk Stoop d...@madebysofa.com wrote:
Hey Tim,
I just noticed that this issue has been fixed in Subversion 1.6.6.
From the release notes:
* fix libsvn_ra_svn/marshal.c assertion failed
I think you can just get svn 1.6.6 via CollabNet binaries for OS X
here:
http://www.open.collab.net/downloads/community/
They install into /opt/subversion/bin/, so you can delete them if you
don't like them. It looks to me like Versions picks them up after you
install them, but the UI does a
It reports which command-line tools are installed to help you avoid working
copy format conflicts, but AFAIK, Versions always uses its bundled version of
the SVn tools.
- Quinn
On Nov 27, 2009, at 6:44 PM, nalundgaard wrote:
I think you can just get svn 1.6.6 via CollabNet binaries for OS X
Hi again,
Does anyone have a way to get around the problem described above? I
really need to work on the project that is creating the crashes in
Versions.
Should I maybe do a clean checkout and create a new working copy??
I'm depending on Versions because I have never used the command line
for
Which Subversion Version are you using?
In our Team (3 People) two persons can use Versions (running
Subversion v1.4.x v1.5.x)
Our new team member runs subversion v1.6.5, with this subversion the
Versions app crashes on start-up.
Anybody experiences the same problems with newer subversion
I hope this might be of some help:
I have the same annoying problem:
Versions starts up, shows me the send recent crash reports? dialog
Versions has crashed or was terminated abnormally 14 times in the
recent past. Please send the anonymous crash reports to help us fix
the problem(s).
If there
Hi Tim,
First of all, sorry for the trouble.
Could you try entering the following command in a Terminal window,
after navigating to your working copy?
svn status -u
Please let me know if you see anything abnormal in the output.
Thanks,
- Dirk
the Versions team
On Nov 19, 2:17 pm, tim
Hi Dirk,
thanks for the fast reply
this is what I get from svn status -u:
svn: In file '/SourceCache/subversion/subversion-35/subversion/
subversion/libsvn_ra_svn/marshal.c' line 486: assertion failed (opt ||
cstr)
Abort trap
doesn't look healthy to me.. right?
good luck!
On Nov 19, 2:29
Hi Guiseppe,
I'm sorry for those crashes.
When you get a crash report, is Versions actually still running in the
background, or does Versions really crash when it shows a crash report
dialog?
The 'ghost' crash report dialogs are a known issue that are isolated
to svn+ssh connections. We are
Everything was fine until today. Now versions crashes and crashes and
crashes just after start. I must have tried no less than 50 (fifty!)
times with the same result. The only way to put a stop to the crashing
was to uncheck the badge option in the settings. Eagerly waiting for
an upgrade that
12 matches
Mail list logo
