# Trying to get a message to the right team about a 8.6 release issue **URL:** \ **Category:** Get Help\ **Created:** [November 9, 2023, 3:58pm UTC](https://forum.ansible.com/t/trying-to-get-a-message-to-the-right-team-about-a-8-6-release-issue/2274 "2023-11-09T15:58:25Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![rit001](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/rit001/32/1483_2.png) [@rit001](https://forum.ansible.com/u/rit001)\ **Post date:** [November 9, 2023, 3:58pm UTC](https://forum.ansible.com/t/trying-to-get-a-message-to-the-right-team-about-a-8-6-release-issue/2274/1 "2023-11-09T15:58:25Z")
The problem is recorded here [https://github.com/ansible-collections/netapp.ontap/issues/190](https://github.com/ansible-collections/netapp.ontap/issues/190) The problem is that the reported issue is not within the above repo, instead an error seems to have found its way into the building of the ppa, which is a separate team/group/system over at [Ansible in Launchpad](https://launchpad.net/~ansible) I do not know the Ansible ecosystem well enough to know who to raise the issue with and it seems that each repo involved is only focused on its own role within the process rather than the overall process of delivering working packages to end users. Somehow the text 'git ’ has been added to the start of a php file which means that the file causes an error when processed with the result that Ansible 8.6 installs will fail. The issue is not who/what caused it, but who/what can resolve the issue. ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [November 9, 2023, 9:02pm UTC](https://forum.ansible.com/t/trying-to-get-a-message-to-the-right-team-about-a-8-6-release-issue/2274/2 "2023-11-09T21:02:43Z")
The issue was with the collection, it was published from a dirty checkout (that contained that `git` before the shebang). It got resolved in the meantime, and [Ansible 8.6.1](https://pypi.org/project/ansible/8.6.1/) got released with that fix included. In this forum, it’s best to ping [release-managers](http://forum.ansible.com/g/release-managers) (I’ve intentionally not added the `@` to avoid pinging them) in case of such problems, since they are responsible for releasing the `ansible` package (from which the PPA is built). Creating an issue in the [ansible-build-data GitHub repository](https://github.com/ansible-community/ansible-build-data/) also works. That’s the main repository for building and releasing Ansible. ---
**Author:** ![rit001](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/rit001/32/1483_2.png) [@rit001](https://forum.ansible.com/u/rit001)\ **Post date:** [November 10, 2023, 12:38am UTC](https://forum.ansible.com/t/trying-to-get-a-message-to-the-right-team-about-a-8-6-release-issue/2274/3 "2023-11-10T00:38:10Z")
Thanks for the reply and update, I was following threads across repos watching the fix as it progressed. Your last comment about using ansible-build-data is something that is not very clear from the overall project and all its repos. Maybe someone could make it clear in the readme file regarding what types of issues can be handled by raising issues there. ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [November 11, 2023, 9:54am UTC](https://forum.ansible.com/t/trying-to-get-a-message-to-the-right-team-about-a-8-6-release-issue/2274/4 "2023-11-11T09:54:57Z")
Thanks, that’s a very useful feedback. I created a PR to improve the repository’s README to hopefully explain this better: [README: clarify what the issue tracker covers by felixfontein · Pull Request #322 · ansible-community/ansible-build-data · GitHub](https://github.com/ansible-community/ansible-build-data/pull/322)