[lug] source rpm dependencies

John Hernandez John.Hernandez at noaa.gov
Thu Mar 15 14:28:42 MST 2001

Can you get around this by doing it in two steps?

rpm --recompile --nodeps

rpm -bb --nodeps

"D. Stimits" wrote:
> I'm having problems on occasion with source rpm rebuilds. What happens
> is that for one reason or another, rpm mistakenly believes some other
> dependency is not met (it is usually wrong, most recently thinking I
> didn't have "sh", but I have "bash"). Now I can add a --nodeps, but
> apparently depencies are checked twice; once for the rebuild itself, and
> then again for the completed binary rpm. So when it gets to the part
> where it is supposed to build the binary rpm, it no longer knows it was
> given --nodeps, and refuses to build it. I *really* want to tell it to
> build that binary rpm no matter what it thinks it will depend on.
> Although it is going on to my system, I can see that it would be useful
> to create rpm's for other people on other systems, and it just irritates
> me that I *must* not build a binary that has missing dependencies on my
> local system. Does anyone here know a way to make it at least attempt to
> build the binary rpm even if the resulting binary would lack
> dependencies on the local machine? At the risk of repeating myself,
> --nodeps will not do the job, it gets lost before the binary compile is
> attempted. I see this as a logic bug in the rpm tool.
> D. Stimits, stimits at idcomm.com
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug

More information about the LUG mailing list