lea
no worries, I'll reopen this issue, by chance, does `pkcon refresh force` make a difference?
TL;DR: The package needs to ship an AppStream XML file. It could be generated, but it would be extremely barebones.
> @venkatamutyala > > I am currently using 1.11.3, not the @lleyton branch > > But I looked at the commits on his branch and that seemed to allow "P"...
Got it!
Would it also be possible to remove the warning from the repology website?
From what I understand, the issue you're encountering is that internal traffic towards a LBed service aren't getting proxy protocol headers? If so, we could implement [a workaround](https://github.com/digitalocean/digitalocean-cloud-controller-manager/blob/master/docs/controllers/services/examples/README.md#accessing-pods-over-a-managed-load-balancer-from-inside-the-cluster) such that...
Alternatively, a solution that may work better (if you have control over the underlying service) is to conditionally handle the PROXY protocol header, such that your service handles the case...
There should be a fix in the linked PR, could you test it and see if it works for your setup? It sets the ip_mode to Proxy when the proxy...