sysusers.d and F42 #1489

Open
opened 2025-09-22 01:30:45 +00:00 by tibbs · 1 comment
Owner

https://docs.fedoraproject.org/en-US/packaging-guidelines/UsersAndGroups/#_creation_of_users_and_groups_with_scriptlets says that F42 and later fully support sysusers.d, and that the various backwards-compatibility macros will evaluate empty there. But I think that's incorrect, and it's actually F43 where this is the case.

Am I just confused about when this was supposed to be supported? Either the guidelines are wrong or somehow the macros weren't updated to null out the definitions on F42.

Also, I wonder if there's any solution for packages where the sysusers file can't live in a SOURCE file (because, perhaps, the user names are defined in macros). Besides the obvious solution of just not sharing the same spec across multiple branches, of course.

Makes the weird extreme rush to get everything patched to do this even stranger.

https://docs.fedoraproject.org/en-US/packaging-guidelines/UsersAndGroups/#_creation_of_users_and_groups_with_scriptlets says that F42 and later fully support sysusers.d, and that the various backwards-compatibility macros will evaluate empty there. But I think that's incorrect, and it's actually F43 where this is the case. Am I just confused about when this was supposed to be supported? Either the guidelines are wrong or somehow the macros weren't updated to null out the definitions on F42. Also, I wonder if there's any solution for packages where the sysusers file can't live in a SOURCE file (because, perhaps, the user names are defined in macros). Besides the obvious solution of just not sharing the same spec across multiple branches, of course. Makes the weird extreme rush to get everything patched to do this even stranger.
Owner

Metadata Update from @james:

  • Issue priority set to: In Committee (was: Needs Review)
  • Issue tagged with: meeting
**Metadata Update from @james**: - Issue priority set to: In Committee (was: Needs Review) - Issue tagged with: meeting
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
packaging/guidelines#1489
No description provided.