Bug 1158

Summary: shadow RPM reports failed dependencies for utilities it ships with
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Scott Garman <scott.a.garman>
Component: coreAssignee: Edwin Zhai <edwin.zhai>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: meta.mr.watcher, meta.watcher, sgw, shane.wang
Version: unspecified   
Target Milestone: 1.1   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Scott Garman 2011-06-10 15:05:52 UTC
When copying the shadow RPM to a sato image and trying to install it fails:

root@qemux86:~# rpm -ivh shadow-4.1.4.3-r2.qemux86.rpm 
error: Failed dependencies:
	/sbin/vipw is needed by shadow-4.1.4.3-r2.qemux86
	/usr/bin/newgrp is needed by shadow-4.1.4.3-r2.qemux86

However vipw and newgrp are both shipped in the shadow RPM. 

A temporary workaround is to use --nodeps when installing with rpm.

Note: when update-alternatives is run, it's output appears to show an extra '/' for each binary it links:

update-alternatives: Linking //usr/bin/newgrp to newgrp.shadow

Mentioning this as a possible hint to the source of the problem (not sure).
Comment 1 Edwin Zhai 2011-08-31 18:18:21 UTC
There are some links become invalid after rename, so that failed dependencies     detected when install rpm package.

E.g. /usr/bin/vigr -> /usr/bin/vipw, after renaming vipw to vipw.shadow, vigr become invalid link. When install rpm, missing of vipw is detected and reported as an error.

Got fixed in poky master @ 7a27253f56f4dd14a4fff56d46083009ae9cb421