Importante: Sourceforge upgrade

[vuott]

Minisini ha inviato alla M.L.I. questa comunicazione che riporto:

« 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.

Alas, this process took a long time, and I forgot to send a mail to the
user mailing-list to warn people *not* to do any commit. (I did on the
developer maling-list)

So I'm afraid that the revision #5417 with German translations has been
lost and must be committed again to the new repository.

Here is the new command for doing the checkout. I will try it soon on my
own machine...

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!)

$ svn checkout --username=<username>
svn+ssh://gambas@svn.code.sf.net/p/gambas/code/gambas/trunk

Regards,

--
Benoît Minisini »

[vuott]

Seguono nella M.L.I. risposte al suo messaggio:

« 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.

Sebi »


« > 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?

Tobias Boege »


« I don't know. Sourceforge to do a fresh checkout from the new URL. If
the Daily Builds do that, you just have to change the SVN url and that's
all (the read-only access url needs no user name and no password).

--
Benoît Minisini »


« 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.)

Bruce »



« Good idea, but you are false: you made your commit to the old repository!
Just check that by looking at the subversion commit mail, or by checking
the "Browse source code" page on the website!
 
Benoît Minisini »


« Salut,

just before doing all the changes, I started my svn-script to see what
happens.
Nothing unusual happened, I had 5409, now I have 5418

Karl Reinl »

[vuott]

Seguono nella M.L.I. altre risposte al suo messaggio:


« 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 ?

Willy »


« Yes.

--
Benoît Minisini »

[sotema]

Seguono nella M.L.I. altre risposte al suo messaggio:


« 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 ?

Willy »


« Yes.

--
Benoît Minisini »

Yes but...
il nuovo link risulta non aggiornato e fermo allarevisione 5417. 

[vuott]

Come anche mi aveva segnalato sotema, pare che il vecchio indirizzo per l'aggiornamento via SVN sia somparso. Infatti nel terminale, lanciando la consueta riga:

~ $ svn checkout https://gambas.svn.sourceforge.net/svnroot/gambas/gambas/trunk/

ho ottenuto il seguente messaggio:
svn: L'URL 'https://gambas.svn.sourceforge.net/svnroot/gambas/gambas/trunk' non esiste


Ora, dunque, per eseguire normalmente un checkout completo delle revisioni, bisogna lanciare quest'altra riga:
svn checkout svn://svn.code.sf.net/p/gambas/code/gambas/trunk

[vuott]

« > 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!)
>
> $ svn checkout --username=<username>
> svn+ssh://gambas@svn.code.sf.net/p/gambas/code/gambas/trunk


The proper URL seem to be svn checkout --username=<username>
svn+ssh://<username>@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=<username>
svn+ssh://<username>@svn.code.sf.net/p/gambas/code/gambas/trunk

Laurent Carlier »


« Thanks Laurent! "gambas" was my user name, and I thought stupidly that
it was the project name...
 
Benoît Minisini »


« 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=<username>  <old url> svn+ssh://<username>@
svn.code.sf.net/p/gambas/code/gambas/trunk

It have worked for me to migrate from Read Only to RW mode

Fabien Bodard »


« 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 »


« Remove the old /trunk completely and do a checkout from scratch with the
new url.

Regards,
--
Benoît Minisini »


« 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?

Matti »


« Don't remove the old /trunk then, just rename the directory, or put it
elsewhere.
Once you have done the new checkout, you will have to get the new
translation from the old trunk and put it into the new one. A file copy
will be enough.
--
Benoît Minisini »