The SVN repository contains two folder entries with conflicting names.
These are:
PS2Ware/tags/START/ containing stuff for quake1_ps2
PS2Ware/tags/start/ containing stuff for ps2ftpd
On a Windows system those two folders will be identical, but since they are separate in the repository their names will cause an error in the checkout process, and future updates or commits related to those projects can not be relied on to work correctly. Someone needs to fix this ASAP, either by merging those two folders, or by renaming one of them.
Best regards: dlanor
Bugged entries in the SVN repository !
Bug in SVN repository still remains (2 weeks after report)
I don't like the practice of 'bumping' threads, but I see no other solution, when everyone involved seems to ignore a serious issue like this.
Perhaps I didn't make myself clear on this, so I'll try to be more explicit:
This bug makes it impossible for any user of any Windows OS version to participate properly in development of 'ps2ftpd'.
The existence of the folder "ps2ware/tags/START/" (used by the quake project) makes it impossible for an SVN client under windows to also create a folder named "ps2ware/tags/start/", which is required for the ps2ftpd project.
A developer using any Windows OS will therefore be able to check out the source code (no conflict exists for the 'trunk'), but will never be able to make proper updates to SVN, since the 'tags' are broken/missing.
All you need do to fix this is simply to rename one of those folders, so it's not really too much to ask. Is it ???
Best regards: dlanor
Perhaps I didn't make myself clear on this, so I'll try to be more explicit:
This bug makes it impossible for any user of any Windows OS version to participate properly in development of 'ps2ftpd'.
The existence of the folder "ps2ware/tags/START/" (used by the quake project) makes it impossible for an SVN client under windows to also create a folder named "ps2ware/tags/start/", which is required for the ps2ftpd project.
A developer using any Windows OS will therefore be able to check out the source code (no conflict exists for the 'trunk'), but will never be able to make proper updates to SVN, since the 'tags' are broken/missing.
All you need do to fix this is simply to rename one of those folders, so it's not really too much to ask. Is it ???
Best regards: dlanor
Please don't think I have any interest in placing blame on anyone.Oobles wrote:As the person looking after Subversion, I probably should have got to this earlier. It's my fault. Blame me, etc.
I just wanted to make someone with write access to this stuff aware of the problem.
I think most of us are very new at this, but hopefully someone out there has had SVN experience from elsewhere, and can help with advice. In any case I'll certainly dig into some docs on this myself, but as I'm a definite 'newb' at SVN stuff, I don't expect to be able to help with any details before you (or others here) solve it.Now the only problem is that I'm very new to all this Subversion administration. So, if someone can tell me what commands need to be done, I'll fix it. :)
Best regards: dlanor
[thanks oopo; sorry about my part too]
In svn, the trunk is the main copy of the project. The tag and branch versions are variations of trunk or a previous branch. The difference is tag is a snap shot. Once a tag is created it is intended that no additional modifications will occur to it. A branch is used to reflect modifications into the future. The documentation implies a tag will become a branch when modifications are applied to it. I don't know if this is automatic or not. A tag is named by the user. I don't know how branches are named. Once a branch is considered stable it can be merged back into the trunk. For this reason tags are very important as they hold an image of the project at a known time and state.
dlanor's bringing attention to this is important. The svn software isn't broken. It is operating correctly. To use it correctly requires users paying attention to how tags are named and staying consistent with platform differences. They should be descriptive of why a 'snap shot' was taken. The two tags in question could be something like 'quake_start' and 'ps2ftpd_start'. That way if someone wanted or needed to work with one of those projects as it was at that time, they would be able to access it regardless of development platform. As it is now, non-posix users can only access one of the tags. Under cygwin you can get either quake or ps2ftpd but not both. I believe under windows you would never be able to checkout the ps2ftpd tag. You would always get the quake tag.
Fixing this isn't easy using a non-posix client. You would have to checkout, delete from the repository, rename the local copy and check it back in. On posix you should be able rename it. Warning: what I just wrote is from reading the documentation one time only. The solution is addressed in svn documentation and should be referenced in preference to my explanation.
http://svn.brouhaha.com/ describes how to move (rename) a file or branch. I am guessing this would work on tags too.
http://subversion.tigris.org/faq.html#case-change describes renaming files. Also seems to be an execellent information resource on svn (considering the source).
In svn, the trunk is the main copy of the project. The tag and branch versions are variations of trunk or a previous branch. The difference is tag is a snap shot. Once a tag is created it is intended that no additional modifications will occur to it. A branch is used to reflect modifications into the future. The documentation implies a tag will become a branch when modifications are applied to it. I don't know if this is automatic or not. A tag is named by the user. I don't know how branches are named. Once a branch is considered stable it can be merged back into the trunk. For this reason tags are very important as they hold an image of the project at a known time and state.
dlanor's bringing attention to this is important. The svn software isn't broken. It is operating correctly. To use it correctly requires users paying attention to how tags are named and staying consistent with platform differences. They should be descriptive of why a 'snap shot' was taken. The two tags in question could be something like 'quake_start' and 'ps2ftpd_start'. That way if someone wanted or needed to work with one of those projects as it was at that time, they would be able to access it regardless of development platform. As it is now, non-posix users can only access one of the tags. Under cygwin you can get either quake or ps2ftpd but not both. I believe under windows you would never be able to checkout the ps2ftpd tag. You would always get the quake tag.
Fixing this isn't easy using a non-posix client. You would have to checkout, delete from the repository, rename the local copy and check it back in. On posix you should be able rename it. Warning: what I just wrote is from reading the documentation one time only. The solution is addressed in svn documentation and should be referenced in preference to my explanation.
http://svn.brouhaha.com/ describes how to move (rename) a file or branch. I am guessing this would work on tags too.
http://subversion.tigris.org/faq.html#case-change describes renaming files. Also seems to be an execellent information resource on svn (considering the source).