mirror of
https://github.com/AGWA/git-crypt.git
synced 2026-01-01 07:27:52 -08:00
Compare commits
5 Commits
0.4.2
...
debian/0.4
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
f3890bed32 | ||
|
|
78fb6ab052 | ||
|
|
1fc9664036 | ||
|
|
2fa2cffba6 | ||
|
|
6b78ef0548 |
12
debian/changelog
vendored
Normal file
12
debian/changelog
vendored
Normal file
@@ -0,0 +1,12 @@
|
||||
git-crypt (0.4.2-1~agwa1) unstable; urgency=low
|
||||
|
||||
* New upstream release.
|
||||
* Various packaging improvements.
|
||||
|
||||
-- Andrew Ayer <agwa@andrewayer.name> Sat, 31 Jan 2015 19:43:06 -0800
|
||||
|
||||
git-crypt (0.3-1) unstable; urgency=low
|
||||
|
||||
* Initial release.
|
||||
|
||||
-- Andrew Ayer <agwa@andrewayer.name> Sat, 29 Mar 2014 12:38:14 -0700
|
||||
1
debian/compat
vendored
Normal file
1
debian/compat
vendored
Normal file
@@ -0,0 +1 @@
|
||||
9
|
||||
24
debian/control
vendored
Normal file
24
debian/control
vendored
Normal file
@@ -0,0 +1,24 @@
|
||||
Source: git-crypt
|
||||
Maintainer: Andrew Ayer <agwa@andrewayer.name>
|
||||
Section: vcs
|
||||
Priority: optional
|
||||
Standards-Version: 3.9.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
|
||||
git repository. Files which you choose to protect are encrypted when
|
||||
committed, and decrypted when checked out. git-crypt lets you freely
|
||||
share a repository containing a mix of public and private content.
|
||||
git-crypt gracefully degrades, so developers without the secret key
|
||||
can still clone and commit to a repository with encrypted files.
|
||||
This lets you store your secret material (such as keys or passwords)
|
||||
in the same repository as your code, without requiring you to lock down
|
||||
your entire repository.
|
||||
34
debian/copyright
vendored
Normal file
34
debian/copyright
vendored
Normal file
@@ -0,0 +1,34 @@
|
||||
Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
|
||||
Upstream-Name: git-crypt
|
||||
Source: https://www.agwa.name/projects/git-crypt
|
||||
|
||||
Files: *
|
||||
Copyright: Copyright 2014 Andrew Ayer <agwa@andrewayer.name>
|
||||
License: GPL-3+ with OpenSSL exception
|
||||
git-crypt is free software: you can redistribute it and/or modify
|
||||
it under the terms of the GNU General Public License as published by
|
||||
the Free Software Foundation, either version 3 of the License, or
|
||||
(at your option) any later version.
|
||||
.
|
||||
git-crypt is distributed in the hope that it will be useful,
|
||||
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
||||
GNU General Public License for more details.
|
||||
.
|
||||
You should have received a copy of the GNU General Public License
|
||||
along with git-crypt. If not, see <http://www.gnu.org/licenses/>.
|
||||
.
|
||||
On Debian systems, the full text of the GNU General Public
|
||||
License version 3 can be found in the file
|
||||
`/usr/share/common-licenses/GPL-3'.
|
||||
.
|
||||
Additional permission under GNU GPL version 3 section 7:
|
||||
.
|
||||
If you modify the Program, or any covered work, by linking or
|
||||
combining it with the OpenSSL project's OpenSSL library (or a
|
||||
modified version of that library), containing parts covered by the
|
||||
terms of the OpenSSL or SSLeay licenses, the licensors of the Program
|
||||
grant you additional permission to convey the resulting work.
|
||||
Corresponding Source for a non-source form of such a combination
|
||||
shall include the source code for the parts of OpenSSL used as well
|
||||
as that of the covered work.
|
||||
5
debian/gbp.conf
vendored
Normal file
5
debian/gbp.conf
vendored
Normal file
@@ -0,0 +1,5 @@
|
||||
[DEFAULT]
|
||||
pristine-tar = True
|
||||
pristine-tar-commit = True
|
||||
debian-branch = debian
|
||||
upstream-tag = %(version)s
|
||||
8
debian/git-crypt.docs
vendored
Normal file
8
debian/git-crypt.docs
vendored
Normal file
@@ -0,0 +1,8 @@
|
||||
CONTRIBUTING.md
|
||||
NEWS
|
||||
NEWS.md
|
||||
README
|
||||
README.md
|
||||
RELEASE_NOTES-0.4.1.md
|
||||
RELEASE_NOTES-0.4.md
|
||||
THANKS.md
|
||||
1
debian/git-crypt.install
vendored
Normal file
1
debian/git-crypt.install
vendored
Normal file
@@ -0,0 +1 @@
|
||||
git-crypt usr/bin
|
||||
6
debian/rules
vendored
Executable file
6
debian/rules
vendored
Executable file
@@ -0,0 +1,6 @@
|
||||
#!/usr/bin/make -f
|
||||
|
||||
%:
|
||||
dh $@
|
||||
|
||||
override_dh_auto_install:
|
||||
1
debian/source/format
vendored
Normal file
1
debian/source/format
vendored
Normal file
@@ -0,0 +1 @@
|
||||
3.0 (quilt)
|
||||
1
debian/source/options
vendored
Normal file
1
debian/source/options
vendored
Normal file
@@ -0,0 +1 @@
|
||||
single-debian-patch
|
||||
17
debian/source/patch-header
vendored
Normal file
17
debian/source/patch-header
vendored
Normal file
@@ -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.
|
||||
Reference in New Issue
Block a user