Re: Determining package set for build

[Dennis Gilmore]

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.

"Richard W.M. Jones" <rjones(a)redhat.com&gt; wrote:

> On Fri, Sep 21, 2012 at 08:21:29PM -0600, Orion Poplawski wrote:
> > I'm trying to track down a problem with scipy not building on F18
> > due to a test crashing.  However it builds fine in rawhide, and on
> > F18 using my local mock builder (which runs F17).  I'd like to
> > compare the package list for the buildroots for each build to look
> > for differences.  I can get this with a fair amount of difficulty
> > from root.log, but it seems like it would be nice if the output of
> > rpm -qa could be added to the mock logs and provided in koji.  Does
> > this seem reasonable?  Or perhaps another rpm -qa in root.log after
> > installing the buildrequires?  In the meantime, if anyone has any
> > root.log parsers to generate this, I'd be grateful.
>
> I guess the potential amount of information that could be logged by
> mock and would be useful to someone sometime is enormous!
>
> Can you run 'rpm -qa' in your package's %prep or %build section
> instead?
>
> Rich.
>
> -- 
> Richard Jones, Virtualization Group, Red Hat
> http://people.redhat.com/~rjones
> New in Fedora 11: Fedora Windows cross-compiler. Compile Windows
> programs, test, and build Windows installers. Over 70 libraries
> supprt'd
> http://fedoraproject.org/wiki/MinGW http://www.annexia.org/fedora_mingw
> -- 
> devel mailing list
> devel(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel 
-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.