Please move Elisa's trunk branch import source

Asked by Florian Boucault

Elisa's vcs import of the official SVN repository (https://code.launchpad.net/~vcs-imports/elisa/trunk) is using a deprecated URL and thus has not received any updates in months. Is it possible to move the trunk branch to the newer SVN repository? SVN checkout command is 'svn co https://code.fluendo.com/elisa/svn/trunk elisa'.

Thanks in advance for the help.

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Launchpad Janitor (janitor) said :
#1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Christian Reis (kiko) said :
#2

I've updated the hostname (core->code) but I'm not sure that's all I need to do.

Revision history for this message
Michael Hudson-Doyle (mwhudson) said :
#3

I think I need more information as to what needs to be imported here.

The provided Subversion URL https://code.fluendo.com/elisa/svn/trunk does not contain the sort of thing we usually import. Generally, it is most useful to import the directory that will get packed up into a tarball when a release is made -- the directory that contains the README, the configure script, etc. To me, it looks like this directory is at https://code.fluendo.com/elisa/svn/trunk/elisa-core. But if you want, I can make the import from the URL provided.

Also, at this stage it would be easier to throw the old branch away and do a new import. The new import would not share any history with the currently existing branch, though, so if anyone has branched off the current import branch it would be best if I got the current import working again. Please let me know which you would prefer :)

Revision history for this message
Florian Boucault (fboucault) said :
#4

For the moment, to get a usable Elisa, one needs to branch from https://code.fluendo.com/elisa/svn/trunk. Thanks for having taken a deeper look into it though.

You can definitely drop the old branch and create a brand new one.

Thanks a big deal Michael!

Revision history for this message
Michael Hudson-Doyle (mwhudson) said :
#5

It's running.

Revision history for this message
Florian Boucault (fboucault) said :
#6

Oddly for some reason the history of the new bazaar branch has only 112 revisions whereas the SVN has 5058 revisions. Can you please have a look at that?

Thanks in advance.

Revision history for this message
Tim Penhey (thumper) said :
#7

Subversion increments the revision number whenever a commit is done across the entire repository which includes other branches (and maybe tags), and sometimes other projects depending on how the subversion server is set up.

The only way to truly confirm whether or not the bazaar version is up to date is to branch from the vcs-imports branch, and checkout the subversion code, then use a directory diffing program (like kdiff3) to check the actual files.

It isn't unusual for the numbers to be different.

Revision history for this message
Florian Boucault (fboucault) said :
#8

Indeed, I understand your point Tim.

However, we are talking about 4900 revisions missing! Given that the way we worked with it was pretty typical (most of the commits were made into trunk/), it is clear that something is wrong.

Revision history for this message
Michael Hudson-Doyle (mwhudson) said :
#9

It looks like at revision 4947 'guidonte' copied revision 4906's version of trunk over the version that existed before:

mwh@grond:archive$ svn log -vvv https://code.fluendo.com/elisa/svn -r4947
------------------------------------------------------------------------
r4947 | guidonte | 2008-02-12 23:34:50 +1300 (Tue, 12 Feb 2008) | 1 line
Changed paths:
   R /trunk (from /trunk:4906)
   M /trunk/elisa-plugins/elisa/plugins/elisa_updater/epm/egg_registry.py

small fixes.
------------------------------------------------------------------------

I think that the import tool (CSCVS) treats this as a new trunk, and that history should start from here.

This is arguably a bug in cscvs, I guess, but I'm not surprised that it gets confused by such things (I know I do :).

Can you help with this problem?

Provide an answer of your own, or ask Florian Boucault for more information if necessary.

To post a message you must log in.