On Sun, Feb 25, 2024 at 07:13:30PM -0000, Julian Andres Klode wrote:
> Steve - it is a server package for hosting a web key server, it's
> entirely reasonable for it to depend on a mail transport agent. A WKS
> server, upon uploading a key, sends confirmation emails to the UIDs in
> the key, before publishing it, so that it only published keys with
> consent.
Ok. This is a sensible rationale, unfortunately. But it was important to
surface that in this bug report.
> It's problematic that it was installed by default, and I'm fixing this
> here and in Debian by doing the restructuring I did. This is not optimal
> for people upgrading without quirks (i.e. Debian users especially) but I
> don't think breaking the wks server to make upgrades without quirks
> nicer is a better choice.
Yeah, I don't see any better solution here. The only non-quirk solution
would be to add an artificial Conflicts: against gpg-wks-server.
On Sun, Feb 25, 2024 at 07:13:30PM -0000, Julian Andres Klode wrote:
> Steve - it is a server package for hosting a web key server, it's
> entirely reasonable for it to depend on a mail transport agent. A WKS
> server, upon uploading a key, sends confirmation emails to the UIDs in
> the key, before publishing it, so that it only published keys with
> consent.
Ok. This is a sensible rationale, unfortunately. But it was important to
surface that in this bug report.
> It's problematic that it was installed by default, and I'm fixing this
> here and in Debian by doing the restructuring I did. This is not optimal
> for people upgrading without quirks (i.e. Debian users especially) but I
> don't think breaking the wks server to make upgrades without quirks
> nicer is a better choice.
Yeah, I don't see any better solution here. The only non-quirk solution
would be to add an artificial Conflicts: against gpg-wks-server.