Commit Graph
2633 Commits
Author SHA1 Message Date
Joshua Colson 899ed92ebc Add -json flag to publish list|show
Signed-off-by: Joshua Colson <joshua.colson@gmail.com>
2021-09-24 10:29:33 +02:00
Joshua Colson 129eb8644d Add -json flag to mirror list|show
Signed-off-by: Joshua Colson <joshua.colson@gmail.com>
2021-09-24 10:29:33 +02:00
Joshua Colson d582f9bab2 Add Debian 11 keys to test fixture keyring
Signed-off-by: Joshua Colson <joshua.colson@gmail.com>
2021-09-24 10:29:33 +02:00
Joshua Colson 0f1575d5af Add -json flag to snapshot show|list
Signed-off-by: Joshua Colson <joshua.colson@gmail.com>
2021-09-24 10:29:33 +02:00
Joshua Colson f9c0d99790 Refactor repo list into json and txt output
Signed-off-by: Joshua Colson <joshua.colson@gmail.com>
2021-09-24 10:29:33 +02:00
Joshua Colson 1f56fb86e3 Add -json output flag to repo list|show
Signed-off-by: Joshua Colson <joshua.colson@gmail.com>
2021-09-24 10:29:33 +02:00
Ratchanan Srirattanamet f9d08e1377 .goxc.json: list os/arch explicitly to avoid darwin/386
Go 1.15 drops support for darwin/386 GOOS/GOARCH pair [1]. So, we have
to skip this pair, and thus cannot use simple os multiply arch anymore.
Switch to goxc's BuildConstraints config, which uses the same syntax as
Go's build constraint header [2].

[1] https://github.com/golang/go/issues/37610
[2] https://golang.org/cmd/go/#hdr-Build_constraints
2021-04-29 14:41:24 +02:00
Max Bruckner cbf0416d7e Filter command: Fix typo Priorioty -> Priority 2021-03-21 09:59:39 +01:00
Sébastien Delafond 82ddc7f9ce Update changelog for 1.4.0+ds1-4 release 2021-03-11 15:21:03 +01:00
Sébastien Delafond 5031adcb7f Install correct bash completion snippet (Closes: #984979) 2021-03-11 15:20:27 +01:00
Sébastien Delafond c5322ff2f6 Update changelog for 1.4.0+ds1-3 release 2021-03-03 10:51:17 +01:00
Sébastien Delafond a1f1cf307b Bump-up Standards-Version 2021-03-03 10:50:49 +01:00
Sébastien Delafond 1b0cad0f1b Bump-up d/watch version 2021-03-03 10:50:49 +01:00
Sébastien Delafond 29c2603d61 Remove unused d/source/include-binaries 2021-03-03 10:50:49 +01:00
Sébastien Delafond ea9657dae0 Fix s3 etag issue (Closes: #983877) 2021-03-03 10:46:05 +01:00
Andrej Shadura 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
Andrej Shadura 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
Lorenzo Bolla af2564c580 Use newer Go for mod file 2021-02-12 09:23:24 +01:00
Lorenzo Bolla 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
Lorenzo Bolla 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
Lorenzo Bolla c43d31f693 Don't fail hard if we can't clean Swift up 2021-02-08 10:52:27 +01:00
Lorenzo Bolla e4259c5045 Always try to get a version
Even if a simple git hash.
2021-02-08 10:52:27 +01:00
Lorenzo Bolla 993dd2ad1c Print test exception right away, in case the full test run crashes 2021-02-08 10:52:27 +01:00
Lorenzo Bolla 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
Lorenzo Bolla 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
Sébastien Delafond b61875fa9c Update changelog for 1.4.0+ds1-2 release 2020-08-21 16:29:22 +02:00
Sébastien Delafond 1308c2f774 Pass version from d/rules (Closes: #968585) 2020-08-21 16:29:22 +02:00
Sébastien Delafond 63bc8282a0 Allow reprotest failure 2019-12-22 16:00:25 +01:00
Sébastien Delafond cd0626e825 Use pipeline from salsa-ci-team 2019-12-22 15:47:01 +01:00
Sébastien Delafond dc4b4a86a4 Update changelog for 1.4.0+ds1-1 release 2019-12-22 15:16:51 +01:00
Sébastien Delafond bb6df8ee63 Depend on gnupg 2 2019-12-22 15:16:51 +01:00
Sébastien Delafond 199b5ab9b8 Rediff patches
Drop : <REASON>
Drop pborman-uuid.patch: <REASON>
Drop kjk-lzma.patch: <REASON>
2019-12-22 15:09:18 +01:00
Sébastien Delafond 5719d6fcdd New upstream version 1.4.0+ds1 2019-12-22 15:09:18 +01:00
Sébastien Delafond 29e4ea6ec0 New upstream version 1.4.0+ds1 2019-12-22 14:57:35 +01:00
Sébastien Delafond 491c8ebdd1 Update changelog for 1.3.0+ds1-4 release 2019-12-22 14:10:39 +01:00
Sébastien Delafond 3afb6e47bf Bump up Standards-Version 2019-12-22 14:10:04 +01:00
Sébastien Delafond f767136371 Update changelog for 1.3.0+ds1-4 release 2019-12-22 13:58:16 +01:00
Sébastien Delafond 86162f0ef5 Merge branch 'lintian-fixes' of salsa.debian.org:janitor-bot-guest/aptly into debian/master 2019-12-22 13:57:47 +01:00
Sébastien Delafond f03f8378b9 Revert "Force gz"
This reverts commit 074b35755d.
2019-12-22 10:22:44 +01:00
Sébastien Delafond 074b35755d Force gz 2019-12-21 10:51:08 +01:00
Sébastien Delafond a92de0d9bd Update changelog for 1.3.0+ds1-3 release 2019-12-21 10:29:34 +01:00
Sébastien Delafond f966258772 Lintian fix 2019-12-21 10:29:34 +01:00
Sébastien Delafond 7938eebdcd Build-Depend on golang-golang-x-tools-dev instead of golang-go.tools (Closes: #945884) 2019-12-21 10:21:18 +01:00
Debian Janitor 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
Debian Janitor 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
Debian Janitor 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
Debian Janitor 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
Don Kuntz 24a027194e Remove unused variable 2019-10-18 18:29:38 +03:00
Don Kuntz 62c4dc1472 Update authors 2019-10-18 18:29:38 +03:00
Don Kuntz 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