Re: Determining package set for build

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxx> 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.

--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux