Sorry it took so long to confirm, but indeed adding -a to the gpg line
fixes this problem. And continues to work at least all the way back to
Sarge...
So, I don't think there is anything to do but a ideally a clearer error
message and also some documentation.
Ah, that's it. It's a binary detached signature. I probably missed the
documentation when it was originally set up (or maybe it hasn't always been
documented well, it was originally set up a decade ago).
I'll fix the signature generation later today and confirm.
I don't see a problem with dropp
Hi,
On Thu, Feb 07, 2019 at 04:54:01PM -0500, Anthony DeRobertis wrote:
> We have a local repository here which is generated with an (ancient!)
> version of mini-dinstall. This worked fine until rc2. The problem
> appears to be that it uses Release and Release.gpg instead of InRelease.
~rc1 adds
Package: libapt-pkg5.0
Version: 1.8.0~rc2
Severity: important
We have a local repository here which is generated with an (ancient!)
version of mini-dinstall. This worked fine until rc2. The problem
appears to be that it uses Release and Release.gpg instead of InRelease.
root@648fb8052f3f:/# a
4 matches
Mail list logo
