Re: [boost] [Important] Boost Subversion repository is now online
on Tue Jul 31 2007, Beman Dawes <bdawes-AT-acm.org> wrote:
Douglas Gregor wrote:
Hello all,
The Boost Subversion repository is now back online. All of the files in CVS (including their histories) have been imported into the Subversion repository.
After an apparently successful checkout, diff from log isn't working.
Edit a file. Say trunk/configure. Using TortoiseSVN, select it. Right click to get context menu. Select diff. Works fine.
Using TortoiseSVN, select it again if needed. Right click to get context menu. Select show log. Works fine. Select one of the log messages. Right click for context menu. Select Compare with working copy.
This results in an error dialog: PROPFIND request failed on '/svn/boost/svn/bc/36681/trunk/boost/configure' ... 207 Multi-Status (https://svn.boost.org)
Beman, Can you reproduce your problem using the canonical command-line tool? I doubt the repo maintainers are set up to test with tortoise. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com The Astoria Seminar ==> http://www.astoriaseminar.com
David Abrahams wrote:
on Tue Jul 31 2007, Beman Dawes <bdawes-AT-acm.org> wrote:
Douglas Gregor wrote:
Hello all,
The Boost Subversion repository is now back online. All of the files in CVS (including their histories) have been imported into the Subversion repository. After an apparently successful checkout, diff from log isn't working.
Edit a file. Say trunk/configure. Using TortoiseSVN, select it. Right click to get context menu. Select diff. Works fine.
Using TortoiseSVN, select it again if needed. Right click to get context menu. Select show log. Works fine. Select one of the log messages. Right click for context menu. Select Compare with working copy.
This results in an error dialog: PROPFIND request failed on '/svn/boost/svn/bc/36681/trunk/boost/configure' ... 207 Multi-Status (https://svn.boost.org)
Beman,
Can you reproduce your problem using the canonical command-line tool? I doubt the repo maintainers are set up to test with tortoise.
No. svn diff works fine from the command line. Maddening. Works fine with local (non-boost) repositories. I'm about to check a remote non-Boost repository. Anyone else using Tortoise SVN having diff problems? --Beman
Beman Dawes wrote:
Anyone else using Tortoise SVN having diff problems?
Fails exactly the same way for me also. Which would be fine given that I just about never do a specific-revision vs. working-copy diff. But the error also shows if one does a version-x vs. version-y diff :-( Hm, although another quick test shows that the diff works in other places outside of the boost import. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
Rene Rivera wrote:
Beman Dawes wrote:
Anyone else using Tortoise SVN having diff problems?
Fails exactly the same way for me also. Which would be fine given that I just about never do a specific-revision vs. working-copy diff. But the error also shows if one does a version-x vs. version-y diff :-( Hm, although another quick test shows that the diff works in other places outside of the boost import.
Thanks, Rene. That would seem to rule out operator error or a problem specific to my machine configuration. --Beman
Beman Dawes wrote:
David Abrahams wrote:
on Tue Jul 31 2007, Beman Dawes <bdawes-AT-acm.org> wrote:
Douglas Gregor wrote:
Hello all,
The Boost Subversion repository is now back online. All of the files in CVS (including their histories) have been imported into the Subversion repository. After an apparently successful checkout, diff from log isn't working.
Edit a file. Say trunk/configure. Using TortoiseSVN, select it. Right click to get context menu. Select diff. Works fine.
Using TortoiseSVN, select it again if needed. Right click to get context menu. Select show log. Works fine. Select one of the log messages. Right click for context menu. Select Compare with working copy.
This results in an error dialog: PROPFIND request failed on '/svn/boost/svn/bc/36681/trunk/boost/configure' ... 207 Multi-Status (https://svn.boost.org) Beman,
Can you reproduce your problem using the canonical command-line tool? I doubt the repo maintainers are set up to test with tortoise.
No. svn diff works fine from the command line.
Maddening. Works fine with local (non-boost) repositories. I'm about to check a remote non-Boost repository.
Not only does TortoiseSVN diff work with other repositories, it works with the boost sandbox. So this is starting to smell like a bug in TortoiseSVN, perhaps related to the little dance Doug did with the devel/trunk names. It really would be helpful if someone else could try a diff on the Boost trunk (say on index.htm) using TortoiseSVN and report whether it worked or not. --Beman
On Aug 1, 2007, at 11:16 AM, Beman Dawes wrote:
Not only does TortoiseSVN diff work with other repositories, it works with the boost sandbox. So this is starting to smell like a bug in TortoiseSVN, perhaps related to the little dance Doug did with the devel/trunk names.
It really would be helpful if someone else could try a diff on the Boost trunk (say on index.htm) using TortoiseSVN and report whether it worked or not.
So, someone else uncovered an error in the MIME types in the Subversion repository, which caused trouble for some other Subversion clients (but not the command-line svn). It's possible that the problems are related... - Doug
Doug Gregor wrote:
On Aug 1, 2007, at 11:16 AM, Beman Dawes wrote:
Not only does TortoiseSVN diff work with other repositories, it works with the boost sandbox. So this is starting to smell like a bug in TortoiseSVN, perhaps related to the little dance Doug did with the devel/trunk names.
It really would be helpful if someone else could try a diff on the Boost trunk (say on index.htm) using TortoiseSVN and report whether it worked or not.
So, someone else uncovered an error in the MIME types in the Subversion repository, which caused trouble for some other Subversion clients (but not the command-line svn). It's possible that the problems are related...
Ah! One of the errors messages I got made me suspect MIME types might be involved. Is there a fix or workaround? --Beman
participants (4)
-
Beman Dawes -
David Abrahams -
Doug Gregor -
Rene Rivera