![](https://seccdn.libravatar.org/avatar/77c4eb3d8ae9cd743ffd1d5872665418.jpg?s=120&d=mm&r=g)
Hi Sebastian, On 25.04.22 at 21:49 Sebix wrote:
On 4/25/22 9:12 PM, Johannes Kastl wrote:
2. Where to submit the packages to? Would it make sense to move all things related to ansible to a subproject of systemsmanagement? I guess the python-* dependencies could go to dlp* somewhere (not sure what the current layout is for python things, lost track ...) and could be maintained there.
My understanding of dlp is, that it was meant for packages related to developing python and is not a haven for all python-related stuff which is not placed elsewhere. But if the packages about are actually ansible (python-ansible-* and python-antsibull*), that does not prevent them from being maintained in systemsmanagement along with the other ansible-related packages. Otherwise we have split responsibilities and also troubles when coordinated updates of these packages are needed.
python-Twiggy, python-perky and python-asyncio-pool look generic and I'd place them in dlp, too.
I think that is a good summary, so unless someone objects I would to that once we are done.
CentOS & derivatives have ansible in official repos, so I wouldn't bother. Leap 15.4 could be interesting, but not as top priority.
I will take a look if I can get it building for Leap 15.4 and SLES15.4 without too much effort, as I will need it on those anyway. But that would be something for a second step, after getting it into Factory.
P.S.: I've already sent you a request with some fixes on the python packages.
Thank you very much, I also saw that Ben sent a SR. I'll check them tomorrow. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537