Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#30436 - [unbound] unbound user not created, please allocate uid/gid pair

Attached to Project: Community Packages
Opened by Geert Hendrickx (ghen) - Monday, 25 June 2012, 10:33 GMT
Last edited by Gaetan Bisson (vesath) - Friday, 29 June 2012, 13:16 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The [community] unbound package ships a simple default config that makes it run as unprivileged user "unbound" (good), but the user/group are not created by the package (bad). I assigned a uid/gid locally but that gid has now been claimed by another package. Can you please allocate a uid/gid pair in https://wiki.archlinux.org/index.php/UID_and_GID_List (I suggest 35:35) and create the user/group accordingly in the PKGBUILD?

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Gaetan Bisson (vesath)
Friday, 29 June 2012, 13:16 GMT
Reason for closing:  Works for me
Comment by Gaetan Bisson (vesath) - Tuesday, 26 June 2012, 20:48 GMT
The unbound user and group *are* created by the package, more specifically by its post_install scriptlet.
They don't have a reserved UID/GID, but I don't see why this would be a problem.
Comment by Geert Hendrickx (ghen) - Tuesday, 26 June 2012, 21:31 GMT
Sorry, I missed that. However it's better to reserve an uid/gid pair (as for most other packages), to avoid collisions later.

I had 54:54 and it clashed with the recent filesystem package upgrade (that creates the "lock" group with gid 54).
Comment by Gaetan Bisson (vesath) - Tuesday, 26 June 2012, 22:11 GMT
There can be no collisions since the statically and dynamically allocated UID range are distinct; read about SYS_UID_MIN and SYS_UID_MAX in the useradd manpage.
In particular, since SYS_UID_MIN=500, the unbound user created by this package cannot have UID 54, which makes me thing that you did something fishy to your system and makes me want to close this bug down.

Loading...