deb/local.go | 4 2 + 2 - 0 !
deb/snapshot.go | 6 3 + 3 - 0 !
2 files changed, 5 insertions(+), 5 deletions(-)

 fix uuid struct field not encoded in msgpack

Upstream uses the old codec library, so there's no problem.
Bug-Debian: https://bugs.debian.org/923866

deb/remote.go | 3 2 + 1 - 0 !
deb/snapshot.go | 3 2 + 1 - 0 !
2 files changed, 4 insertions(+), 2 deletions(-)

 fix time.time msgpack decoding backwards compatibility

This allows aptly to decode DB created by old codec library.

s3/public.go | 38 34 + 4 - 0 !
1 file changed, 34 insertions(+), 4 deletions(-)

 fix etag issue with s3 backend
 The S3 backend relies on ETag S3 returns being equal to the MD5 of
 the object, but its not necessarily true. For that purpose we store
 the MD5 object in a separate metadata field as well to make sure it
 isnt lost. When the value returned clearly doesnt look like a valid
 MD5 hash (length isnt exactly 32 characters), attempt to retrieve
 the MD5 hash possibly stored in the metadata.
 .
  We cannot always do this since user-defined metadata isnt returned
  by the ListObjects call, so verifying it for each object is
  expensive as it requires one HEAD request per each object.