The community.sap_libs collection looks unmaintained / abandoned, it has:
On the other hand, there has been a reaction on Validate compatibility with ansible-core 2.19.
But considering everything, this collection doesn’t look healthy or really alive to me.
There’s also GitHub · Where software is built it looks like pyrfc, one of its requirements, is no longer maintained (GitHub - SAP-archive/PyRFC: Asynchronous, non-blocking SAP NW RFC SDK bindings for Python). That only affects slightly over half of the modules though, everything else might be unaffected.
@rainer pinging you since you’ve been involved with the collection. (I’m not sure whether marcelmamula (Marcel Mamula) · GitHub is on the forum as well.)
Additionally, they don’t test with ansible-core 2.19. This is a violation of our requirements.
I’ve opened a PR about this.
@mariolenz @felixfontein I just signed up here.
I have merged all open PRs and closed those not applicable. Also did some cleanup with dev/main branches with mergeback.
CI action is now enabled and I am working on fixing errors. Sanity tests are fixed but I am having issue resolving units tests because ansible-community/ansible-test-gh-action@release/v1 loads all pythons for given ansible-core version, which does not make sense to load 3.8 for 2.19.
Is there parameter to force specific version like for Integration tests with target-python-version?
Thanks for improving the collection!
Why doesn’t it make sense? Ansible-core 2.19 supports Python 3.8 on targets.
@felixfontein @mariolenz Release 1.5.0 was completed now. Thank you for your patience and let me know if you need more from us to cancel your abandonment process.
FYI I have reworked CI to add more combinations and non-EOL vs EOL split to give us more information.
@felixfontein @mariolenz I have not seen response so can I take it that this activity is closed without action on your side?
Also devel just added 2.21 which i failing because ignore file is missing. Do you have some future proof solution so I dont have to add new versioned file every time devel is updated?
Sorry for not replying earlier, the last weeks were pretty busy 
I think everything’s fine now, and there’s nothing to do here (I’m not sure if there’s a way to properly “close” this thread).
I think the only future-proof solution is to make sure that the ignore file is empty, which unfortunately isn’t easy in many cases… I wish it would be easier to configure ansible-test, but it’s still totally unclear what will happen to ansible-test from the community side. Maybe someone at RH knows more…
@felixfontein
This collection and few others that I maintain contain python modules/plugins which are under our Apache 2 license, but forced GPL3 requirement is forcing us to use ignore files.
validate-modules:missing-gplv3-license # Licensed under Apache 2.0
Why is there no flag to ignore this check in ansible-community/ansible-test-gh-action to avoid this?
That’s what I meant with “I wish it would be easier to configure ansible-test, but it’s still totally unclear what will happen to ansible-test from the community side. Maybe someone at RH knows more…”. I’ve heard many times that “soon the situation with ansible-test will get better”, but over the years, nothing happened.
Thank you @felixfontein . I have raised Create dedicated license test for missing-gplv3-license instead of validate-modules · Issue #86015 · ansible/ansible · GitHub to get some feels on what is their opinion because this would be simplest solution.
See ansible-test sanity expects all modules to be licensed under the GPLv3 · Issue #67032 · ansible/ansible · GitHub, which your issue is a duplicate of. But maybe you’ll get a more helpful answer… And then there’s ERROR: invalid-extension: Official Ansible modules must have - #4 by sivel.
Sorry for not replying earlier, I’ve somehow overlooked it.
I’ve already checked this in Possibly unmaintained collections in Ansible 12. Sorry, I didn’t mention this explicitly here or on Bullhorn.
I don’t think so. For me, the removal process stopped when you did a new release. That’s why I’ve checked the collection in my list (see above) and closed Unmaintained collection: Removal from the Ansible Community Package.