[Pkg-tcltk-devel] Team migration (alioth -> salsa)

[Héctor Romojaro Gómez]

Hi,

El vie, 23-02-2018 a las 16:20 +0300, Sergei Golovan escribió:
> Hi Hector!
> 
> On Fri, Feb 23, 2018 at 3:50 PM, Héctor Romojaro Gómez
> <hector.romojaro at gmail.com> wrote:
> > Dear all,
> > 
> > I have just migrated one of the svn repositories (tdom) to git, so
> > far
> > so good. As "Master" role is required to create new repos in salsa,
> > i
> 
> Yes, I'll create the repositories at salsa after we'll agree on the
> migration procedure.
> 
> > just created it in alioth, moving it to salsa should be easy
> > afterwards.
> > 
> 
> Very nice work!

Thanks!

> But there's a few things to do yet:
> 
> 1) Only the latest upstream version is imported into the repository
> (0.9.0 in this particular case)
> which is not ideal. It would be nice to be able to recreate any
> packaged version from the repository.

Yes, that is certainly a better option, i wonder if it can be done
easily, will have a look at it.

> 2) I'd prefer to use the approach with a pristine-tar branch. If we
> have the full sources tree in the
> repository then why can't we recreate the upstream tarballs as well?

Agree!

I have populated the naviserver repo[1] on salsa with such a method,
which by the way would like to shamelessly ask for a first upload to
sid, but will use a different mail for that :)

> > If it works, this could probably be easily automated for all repos,
> > in
> > case the branch/tag structure fits in our workflows...
> 
> Looks like tags are converted just fine, but I don't know what would
> be with branches (tdom doesn't have them, one can try to convert
> tcllib with pretty simple branch structure - there were two branches
> for security upgrades, one for experiments, and another one called
> 'upstream', hehe).

Mmmmmmm there seems to be another way to do the whole process using
svn-all-fast-export[2], that may  take into account such scenario, in
particular on svn repositories created with svn-buildpackage. I will
try to convert tcllib and see what happens...

[1] https://salsa.debian.org/tcltk-team/naviserver
[2] https://wiki.debian.org/PackagingWithGit/Svn-buildpackageConversion

Kind regards,
Héctor
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-tcltk-devel/attachments/20180225/d28e3c38/attachment.sig>