This is an automated email from the git hooks/post-receive script. tille pushed a commit to branch debian/unstable in repository bedtools.
commit 6e2262df973c2990ae05fe212796458d1b2d717b Author: Andreas Tille <[email protected]> Date: Tue Jul 7 10:46:06 2015 +0200 Add README.source to descripe the workflow for this repository that derives from Debian Med policy --- debian/README.source | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/debian/README.source b/debian/README.source new file mode 100644 index 0000000..db53f4a --- /dev/null +++ b/debian/README.source @@ -0,0 +1,27 @@ +Since this Git repository does not follow the usual Debian Med +workflow it is documented here, how the package can be updated: + + 1. in the master branch, pull the upstream master branch and its tags. + + git pull https://github.com/arq5x/bedtools2 --tags + + FIXME: If this leads to lot of merge conflicts, do what? + + 2. download the upstream tarball + + uscan --force-download + + 3. Register the upstream tarball in the pristine-tar branch directly with + the pristine-tar command directly. + + pristine-tar ../bedtools_<version>.orig.tar.gz v<version> + + 4. Merge the tag in the debian/unstable branch + + git checkout debian/unstable ; git merge v2.24.0 + + 5. Update the packaging files, build with gbp - debian-branch and + upstream-branch are properly set in debian/gbp.conf + +According to Charles Plessy this workflow has the advantage to propose +upstream via pull requests on GitHub -- Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/debian-med/bedtools.git _______________________________________________ debian-med-commit mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-commit
