[Python-Dev] Is some magic required to check out new files from svn?

skip@pobox.com skip at pobox.com
Sun Nov 13 00:48:17 CET 2005

Is there some magic required to check out new files from the repository?
I'm trying to build on the trunk and am getting compilation errors about
code.h not being found.  If I remember correctly, this is a new file brought
over from the ast branch.  Using cvs I would have executed something like
"cvs up -dPA ." if I found I was missing something (usually a new directory)
and wanted to make sure I was in sync with the trunk.

I read the developer's FAQ and the output of "svn up --help".  Executing
"svn up" or "svn info" tells me I'm already at rev 41430, which is the
latest rev, right?  Creating a fresh build subdirectory followed by
configure and make gives me this error:

    ../Objects/frameobject.c:6:18: code.h: No such file or directory

Sure enough, I have no code.h in my Include directory.

Before I wipe out Include and svn up again is there any debugging I can do
for someone smarter in the ways of Subversion than me?  Regarding my
checksum problems (which are not appearing at the moment), Martin asked for

    1. what specific revision you had checked out (svn info)
    2. what the recorded checksum is (see .svn/entries)
    3. what the commited-rev is
    4. what the actual checksum is on the file on disk
    5. whether or not the checksums svn reports match the
        ones you determined yourself.

I don't think #2, #4 or #5 apply here.  According to .svn/entries I have:


Here's "svn info" output:

    Path: .
    URL: svn+ssh://pythondev@svn.python.org/python/trunk
    Repository UUID: 6015fed2-1504-0410-9fe1-9d1591cc4771
    Revision: 41430
    Node Kind: directory
    Schedule: normal
    Last Changed Author: fredrik.lundh
    Last Changed Rev: 41430
    Last Changed Date: 2005-11-12 09:55:04 -0600 (Sat, 12 Nov 2005)
    Properties Last Updated: 2005-11-12 12:00:07 -0600 (Sat, 12 Nov 2005)

I was running 1.2.0.  I just downloaded and built 1.2.3.  It made no

This is getting kinda frustrating.  I haven't got a lot of confidence in
Subversion at this point.


More information about the Python-Dev mailing list