When I do a Project Based Command of UPDATE, Tortoise will report... action complete at revision 2976.... but when I right click on the trunk in explorer and perform an update, it infact does update the trunk and pulls down the modified files... any idea why this would act in this manner?
Thanks
Possible causes
1. Something wrong with Berlios Server
Just worked for me; not likely cause right now; it it does happen from time to time.
I check this URL for Berlios Server status
http://monitor.berlios.de/berlios-status/index.php
2. Something wrong with TortoiseSVN
What version of TortoiseSVN are you using?
Did you try re-booting the computer, I have had TortoiseSVN lockup on me.
3. User Error/data entry error
What URL are/did you using for checkout?
http://www.codeblocks.org/source_code.shtml
Sometimes one/two of the four methods is down.
Did you Try "Update to Revision" using "Head" ?
Did you branch/tag/pin the entries?
( Never did above under SVN not sure if it would cause this issue or not.)
Tim S
Quote from: Oulaxer11 on January 24, 2008, 05:03:39 PM
When I do a Project Based Command of UPDATE
The above is not done inside of Code::Blocks right? Because the main Code::Blocks "Nightly Build" code does not support internal SVN updates.
The Code::Blocks RC2 did, are you using RC2?
Are you using an SVN plugin to Code::Blocks?
If so, which plugin are you using? CBTortoiseSVN plugin? or SVNInside?
Note, I currently do not use either SVN Plugins for Codeblocks, but test SVNInside from time to time.
Tim S
TortoiseSVN info
TortoiseSVN 1.4.6, Build 11647 - 32 Bit , 2007/12/21 19:18:56
Subversion 1.4.6,
apr 0.9.12
apr-iconv 0.9.7
apr-utils 0.9.12
berkeley db 4.4.20
neon 0.26.4
OpenSSL 0.9.8d 28 Sep 2006
zlib 1.2.3
I have tried to reboot - it is not like Tortoise does not respond... you can update individual files correctly.. if you try to update the entire project... it acts as though its updates... displays the correct version that it needs to pull down, but then does not pull down any files....
I am a very novice user of Tortoise, I have never branched/tag/pin the entries...
I am using CBTortoiseSVN plugin
I am using Code::Blocks version 4771, which I feel is that January 2nd nightly build
bump?
Ok, I am trying to duplicate the problem. I am trying to compile CBTortoiseSVN plugin from trunk.
I am trying TortoiseSVN version 1.4.7 build 11792
I am trying CollabNet svn.exe version 1.4.6 (r28521)
Here's what showed up in Code::Blocks log; using Code::Blocks SVN 4852
CBTortoiseSVN: Filename: F:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks\src\CodeBlocks.cbp, Filebased: 0, Projectbased: 1, Workspacebased: 0
CBTortoiseSVN: Executing: "tortoiseproc.exe" /command:update /path:"F:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks\src" /notempfile
Tim S
Where is the project file (.cbp) relative to the top SVN folder.
svn-folder
sub-folder
project.cbp
or is it
svn-folder
project.cbp
I asked because it looks like in the first case, only sub-folder would be update not svn-folder.
Tim S
J:\PROJECTNAME\trunk\utils\PROJECTNAME\PROJECTNAME.cpb
and you can update / commit / etc... from the trunk
Quote from: Oulaxer11 on January 31, 2008, 03:57:50 PM
J:\PROJECTNAME\trunk\utils\PROJECTNAME\PROJECTNAME.cpb
and you can update / commit / etc... from the trunk
If you can update the trunk inside of Code::Blocks using the plug-in, I must not understand what the problem is. Because I thought you could not update using the CBTortoiseSVN plugin.
If my theory of the issue is right the CBTortoiseSVN plugin would only update the folder PROJECTNAME below utils; when you do a project update using the plugin.
Tim S
I apologize, the start of the SVN is the "trunk" Tortoise works correctly from EXPLORER, my last post was not clear... so are you suggesting I need to move the location of the CBB file to just outside the TRUNK folder?
Quote from: Oulaxer11 on January 31, 2008, 09:14:07 PM
I apologize, the start of the SVN is the "trunk" Tortoise works correctly from EXPLORER, my last post was not clear... so are you suggesting I need to move the location of the CBB file to just outside the TRUNK folder?
I am saying the way the plug-in seems to work on a project update is that it updates the folder that contains the project/cbp file. It might be better to re-write the plugin, but I have no idea on how to change the plugin, to update the top folder since I have no idea how the plug-in could tell what the top folder is.
So, if it was me I would move the project/cbp file to see if the problem is fixed. But, if that is not possible might look at fixing the plug-in somehow.
Tim S