Dear all, Next time you do "svn update" you will encounter this error: svn: Failed to add directory 'third_party\speex': object of the same name already exists The solution is pretty simple: - just delete third_party/speex directory - and do "svn update" again I'm terribly sorry for that. The reason for that is because previously we didn't store Speex in our repository; instead we just link Speex SVN to our SVN with "svn:externals" so when you "svn update" from PJSIP SVN actually you're downloading directly from their SVN repository. But recently Speex moved their repository away from SVN to git, and because of that we can no longer link to their SVN (well we can, it's just that their SVN does not have the very latest version), and rather we had to make copy of the Speex distribution in our SVN. And it's unfortunate that this process causes "svn update" to fail. Maybe it's something that we did wrongly, but anyway it has happened. Once again sorry. Cheers Benny

Benny, Have you thought about moving to git or some other DVCS program like Bazaar? Not that I am recommending you should do so, just asking if you have considered it. We are looking into DVCS's for our project, and currently Bazaar is the front runner. Git is not an option, since it does not have Windows support. Regards, Jim Gomes > -----Original Message----- > From: pjsip-bounces@lists.pjsip.org [mailto:pjsip-bounces@lists.pjsip.org] On Behalf Of > Benny Prijono > Sent: Tuesday, 10 June, 2008 7:53 AM > To: pjsip list > Subject: [pjsip] svn update error: Failed to add directory'third_party\speex' > > Dear all, > > Next time you do "svn update" you will encounter this error: > > svn: Failed to add directory 'third_party\speex': object of the same > name already exists > > The solution is pretty simple: > - just delete third_party/speex directory > - and do "svn update" again > > I'm terribly sorry for that. The reason for that is because previously > we didn't store Speex in our repository; instead we just link Speex > SVN to our SVN with "svn:externals" so when you "svn update" from > PJSIP SVN actually you're downloading directly from their SVN > repository. But recently Speex moved their repository away from SVN to > git, and because of that we can no longer link to their SVN (well we > can, it's just that their SVN does not have the very latest version), > and rather we had to make copy of the Speex distribution in our SVN. > > And it's unfortunate that this process causes "svn update" to fail. > Maybe it's something that we did wrongly, but anyway it has happened. > Once again sorry. > > Cheers > Benny > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

On Tue, Jun 10, 2008 at 5:35 PM, Jim Gomes <Jim.Gomes@tideworks.com> wrote: > Benny, > > Have you thought about moving to git or some other DVCS program like > Bazaar? Not that I am recommending you should do so, just asking if you > have considered it. We are looking into DVCS's for our project, and > currently Bazaar is the front runner. Git is not an option, since it > does not have Windows support. > Hi Jim, yeah I've thought of that a bit, in more than one occasions, and in the end always concluded that we don't DVCS yet. Mostly it's because we only have few people working with the source (read: having write access), we don't have problem with reliability (or so we thought), and the seamless integration of SVN with Trac is just very very nice. One thing that I'm still not sure about is whether DVCS will make life easier for our users. One of the drawback of SVN (and maybe other/similar VC) is it makes it very difficult to manage if you maintain your own repository and have pjsip repository inside it, and if you make modifications to pjsip. I have a hunch that the distributed nature of a DVCS will somewhat makes this task easier, but haven't investigated this further. What makes you want a DVCS btw? Cheers Benny

Hi Benny, Yes, you don't have many committers, but you have many integrators. I think that is where the power of DVCS really shines. Now, I am not an expert on DVCS yet, and I am still wrapping my head around its concepts. However, its main reason for being is to support multiple lines of development and to allow the developers to control which pieces make it into "their" codebase. For instance, I have made some significant modifications to your codebase to integrate into my codebase. I have also submitted back changes to you. Theoretically, a DVCS system would make this much easier. I know you use Trac to manage your bugs, and that is also the system I am looking it, because it will integrate with Bazaar as well as the default SVN. I like Bazaar the best so far, because of its concentration on merge and its professional level quality website. Even its icon is a merge sign. I agree with the premise that merging is the all-important activity, and branching is secondary. Most VCS's invert those priorities. Anyway, I am still investigating and learning about DVCS. I'll be looking more closely at Mercurial, but so far Bazaar seems to be superior to it. Regards, Jim Gomes > -----Original Message----- > From: pjsip-bounces@lists.pjsip.org [mailto:pjsip-bounces@lists.pjsip.org] On Behalf Of > Benny Prijono > Sent: Tuesday, 10 June, 2008 10:43 AM > To: pjsip list > Subject: Re: [pjsip] svn update error: Failed to adddirectory'third_party\speex' > > On Tue, Jun 10, 2008 at 5:35 PM, Jim Gomes <Jim.Gomes@tideworks.com> wrote: > > Benny, > > > > Have you thought about moving to git or some other DVCS program like > > Bazaar? Not that I am recommending you should do so, just asking if you > > have considered it. We are looking into DVCS's for our project, and > > currently Bazaar is the front runner. Git is not an option, since it > > does not have Windows support. > > > > Hi Jim, > > yeah I've thought of that a bit, in more than one occasions, and in > the end always concluded that we don't DVCS yet. Mostly it's because > we only have few people working with the source (read: having write > access), we don't have problem with reliability (or so we thought), > and the seamless integration of SVN with Trac is just very very nice. > > One thing that I'm still not sure about is whether DVCS will make life > easier for our users. One of the drawback of SVN (and maybe > other/similar VC) is it makes it very difficult to manage if you > maintain your own repository and have pjsip repository inside it, and > if you make modifications to pjsip. I have a hunch that the > distributed nature of a DVCS will somewhat makes this task easier, but > haven't investigated this further. > > What makes you want a DVCS btw? > > Cheers > Benny > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org