# Unmaintained collection: community.sap\_libs **URL:** \ **Category:** Project Discussions\ **Tags:** community-wg, collections\ **Created:** [September 16, 2025, 6:06pm UTC](https://forum.ansible.com/t/unmaintained-collection-community-sap-libs/44501 "2025-09-16T18:06:23Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [September 16, 2025, 6:06pm UTC](https://forum.ansible.com/t/unmaintained-collection-community-sap-libs/44501/1 "2025-09-16T18:06:23Z")
The [community.sap\_libs](https://github.com/sap-linuxlab/community.sap_libs) collection looks unmaintained / abandoned, it has: - no new commits since [Apr 29, 2024](https://github.com/sap-linuxlab/community.sap_libs/pull/42) - no new release since [Jan 23, 2024](https://github.com/sap-linuxlab/community.sap_libs/releases/tag/1.4.2) - no CI run since [Jan 1, 2025](https://github.com/sap-linuxlab/community.sap_libs/actions/runs/12567972135) - CI doesn’t test with ansible-core \> 2.17 On the other hand, there has been a reaction on [Validate compatibility with ansible-core 2.19](https://github.com/sap-linuxlab/community.sap_libs/issues/52). But considering everything, this collection doesn’t look healthy or really alive to me. ---
**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:** [September 17, 2025, 5:24am UTC](https://forum.ansible.com/t/unmaintained-collection-community-sap-libs/44501/2 "2025-09-17T05:24:22Z")
There’s also [GitHub · Where software is built](https://github.com/sap-linuxlab/community.sap_libs/issues/46:) 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](https://github.com/SAP-archive/PyRFC?tab=readme-ov-file#deprecation-notice)). 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](https://github.com/marcelmamula) is on the forum as well.) ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [September 20, 2025, 2:06pm UTC](https://forum.ansible.com/t/unmaintained-collection-community-sap-libs/44501/3 "2025-09-20T14:06:22Z")
Additionally, they don’t test with ansible-core 2.19. This is a violation of our [requirements](https://docs.ansible.com/ansible/latest/community/collection_contributors/collection_requirements.html#ci-testing). I’ve opened a [PR](https://github.com/sap-linuxlab/community.sap_libs/pull/54) about this. ---
**Author:** ![marcelmamula](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/marcelmamula/32/9471_2.png) [@marcelmamula](https://forum.ansible.com/u/marcelmamula)\ **Post date:** [September 22, 2025, 1:19pm UTC](https://forum.ansible.com/t/unmaintained-collection-community-sap-libs/44501/4 "2025-09-22T13:19:45Z")
@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? > > > \# WIP > > \## Changes > TODO ---
**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:** [September 22, 2025, 4:31pm UTC](https://forum.ansible.com/t/unmaintained-collection-community-sap-libs/44501/5 "2025-09-22T16:31:31Z")
Thanks for improving the collection! > [@marcelmamula](#): > > 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. Why doesn’t it make sense? Ansible-core 2.19 supports Python 3.8 on targets. ---
**Author:** ![marcelmamula](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/marcelmamula/32/9471_2.png) [@marcelmamula](https://forum.ansible.com/u/marcelmamula)\ **Post date:** [September 25, 2025, 12:41pm UTC](https://forum.ansible.com/t/unmaintained-collection-community-sap-libs/44501/6 "2025-09-25T12:41:24Z")
@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. > **[Ansible Galaxy](https://galaxy.ansible.com/ui/repo/published/community/sap_libs/?version=1.5.0)** > **[Release 1.5.0 · sap-linuxlab/community.sap\_libs](https://github.com/sap-linuxlab/community.sap_libs/releases/tag/1.5.0)** > > Release Summary > This release removes Python 2 support and updates ansible-test workflow to validate latest versions. > Documentation was updated to reflect supported and tested versions. > Minor Change... FYI I have reworked CI to add more combinations and non-EOL vs EOL split to give us more information. ---
**Author:** ![marcelmamula](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/marcelmamula/32/9471_2.png) [@marcelmamula](https://forum.ansible.com/u/marcelmamula)\ **Post date:** [October 16, 2025, 7:03am UTC](https://forum.ansible.com/t/unmaintained-collection-community-sap-libs/44501/7 "2025-10-16T07:03:06Z")
@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? ---
**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:** [October 16, 2025, 7:56am UTC](https://forum.ansible.com/t/unmaintained-collection-community-sap-libs/44501/8 "2025-10-16T07:56:35Z")
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). > [@marcelmamula](#): > > 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? 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… ---
**Author:** ![marcelmamula](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/marcelmamula/32/9471_2.png) [@marcelmamula](https://forum.ansible.com/u/marcelmamula)\ **Post date:** [October 16, 2025, 8:10am UTC](https://forum.ansible.com/t/unmaintained-collection-community-sap-libs/44501/9 "2025-10-16T08:10:30Z")
@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? ---
**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:** [October 16, 2025, 1:08pm UTC](https://forum.ansible.com/t/unmaintained-collection-community-sap-libs/44501/10 "2025-10-16T13:08:25Z")
> [@marcelmamula](#): > > `` > > 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. ---
**Author:** ![marcelmamula](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/marcelmamula/32/9471_2.png) [@marcelmamula](https://forum.ansible.com/u/marcelmamula)\ **Post date:** [October 16, 2025, 1:19pm UTC](https://forum.ansible.com/t/unmaintained-collection-community-sap-libs/44501/11 "2025-10-16T13:19:45Z")
Thank you @felixfontein . I have raised [Create dedicated license test for missing-gplv3-license instead of validate-modules · Issue #86015 · ansible/ansible · GitHub](https://github.com/ansible/ansible/issues/86015) to get some feels on what is their opinion because this would be simplest solution. ---
**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:** [October 16, 2025, 1:46pm UTC](https://forum.ansible.com/t/unmaintained-collection-community-sap-libs/44501/12 "2025-10-16T13:46:47Z")
See [ansible-test sanity expects all modules to be licensed under the GPLv3 · Issue #67032 · ansible/ansible · GitHub](https://github.com/ansible/ansible/issues/67032), 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](https://forum.ansible.com/t/error-invalid-extension-official-ansible-modules-must-have/5719/4). ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [October 16, 2025, 4:13pm UTC](https://forum.ansible.com/t/unmaintained-collection-community-sap-libs/44501/13 "2025-10-16T16:13:39Z")
Sorry for not replying earlier, I’ve somehow overlooked it. > [@marcelmamula](#): > > @felixfontein @mariolenz I have not seen response so can I take it that this activity is closed without action on your side? I’ve already checked this in [Possibly unmaintained collections in Ansible 12](https://forum.ansible.com/t/44451). Sorry, I didn’t mention this explicitly here or on Bullhorn. > [@marcelmamula](#): > > Thank you for your patience and let me know if you need more from us to cancel your abandonment process. 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](https://github.com/sap-linuxlab/community.sap_libs/issues/55).