| Summary: | sys-apps/slocate-2.7-r8 requires impossible group rename | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Timothy Stotts <devel> |
| Component: | New packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | VERIFIED FIXED | ||
| Severity: | minor | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Yeah, so rename it... I have software that *requires* the presence of both groups. Perhaps this ebuild should be modified to permit this case? Thank you for your thoughtful consideration. sounds reasonable ... should be fixed in cvs now, thanks for being anal ! http://sources.gentoo.org/sys-apps/slocate/slocate-2.7-r8.ebuild?r1=1.15&r2=1.16 http://sources.gentoo.org/sys-apps/slocate/slocate-3.1-r1.ebuild?r1=1.2&r2=1.3 thank you too. works great. |
If the group 'slocate' exists on the current system, emerge sys-apps/slocate-2.7-r8 dies with a message to rename the group 'slocate' to 'locate'. Reproducible: Always Steps to Reproduce: The system in question is a client on an "NIS" network with a heterogeneous cluster of systems. The groups 'slocate' and 'locate' are needed to both exist due to the needs of other systems. Actual Results: The ebuild fails to emerge due to both groups existing. Expected Results: Please modify pkg_setup() of this ebuild to have an option to install without strict group checking. Thanks! Example: # just use 'locate' group and ignore presence of 'slocate' group NO_GROUP_CHECK='1' emerge slocate