headers
Arild Fines | 1 Aug 2003 02:23
Picon

RE: AnkhSVN Alpha 2 released

Arild Fines wrote:
> We are happy to announce the Alpha 2 release of AnkhSVN, an open
> source Subversion addin for Visual Studio .NET.
>
> A source .zip and a Windows Installer package can be found at
> http://ankhsvn.tigris.org/servlets/ProjectDocumentList The source
> compiles against Subversion 0.26.

I have since then updated the MSI package, due to a small flaw in the
installer. The installer originally failed to set the LoadBehavior registry
key for the addin to 1, meaning that the addin wouldn't automatically load
with VS.NET after the initial startup.

If you already have the original package, there is no need to get the new
one. To ensure Ankh loads automatically when VS.NET starts,  just go into
the Tools->Addin Manager.. dialog and check the Startup checkbox next to
"AnkhSVN Addin"(That is, of course, if you want Ankh to load automatically
with VS.NET).

Sorry for any inconvenience.

--
Arild
Permalink | Reply | 0 comments |
headers
Blair Zajac | 1 Aug 2003 02:27
Gravatar

Re: AnkhSVN Alpha 2 released

Arild Fines wrote:
> 
> Arild Fines wrote:
> > We are happy to announce the Alpha 2 release of AnkhSVN, an open
> > source Subversion addin for Visual Studio .NET.
> >
> > A source .zip and a Windows Installer package can be found at
> > http://ankhsvn.tigris.org/servlets/ProjectDocumentList The source
> > compiles against Subversion 0.26.
> 
> I have since then updated the MSI package, due to a small flaw in the
> installer. The installer originally failed to set the LoadBehavior registry
> key for the addin to 1, meaning that the addin wouldn't automatically load
> with VS.NET after the initial startup.

Hi Arild,

Would you mind adding version numbers to the .zip and .msi files so
if we ever forget which one we have, we can tell by the name?

Best,
Blair

--

-- 
Blair Zajac <blair <at> orcaware.com>
Plots of your system's performance - http://www.orcaware.com/orca/
Permalink | Reply | 0 comments |
headers
Arild Fines | 1 Aug 2003 03:04
Picon

RE: AnkhSVN Alpha 2 released

Blair Zajac wrote:
> Subject: Re: AnkhSVN Alpha 2 released
>> Arild Fines wrote:
>>> We are happy to announce the Alpha 2 release of AnkhSVN, an open
>>> source Subversion addin for Visual Studio .NET.
>>>
>>> A source .zip and a Windows Installer package can be found at
>>> http://ankhsvn.tigris.org/servlets/ProjectDocumentList The source
>>> compiles against Subversion 0.26.
>>
>> I have since then updated the MSI package, due to a small flaw in the
>> installer. The installer originally failed to set the LoadBehavior
>> registry key for the addin to 1, meaning that the addin wouldn't
>> automatically load with VS.NET after the initial startup.
>
> Hi Arild,
>
> Would you mind adding version numbers to the .zip and .msi files so
> if we ever forget which one we have, we can tell by the name?

You're right - I should have done that. I have now renamed the zip and msi
on tigris.org for the updated release. I have also pulled the original MSI,
to avoid any confusion. The source .zip has not been replaced, since the
minuscule 0.2.1 change has no impact on someone building Ankh from source.

--
Arild
Permalink | Reply | 0 comments |
headers
kfogel | 1 Aug 2003 17:46
Favicon

Re: MacOS X problems---Corrupt repository

"Hamilton Link" <helink <at> sandia.gov> writes:
> I don't suppose there are any other ways in which the INSTALL file for
> svn is increasingly out of date? It specifically says (still) that
> 4.0.14 is the Berkeley DB version to use. Since I certainly have never
> been able to definitively say what is and isn't required to run svn,
> do people on the dev team occasionally give a quick peek at the FAQ
> and INSTALL, etc. files?

Generally, 4.0.14 is still the recommended Berkeley, but on Mac OS/X
4.1.24 or higher is required -- 4.0.14 will not work.

We'd like to recommend 4.1.x for Subversion in general, but
experiments have shown that it's slower.  The problem may be more with
the way we use Berkeley than with Berkeley itself.  I can't quantify
this precisely only because I don't have the threads or issues handy
right now.  Some people use 4.1.x anyway; as far as I know, they don't
have correctness issues.

I'm cross-posting this to the 'users' list, where I think it would be
useful for it to be seen.  If people follow up, please trim 'dev' out
of the recipients, unless there's some reason it really should go to
dev, thanks.

-Karl
Permalink | Reply | 0 comments |
headers
Blair Zajac | 1 Aug 2003 18:56
Gravatar

Re: MacOS X problems---Corrupt repository

kfogel <at> collab.net wrote:
> 
> "Hamilton Link" <helink <at> sandia.gov> writes:
> > I don't suppose there are any other ways in which the INSTALL file for
> > svn is increasingly out of date? It specifically says (still) that
> > 4.0.14 is the Berkeley DB version to use. Since I certainly have never
> > been able to definitively say what is and isn't required to run svn,
> > do people on the dev team occasionally give a quick peek at the FAQ
> > and INSTALL, etc. files?
> 
> Generally, 4.0.14 is still the recommended Berkeley, but on Mac OS/X
> 4.1.24 or higher is required -- 4.0.14 will not work.
> 
> We'd like to recommend 4.1.x for Subversion in general, but
> experiments have shown that it's slower.  The problem may be more with
> the way we use Berkeley than with Berkeley itself.  I can't quantify
> this precisely only because I don't have the threads or issues handy
> right now.  Some people use 4.1.x anyway; as far as I know, they don't
> have correctness issues.

To put this back on the radar screen, there has been a number of issues
with people using 4.1.25 on Linux/FreeBSD boxes that have had repositories
that end up being corrupted where the only way to recover is to restore
a backup copy.

I'm hoping svn.collab.net will be moved again to 4.1.25 at some point to
get the experts on it.

See
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ben Collins-Sussman | 1 Aug 2003 18:58
Favicon

Re: MacOS X problems---Corrupt repository

Blair Zajac <blair <at> orcaware.com> writes:

> To put this back on the radar screen, there has been a number of issues
> with people using 4.1.25 on Linux/FreeBSD boxes that have had repositories
> that end up being corrupted where the only way to recover is to restore
> a backup copy.

My recollection is that Sander Striker was having discussions with
sleepycat folk, and that some deep issue was revealed.  In almost all
of these cases, a berkeley db table had switched 'type' for some
reason;  the sleepycat people revealed that this might happen if
recovery is happening whilst something else changes the db.  (Is this
accurate, Sander?)
Permalink | Reply | 0 comments |
headers
Sander Striker | 1 Aug 2003 19:05
Picon
Favicon

RE: MacOS X problems---Corrupt repository

> From: sussman <at> collab.net [mailto:sussman <at> collab.net]
> Sent: Friday, August 01, 2003 6:58 PM

> Blair Zajac <blair <at> orcaware.com> writes:
> 
> > To put this back on the radar screen, there has been a number of issues
> > with people using 4.1.25 on Linux/FreeBSD boxes that have had repositories
> > that end up being corrupted where the only way to recover is to restore
> > a backup copy.
> 
> My recollection is that Sander Striker was having discussions with
> sleepycat folk, and that some deep issue was revealed.  In almost all
> of these cases, a berkeley db table had switched 'type' for some
> reason;  the sleepycat people revealed that this might happen if
> recovery is happening whilst something else changes the db.  (Is this
> accurate, Sander?)

Let me dig up the mail.  Note that a big chunk of communication was done by
cmpilato BTW.

What it basically comes down to is that a recover will recreate the environment.
Which means that if you modify the db while recovering you get an inconsistent
environment (wrong allocation counts etc).

Sander
Permalink | Reply | 0 comments |
headers
Nicholas Riley | 1 Aug 2003 19:32
Picon

Re: MacOS X problems---Corrupt repository

On Fri, Aug 01, 2003 at 10:46:57AM -0500, kfogel <at> collab.net wrote:
> "Hamilton Link" <helink <at> sandia.gov> writes:
> > I don't suppose there are any other ways in which the INSTALL file for
> > svn is increasingly out of date? It specifically says (still) that
> > 4.0.14 is the Berkeley DB version to use. Since I certainly have never
> > been able to definitively say what is and isn't required to run svn,
> > do people on the dev team occasionally give a quick peek at the FAQ
> > and INSTALL, etc. files?
> 
> Generally, 4.0.14 is still the recommended Berkeley, but on Mac OS/X
> 4.1.24 or higher is required -- 4.0.14 will not work.

There are patches to 4.0.14 which were circulated about a year ago,
and cause it to work properly on Mac OS X.  This is the setup I've run
since last October without problems.  I haven't tried 4.1.25 recently,
but the last time I did, it repeatedly blew up in my face - corrupting
itself with a single commit.

The patch is available here:

<http://www.contactor.se/~dast/svn/archive-2002-10/0715.shtml>

--

-- 
=Nicholas Riley <njriley <at> uiuc.edu> | <http://www.uiuc.edu/ph/www/njriley>
        Pablo Research Group, Department of Computer Science and
  Medical Scholars Program, University of Illinois at Urbana-Champaign
Permalink | Reply | 0 comments |
headers
Steele Price | 1 Aug 2003 23:07
Picon

Subversion on Debian

For anyone using debian:

After much hair pulling trying to find the right voodoo to compile the head releases on debian, and not being
patient enough to wait for binaries...

I had forgotten that debian was maintaining source packages for subversion and thought I might remind
anyone who wants to build the most recent sources on debian that they can use the debian sources instead of
the raw sources at collab.net. (unless of course you want to create your own set of debian rules for some
reason, they are only a day or 2 behind the most current releases)

Debian has some peculiarities as most know and the unstable apt sources are being maintained in such a way
that it will only require 2 commands to actually build .deb files from the latest source code.

Point your /etc/apt/sources.list to an unstable sources mirror such as:
	deb-src http://ftp.us.debian.org/debian/ unstable main contrib non-free
then:

apt-get update
apt-get build-dep subversion    
apt-get source -b subversion 

I had forgotten that building sources on debian can be quite painful for complexly linked systems such as
subversion, but the above method makes it real joy to work with.

It will result in a complete set of the following debs:
-rw-r--r--    1 root     src        267126 Jul 31 17:14 libapache2-svn_0.26.0-1_i386.deb
-rw-r--r--    1 root     src       4151784 Jul 31 17:14 libsvn0-dev_0.26.0-1_i386.deb
-rw-r--r--    1 root     src       1842552 Jul 31 17:13 libsvn0_0.26.0-1_i386.deb
-rw-r--r--    1 root     src        972474 Jul 31 17:14 python2.2-subversion_0.26.0-1_i386.deb
-rw-r--r--    1 root     src         88486 Jul 31 17:11 subversion-tools_0.26.0-1_all.deb
(Continue reading)

Permalink | Reply | 0 comments |
headers
Fraser Campbell | 2 Aug 2003 17:59

Re: Subversion on Debian

On August 1, 2003 05:07 pm, Steele Price wrote:

> After much hair pulling trying to find the right voodoo to compile the head
> releases on debian, and not being patient enough to wait for binaries...
>
> I had forgotten that debian was maintaining source packages for subversion
> and thought I might remind anyone who wants to build the most recent
> sources on debian that they can use the debian sources instead of the raw
> sources at collab.net. (unless of course you want to create your own set of
> debian rules for some reason, they are only a day or 2 behind the most
> current releases)

I've been running my subversion server on an "unstable" Debian system.  It's 
been through a few upgrades and no problems have cropped up but I've only 
been running it for about a month.  I'm accessing it over the network (apache 
server).  Interestingly the current state is that the subversion programs are 
at version 0.26 but the apache dav module is still at version 0.25 ... that 
isn't causing any problems though (at least that I've found).  It's close 
enough to the latest release that I don't bother hand building anything.

For those that want to stick with the stable Debian distribution someone out 
there is maintaining the necessary packages for subversion on woody at:

    deb http://people.debian.org/~cjwatson/subversion-woody ./

Add that to your /etc/apt/source.list and "apt-get install subversion".  I'm 
only using these subversion programs on the client side but they're working 
great for me.  Everything you need should be in there to run a subversion 
server on woody as well, though I haven't tried it.
(Continue reading)

Permalink | Reply | 0 comments |

Gmane