You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As already reported by users on our Telegram channel, trying to update openSUSEway fails since a few Tumbleweed snapshots with the errors:
Problem: nothing provides 'group(greeter)' needed by the to be installed openSUSEway-0.16.0-1.2.noarch
Problem: nothing provides 'group(greeter)' needed by the to be installed greetd-0.9.0-1.6.x86:64
This is caused by new rpm features introduced in 4.19.0. A warning was posted on the openSUSE Factory mailing list, but I had missed it.
Here is the description of the issue and the suggested fixes:
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 or the /etc/passwd and /etc/group files themselves.
Existing packages shipping any of these files will have to be rebuilt with
RPM 4.19 in order for them to carry the respective user and/or group
provides. This may require distro-level coordination to ensure proper
installation of all the affected packages. For more information, please
consult the manual.
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)
I am planning to look into the first solution (using sysusers.d).
The text was updated successfully, but these errors were encountered:
As already reported by users on our Telegram channel, trying to update openSUSEway fails since a few Tumbleweed snapshots with the errors:
This is caused by new
rpm
features introduced in 4.19.0. A warning was posted on the openSUSE Factory mailing list, but I had missed it.Here is the description of the issue and the suggested fixes:
I am planning to look into the first solution (using sysusers.d).
The text was updated successfully, but these errors were encountered: