Issue #3 is about adding support for rpm-ostree; it has a different User-Agent product string, which we currently don't store anywhere. Since rpm-ostree's countme behavior is different from DNF's (and since people can run DNF on top of rpm-ostree systems) we're going to double-count systems unless we can tell which client is which.
product
This means changing CountmeItem, the database schemas, etc. Oh well, should have seen this coming.
CountmeItem
Discarded comment.
@siosm Is this resolved in the current rpm-ostree mechanism?
I'm afraid that's a part of the backend that I don't know about so I can not say.
No idea myself either.
I have two possible theories:
From an rpm-ostree perspective, libdnf based Count Me support is fully disabled by default since https://github.com/coreos/rpm-ostree/releases/tag/v2021.5 so we should not get double counting from that.
Thus I think this means that this should be OK now.
Log in to comment on this ticket.