Bug 81364 - rpmbuild can't see LDAP user
Summary: rpmbuild can't see LDAP user
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: openldap
Version: 1.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jay Fenlason
QA Contact: Jay Turner
Depends On:
Blocks: 79579 CambridgeTarget
TreeView+ depends on / blocked
Reported: 2003-01-08 15:43 UTC by Jonathan Kamens
Modified: 2015-01-08 00:02 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-09-03 07:37:06 UTC

Attachments (Terms of Use)

Description Jonathan Kamens 2003-01-08 15:43:43 UTC
After upgrading to the current Raw Hide (as of yesterday) and attempting to
build from a spec file using rpmbuild, it complained "bad user/group" on one of
the source files listed in the spec file.  The user in question is listed in
LDAP but not in the local passwd file.  After adding the user to the local
passwd file, the problem went away.  jbj said I should report this under the
openldap component rather than under rpm because "rpm doesn't know anything
about LDAP" or some such thing.  I suppose it could also be a glibc bug.

Comment 1 Bill Nottingham 2006-08-08 02:03:53 UTC
'Red Hat Raw Hide' refers to the development tree for Red Hat Linux.
Red Hat Linux is no longer supported by Red Hat, Inc. If you are still
running Red Hat Linux, you are strongly advised to upgrade to a
current Fedora Core release or Red Hat Enterprise Linux or comparable.
Some information on which option may be right for you is available at

Red Hat apologizes that these issues were not resolved in a more
timely manner. However, we do want to make sure that important 
don't slip through the cracks. If these issues are still present
in a current release, such as Fedora Core 5, please move these
bugs to that product and version. Note that any remaining Red Hat
Raw Hide bugs will be closed as 'CANTFIX' on September 30, 2006.
Thanks again for your help.

Comment 2 Jonathan Kamens 2006-09-03 07:37:06 UTC
I no longer have any way of testing for this bug, and I suspect that nobody else
cares about it, so closing it.

Note You need to log in before you can comment on or make changes to this bug.