Freshen Debian packaging

debian/control

@@ -3,13 +3,14 @@ Maintainer: Andrew Ayer <agwa@andrewayer.name>
 Section: vcs
 Priority: optional
 Standards-Version: 3.9.4
-Build-Depends: debhelper (>= 9), make (>= 3.81-5), libc6-dev (>= 2.7-18), gcc (>= 4:4.3.2-2), coreutils (>= 6.10-6), libssl-dev (>= 0.9.8o-4)
+Build-Depends: debhelper (>= 9), libssl-dev
 Vcs-Git: https://www.agwa.name/git/git-crypt.git -b debian
 Homepage: https://www.agwa.name/projects/git-crypt
 
 Package: git-crypt
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, git (>= 1.7.2)
+Recommends: gnupg
 Enhances: git
 Description: Transparent file encryption in git
  git-crypt enables transparent encryption and decryption of files in a

debian/copyright

@@ -1,6 +1,6 @@
 Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Name: git-crypt
-Source: https://github.com/AGWA/git-crypt
+Source: https://www.agwa.name/projects/git-crypt
 
 Files: *
 Copyright: Copyright 2014 Andrew Ayer <agwa@andrewayer.name>

debian/gbp.conf

@@ -1,4 +1,5 @@
 [DEFAULT]
+pristine-tar = True
+pristine-tar-commit = True
 debian-branch = debian
 upstream-tag = %(version)s
-

debian/rules

@@ -1,13 +1,4 @@
 #!/usr/bin/make -f
-# -*- makefile -*-
-# Sample debian/rules that uses debhelper.
-# This file was originally written by Joey Hess and Craig Small.
-# As a special exception, when this file is copied by dh-make into a
-# dh-make output file, you may use that output file without restriction.
-# This special exception was added by Craig Small in version 0.37 of dh-make.
-
-# Uncomment this to turn on verbose mode.
-#export DH_VERBOSE=1
 
 %:
 	dh  $@

debian/source/format

@@ -0,0 +1 @@
+3.0 (quilt)

debian/source/options

@@ -0,0 +1 @@
+single-debian-patch

debian/source/patch-header

@@ -0,0 +1,17 @@
+Subject: Collected Debian patches for git-crypt
+Author: Andrew Ayer <agwa@andrewayer.name>
+
+Since I am also upstream for this package, there will normally not be
+any patches to apply to the upstream source.  However, occasionally
+I'll pull up specific upstream commits prior to making an upstream
+release.  When this happens, this patch will collect all of those
+modifications.
+
+I use Git to maintain both the upstream source and the Debian
+packages, and generating individual patches rather than using git
+cherry-pick takes extra work for no gain.  Since I'm also upstream,
+there's no need to separate the patches for later upstream submission.
+Hence, I take this approach with a unified patch when it's necessary.
+
+For full commit history and separated commits, see the upstream Git
+repository.