Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Zope: Coders

ATTENTION! cvs to subversion transition tomorrow

 

 

Zope coders RSS feed   Index | Next | Previous | View Threaded


jim at zope

Apr 27, 2004, 12:10 PM

Post #1 of 11 (1002 views)
Permalink
ATTENTION! cvs to subversion transition tomorrow

Tomorrow, as planned. I'm going to move the main development branches for
Zope 2, Zope 3, and ZODB to subversion. I will start the move at 10am
US/Eastern time tomorrow. I plan to be done before 5pm US/Eastern time.
During this time, I ask that no one make checkins to the CVS head for
those projects. The first thing I will do is to tag the head with the
tag: 'cvs-to-svn-conversion'. When I'm done, I will remove all files from the
heads of the preojects in CVS, except README.txt files giving subversion access
instructions.

Speaking of subversion instructions, I'll be sending some later today.

If you want to do writable subversion checkouts, you'll need to submit
a version 1.1 contributor's agreement (if you haven't already).

The contributor's agreement can be found at:

http://dev.zope.org/DevHome/CVS/Contributor.pdf

You can print and then send the filled out and signed agreement to us in
one of 3 ways:

- Ordinary mail to:

Zope Corporation,
513 Prince Edward Street
Fredericksburg, VA, USA, 22401

- Fax to 1.703.995.0412

- Email a scanned form to: jim [at] zope



Jim

--
Jim Fulton mailto:jim [at] zope Python Powered!
CTO (540) 361-1714 http://www.python.org
Zope Corporation http://www.zope.com http://www.zope.org

_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


jim at zope

Apr 27, 2004, 2:47 PM

Post #2 of 11 (990 views)
Permalink
Re: [Zope3-dev] ATTENTION! cvs to subversion transition tomorrow [In reply to]

Jim Fulton wrote:
>
> Tomorrow, as planned. I'm going to move the main development branches for
> Zope 2, Zope 3, and ZODB to subversion. I will start the move at 10am
> US/Eastern time tomorrow. I plan to be done before 5pm US/Eastern time.
> During this time, I ask that no one make checkins to the CVS head for
> those projects. The first thing I will do is to tag the head with the
> tag: 'cvs-to-svn-conversion'. When I'm done, I will remove all files
> from the
> heads of the preojects in CVS, except README.txt files giving subversion
> access
> instructions.

Grrrrr.

The conversion is going to take longer than I planned.

I'm going to start at 6am US/Eastern. I still hope to be done by 5pm.

> Speaking of subversion instructions, I'll be sending some later today.

At this point, we have one "main" repository. Initially, this repository
will include the Zope (Zope 2), Zope3, ZODB, ZConfig, zLOG, and zdaemon
projects. I've set up a partial converion of these projects on svn.zope.org
for you to play with tonight.

You will be able to browse the repository at:

http://svn.zope.org

You will be able to do read-only anonymous checkouts like so:

svn co svn://svn.zope.org/repos/main/<project>/trunk

For example:

svn co svn://svn.zope.org/repos/main/ZConfig/trunk

To do a writable checkout (if you are a contributor who
has submitted a version 1.1 contributor's agreement), you will
use svn+ssh:

svn co svn+ssh://svn.zope.org/repos/main/<project>/trunk

Jim

--
Jim Fulton mailto:jim [at] zope Python Powered!
CTO (540) 361-1714 http://www.python.org
Zope Corporation http://www.zope.com http://www.zope.org

_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


tim at zope

Apr 27, 2004, 7:58 PM

Post #3 of 11 (979 views)
Permalink
RE: [Zope-dev] Re: [Zope3-dev] ATTENTION! cvs to subversion transitiontomorrow [In reply to]

[Jim Fulton]
...
> You will be able to do read-only anonymous checkouts like so:
>
> svn co svn://svn.zope.org/repos/main/<project>/trunk
>
> For example:
>
> svn co svn://svn.zope.org/repos/main/ZConfig/trunk

FYI, I tried that on Windows (XP), and it worked fine.

One glitch, which may be all over the place: some of the "text files" got
checked out with Windows line ends, but most did not. For example, 14 of
the 19 *.txt files in ZConfig ended up with Windows line ends, but none of
the 37 *.py files did.

Ack, no, none of the checked-out .txt files did either. The .txt files that
had Windows line ends were all created by svn for its own purposes
(README.txt files in .svn directories).

I'm not sure what to do about this. Best I can tell from the docs so far,
svn wants a

svn:eol-style

property added to every line-oriented file, with value

native

in order to get platform-sane line-end conversions. The doc's explanation
of the effect of that matches my understanding of what CVS does for all
non-binary files, which is usually exactly right.

I noticed that Fredrik Lundh complained about something similar here:

http://effbot.org/zone/subversion.htm
...
Properties are nice, but having to use three different commands
to check in a text file from Windows is pretty annoying.

Looks like svn *expected* us to do this by setting enable-auto-props during
the intial imports, with a bunch of [auto-props] settings in a config file;
like

"""
[auto-props]
*.c = svn:eol-style=native
*.cpp = svn:eol-style=native
*.h = svn:eol-style=native
*.py = svn:eol-style=native
*.dsp = svn:eol-style=CRLF
*.dsw = svn:eol-style=CRLF
*.sh = svn:eol-style=native;svn:executable
*.txt = svn:eol-style=native
*.png = svn:mime-type=image/png
*.jpg = svn:mime-type=image/jpeg
"""

I think we'll have to develop a standard set of config file settings like
that for committers to add to their personal svn configs -- or can that be
done on the server side?

> To do a writable checkout (if you are a contributor who
> has submitted a version 1.1 contributor's agreement), you will
> use svn+ssh:
>
> svn co svn+ssh://svn.zope.org/repos/main/<project>/trunk

Is that supposed work already? All I've been able to get out of it is,
e.g.,

C:\Code>svn co svn+ssh://svn.zope.org/repos/main/ZConfig/trunk szc2
svn: Connection closed unexpectedly

where the error msg appears very quickly (usually well under a second).


_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


arathorn at fastwebnet

Apr 28, 2004, 12:25 AM

Post #4 of 11 (986 views)
Permalink
Re: [Zope-dev] Re: [Zope3-dev] ATTENTION! cvs to subversion transitiontomorrow [In reply to]

Tim Peters wrote:

> One glitch, which may be all over the place: some of the "text files" got
> checked out with Windows line ends, but most did not. For example, 14 of
> the 19 *.txt files in ZConfig ended up with Windows line ends, but none of
> the 37 *.py files did.
>
> Ack, no, none of the checked-out .txt files did either. The .txt files that
> had Windows line ends were all created by svn for its own purposes
> (README.txt files in .svn directories).
>

This is strange... from the SVN book

...
Subversion examines the svn:mime-type property. If the file has no
svn:mime-type property, or has a mime-type that is textual (e.g.
text/*), Subversion assumes it is text. Otherwise, Subversion assumes
the file is binary. Subversion also helps users by running a
binary-detection algorithm in the svn import and svn add commands.
These commands will make a good guess and then (possibly) set a binary
svn:mime-type property on the file being added.
...

What mime-types are associated with the files?

---
Paolo Invernizzi


_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


jim at zope

Apr 28, 2004, 5:16 AM

Post #5 of 11 (996 views)
Permalink
Re: [Zope-dev] Re: [Zope3-dev] ATTENTION! cvs to subversion transitiontomorrow [In reply to]

Paolo Invernizzi wrote:
> Tim Peters wrote:
>
>> One glitch, which may be all over the place: some of the "text files"
>> got
>> checked out with Windows line ends, but most did not. For example, 14 of
>> the 19 *.txt files in ZConfig ended up with Windows line ends, but
>> none of
>> the 37 *.py files did.
>>
>> Ack, no, none of the checked-out .txt files did either. The .txt
>> files that
>> had Windows line ends were all created by svn for its own purposes
>> (README.txt files in .svn directories).
>>
>
> This is strange... from the SVN book
>
> ...
> Subversion examines the svn:mime-type property. If the file has no
> svn:mime-type property, or has a mime-type that is textual (e.g.
> text/*), Subversion assumes it is text. Otherwise, Subversion assumes
> the file is binary. Subversion also helps users by running a
> binary-detection algorithm in the svn import and svn add commands.
> These commands will make a good guess and then (possibly) set a binary
> svn:mime-type property on the file being added.
> ...
>
> What mime-types are associated with the files?

None. The files were not added or imported. They were input
via cvs2svn, which uses dump files. The cvs2svn utility apparently
doesn't set mime types, or any other property except cvs2svn:cvs-rev.

So, given your explanation, why did Tim get bad line endings I wonder.

Jim

--
Jim Fulton mailto:jim [at] zope Python Powered!
CTO (540) 361-1714 http://www.python.org
Zope Corporation http://www.zope.com http://www.zope.org

_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


arathorn at fastwebnet

Apr 28, 2004, 5:22 AM

Post #6 of 11 (977 views)
Permalink
Re: [Zope-dev] Re: [Zope3-dev] ATTENTION! cvs to subversion transitiontomorrow [In reply to]

Jim Fulton wrote:

> None. The files were not added or imported. They were input
> via cvs2svn, which uses dump files. The cvs2svn utility apparently
> doesn't set mime types, or any other property except cvs2svn:cvs-rev.
>
> So, given your explanation, why did Tim get bad line endings I wonder.
>
> Jim
>

I've never used cvs2svn, but if It emit a dump file, I guess you
imported the dump with "svnadmin load", wich I think does not try to
guess the mime type...

---
Paolo

_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


tim at zope

Apr 28, 2004, 5:45 AM

Post #7 of 11 (992 views)
Permalink
RE: [Zope-dev] Re: [Zope3-dev] ATTENTION! cvs tosubversion transitiontomorrow [In reply to]

[Jim]
...
> So, given your explanation, why did Tim get bad line endings I wonder.

The relevant info is scattered all over the docs. Bottom line is that svn
does line-end conversions if and only if the svn:eol-style property on a
file is set to a valid value (where "native" is what's wanted most often for
text files). The text versus binary distinction also exists, but is
irrelevant to whether svn converts line ends; the t-vs-b distinction only
controls "whether a contextual merge is possible" ("Binary Files and
Translation" section of the CVS Appendix).


_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


jim at zope

Apr 28, 2004, 6:00 AM

Post #8 of 11 (984 views)
Permalink
Re: [Zope-dev] Re: [Zope3-dev] ATTENTION! cvs to subversion transitiontomorrow [In reply to]

Paolo Invernizzi wrote:
> Jim Fulton wrote:
>
>> None. The files were not added or imported. They were input
>> via cvs2svn, which uses dump files. The cvs2svn utility apparently
>> doesn't set mime types, or any other property except cvs2svn:cvs-rev.
>>
>> So, given your explanation, why did Tim get bad line endings I wonder.
>>
>> Jim
>>
>
> I've never used cvs2svn, but if It emit a dump file, I guess you
> imported the dump with "svnadmin load", wich I think does not try to
> guess the mime type...

I think that dump/load is lower level than that. I expect that the setting
of properties should be done when the dump file is created.

Jim


--
Jim Fulton mailto:jim [at] zope Python Powered!
CTO (540) 361-1714 http://www.python.org
Zope Corporation http://www.zope.com http://www.zope.org

_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


tim at zope

Apr 28, 2004, 10:51 PM

Post #9 of 11 (996 views)
Permalink
RE: RE: [Zope-dev] Re: [Zope3-dev] ATTENTION! cvs tosubversion transitiontomorrow [In reply to]

[Jim]
>> svn co svn+ssh://svn.zope.org/repos/main/<project>/trunk

[Tim]
> Is that supposed [to] work already? All I've been able to get out
> of it is, e.g.,
>
> C:\Code>svn co svn+ssh://svn.zope.org/repos/main/ZConfig/trunk szc2
> svn: Connection closed unexpectedly
>
> where the error msg appears very quickly (usually well under a second).

Jeez Louise -- I peed away the whole night on this. Read about 70 messages
on various lists with various people on Windows having the symptom. Most
threads eventually fizzled out without a cure being found. The others had a
variety of causes, none of which applied to me. Finally hit paydirt at the
very end of:

http://www.contactor.se/~dast/svnusers/archive-2004-02/1053.shtml

which is a guide to setting up an svn *server* on Windows.

The ultimate problem was that my user name on zope.org is tim_one, but
that's not what svn on Windows thinks my user name is. In fact, I still
have no idea what svn makes up for that, but it ain't tim_one.

Things that don't work:

+ The svn --username switch:

svn co --username tim_one svn+ssh://svn.zope.org/repos/main/ZConfig/trunk
svn: Connection closed unexpectedly

The link above warned that this wouldn't work, which opened the
floodgates.

+ Embedding my user name in the URL:

svn co svn+ssh://tim_one [at] svn/repos/main/ZConfig/trunk
svn: Connection closed unexpectedly

+ Setting the USERNAME envar (which WinXP sets automatically, and here
I'm overriding it):

set USERNAME=tim_one
svn co svn+ssh://svn.zope.org/repos/main/ZConfig/trunk
svn: Connection closed unexpectedly

+ Setting the Unixish LOGNAME envar, in poke-and-hope desperation:

set LOGNAME=tim_one
svn co svn+ssh://svn.zope.org/repos/main/ZConfig/trunk
svn: Connection closed unexpectedly

+ Adding

host svn.zope.org
user tim_one

to an .ssh\config file. I think that *should* have worked, but
it's probably a limitation of the specific for-Windows ssh.exe I'm
using here (but which has worked fine with CVS for years, and without
a config file).

Finally (give up <wink>?), what does work:

+ Setting the SVN_SSH envar appropriately:

set SVN_SSH=ssh -l tim_one
svn co svn+ssh://svn.zope.org/repos/main/ZConfig/trunk
A trunk\info.py
A trunk\datatypes.py
...

Aarghghgh. Here's another that works, and this is the best:

+ Adding

Host svn.zope.org
User tim_one

to an .ssh\config file.

I tried that after reading a man page for SSH_CONFIG. It claimed that the
keywords were case-insensitive, so I figured whoever wrote the Windows
implementation must have screwed that up -- and, apparently, they did!

all-obvious-to-the-most-casual-observer-ly y'rs - tim


_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


chris at simplistix

May 5, 2004, 6:27 AM

Post #10 of 11 (980 views)
Permalink
Re: [ZODB-Dev] RE: RE: [Zope-dev] Re: [Zope3-dev] ATTENTION! cvs tosubversion transitiontomorrow [In reply to]

Tim Peters wrote:
<snip much pain and suffering>

This, btw, is why I prefer the:
svn co https://

...protocol.

Will this be supported?

cheers,

Chris - who suddenly wonder how the hell you get https to use key-based auth :-S

--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk


_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


tseaver at zope

May 5, 2004, 9:31 AM

Post #11 of 11 (975 views)
Permalink
Re: [ZODB-Dev] RE: RE: [Zope-dev] Re: ATTENTION! cvs tosubversion transitiontomorrow [In reply to]

Chris Withers wrote:
> Tim Peters wrote:
> <snip much pain and suffering>
>
> This, btw, is why I prefer the:
> svn co https://
>
> ...protocol.
>
> Will this be supported?

No. We discussed this already: the WebDAV stuff is slow, and has much
weaker authentication semantics; it would also require us to go into
the business of issuing SSL certificates.

Tres.
--
===============================================================
Tres Seaver tseaver [at] zope
Zope Corporation "Zope Dealers" http://www.zope.com

_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders

Zope coders RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.