Re: [Gambas-user] IMPORTANT! Sourceforge upgrade

2012-12-09 Thread Sebastian Kulesz
Please check revision #5423. BTW, the Daily Builds PPA is up again, please give it a few hours for the new updates to show up! On Sun, Dec 9, 2012 at 4:13 PM, Matti wrote: > Whow! That would be great. Let's try! > M. > > Am 09.12.2012 19:52, schrieb Sebastian Kulesz: > > On Sun, Dec 9, 2012 at

Re: [Gambas-user] IMPORTANT! Sourceforge upgrade

2012-12-09 Thread Matti
Whow! That would be great. Let's try! M. Am 09.12.2012 19:52, schrieb Sebastian Kulesz: > On Sun, Dec 9, 2012 at 3:46 PM, Matti wrote: > > I have a backup of the old repository. If you want, i can import your > commit to the new repository, then you can just do a fresh checkout.

Re: [Gambas-user] IMPORTANT! Sourceforge upgrade

2012-12-09 Thread Sebastian Kulesz
On Sun, Dec 9, 2012 at 3:46 PM, Matti wrote: > But then all my recent translations (that have been sent to theo old URL) > would > be lost. > > Would it be possible to save all those *.po and *.mo files somewhere, do > the > checkout from scatch, copy them to the new trunk directory and do a comm

Re: [Gambas-user] IMPORTANT! Sourceforge upgrade

2012-12-09 Thread Benoît Minisini
Le 09/12/2012 19:46, Matti a écrit : > But then all my recent translations (that have been sent to theo old URL) > would > be lost. > > Would it be possible to save all those *.po and *.mo files somewhere, do the > checkout from scatch, copy them to the new trunk directory and do a commit > again

Re: [Gambas-user] IMPORTANT! Sourceforge upgrade

2012-12-09 Thread Matti
But then all my recent translations (that have been sent to theo old URL) would be lost. Would it be possible to save all those *.po and *.mo files somewhere, do the checkout from scatch, copy them to the new trunk directory and do a commit again? M. Am 09.12.2012 19:37, schrieb Benoît Minisi

Re: [Gambas-user] IMPORTANT! Sourceforge upgrade

2012-12-09 Thread Benoît Minisini
Le 09/12/2012 19:17, Matti a écrit : > I tried both commands, but I still get the message: > //gambas3/5421/trunk' is already a working copy for a different URL > > svn checkout works, but the old URL isn't changed. > 'svn update' and 'svn info' still point to the old URL. > > Does somebod

Re: [Gambas-user] IMPORTANT! Sourceforge upgrade

2012-12-09 Thread Matti
I tried both commands, but I still get the message: //gambas3/5421/trunk' is already a working copy for a different URL svn checkout works, but the old URL isn't changed. 'svn update' and 'svn info' still point to the old URL. Does somebody know how to tell svn to save the new URL? Matti

Re: [Gambas-user] IMPORTANT! Sourceforge upgrade

2012-12-08 Thread Fabien Bodard
Hi , For svn relocate you need to give the old url too Go in the trunk folder and then type: $ svn info take the url line : URL : svn://svn.code.sf.net/p/gambas/code/gambas/trunk then do : $ svn relocate --username= svn+ssh://@ svn.code.sf.net/p/gambas/code/gambas/trunk It have worked for m

Re: [Gambas-user] IMPORTANT! Sourceforge upgrade

2012-12-08 Thread Benoît Minisini
Le 08/12/2012 18:04, Laurent Carlier a écrit : > > The proper URL seem to be svn checkout --username= > svn+ssh://@svn.code.sf.net/p/gambas/code/gambas/trunk > > For migrating from the old repo, you can try (not tested) the command svn > relocate like this: > > svn relocate --username= > svn+ssh://

Re: [Gambas-user] IMPORTANT! Sourceforge upgrade

2012-12-08 Thread Laurent Carlier
Le samedi 8 décembre 2012 02:30:26 Benoît Minisini a écrit : > > The information is on https://sourceforge.net/p/gambas/code/ > > For a read-only access: > > $ svn checkout svn://svn.code.sf.net/p/gambas/code/gambas/trunk > > For a read-write access: (I don't know why there is a difference!) > > $

Re: [Gambas-user] IMPORTANT! Sourceforge upgrade

2012-12-08 Thread Ron
This is why I host my own svn... What a mess sourceforge makes of this.. Op 8 dec. 2012 16:36 schreef "Charlie Reinl" het volgende: > Am Samstag, den 08.12.2012, 16:16 +0100 schrieb Benoît Minisini: > > Le 08/12/2012 16:12, Benoît Minisini a écrit : > > > Le 08/12/2012 10:41, Bruce a écrit : > >

Re: [Gambas-user] IMPORTANT! Sourceforge upgrade

2012-12-08 Thread Charlie Reinl
Am Samstag, den 08.12.2012, 16:16 +0100 schrieb Benoît Minisini: > Le 08/12/2012 16:12, Benoît Minisini a écrit : > > Le 08/12/2012 10:41, Bruce a écrit : > >> > >> Hi Benoît and all, > >> > >> I have added 5418 simply as a checkpoint so people can see that they are > >> using the new sourceforge l

Re: [Gambas-user] IMPORTANT! Sourceforge upgrade

2012-12-08 Thread Benoît Minisini
Le 08/12/2012 16:12, Benoît Minisini a écrit : > Le 08/12/2012 10:41, Bruce a écrit : >> >> Hi Benoît and all, >> >> I have added 5418 simply as a checkpoint so people can see that they are >> using the new sourceforge links. >> >> (I had no problems but we use eSVN, which seems to have resolved al

Re: [Gambas-user] IMPORTANT! Sourceforge upgrade

2012-12-08 Thread Benoît Minisini
Le 08/12/2012 10:41, Bruce a écrit : > > Hi Benoît and all, > > I have added 5418 simply as a checkpoint so people can see that they are > using the new sourceforge links. > > (I had no problems but we use eSVN, which seems to have resolved all the > neccessaries without any intervention.) > > hth

Re: [Gambas-user] IMPORTANT! Sourceforge upgrade

2012-12-08 Thread Benoît Minisini
Le 08/12/2012 14:51, Willy Raets a écrit : > > So for installing the trunk version Gambas documentation says to do: svn > checkout https://gambas.svn.sourceforge.net/svnroot/gambas/gambas/trunk/ > > This old link has to be replaced by svn checkout > svn://svn.code.sf.net/p/gambas/code/gambas/trunk

Re: [Gambas-user] IMPORTANT! Sourceforge upgrade

2012-12-08 Thread Willy Raets
On Sat, 2012-12-08 at 02:30 +0100, Benoît Minisini wrote: > Hi, > > Sourceforge has upgraded the Gambas project from its old management > software to the new one. > > Consequently, the subversion repository has been migrated to a new > place, and then all the "checkout" you have done on your lo

Re: [Gambas-user] IMPORTANT! Sourceforge upgrade

2012-12-08 Thread Tobias Boege
On Sat, 08 Dec 2012, Beno?t Minisini wrote: > For a read-write access: (I don't know why there is a difference!) I think because you have to be authenticated via SSH to commit? > > $ svn checkout --username= > svn+ssh://gam...@svn.code.sf.net/p/gambas/code/gambas/trunk

Re: [Gambas-user] IMPORTANT! Sourceforge upgrade

2012-12-08 Thread Charlie Reinl
Am Samstag, den 08.12.2012, 02:30 +0100 schrieb Benoît Minisini: > Hi, > > Sourceforge has upgraded the Gambas project from its old management > software to the new one. > > Consequently, the subversion repository has been migrated to a new > place, and then all the "checkout" you have done on

Re: [Gambas-user] IMPORTANT! Sourceforge upgrade

2012-12-08 Thread Bruce
On Sat, 2012-12-08 at 02:30 +0100, Benoît Minisini wrote: > Hi, > > Sourceforge has upgraded the Gambas project from its old management > software to the new one. > > Consequently, the subversion repository has been migrated to a new > place, and then all the "checkout" you have done on your lo

Re: [Gambas-user] IMPORTANT! Sourceforge upgrade

2012-12-07 Thread Benoît Minisini
Le 08/12/2012 03:36, Sebi a écrit : > Until I sort out the automatic import of the SVN repository, the > Daily Builds PPA will be stuck at revision #5418 (somehow it got > imported). I'm not sure if I can just change the repository URL, so > the reimport is most likely going to take some time. I d

Re: [Gambas-user] IMPORTANT! Sourceforge upgrade

2012-12-07 Thread Sebi
enoît Minisini Date: Sat, 08 Dec 2012 02:30:26 To: mailing list for gambas users Reply-To: mailing list for gambas users Subject: [Gambas-user] IMPORTANT! Sourceforge upgrade Hi, Sourceforge has upgraded the Gambas project from its old management software to the new one. Consequently, the subve

[Gambas-user] IMPORTANT! Sourceforge upgrade

2012-12-07 Thread Benoît Minisini
Hi, Sourceforge has upgraded the Gambas project from its old management software to the new one. Consequently, the subversion repository has been migrated to a new place, and then all the "checkout" you have done on your local computer is now invalid, and you must do a full "checkout" again.