On Wed, 2010-08-04 at 18:29 +0100, Paul Howarth wrote:
> > That's a neat trick, since 1.1.1 didn't even have configs for Fedora
> > 14.
>
> I roll all of my own mock configs, with different names from the bundled
> ones so they don't disappear when a new mock version comes around.
>
> > They wer
On Wed, 04 Aug 2010 09:47:43 -0700
Adam Williamson wrote:
> On Wed, 2010-08-04 at 17:31 +0100, Paul Howarth wrote:
> > On 04/08/10 17:28, Adam Williamson wrote:
> > > On Tue, 2010-08-03 at 15:06 +0100, David Woodhouse wrote:
> > >> I have a modified package locally and want to install and test
>
On Wed, 2010-08-04 at 17:31 +0100, Paul Howarth wrote:
> On 04/08/10 17:28, Adam Williamson wrote:
> > On Tue, 2010-08-03 at 15:06 +0100, 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
On 04/08/10 17:28, Adam Williamson wrote:
> On Tue, 2010-08-03 at 15:06 +0100, 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?
>
> Is there a reason not to use mock locally?
I mi
On Tue, 2010-08-03 at 15:06 +0100, 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?
Is there a reason not to use mock locally? That's how I'd do it - just
'fedpkg srpm' then 'mock -
On Tue, 2010-08-03 at 15:06 +0100, David Woodhouse wrote:
> $ 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=/us
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
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
...
+ ./conf
