local / scratch builds with fedpkg

[Paul Howarth]

On 03/08/10 15:06, David Woodhouse wrote:
> I have a modified package locally and want to install and test it. Since
> it's a biarch package, I need to build the i686 version too. How?
>
> A local build no longer seems to work for anything but the primary arch,
> because it still configures for x86_64:
>
> $ i386 fedpkg local --arch=i686
>   ...
> + ./configure --build=x86_64-unknown-linux-gnu
> --host=x86_64-unknown-linux-gnu --program-prefix=
> --disable-dependency-tracking --prefix=/usr --exec-prefix=/usr
> --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc
> --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib
> --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib
> --mandir=/usr/share/man --infodir=/usr/share/info --disable-gtk-doc
> --enable-static --with-runtime-libdir=../../lib
>
> And scratch-build doesn't seem to work either. It won't let me build
> unless I push.... but I thought the whole point of a scratch build was
> to test stuff I'm not yet *ready* to push (and I'm not even the
> maintainer of this package).
>
> $ fedpkg scratch-build
> Traceback (most recent call last):
>    File "/usr/bin/fedpkg", line 959, in<module>
>      args.command(args)
>    File "/usr/bin/fedpkg", line 573, in scratchbuild
>      build(args)
>    File "/usr/bin/fedpkg", line 319, in build
>      url, chain)
>    File "/usr/lib/python2.6/site-packages/pyfedpkg/__init__.py", line
> 797, in build
>      raise FedpkgError('There are unpushed changes in your repo')
> pyfedpkg.FedpkgError: There are unpushed changes in your repo

The scratch-build Make target used to work with committed and tagged 
files in CVS. Unpushed changes could be tested using "make 
srpm-scratch-build" but fedpkg doesn't have an srpm-scratch-build yet 
(hint, hint).

For the moment I've been doing "fedpkg srpm" and running koji scratch 
builds manually with the resulting SRPM.

Paul.