Re: [Pkg-tcltk-devel] Team migration (alioth -> salsa)
On Tue, Feb 27, 2018 at 12:59 AM, Stefan Sobernig wrote: >> Ah, it's already uses Git. So I guess, you can create a new 'nsf' >> project on salsa, then replace the origin url at your local repository >> and push it all to salsa. > > Okay, I used the GitLab generic import feature, should be fine this way: > > https://salsa.debian.org/tcltk-team/nsf > > Do I have to change any repository settings at salsa? I don't think so if it works for you. > > At which point should the changed Vcs details be reflected in > debian/control? I would say that "at the next upload, whenever it will happen". There's no hurry in that. Cheers! -- Sergei Golovan ___ Pkg-tcltk-devel mailing list Pkg-tcltk-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tcltk-devel
Re: [Pkg-tcltk-devel] Team migration (alioth -> salsa)
> Ah, it's already uses Git. So I guess, you can create a new 'nsf' > project on salsa, then replace the origin url at your local repository > and push it all to salsa. Okay, I used the GitLab generic import feature, should be fine this way: https://salsa.debian.org/tcltk-team/nsf Do I have to change any repository settings at salsa? At which point should the changed Vcs details be reflected in debian/control? Thx, Stefan ___ Pkg-tcltk-devel mailing list Pkg-tcltk-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tcltk-devel
Re: [Pkg-tcltk-devel] Team migration (alioth -> salsa)
Ah, it's already uses Git. So I guess, you can create a new 'nsf' project on salsa, then replace the origin url at your local repository and push it all to salsa. On Mon, Feb 26, 2018 at 11:35 PM, Stefan Sobernig wrote: > Hi Sergei! > >> I don't see nsf repository anywhere. > > https://tracker.debian.org/pkg/nsf > https://anonscm.debian.org/git/collab-maint/nsf.git > > //stefan -- Sergei Golovan ___ Pkg-tcltk-devel mailing list Pkg-tcltk-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tcltk-devel
Re: [Pkg-tcltk-devel] Team migration (alioth -> salsa)
Hi Sergei! > I don't see nsf repository anywhere. https://tracker.debian.org/pkg/nsf https://anonscm.debian.org/git/collab-maint/nsf.git //stefan ___ Pkg-tcltk-devel mailing list Pkg-tcltk-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tcltk-devel
Re: [Pkg-tcltk-devel] Team migration (alioth -> salsa)
Hi Stefan, On Mon, Feb 26, 2018 at 11:09 PM, Stefan Sobernig wrote: > Hi everybody, > > I acknowledge having received privileges as a member of the tclk-team at > salsa. Thx. Good to know. > > I am wondering: Am I supposed to transfer (migrate) tdom, nsf, and > xotcl, now? tdom seems to in the process, xotcl appears at salsa, nsf is > missing ... am I missing anything? I've migrated tdom (it's a bit messy, because there was a clash in upstream versions, but the latest commits are fine) and xotcl from Alioth's subversion. I don't see nsf repository anywhere. Cheers! -- Sergei Golovan ___ Pkg-tcltk-devel mailing list Pkg-tcltk-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tcltk-devel
Re: [Pkg-tcltk-devel] Team migration (alioth -> salsa)
Hi everybody, I acknowledge having received privileges as a member of the tclk-team at salsa. Thx. I am wondering: Am I supposed to transfer (migrate) tdom, nsf, and xotcl, now? tdom seems to in the process, xotcl appears at salsa, nsf is missing ... am I missing anything? Thanks again, Stefan ___ Pkg-tcltk-devel mailing list Pkg-tcltk-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tcltk-devel
Re: [Pkg-tcltk-devel] Team migration (alioth -> salsa)
Hi Sergei! > Stefan Sobernig > > If any of you wants to be added to the team, please, register at salsa [2] and > request the participation at [1]. So I did: ssoberni-guest. All the best, Stefan ___ Pkg-tcltk-devel mailing list Pkg-tcltk-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tcltk-devel
Re: [Pkg-tcltk-devel] Team migration (alioth -> salsa)
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 > 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). Mmm 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 signature.asc Description: This is a digitally signed message part ___ Pkg-tcltk-devel mailing list Pkg-tcltk-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tcltk-devel
Re: [Pkg-tcltk-devel] Team migration (alioth -> salsa)
Hi Hector! On Fri, Feb 23, 2018 at 3:50 PM, Héctor Romojaro Gómez 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! 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. 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? > > 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). Cheers! -- Sergei Golovan ___ Pkg-tcltk-devel mailing list Pkg-tcltk-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tcltk-devel
Re: [Pkg-tcltk-devel] Team migration (alioth -> salsa)
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
just created it in alioth, moving it to salsa should be easy
afterwards.
The repo is here[1], and for svn to git migration i used a similar
process to what is described in the alioth guide[2], details below.
For the authors file (users.txt) linking old alioth usernames to names
and emails, i have used the information available in the project
members page, in alioth[3].
The process in detail:
1- Convert the repository
$ git svn clone svn://anonscm.debian.org/pkg-tcltk/tdom/ --prefix=svn-
import/ --stdlayout --authors-file=users.txt --no-metadata tdom
2- Convert remote tags and branches to local
for branch in `git branch -r`; do
if [ `echo $branch | egrep "svn-import/tags/.+$"` ]; then
version=`basename $branch`
subject=`git log -1 --pretty=format:"%s" $branch`
GIT_COMMITTER_DATE=`git log -1 --pretty=format:"%ci" $branch` \
git tag -f -m "$subject" "debian/$version" "$branch^"
git branch -d -r $branch
fi
done
3- Remove old references and convert remote branches to locals
$ git branch -d -r svn-import/trunk
$ git config --remove-section svn-remote.svn
$ rm -rf .git/svn .git/{logs/,}refs/remotes/svn/
$ git config remote.origin.url .
$ git config --add remote.origin.fetch +refs/remotes/*:refs/heads/*
$ git fetch
4- Import upstream source
$ git symbolic-ref HEAD refs/heads/upstream
$ git rm --cached -r .
$ git commit --allow-empty -m 'initial upstream branch'
$ git checkout -f master
$ git merge upstream --allow-unrelated-histories
$ gbp import-orig ../tdom_0.9.0.orig.tar.gz
5- Create the empty repo (on alioth)
(alioth) $ /git/pkg-tcltk/packages/setup-repository tdom 'Fast
XML/DOM/XPath/XSLT extension for Tcl written in C'
6- Push our local repo (geox-guest is my alioth account)
$ git remote set-url origin ssh://geox-gu...@git.debian.org/git/pkg-tcl
tk/packages/tdom.git
$ git push --follow-tags --force --all origin
And that's it. There are probably other ways of doing it, and perhaps a
script for automating it somewhere, but whatever.
In any case, it looks good at first glance, but i haven't tested the
build process yet.
If it works, this could probably be easily automated for all repos, in
case the branch/tag structure fits in our workflows...
[1] https://anonscm.debian.org/cgit/pkg-tcltk/packages/tdom.git/
[2] https://wiki.debian.org/de/Alioth/Git#Convert_a_SVN_Alioth_repository_to_Git
[3] https://alioth.debian.org/project/memberlist.php?group_id=30825
Kind regards,
Héctor
signature.asc
Description: This is a digitally signed message part
___
Pkg-tcltk-devel mailing list
Pkg-tcltk-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tcltk-devel
Re: [Pkg-tcltk-devel] Team migration (alioth -> salsa)
El vie, 23-02-2018 a las 08:51 +0300, Sergei Golovan escribió: > > So, in short, is anyone else looking into this? I can volunteer to > > help, but my current DM status only allows me to create a new > > account > > (hromojaro-guest), but not much more (i guess[3])... :-/ > > You are a member of the team now. Next task would be moving the > projects > repositories to salsa, converting them from svn. Thanks, Sergei, will have a look at it. Kind regards, Héctor signature.asc Description: This is a digitally signed message part ___ Pkg-tcltk-devel mailing list Pkg-tcltk-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tcltk-devel
Re: [Pkg-tcltk-devel] Team migration (alioth -> salsa)
Hi Hector, On Thu, Feb 22, 2018 at 10:02 PM, Héctor Romojaro Gómez wrote: > Dear all, > > Not sure if anyone is looking into this already, but as alioth is > reaching its end[1], there seems to be necessary to move the whole > tcltk team and its repositories to gitlab's based salsa.debian.org[2], > which also implies transforming old svn repos into git ones, and maybe > eventually closing the mailing lists... I've created the Tcl/Tk team at salsa [1] and added all members from the Alioth project which are registered at salsa at the moment. Missing members are: Chris Waters Dinakar Desai Daniel Rus Morales Stefan Sobernig If any of you wants to be added to the team, please, register at salsa [2] and request the participation at [1]. > > So, in short, is anyone else looking into this? I can volunteer to > help, but my current DM status only allows me to create a new account > (hromojaro-guest), but not much more (i guess[3])... :-/ You are a member of the team now. Next task would be moving the projects repositories to salsa, converting them from svn. As for mailing lists I've asked to migrate them from lists.alioth.debian.org, haven't heard the migration news yet. > > [1] https://wiki.debian.org/Alioth#Deprecation_of_Alioth > [2] https://wiki.debian.org/Salsa/Doc > [3] https://lists.debian.org/debian-devel/2018/01/msg00386.html [1] https://salsa.debian.org/tcltk-team [2] https://signup.salsa.debian.org/ -- Sergei Golovan ___ Pkg-tcltk-devel mailing list Pkg-tcltk-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tcltk-devel
Re: [Pkg-tcltk-devel] Team migration (alioth -> salsa)
Also, regarding list migration, there is a deadline on 15th March for automatic migration: https://lists.debian.org/debian-devel-announce/2018/01/msg3.html Kind regards, Héctor El jue, 22-02-2018 a las 20:02 +0100, Héctor Romojaro Gómez escribió: > Dear all, > > Not sure if anyone is looking into this already, but as alioth is > reaching its end[1], there seems to be necessary to move the whole > tcltk team and its repositories to gitlab's based > salsa.debian.org[2], > which also implies transforming old svn repos into git ones, and > maybe > eventually closing the mailing lists... > > So, in short, is anyone else looking into this? I can volunteer to > help, but my current DM status only allows me to create a new account > (hromojaro-guest), but not much more (i guess[3])... :-/ > > [1] https://wiki.debian.org/Alioth#Deprecation_of_Alioth > [2] https://wiki.debian.org/Salsa/Doc > [3] https://lists.debian.org/debian-devel/2018/01/msg00386.html > > Kind regards, > Héctor signature.asc Description: This is a digitally signed message part ___ Pkg-tcltk-devel mailing list Pkg-tcltk-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tcltk-devel
