How do we convert old SVN imports to the new mechanism?

On Sat, 17 Apr 2010 07:28:01 you wrote:
> New question #107625 on Launchpad Bazaar Integration:
> https://answers.edge.launchpad.net/launchpad-code/+question/107625
>
> The Zope Toolk Kit project has the following SVN code imports done before
> the switch to bzr-svn:
>
> - lp:zope.deprecation
> - lp:zope.publisher
> - lp:zope.event
> - lp:zope.tal
> - lp:zope.component
> - lp:zope.deferredimport
> - lp:zope.formlib
> - lp:zope.interface
> - lp:zope.i18nmessageid
> - lp:zope.testbrowser
> - lp:zope.exceptions
> - lp:zope.tales
> - lp:zope.schema
> - lp:zope.proxy
> - lp:zope.pagetemplate
>
> I'd like to have new imports of these, so the Zope developers can take
> advantage of the ease-of-use that the bzr-svn imports offer. People might
> still be using the old imports. What can we do?
>
> My personal preferred option is that these imports continue to exist, but
> we get new imports going using the new mechanism. Is that reasonable and
> possible?
>
> Tres Seaver is the person leading this effort on the Zope side. I'm asking
> the question here both to try and help and to get my two cents in. :-)
>
> Thanks

We don't have a way to convert old style imports. Easiest way is to delete
the old and request new ones.

I would be glad to request new imports on behalf of the ZTK team, if only the UI would let me, but the existing imports are all owned by the 'vcs-imports' group: the ZTK team can't delete them.

Gary was worried that they might be needed to support ongoing work within the Launchpad team (or maybe other Ubuntu / Canonical teams).

On Sat, 17 Apr 2010 13:45:43 you wrote:
> Question #107625 on Launchpad Bazaar Integration changed:
> https://answers.launchpad.net/launchpad-code/+question/107625
>
> Tres Seaver posted a new comment:
> I would be glad to request new imports on behalf of the ZTK team, if
> only the UI would let me, but the existing imports are all owned by the
> 'vcs-imports' group: the ZTK team can't delete them.
>
> Gary was worried that they might be needed to support ongoing work
> within the Launchpad team (or maybe other Ubuntu / Canonical teams).

If you tell me the projects, and your launchpad ID, I could either assign all
the current branches to you, or just delete them.

On Sat, 17 Apr 2010 07:28:01 you wrote:
> My personal preferred option is that these imports continue to exist, but
> we get new imports going using the new mechanism. Is that reasonable and
> possible?

We can suspend the old imports. There is an issue where you can't have two
imports with the same url, so I'd do something hacky like add '.old' to the
urls.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tim Penhey wrote:
> Question #107625 on Launchpad Bazaar Integration changed:
> https://answers.launchpad.net/launchpad-code/+question/107625
>
> Tim Penhey proposed the following answer:
> On Sat, 17 Apr 2010 13:45:43 you wrote:
>> Question #107625 on Launchpad Bazaar Integration changed:
>> https://answers.launchpad.net/launchpad-code/+question/107625
>>
>> Tres Seaver posted a new comment:
>> I would be glad to request new imports on behalf of the ZTK team, if
>> only the UI would let me, but the existing imports are all owned by the
>> 'vcs-imports' group: the ZTK team can't delete them.
>>
>> Gary was worried that they might be needed to support ongoing work
>> within the Launchpad team (or maybe other Ubuntu / Canonical teams).
>
> If you tell me the projects, and your launchpad ID, I could either assign all
> the current branches to you, or just delete them.

The list of projects is in the original question text. ;) In case you
are doing your answering via e-mail and don't have the original question
handy, they include:

- - lp:zope.deprecation
- - lp:zope.publisher
- - lp:zope.event
- - lp:zope.tal
- - lp:zope.component
- - lp:zope.deferredimport
- - lp:zope.formlib
- - lp:zope.interface
- - lp:zope.i18nmessageid
- - lp:zope.testbrowser
- - lp:zope.exceptions
- - lp:zope.tales
- - lp:zope.schema
- - lp:zope.proxy
- - lp:zope.pagetemplate

My LP ID is 'tseaver'. The better logical owner for the branches is
'ztk-steering-group', of which I am a member.

Even if you reassign the branches right away, I will hold off on munging
anything about those branches until Gary gives me a thumbs up that I
won't be disrupting existing users. I think folks may have to do some
kind of migration to be able to push existing non-trunk branches, at
least if they are basd on the shortcut name, rather than the
lp:~vcs-imports/... name or its expansion.

Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 <email address hidden>
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkvJHL4ACgkQ+gerLs4ltQ5GkACeO1MJ6pt8ZgzD0KFRmDtAuc1y
uz8An1u5BVNGgRMc7+7U+04bYvA/NaMH
=JNzT
-----END PGP SIGNATURE-----

It looks as though the new branches now exist for all the ZTK projects except:

- zope.exception
- zope.pagetemplate
- zope.proxy
- zope.schema
- zope.tales
- zope.testbrowser
- zope.testing

The development focus was still pointed for some projects to the old branches: I have switched them over.

Thanks very much!

OK, I think they're all done now. I haven't done the development focus thing, my attempt to script that didn't work for mysterious reasons.

Thanks very much! I have updated the development focus for all the ZTK projects to point at the new branches.

While doing that, I noticed what seemed to be a UI change (which might be related to your script failure?): the link to set the development focus has disappeared from the overview page: I had to click through to the trunk series and edit it instead.