Import git-repair_1.20151215.orig.tar.xz

[dgit import orig git-repair_1.20151215.orig.tar.xz]

1 files changed, 36 insertions, 0 deletions

diff --git a/debian/control b/debian/control
new file mode 100644
index 0000000..cdbef1c
--- /dev/null
+++ b/debian/control
@@ -0,0 +1,36 @@
+Source: git-repair
+Section: utils
+Priority: optional
+Build-Depends: 
+	debhelper (>= 9),
+	ghc,
+	git,
+	libghc-missingh-dev,
+	libghc-hslogger-dev,
+	libghc-network-dev,
+	libghc-exceptions-dev (>= 0.6),
+	libghc-transformers-dev,
+	libghc-unix-compat-dev,
+	libghc-ifelse-dev,
+	libghc-text-dev,
+	libghc-quickcheck2-dev,
+	libghc-utf8-string-dev,
+	libghc-async-dev,
+	libghc-optparse-applicative-dev (>= 0.10.0)
+Maintainer: Richard Hartmann <richih@debian.org>
+Standards-Version: 3.9.5
+Vcs-Git: git://git-repair.branchable.com/
+Homepage: http://git-repair.branchable.com/
+
+Package: git-repair
+Architecture: any
+Section: utils
+Depends: ${misc:Depends}, ${shlibs:Depends}, git, rsync
+Description: repair various forms of damage to git repositories
+ git-repair can repair various forms of damage to git repositories.
+ .
+ It is a complement to git fsck, which finds problems, but does not fix them.
+ .
+ As well as avoiding the need to rm -rf a damaged repository and re-clone,
+ using git-repair can help rescue commits you've made to the damaged
+ repository and not yet pushed out.