[issue5267] Subversion problem with PythonLauncher after building 3.0 or 3.1 on Mac

Ronald Oussoren added the comment: Fixed for 3.1 in r73187, and for 3.0 in r73188. -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue5267] Subversion problem with PythonLauncher after building 3.0 or 3.1 on Mac

Changes by Ronald Oussoren : -- assignee: -> ronaldoussoren ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue5267] Subversion problem with PythonLauncher after building 3.0 or 3.1 on Mac

Ned Deily added the comment: I see what the problem is. In 2.x, the PythonLauncher Makefile uses bundlebuilder to build Python Launcher.app in Mac/PythonLauncher and from there it gets installed into /Applications/Python nn. Because bundlebuilder was removed in 3.0, r64618 checked in a copy o

[issue5267] Subversion problem with PythonLauncher after building 3.0 or 3.1 on Mac

Mitchell Model added the comment: Sorry -- msg 82178 refers to "my previous message" but I sent them out of order. The "previous message" was 82190, just below 82178. ___ Python tracker

[issue5267] Subversion problem with PythonLauncher after building 3.0 or 3.1 on Mac

Mitchell Model added the comment: >Martin v. Löwis added the comment: > >How precisely did you build? Can you check whether any build step >removed PythonLauncher, then recreated it? in the svn directory for, say, py3k % svn update % make clean % ./configure --enable-frameworks % make % sudo

[issue5267] Subversion problem with PythonLauncher after building 3.0 or 3.1 on Mac

Mitchell Model added the comment: >Ned Deily added the comment: > >There are various steps in the Mac build process where the files are >copied from the build source to the build destination and then .svn >directories (among other things) are removed. Perhaps you tried building >using the sour

[issue5267] Subversion problem with PythonLauncher after building 3.0 or 3.1 on Mac

Ned Deily added the comment: There are various steps in the Mac build process where the files are copied from the build source to the build destination and then .svn directories (among other things) are removed. Perhaps you tried building using the source directory as the destination directo

[issue5267] Subversion problem with PythonLauncher after building 3.0 or 3.1 on Mac

Martin v. Löwis added the comment: How precisely did you build? Can you check whether any build step removed PythonLauncher, then recreated it? If you remove Python Launcher.app, you should be able to svn update. -- nosy: +loewis ___ Python tracker

[issue5267] Subversion problem with PythonLauncher after building 3.0 or 3.1 on Mac

New submission from Mitchell Model : After checking out 3.0 and 3.1 and building them on a Mac (Leopard, Intel) when I subsequently try to do "svn update" I get the error: svn: Directory 'Mac/PythonLauncher/Python Launcher.app/.svn' containing working copy admin area is missing As a result, "