Raphaël G. Git Repositories - youtubedl/blob - README.source

   1 Debian packaging for youtube-dl
   2 -------------------------------
   3
   4 # Basic building of the package
   5
   6 A quick summary of how one can update the Debian packaging of youtube-dl is
   7 to, assuming that one already has the packages `devscripts`,
   8 `git-buildpackage`, and `pristine-tar` installed:
   9
  10     gbp clone --all https://github.com/rbrito/pkg-youtube-dl
  11     cd pkg-youtube-dl
  12     gbp import-orig --pristine-tar --uscan
  13     gbp dch -S -a
  14     [ Make here some adaptations, like updating debian/patches, if needed ]
  15     gbp buildpackage -us -uc # create a test build
  16
  17     # Final package creation:
  18
  19     gbp dch -R -a
  20     gbp buildpackage -k8F930BD1934C3E2140A258790747BD39BCFCAAAA --git-tag
  21
  22     # Push the results to the repositories:
  23     git push --all; git push --tags
  24     git push git@salsa.debian.org:debian/youtube-dl.git --all; git push git@salsa.debian.org:debian/youtube-dl.git --tags
  25     dput ftp-master youtube-dl*changes
  26
  27 These are the important steps and may need to be changed according to
  28 deviations, say, in the release process of upstream releases (e.g., if
  29 upstream changes the location where the tarballs reside).
  30
  31 # Maintaining the repository
  32
  33 I keep my development of the package (in particular, the master branch) at
  34 GitHub and I usually try to have my changes there, since I am not always
  35 with my SSH/GPG keys at hand.
  36
  37 For the benefit of the co-maintainers, I keep a backup copy of the changes
  38 at salsa.debian.org, where, due to said keys not being available at all times,
  39 I can't push my changes, which leads, sometimes to my GitHub repository to
  40 be ahead of the Debian mirror.
  41
  42 I prefer that, if possible, when working with the master branch:
  43
  44 * Please, check if I don't have changes already made at:
  45
  46       https://github.com/rbrito/pkg-youtube-dl
  47
  48 * People send me pull requests there
  49
  50 * If they are not comfortable with the use of GitHub for any kind of reason
  51   (political, ideological etc.), that they send me patches via email (git
  52   send-email is best).
  53
  54   This can be sent to my personal email or to the Debian BTS. I'm flexible.
  55
  56 Of course, if it is not possible to coordinate in the way described above,
  57 alas... :-(
  58
  59
  60  -- Rogério Brito <rbrito@ime.usp.br>, Mon, 21 Jan 2019 12:46:26 -0200