Re: Can pungi put packages in the iso that are not installed?
On Tue, Dec 23, 2008 at 2:53 PM, Yaakov Nemoy loupgaroubl...@gmail.com wrote: Would this require a second ks file that omits the package name, for the automated install, so that it will be on the media, but not actually installed by default? The ks file that you compose from and the one that you install from aren't the same thing. Not sure what the question is. -- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
Re: Assembling packages for ISO's
On Wed, Sep 10, 2008 at 7:33 AM, Bryce [EMAIL PROTECTED] wrote:
mkdir pool; cd pool
TAG=f9-bryced
koji list-pkgs --tag=${TAG} --quiet | cut -f 1 -d | xargs koji latest-pkg
${TAG} --quiet | cut -f1 -d | xargs -n1 koji download-build --arch=i386
--arch=i686 --arch=noarch
Maybe not succinct, but have you looked into mash (what Fedora uses to
pull packages and make repos)?
git clone git://git.fedorahosted.org/mash
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
Re: corrupt rpmdb in mock-chroot
On Sat, May 31, 2008 at 7:04 PM, Paul B Schroeder [EMAIL PROTECTED] wrote: Rebuilding the rpm database seems to fix this, but it's a pain to be sure. Any ideas as to why I'm seeing this corruption when creating an i386 mock chroot from a x86_64 system? This is normal and expected. You created the rpmdb with x86_64 rpm, and are accessing it with i386 rpm. The Berkeley DB format is different based on the arch of the creating machine, therefore generates the database differently on the two platforms. If I plan on doing anything in a chroot (especially a non-native arch one) other than building a SRPM, the first thing that happens is to rm -f /var/lib/rpm/__db*. Don't worry, this got me the first time too (and is fatal to a pungi compose) :) -- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
