File: README.source

package info (click to toggle)
bedtools 2.26.0%2Bdfsg-3
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 55,328 kB
  • sloc: cpp: 37,989; sh: 6,930; makefile: 2,225; python: 163
file content (34 lines) | stat: -rw-r--r-- 1,284 bytes parent folder | download | duplicates (6)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
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.

       checkout master
       git pull https://github.com/arq5x/bedtools2 --tags

     Remark: If this pull fails with a lot of stuff to merge you might
     have some ~/.gitconfig that breaks the pull above.  Please try to
     deactivate it for the moment.

  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 (stay in master branch when doing this)

       pristine-tar commit ../bedtools_<version>.orig.tar.gz v<version>

  4. Merge the tag in the debian/unstable branch

       git checkout debian/unstable ; git merge v<version>

  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.  The Debian Med policy currently
does only contain a short paragraph to mention the derived workflow:

    http://debian-med.alioth.debian.org/docs/policy.html#git-without-tarball