Breaking from another thread
On 31/03/15 15:57, Barry Warsaw wrote:
The team still officially supports only Subversion, but we have been
experimenting with switching to git.
https://wiki.debian.org/Python/GitPackaging
I personally favor and advocate git-dpm, but this has not yet been decided by
the team. I'd like for the team to make the switch very soon after Jessie is
released, and I would personally be comfortable switching now. We'll need to
decide a few things before we can do that:
> * Do we adopt git-dpm or something else?
Hello,
I have only been introduced to git-buildpackage and using Jenkins to
more or less automatically build them when proposing a patch or a change
is merged.
Michael "mika" Prokop [MIKA] maintains a very nice set of shell scripts
that makes it a breeze to integrate in Jenkins a git-buildpackage aware
repository and it uses cowbuilder to speed up the process.
http://jenkins-debian-glue.org/
[MIKA] https://qa.debian.org/developer.php?login=mika%40debian.org
Random example of pull requests being build by Jenkins and providing
lintian/piuparts/.deb:
https://integration.wikimedia.org/ci/view/Ops-DebGlue/job/labs-toollabs-debian-glue/
* Do we migrate all packages at once or one-at-a-time as needed?
From past experience in migrating a huge svn tree, it is usually easier
to move them in batches as developers request it. If you get to find
some volunteers, they will by the first line dealing with potential
issues and updating the doc. Will make it easier for others.
* Do we try to keep all svn history, or just upload history?
I tend to like the history, the blame and commit message logs are
sometime useful to get the context of a change/line of code.
I have recently migrated python-gear module which only had two tags. Did
that with git-svn which created something more or less appropriate. You
have to provide a map of:
svn login -> First Last <em...@example.org>
Can probably be generated.
The tags ended up being orphan branches but I did not care that much.
End result:
http://anonscm.debian.org/cgit/python-modules/packages/python-gear.git/log/
There is a bunch of tools to migrate from svn to git, can't find any
reference right now but there are. In lot of cases, you will have to
tweak the tool / write code to adjust it to your svn history.
At worse, one can import the trunk with git-svn then manually tag.
See also:
http://anonscm.debian.org/cgit/users/barry/import-dscs.git/tree/import-dscs.py
I'm sure there's more I'm missing. I would definitely like to keep this on
the radar.
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/551ab3b1.9050...@free.fr
