On Fri, 19 Jan 2024, 12:57 Ana Guerrero Lopez via openSUSE Factory, < factory@lists.opensuse.org> wrote:
Dear Tumbleweed hackers and packagers,
After a lengthy staging period, RPM 4.19 is shaping up and all issues noticed in the rings (packages guaranteed to build/be installable) have been addressed or have fixes pending.
As you are all aware, the rings cover only about 20% of the packages in Factory.
* Any non-root ownership in the %files section (through %attr() or %defattr()) now generates an automatic dependency on the named user and/or group. This dependency can be satisfied by another package shipping a sysusers.d(5) file
It doesn't have to be another package, it can be the same one. Another package is only needed if another package needs the same user/group aswell then it'll need to be seperated to prevent duplication which would cause duplicate provides which would upset RPM.
The story around the users can be trickier to be identified, as the build might succeed, but the package not being installable at the end due to missing dependencies reported. This usually happens when users are generated in %pre scripts using useradd. Either convert those packages to use sysusers.d ( https://en.opensuse.org/openSUSE:Packaging_guidelines#Users_and_Groups) or, as a quickest measure, usually helpful if no other package relies on the same users, manually add the respective Provides: user(USERNAME) and Provides: group(GROUPNAME) to the package generating the relevant user (as done for example in cluster-glue, https://build.opensuse.org/request/show/1138101 for reference)
Ideally, migrate it to sysusers.d, the process is listed at the page Ana pointed to above which I've attempted to make as clear as possible
If you have any questions or need with your package, the opensuse-packaging mailing list is always at your disposal.
Yep, any help needed with migration I'll be available to help, post to openSUSE Packaging (packaging@lists.opensuse.org) and I'll see it unless someone else manages to help before I get to it if I'm busy. Callum F
Ana,
on behalf of the Release Team