Getting debuginfo into a mock chroot?

[Tom Lane]

Jesse Keating <jkeating at redhat.com> writes:
> On Wed, 2009-04-08 at 15:32 -0400, Tom Lane wrote:
>> Ah-hah, the actual answer is you have to put the debuginfo repo into
>> /etc/yum.conf inside the chroot.  For some reason, marking it enabled
>> in the chroot's /etc/yum.repos.d/* does nothing.

> Once you've created the chroot and are making --install calls, yes it
> uses the yum setup in the chroot.  The yum conf in the chroot comes from
> the mock config file though.

Ah, so had I changed the mock config before populating the chroot, life
would have been good.  It makes sense now.

Now, if we could only have non-broken build tools in rawhide ...

DEBUG util.py:280:  Executing command: ['rpm', '-Uvh', '--nodeps', '/builddir/build/originals/mysql-5.1.33-1.fc11.src.rpm']
DEBUG util.py:256:  error: Unterminated {: {_%{_keyringpath}/*.k
DEBUG util.py:256:    0< /
DEBUG util.py:256:  error: /: reading of public key failed.
DEBUG util.py:256:  error: cannot open Packages index using db3 - No such file or directory (2)
DEBUG util.py:256:  error: Unterminated {: {_%{_dbpat)
DEBUG util.py:256:    0< /
DEBUG util.py:256:  error: cannot open Packages database in /
DEBUG util.py:256:  error: Unterminated {: {_%{_topdiY
DEBUG util.py:256:    0< /
DEBUG util.py:256:  mysql                       error: Unterminated {: {_%{_sourcedi
DEBUG util.py:256:    0< /
DEBUG util.py:256:  error: Unterminated {: {_%{_specdi
DEBUG util.py:256:    0< /
DEBUG util.py:256:  ##################################################
DEBUG util.py:256:  error: unpacking of archive failed on file /b/builddir/build/SOURCE/ffilter-requires-mysql.sh9;49dd089d: cpio: mkdir failed - Invalid argument
DEBUG util.py:256:  error: /builddir/build/originals/mysql-5.1.33-1.fc11.src.rpm cannot be installed
DEBUG util.py:319:  Child returncode was: 1

Think I'm going to take a break for awhile and let my blood pressure
drop.

			regards, tom lane