Import request: jeliot3

Asked by Andrés Moreno on 2008-03-31

Hello,

Could somebody check the svn import of jeliot3 trunk?

https://edge.launchpad.net/jeliot3/trunk/

Thanks in advance,
Andrés

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
2008-04-02
Last reply:
2008-04-03
Aaron Bentley (abentley) said : #1

Hi Andrés,

I'm afraid we weren't able to complete this import. We have a lot of problems with Google Code timing out, and this time it looks like it's dropping the connection partway through.

If you can provide us with a copy of the repository, we can do a manual import. Otherwise, I don't think we can make it work.

Andrés Moreno (andresfib) said : #2

Hi Aaron,

Thanks for trying. I can provide you with a local copy of the repository (~22MB). Where can I place it?

I am interested in having the bzr/launchpad trunk repository synchronized with the google code repository. Will this be possible once the heavy package has been manually imported?

Cheers,

Christian Reis (kiko) said : #3

On Mon, Mar 31, 2008 at 09:42:21PM -0000, Andrés Moreno wrote:
> Thanks for trying. I can provide you with a local copy of the repository
> (~22MB). Where can I place it?

Awesome. Can you put it somewhere that is wgettable?

> I am interested in having the bzr/launchpad trunk repository
> synchronized with the google code repository. Will this be possible once
> the heavy package has been manually imported?

It should be once the initial import is done -- Google code is fine for
updates, just not for an initial import. It may be that there is a bug
in the import code which prevents it from succeeding, but we can try at
least and then proced from there.

By the way, can you tell me how you obtained the copy of the repository?
I'd like to know this so I can advise other users of Google code.

Andrés Moreno (andresfib) said : #4

That was fast.

You can find the repository files at http://cs.joensuu.fi/jeliot/repository.tar.bz2

Unfortunately, my case maybe different from others. Long story short, the source comes from our CVS repository, which is in an intranet server. I imported it to svn (cvs2svn), and uploaded it to Google Code, which fetch the all the history. The repository tar.bz2 contains the result of the conversion before I svnsync with the google repository.

I'll write some longer explanation at http://cs.joensuu.fi/~amoreno/blog/

Irritatingly, it seems that repository format in that repo dump is too new for the version of svn on the build machines :(

We'll be upgrading "soon", but unfortunately not before hardy is released.

Andrés Moreno (andresfib) said : #6

If it is of any help, I did the conversion from ubuntu...Good to see you all busy before release day :)

Is there any other alternative solution to upload the trunk that will let me sync with googlecode later in the road?

Reason is that at the moment I have some students working on Jeliot; and I am interested in having them using branches in launchpad to have it later merged to the main repo at googlecode.

Aaron Bentley (abentley) said : #7

If you are planning to merge the results back into Google Code, you should seriously consider using bzr-svn, rather than Launchpad's converter.

bzr-svn allows merging bazaar-originated revisions into Subversion repositories. But Launchpad's conversions use their own algorithm, so they are not compatible with bzr-svn.

Bzr-svn is available here: http://bazaar-vcs.org/BzrForeignBranches/Subversion

It is normally also available from the Bazaar package archive, but there have been some issues lately, and I am not sure whether a version compatible with bzr 1.3 is currently available there.

Andrés Moreno (andresfib) said : #8

So what will the workflow be for one student willing to develop a feature for Jeliot?
If I understand you right, s/he should:

Checkout trunk from google code using bzr-svn
Create a branch in launchpad
Push the trunk to launchpad bazaar
Develop comitting to that branch
Merge back to google code when done using bzr-svn

Could you correct me?
Thanks,

Aaron Bentley (abentley) said : #9

I'm not sure if this is the same thing as you were suggesting, but I would suggest:

1. branch the trunk from google code using bzr-svn to the local machine
2. optionally, push the imported trunk to launchpad
3. locally, make a branch of the imported trunk
4. develop on the local branch
5. merge back to google code periodically, using bzr-svn

Can you help with this problem?

Provide an answer of your own, or ask Andrés Moreno for more information if necessary.

To post a message you must log in.