3. Include just the tarball and fix the build so that it doesn't try to
download the source rpm. I haven't taken a look at that part of the code yet
and given this week's schedule can't do anything until next week.
Dan W.
On Tue, Jul 19, 2005 at 03:39:29PM -0500, Brian Elliott Finley wrote:
> S
So are you saying we should:
1. Include both the source rpm and the tarball
2. Just the source rpm, but have the rpm package as a build dep?
Daniel Widyono wrote:
>I'd agree with including the tarball at first glance. This download of the
>src.rpm is annoying and seems buggy (and especia
I'd agree with including the tarball at first glance. This download of the
src.rpm is annoying and seems buggy (and especially annoying that after
build, the src.rpm has been deleted so I can't just copy it over to /usr/src
to prevent a re-download). Had to find it manually to download it (and
ac
I forgot to mention that this is RHEL4 on x86_64...
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Bernard Li
> Sent: Tuesday, July 12, 2005 15:03
> To: sisuite-devel@lists.sourceforge.net
> Subject: [Sisuite-devel] r3
Hey guys:
Just reporting in that r3178 compiled fine under RHEL4 after applying
the following outstanding patches:
- systemimager.spec
- linux.x86_64.config
Brian, is there a way to prevent rpm-4.2-1.src.rpm from being d/led if
rpm-4.2.tar.gz is present in the tarball? This is what I was trying
