On Mon, 2013-10-28 at 04:37 +0100, Jan Kratochvil wrote:
On Fri, 25 Oct 2013 01:07:15 +0200, Adam Williamson wrote:
generate the SRPM and do 'koji build --scratch fXX blah.src.rpm' , where
You would have to rpmbuild -bs *.spec first to get blash.src.rpm.
Yes. That's what 'generate the SRPM'
On Fri, 25 Oct 2013 01:07:15 +0200, Adam Williamson wrote:
generate the SRPM and do 'koji build --scratch fXX blah.src.rpm' , where
You would have to rpmbuild -bs *.spec first to get blash.src.rpm.
It is done all by: fedpkg build --scratch --srpm
The problem is that it uploads the whole
On Fri, Oct 25, 2013 at 2:07 AM, Adam Williamson awill...@redhat.com wrote:
The koji builders are usually faster than your system anyway
Maybe, if building only a specific arch (e.g. koji build
--arch-override=x86_64). The arm builders tend to be quite slow in the
first place, and I don't think
On Fri, 2013-10-25 at 11:24 +0300, Ville Skyttä wrote:
On Fri, Oct 25, 2013 at 2:07 AM, Adam Williamson awill...@redhat.com wrote:
The koji builders are usually faster than your system anyway
Maybe, if building only a specific arch (e.g. koji build
--arch-override=x86_64). The arm
On Thu, 2013-10-10 at 16:31 +0100, Richard W.M. Jones wrote:
You don't really need to use mock either. Just use 'rpmbuild -ba'
directly or 'fedpkg local' which is a wrapper.
You don't need to, but there are a few reasons it's superior:
1) Your local environment is almost certainly dirty in
On Thu, 2013-10-24 at 16:07 -0700, Adam Williamson wrote:
There's only a few times a scratch build isn't practical: if you're
doing a set of chained builds, you can't use scratch builds, as you
can't have one scratch build build against another scratch build. In
this case I use mock: copy the
Rich, Matthew, and Richard
Thanks for your guys' input. It's good to know that I can turn here,
when I have to and not have it seem that I'm asking a silly question. I
will try to keep everyone abreast of progress and once I'm ready for
review, I'll let you all know.
Thanks again.
M
--
devel
Hi Matt,
I believe this is the easiest way to setup your build host:
sudo yum group install Fedora Packager
sudo yum install fedora-review
I personally use rpmbuild and then mock before submitting the packages.
Best Regards,
Dridi
On Thu, Oct 10, 2013 at 4:31 PM, Richard W.M. Jones
On Wed, Oct 09, 2013 at 12:32:08PM -0700, Matt Eskes wrote:
It's taking a bit of time, but I plan to start packaging a couple of
packages that are not currently available for either Red Hat nor Fedora.
The main reason for it taking a bit longer really has to do with
personal
Hi folks.
It's taking a bit of time, but I plan to start packaging a couple of
packages that are not currently available for either Red Hat nor Fedora.
The main reason for it taking a bit longer really has to do with
personal infrastructure and setting up my build host, etc.
On Wed, Oct 09, 2013 at 12:32:08PM -0700, Matt Eskes wrote:
Will using mock in this environment be more beneficial to using
fakeroot? Will it be harder for lack of a better word, to build from
within the build system using fakeroot , once I get to that point or, is
Koji flexible enough
On Wed, Oct 9, 2013 at 2:32 PM, Matt Eskes mes...@gmail.com wrote:
As I am more familiar with fakeroot, I'd like to keep using that,
but
at the same time, I'd like to do it the Red Hat way to ensure that the
package conforms to both Red Hat and Fedora packaging standards.
Mock would
12 matches
Mail list logo
