Description of problem: The docs for countme don't say whether it's enough to set 'countme=0' in the global config to disable, or whether the user needs to set 'countme=0' in each and every repo file. In general, how is a user that wants to opt-out to go about this? Expected results: https://fedoraproject.org/wiki/Changes/DNF_Better_Counting says that it's possible to opt out, but it's not clear how to do that.
It is just another option and this documented behavior applies to it: > OPTIONS FOR BOTH [MAIN] AND REPO > Some options can be applied in either the main section, per repository, > or in a combination. The value provided in the main section is used for > all repositories as the default value, which repositories can then > override in their configuration. Opt-out is possible by changing the individual .repo files. There's no global option to turn it all off at once.
Makes sense, thanks.
I need to document how to opt out (I'm writing some end-user docs). I tried 'dnf config-manager --setopt={fedora,updates,rawhide,…}.countme=0 --save', but that is fragile because the repo list needs to match exactly. The best I could come up with: sudo sed -r -i s/countme=0/countme=1/ /etc/yum.repos.d/*repo Any better ideas?
I now realized that needs to be done after every update of fedora-repos and fedora-workstation-repositories and whatever other packages. That's a very bad UX. https://fedoraproject.org/wiki/Changes/DNF_Better_Counting#User_Experience said: > Users who wish to opt out of counting will have an easy way to do so. Personally, I don't have anything against counting, or even more popcon-style statistics. But some people do, and since we promised an opt-out mechanism, I would be nice to provide one. We should at least discuss this. @mattdm, comments?
Slightly better might be `dnf config-manager --setopt='*.countme=0' --save`. But it still is kind of fragile - once you add a new repo, you need to repeat the step.
We'll look into implementing global (repo) configuration overrides.
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle. Changing version to 38.
I can confirm this is enabled by default in Fedora 39. I'd love an Anaconda kickstart setting to disable it.
This message is a reminder that Fedora Linux 38 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '38'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 38 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.