swh-vault Debian release 0.0.26-1~swh1

# Conflicts:
#	debian/changelog

with Debian dir d435cc74c902a170b5fdc48da145889fe06e8da5

Might as well, as we already depend on 0.0.56+.

swh-vault Debian release 0.0.25-1~swh1

# Conflicts:
#	debian/changelog

with Debian dir 83155f91b0c5a0c0814f6c097e37b7e2da3dfc98

this later does not brings anything over the default's one.

This requires swh.core >= 0.0.56

Related T1532

swh-vault Debian release 0.0.24-1~swh3

# gpg: Signature made Mon Feb 18 15:22:18 2019 UTC
# gpg:                using RSA key BF00203D741AC9D546A8BE0752E2E9840D10C3B8
# gpg: Can't check signature: No public key

# Conflicts:
#	debian/changelog

For the backport build.

For the backport build.

swh-vault Debian release 0.0.24-1~swh2

# gpg: Signature made Mon Feb 18 15:13:52 2019 UTC
# gpg:                using RSA key BF00203D741AC9D546A8BE0752E2E9840D10C3B8
# gpg: Can't check signature: No public key

# Conflicts:
#	debian/changelog

with Debian dir 2d3ce91d0c7391e64dfae77d2e5a2ea02f99e008

with Debian dir cd06419825e0eb80e25bd7b1e337048320f724ad

Prior to this commit, during the case of committing in another
branch (ref), there were dangling files in the HEAD branch.

Related T1525

Related T1525