project "clam" vcs-import remains "non imported" after 5+ days

Well, my wrists prefer it when you give me URLs :-)

Ok, now the branch have been imported. But only the "CLAM" subdir of the our subversion trunk. In other words the imported branch corresponds to:
svn co http://iua-share.upf.edu/svn/clam/trunk/CLAM

While we need all the dirs (CLAM, NetworkEditor...) in the provided subversion URL:
svn co http://iua-share.upf.edu/svn/clam/trunk

Note that CLAM project is composed of some libraries and plugins (that sits in CLAM/) and some core applications (like NetworkEditor) to use them.

Could you re-import? Thanks.

On Sat, Jun 28, 2008 at 04:11:48PM -0000, Pau Arumi wrote:
> Ok, now the branch have been imported. But only the "CLAM" subdir of the our subversion trunk. In other words the imported branch corresponds to:
> svn co http://iua-share.upf.edu/svn/clam/trunk/CLAM
>
> While we need all the dirs (CLAM, NetworkEditor...) in the provided subversion URL:
> svn co http://iua-share.upf.edu/svn/clam/trunk
>
> Note that CLAM project is composed of some libraries and plugins (that
> sits in CLAM/) and some core applications (like NetworkEditor) to use
> them.

I think these different libraries and plugins should be registered as
separate projects. The reason I say this is that Launchpad supports
groups of projects (project groups!); individual projects are meant to
be separately registered.
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125

On ds, 2008-06-28 at 16:36 +0000, Christian Reis wrote:

>
> I think these different libraries and plugins should be registered as
> separate projects. The reason I say this is that Launchpad supports
> groups of projects (project groups!); individual projects are meant to
> be separately registered.

Well, the point is that we move things from apps (e.g. NetworkEditor) to
the libs, and the other way around, very often.
I'm not sure if this kind of movements are more difficult to track when
they are from different branches that if done within the same branch.
But I'd say it is.

And also, we do release the libs and apps at the same time, and share a
common version number.

We might be convinced of the contrary, or that we'll decide to further
separate the sub-projects in the future, but right now we'd be more
confortable to work as we are used.
Also note that I'm trying to promote the experimentation with bzr
branches along with the main subversion repository, as a matter of
evaluation. So I'd like to go in small steps.

Seems that the imported bazaar branch remains at trunk/CLAM instead of trunk/
Right now, we tend to treat all the code in trunk/ as a whole, doing a lot of cross-application/library refactorings, and doesn't have sense to split our code base in different bazaar branches. It is likely it will make sense in the future, but not now.

Could you please take action?

The complete URL is: http://iua-share.upf.edu/svn/clam/trunk (which includes CLAM/ NetworkEditor/ etc)

Thanks

Ok, that import (to trunk/CLAM) have been suspended, and a new one (to trunk/) has been requested and aproved. Thanks Michael Hudson at #launchpad irc for the quick help! :-)