| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| Fix-UUID-struct-field-not-encoded-in-msgpack.patch | Fix UUID struct field not encoded in msgpack Upstream uses the old codec library, so there's no problem. |
Shengjing Zhu <zhsj@debian.org> | no | debian | 2019-03-26 | |
| Fix-time.Time-msgpack-decoding-backwards-compatibili.patch | Fix time.Time msgpack decoding backwards compatibility This allows aptly to decode DB created by old codec library. |
Shengjing Zhu <zhsj@debian.org> | yes | 2019-04-13 | ||
| s3-etag.patch | fix etag issue with s3 backend 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. 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. |
Andrej Shadura <andrew.shadura@collabora.co.uk> | yes | debian upstream | upstream | 2021-03-02 |