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