You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running the server locally with a manually-created anitya.toml file including Adélie Linux worked completely fine, so I'm guessing the issue may be with Ansible somehow corrupting the file before it ends up in /etc/anitya/anitya.toml on the server. I've opened the issue here because it specifically affects Anitya and I can't prove it relates to Ansible.
The text was updated successfully, but these errors were encountered:
If you go to that "commit" in in the broweser, the server is providing the false header line content-type: text/plain; charset=ISO-8859-1 so the browser is displaying the file incorrectly. If you download the file and view it as UTF-8, it's correct.
I confirmed that Anitya handles UTF-8 fine when I tried it locally, which is why I think the file is being corrupted elsewhere.
An attempt was made to add a distro mapping for Adélie Linux in https://pagure.io/fedora-infra/ansible/pull-request/1349 that was reverted because it caused Anitya to fail. A subsequent attempt to add other distro mappings without the Adélie Linux entry succeeded (https://pagure.io/fedora-infra/ansible/pull-request/1352) so it is likely that the UTF-8 in the anitya.toml Ansible file was the source of the problem.
Running the server locally with a manually-created anitya.toml file including Adélie Linux worked completely fine, so I'm guessing the issue may be with Ansible somehow corrupting the file before it ends up in /etc/anitya/anitya.toml on the server. I've opened the issue here because it specifically affects Anitya and I can't prove it relates to Ansible.
The text was updated successfully, but these errors were encountered: