Legacy ImageMagick Discussions Archive

> http://trac.imagemagick.org/browser

Warning: Can't synchronize with the repository (No changeset 2645 in the repository). Look in the Trac log for more information.

Also:

> svn co https://www.imagemagick.org/subversion/ ... gick/trunk ImageMagick

> svn up

At revision 2642.

and my recent changes to resize.c are gone.

------

Is something broken, did I break something, or did one of you "hard revert" my recent changes?

https://www.imagemagick.org/subversion/ ... gick/trunk ImageMagick

Wrong repository. Its read-only. You want the developers repository at https://subversion.imagemagick.org/subversion. We checkout world, for example, like this: svn co https://subversion.imagemagick.org/subv ... dows/trunk ImageMagick.

Cristy:

Thanks for the quick answer.

-----

I shoud use

https://subversion.imagemagick.org/subv ... ows/trunk/

even though I develop in linux?

Or should I use

https://subversion.imagemagick.org/subv ... ick/trunk/

?

(Sorry: I'm sounding like a real noob.)

... and I should override

svn: OPTIONS of 'https://subversion.imagemagick.org/subv ... dows/trunk': SSL handshake failed: SSL error: A TLS warning alert has been received. (https://subversion.imagemagick.org)

(or

svn: OPTIONS of 'https://subversion.imagemagick.org/subv': SSL handshake failed: SSL error: A TLS warning alert has been received. (https://subversion.imagemagick.org)

?

The Windows trunk just gives you everything. For the ImageMagick only trunk, use ImageMagick rather than ImageMagick-Windows.

We're not sure why you're getting the TLS exception. We are using the most up-to-date Subversion release and perhaps its causing problems for an older Subversion client.

I'm pretty mystified.

I'm running Linux Mint 9 (June 2010) kept updated.

Added the Ubuntu repos.

No fix.

Installed debian testing subversion.

No fix.

Installed debian unstable subversion. The output of svn --version is at the end of this post.

No fix.

Regenerated my ssh keys just in case.

No fix.

The TLS error message still appears:

svn co https://subversion.imagemagick.org/subv ... ick/trunk/ ImageMagick
svn: OPTIONS of 'https://subversion.imagemagick.org/subv ... gick/trunk': SSL handshake failed: SSL error: A TLS warning alert has been received. (https://subversion.imagemagick.org)

Was I supposed to submit my public key to you guys somehow?

-----

svn --version
svn, version 1.6.6 (r40053)
compiled Dec 12 2009, 05:06:12

Copyright (C) 2000-2009 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet (http://www.Collab.Net/).

The following repository access (RA) modules are available:

* ra_neon : Module for accessing a repository via WebDAV protocol using Neon.
- handles 'http' scheme
- handles 'https' scheme
* ra_svn : Module for accessing a repository using the svn network protocol.
- with Cyrus SASL authentication
- handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
- handles 'file' scheme

Good luck fixing the problem. We tried a Subversion checkout from a number of our computers around the world and in each case the checkout ran without complaint.

I'm not the only one to whom such problems happen with some svn repo:

http://www.listware.net/201008/subversi ... eived.html

Cristy:

Thank you for checking into this.

------

To add another piece of information: My very up to date linux firefox also complained of invalid security certificate when I accessed the subversion server for the first time. I had to add a security exception (which I almost never have to do).

I'll try to see figure out how to do this with svn (the obvious --trust-server-cert does not fix the problem).

Chromium also issues the "This site's security certificate is not trusted" message.

So, applications are pretty consistent at their not liking the security certificate. I'm starting to think that the issue is that I have a more finicky because very recent ssh family of tools.

subversion.imagemagick.org has a self-signed certificate which some certificate handlers balk at but generally there is a way around the problem. Firefox, for example, complains but permits you to accept the certificate with a couple of button presses. We use self-signed because its cheaper than getting it signed (free vs. $100 - $2500 annually).

Also tried:

In ~/.subversion/servers:

...
[groups]
group1 = *.subversion.imagemagick.org
...
[group1]
ssl-trust-default-ca = yes
...

No fix.

One more try:

ssh subversion.imagemagick.org

saying "yes" at the "proceed?" prompt adds two keys to my .ssh/known_hosts file.

But svn still does not work.

Next try:

Basically, follow

http://www.roysindre.no/a/2008/12/02/ho ... ubversion/

Install the Cert Viewer Plus certificate viewer add-on for firefox.

Export the subversion.imagemagick.org certificate my NUMBERS folder. (I also tried cut and paste the PEM viewer output.)

Add

[global]
ssl-authority-files = /home/nicolas/NUMBERS/subversion.imagemagick.org

to .subversion/servers

No fix.

I also tried svn co ... from a server at the dept (running ubuntu 10.04).

Same LTS message.

I'll try from home. Firewall?