Accepted s3fs-fuse 1.80-1~bpo8+1 (source) into jessie-backports
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 28 Jun 2016 10:35:27 +0000
Source: s3fs-fuse
Binary: s3fs
Architecture: source
Version: 1.80-1~bpo8+1
Distribution: jessie-backports
Urgency: medium
Maintainer: Andriy Senkovych <jolly_roger@itblog.org.ua>
Changed-By: Mattia Rizzolo <mattia@debian.org>
Description:
s3fs - FUSE-based file system backed by Amazon S3
Changes:
s3fs-fuse (1.80-1~bpo8+1) jessie-backports; urgency=medium
.
* Rebuild for jessie-backports.
.
s3fs-fuse (1.80-1) unstable; urgency=medium
.
* Import new upstream release 1.80.
* Drop patch fixing typo, applied upstream.
* Bump Standards-Version to 3.9.8, no changes needed.
* Update copyright.
.
s3fs-fuse (1.79+git90-g8f11507-2) unstable; urgency=medium
.
[ Andriy Senkovych ]
* Update Vcs-* fields to point to collab-maint repository.
* Add some comments to gbp.conf.
.
[ Mattia Rizzolo ]
* debian/control:
+ Build only for {linux,kfreebsd}-any since fuse is not available on hurd.
+ Use my @debian.org email address.
+ Bump Standards-Version to 3.9.7, no changes needed.
+ Use https in Vcs-Git.
* Stop building s3fs-dbg package, nowadays we have automatic debug packages.
* Add patch to fix typo s/returing/returning/.
Checksums-Sha1:
9419baf39cc70fc55af0c8f9f03611b4fa808e6f 2068 s3fs-fuse_1.80-1~bpo8+1.dsc
f90f866ddb34497b2a9eaac9aa47a64a7dce656f 2672 s3fs-fuse_1.80-1~bpo8+1.debian.tar.xz
Checksums-Sha256:
fe338dbc20ac76fa06fa1450f40f89b6afe9f2b3502173d040a13daef7338cbe 2068 s3fs-fuse_1.80-1~bpo8+1.dsc
b222d67a0ecd6d7ce94d74cf274b46b4b77853349440beefc04b8fd676b8f7ea 2672 s3fs-fuse_1.80-1~bpo8+1.debian.tar.xz
Files:
7282fe07ee7a9144fa7efe9a7e5dc1b7 2068 utils optional s3fs-fuse_1.80-1~bpo8+1.dsc
1968da487ed03a272bb7cc1b4bd7b953 2672 utils optional s3fs-fuse_1.80-1~bpo8+1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCgAGBQJXclMaAAoJEEsEP825REVArb8P/RCa1KZN6aw1yFCJhlnbuFxg
8YhVWFGqB0Askxof+53w70zXPAqizge6ravKn4vrTILddo3/Rp+cLR5iqI7onD3u
MZ6lIdxja05FoYu4h5SIW5f26qfbNP6N4fvxihRBKgaaq4e57111sJov6IjOqF6X
CWCrLkk9wgXw4I+/QGzHkMkNGlJiEnGwCdiEupod+0/1w46tJxCWeCOAkqcrVVKe
EP2jqHsnhDrqZYfy5YbK05MO2s0f1Qr5UM/8YTompZS1yKDlVpEQ98HJbrh/li9u
lcjJE8pgPIxb7OeD+CXPMs5NNyuX0J6uXNTHmcuWEX8weM3k6w/KF7RySrhx08MG
j4apIEAHv8UahahS3VIPh0ClW34AZnB77Jk+k6RV2dFT9vOKIYEvkcZP0mPNe0Pi
MIO12kZhYMWxAwBXtBeCivzgoh7XyWU83y9do6NjwTrL21REh6LPHJ0OLO9J+O7+
iushxP5ypIrYd3DqVSrZznqMLXnKv4StfoC7PKp81HrTWMGa2zutp1kEFZwv6xuJ
SGTkyWj/E97pJY87HOQiNzuZuOC7wfQytc/iTS2hIff6JY4PebDP4W4RHoNzFBFp
oRb/WRO6d7jA9l3adwZx2LwGhW9iFE0stkQJOqXmkYqpB050938bG3dXj9BYbNza
q5MePNzSd+kQ3ri2dZeZ
=gHQJ
-----END PGP SIGNATURE-----
Reply to: