5031adcb7f
Install correct bash completion snippet ( Closes : #984979 )
2021-03-11 15:20:27 +01:00
c5322ff2f6
Update changelog for 1.4.0+ds1-3 release
2021-03-03 10:51:17 +01:00
a1f1cf307b
Bump-up Standards-Version
2021-03-03 10:50:49 +01:00
1b0cad0f1b
Bump-up d/watch version
2021-03-03 10:50:49 +01:00
29c2603d61
Remove unused d/source/include-binaries
2021-03-03 10:50:49 +01:00
ea9657dae0
Fix s3 etag issue ( Closes : #983877 )
2021-03-03 10:46:05 +01:00
2422d3ab40
When ETag doesn’t look like MD5, use the value from metadata instead
...
The S3 backend relies on ETag S3 returns being equal to the MD5 of the
object, but it’s not necessarily true. When the value returned clearly
doesn’t look like a valid MD5 hash (length isn’t exactly 32 characters),
attempt to retrieve the MD5 hash possibly stored in the metadata.
We cannot always do this since user-defined metadata isn’t returned by
the ListObjects call, so verifying it for each object is expensive as it
requires one HEAD request per each object.
This commit fixes #923 .
Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk >
2021-03-02 13:37:17 +00:00
960cf76c42
Store MD5 in a separate metadata field as well
...
The S3 backend relies on ETag S3 returns being equal to the MD5 of the
object, but it’s not necessarily true. For that purpose we store the MD5
object in a separate metadata field as well to make sure it isn’t lost.
From https://docs.aws.amazon.com/AmazonS3/latest/API/RESTCommonResponseHeaders.html :
> The entity tag is a hash of the object. The ETag reflects changes only
> to the contents of an object, not its metadata. The ETag may or may not
> be an MD5 digest of the object data. Whether or not it depends on how
> the object was created and how it is encrypted as described below:
>
> Objects created by the PUT Object, POST Object, or Copy operation,
> or through the AWS Management Console, and are encrypted by SSE-S3 or
> plaintext, have ETags that are an MD5 digest of their object data.
>
> Objects created by the PUT Object, POST Object, or Copy operation,
> or through the AWS Management Console, and are encrypted by SSE-C or
> SSE-KMS, have ETags that are not an MD5 digest of their object data.
>
> If an object is created by either the Multipart Upload or Part Copy
> operation, the ETag is not an MD5 digest, regardless of the method
> of encryption.
Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk >
2021-03-02 13:37:17 +00:00
af2564c580
Use newer Go for mod file
2021-02-12 09:23:24 +01:00
b385b1e975
Fix test breaking on newer versions of Go
...
Apparently, Go error message slightly changed in newer versions.
2021-02-12 09:23:24 +01:00
ce1d4b852a
Test against more recent versions of Go
...
Run basic tests for all minor versions since 1.11 and full tests for the last
two most recent versions.
Fix #939
2021-02-12 09:23:24 +01:00
c43d31f693
Don't fail hard if we can't clean Swift up
2021-02-08 10:52:27 +01:00
e4259c5045
Always try to get a version
...
Even if a simple git hash.
2021-02-08 10:52:27 +01:00
993dd2ad1c
Print test exception right away, in case the full test run crashes
2021-02-08 10:52:27 +01:00
3201244d9b
Fix tests and fixtures relying on expired pgp keys
...
PGP tests relied on expired gpg keys: upgrade with newer Debian keys from
https://ftp-master.debian.org/keys.html .
Download new fixtures files from http://ftp.debian.org/debian/dists/buster/
2021-02-08 10:52:27 +01:00
f4dc87fa44
Use a hostname more likely to be non-existent than localhost
...
Otherwise, it's possible that certain network configuration defining
*.localhost cause the tests to fail.
2021-02-08 10:52:27 +01:00
b61875fa9c
Update changelog for 1.4.0+ds1-2 release
2020-08-21 16:29:22 +02:00
1308c2f774
Pass version from d/rules ( Closes : #968585 )
2020-08-21 16:29:22 +02:00
63bc8282a0
Allow reprotest failure
2019-12-22 16:00:25 +01:00
cd0626e825
Use pipeline from salsa-ci-team
2019-12-22 15:47:01 +01:00
dc4b4a86a4
Update changelog for 1.4.0+ds1-1 release
2019-12-22 15:16:51 +01:00
bb6df8ee63
Depend on gnupg 2
2019-12-22 15:16:51 +01:00
199b5ab9b8
Rediff patches
...
Drop : <REASON>
Drop pborman-uuid.patch: <REASON>
Drop kjk-lzma.patch: <REASON>
2019-12-22 15:09:18 +01:00
5719d6fcdd
New upstream version 1.4.0+ds1
2019-12-22 15:09:18 +01:00
29e4ea6ec0
New upstream version 1.4.0+ds1
2019-12-22 14:57:35 +01:00
491c8ebdd1
Update changelog for 1.3.0+ds1-4 release
2019-12-22 14:10:39 +01:00
3afb6e47bf
Bump up Standards-Version
2019-12-22 14:10:04 +01:00
f767136371
Update changelog for 1.3.0+ds1-4 release
2019-12-22 13:58:16 +01:00
86162f0ef5
Merge branch 'lintian-fixes' of salsa.debian.org:janitor-bot-guest/aptly into debian/master
2019-12-22 13:57:47 +01:00
f03f8378b9
Revert "Force gz"
...
This reverts commit 074b35755d
2019-12-22 10:22:44 +01:00
074b35755d
Force gz
2019-12-21 10:51:08 +01:00
a92de0d9bd
Update changelog for 1.3.0+ds1-3 release
2019-12-21 10:29:34 +01:00
f966258772
Lintian fix
2019-12-21 10:29:34 +01:00
7938eebdcd
Build-Depend on golang-golang-x-tools-dev instead of golang-go.tools ( Closes : #945884 )
2019-12-21 10:21:18 +01:00
dccf1acb78
Set debhelper-compat version in Build-Depends.
...
Fixes lintian: uses-debhelper-compat-file
See https://lintian.debian.org/tags/uses-debhelper-compat-file.html for more details.
2019-11-29 08:02:45 +00:00
20278a7b5d
Bump debhelper from old 11 to 12.
...
Fixes lintian: package-uses-old-debhelper-compat-version
See https://lintian.debian.org/tags/package-uses-old-debhelper-compat-version.html for more details.
2019-11-29 08:02:25 +00:00
d4268fd4c6
Use secure URI in Homepage field.
...
Fixes lintian: homepage-field-uses-insecure-uri
See https://lintian.debian.org/tags/homepage-field-uses-insecure-uri.html for more details.
2019-11-29 08:02:06 +00:00
e7af54999f
Rename obsolete path debian/tests/control.autodep8 to debian/tests/control.
...
Fixes lintian: debian-tests-control-autodep8-is-obsolete
See https://lintian.debian.org/tags/debian-tests-control-autodep8-is-obsolete.html for more details.
2019-11-29 08:01:46 +00:00
24a027194e
Remove unused variable
2019-10-18 18:29:38 +03:00
62c4dc1472
Update authors
2019-10-18 18:29:38 +03:00
b7f74b4e55
Allow GPGFinder to work with nonstandard GPG version strings
...
Specifically, I have MacGPG installed instead of upstream GPG, which
results in the version string reading
gpg (GnuPG/MacGPG2) 2.2.17
instead of the expected
gpg (GnuPG) 2.2.17
2019-10-18 18:29:38 +03:00
2da853dcbe
Bump golangci-lint to 19.1
2019-09-27 15:44:33 +03:00
0438a7c76b
Upgrade AWS SDK to the latest version
2019-09-27 15:39:48 +03:00
c86c3a803f
Really upgrade goleveldb to the latest master version
...
PR #876 actually upgraded goleveldb to 1.0.0, not to the latest master.
Recent changes to goleveldb should improve performance
https://github.com/syndtr/goleveldb/issues/226#issuecomment-477568827
2019-09-27 14:19:39 +03:00
19db62d74f
Add new Go modules stuff
2019-09-27 13:59:19 +03:00
0146411483
Remove vendor/ tree, and dep files
2019-09-27 13:59:19 +03:00
b731e17850
Update nvidia repo key
2019-09-27 13:01:03 +03:00
bb66b2296d
Vendor update goleveldb
...
There are number of changes which went in recently which should improve
performance: https://github.com/syndtr/goleveldb/issues/226#issuecomment-477568827
2019-09-18 16:49:50 +04:00
c75ef8546e
Fix system tests for Debian Stretch 9.11
2019-09-18 01:23:58 +03:00
916d5a22c2
remove myself from uploaders
2019-09-15 19:28:43 -04:00
Sébastien Delafond
Andrej Shadura
Lorenzo Bolla
Debian Janitor
Don Kuntz
Andrey Smirnov
Alexandre Viau