<html><head/><body><html><head></head><body>You are not guaranteed that the rpm making the chroot uses a compatible db4 with what's inside the chroot. so you can not run rpm in the chroot. It may or may not work and is not supported.<br><br><div class="gmail_quote">"Richard W.M. Jones" <rjones@redhat.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre style="white-space: pre-wrap; word-wrap:break-word; font-family: sans-serif; margin-top: 0px">On Fri, Sep 21, 2012 at 08:21:29PM -0600, Orion Poplawski wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">I'm trying to track down a problem with scipy not building on F18<br />due to a test crashing. However it builds fine in rawhide, and on<br />F18 using my local mock builder (which runs F17). I'd like to<br />compare the package list for the buildroots for each build to look<br />for differences. I can get this with a fair amount of difficulty<br />from root.log, but it seems like it would be nice if the output of<br />rpm -qa could be added to the mock logs and provided in koji. Does<br />this seem reasonable? Or perhaps another rpm -qa in root.log after<br />installing the buildrequires? In the meantime, if anyone has any<br />root.log parsers to generate this, I'd be grateful.</blockqu
ote><br
/>I guess the potential amount of information that could be logged by<br />mock and would be useful to someone sometime is enormous!<br /><br />Can you run 'rpm -qa' in your package's %prep or %build section<br />instead?<br /><br />Rich.<br /></pre></blockquote></div><br>
-- <br>
Sent from my Android phone with K-9 Mail. Please excuse my brevity.</body></html></body></html>