I guess you are using external-repos, right ?
Are your external repos configured rightly ?
Or, the external repo was updated and koji still has the old versions and
links of the rpms from there.
Try regen the repo ( koji regen-repo <build-tag>).
Rodrigo
From:
Doug Reiland <dreiland(a)gmail.com>
To:
Discussion of Fedora build system <buildsys(a)lists.fedoraproject.org>
Date:
23/02/2010 13:49
Subject:
Re: workflow help
Sent by:
buildsys-bounces(a)lists.fedoraproject.org
It was a problem with the yum groupinstall build not doing anything.
I deleted all my dist-f12 stuff and removed the external repos,, and
redid.
I resubmitted the job after a regen-repo and package is now building.
Cool!!
On Tue, Feb 23, 2010 at 9:25 AM, Doug Reiland <dreiland(a)gmail.com> wrote:
OK, I am trying this again.
It looks like the process is:
koji add-pkg --owner <some_owner> dist-f12 zsh
koji build dist-f12 zsh*.src.rpm
I got this working at home.
However, at work. I am having mock issues. It doesn't look like any
build group packages get installed:
redhat-rpm-config-9.0.3-18.fc12.noarch from build has depsolving
problems
DEBUG util.py:256: --> Missing Dependency: /bin/bash is needed
by
package redhat-rpm-config-9.0.3-18.fc12.noarch (build)
DEBUG util.py:256: redhat-rpm-config-9.0.3-18.fc12.noarch from build
has depsolving problems
DEBUG util.py:256: --> Missing Dependency: /usr/bin/perl is needed
by package redhat-rpm-config-9.0.3-18.fc12.noarch (build)
DEBUG util.py:256: redhat-rpm-config-9.0.3-18.fc12.noarch from build
has depsolving problems
DEBUG util.py:256: --> Missing Dependency: /bin/sh is needed by
package redhat-rpm-config-9.0.3-18.fc12.noarch (build)
DEBUG util.py:256: redhat-rpm-config-9.0.3-18.fc12.noarch from build
has depsolving problems
DEBUG util.py:256: --> Missing Dependency: mktemp is needed by
package redhat-rpm-config-9.0.3-18.fc12.noarch (build)
DEBUG util.py:256: redhat-rpm-config-9.0.3-18.fc12.noarch from build
has depsolving problems
DEBUG util.py:256: --> Missing Dependency: perl(Getopt::Long) is
needed by package redhat-rpm-config-9.0.3-18.fc12.noarch (build)
DEBUG util.py:256: Error: Missing Dependency: /bin/bash is needed by
package redhat-rpm-config-9.0.3-18.fc12.noarch (build)
DEBUG util.py:256: Error: Missing Dependency: /bin/sh is needed by
package redhat-rpm-config-9.0.3-18.fc12.noarch (build)
DEBUG util.py:256: Error: Missing Dependency: mktemp is needed by
package redhat-rpm-config-9.0.3-18.fc12.noarch (build)
DEBUG util.py:256: Error: Missing Dependency: perl(Getopt::Long) is
needed by package redhat-rpm-config-9.0.3-18.fc12.noarch (build)
I do koji list-groups dist-f12-build and it shows:
build [dist-f12-build]
bash: None, default [dist-f12-build]
bc: None, default [dist-f12-build]
bzip2: None, default [dist-f12-build]
coreutils: None, default [dist-f12-build]
cpio: None, default [dist-f12-build]
diffutils: None, default [dist-f12-build]
fedora-release: None, default [dist-f12-build]
findutils: None, default [dist-f12-build]
gawk: None, default [dist-f12-build]
gcc: None, default [dist-f12-build]
gcc-c++: None, default [dist-f12-build]
grep: None, default [dist-f12-build]
gzip: None, default [dist-f12-build]
info: None, default [dist-f12-build]
make: None, default [dist-f12-build]
patch: None, default [dist-f12-build]
redhat-rpm-config: None, default [dist-f12-build]
rpm-build: None, default [dist-f12-build]
sed: None, default [dist-f12-build]
shadow-utils: None, default [dist-f12-build]
tar: None, default [dist-f12-build]
unzip: None, default [dist-f12-build]
util-linux-ng: None, default [dist-f12-build]
which: None, default [dist-f12-build]
srpm-build [dist-f12-build]
bash: None, default [dist-f12-build]
curl: None, default [dist-f12-build]
cvs: None, default [dist-f12-build]
fedora-release: None, default [dist-f12-build]
gnupg: None, default [dist-f12-build]
make: None, default [dist-f12-build]
redhat-rpm-config: None, default [dist-f12-build]
rpm-build: None, default [dist-f12-build]
shadow-utils: None, default [dist-f12-build]
On Mon, Feb 22, 2010 at 12:02 PM, Mike McLean <mikem(a)redhat.com> wrote:
> On 02/22/2010 09:27 AM, Doug Reiland wrote:
>> So, I import a src.rpm. What is the process for generating the binary
rpms?
>> I was assuming koji would do a rpnmbuild --rebuild via mock??
somehow.
>>
>> How are updates managed in fedora? I was assuming packages were always
>> getting rebuilt based on some kind of trigger (source update, ...),
>> and tagged, after testing or time-frame moved to an update repository.
>> Is this or something like it done in koji or outside koji.
>
> For a "how to use koji" doc from the building perspective, you should
> read the Fedora developer docs:
>
http://fedoraproject.org/wiki/Koji
> Some of it is specific to their setup, but most of it is generic.
>
> In Koji, a build is the set set of rpms that originate from a single
> source rpm. All the binary and/or noarch packages and subpackages, as
> well as the srpm itself, are part of the build. Since the srpm is the
> defining element, the build is referred to by the name of the srpm.
>
> Koji only knows about rpms that is tracks in its database. There are
two
> ways to get a build into koji:
> 1) build it in koji (koji build)
> 2) manually import an entire external build (koji import)
>
> In the course of normal operation, manual imports should be rare.
>
> To build from a source rpm, you simply need to pass that file to the
> build command. When you imported your source rpm before, you were
> creating a manually imported build that consisted solely of that source
> rpm. Because Koji enforces N-V-R uniqueness you will not be able to
> build that srpm normally; Koji thinks it's already been built.
> --
> buildsys mailing list
> buildsys(a)lists.fedoraproject.org
>
https://admin.fedoraproject.org/mailman/listinfo/buildsys
>
--
buildsys mailing list
buildsys(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys