workflow help

[Doug Reiland]

I am trying to get my hands around koji.
I have setup a local koji server. I have followed examples on setting up tags/groups.
I have dist-f12 and dist-f12-build
I have linked dist-f12-build to external repos in mirrors.kernel.org.
    - what does this do you me? I this just the place where any rpm needed to satisfy a build request get pulled from?

I regen-repo and everything I think is ok, so far.

For testing, I download the src rpm for bc.
I did koji import dist-f12 bc*src.rpm

via web interface, it looks ok.
Why does this show up as a build? The bc package shows up under builds. I guess a build is any rpm, src or binary correct?

How do I trigger a build of this rpm?
koji build dist-f12 bc*src*rpm - complains has it tries to do an import again.
Using --scratch option works or doesn't fail. but I don't know what that does.

How do I just say build everything under a tag, for example dist-f12?
Is there a  I way to trigger this via web interface?

How does a user, via koji cli, checkout src package, make changes, checkin, build, ...?

Thanks!

Doug

[Steve Traylen]

On Mon, Feb 22, 2010 at 1:01 PM, Doug Reiland  wrote:
> I am trying to get my hands around koji.
> I have setup a local koji server. I have followed examples on setting up
> tags/groups.
> I have dist-f12 and dist-f12-build
> I have linked dist-f12-build to external repos in mirrors.kernel.org.
>     - what does this do you me? I this just the place where any rpm needed
> to satisfy a build request get pulled from?
>
> I regen-repo and everything I think is ok, so far.
>
> For testing, I download the src rpm for bc.
> I did koji import dist-f12 bc*src.rpm

koji import is a way of importing a pre built .src.rpm and binaries into koji.

Instead you want to build the package.

koji build dist-f12 yourrpm.src.rpm
> via web interface, it looks ok.
> Why does this show up as a build? The bc package shows up under builds. I
> guess a build is any rpm, src or binary correct?
>
> How do I trigger a build of this rpm?
> koji build dist-f12 bc*src*rpm - complains has it tries to do an import
> again.
> Using --scratch option works or doesn't fail. but I don't know what that
> does.

When you imported it you effectivly built it. You can never build the
same thing again.
> How do I just say build everything under a tag, for example dist-f12?
> Is there a  I way to trigger this via web interface?

Again once built you cannot build again so the question does not make sense.
You have to increase the release number at least and then they can be built.
> How does a user, via koji cli, checkout src package, make changes, checkin,
> build, ...?
>
> Thanks!
>
> Doug
>
> --
> buildsys mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/buildsys

[Doug Reiland]

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.

Again, thanks while I catch up.

Doug

On Mon, Feb 22, 2010 at 7:51 AM, Steve Traylen  wrote:
> On Mon, Feb 22, 2010 at 1:01 PM, Doug Reiland  wrote:
> > I am trying to get my hands around koji.
> > I have setup a local koji server. I have followed examples on setting up
> > tags/groups.
> > I have dist-f12 and dist-f12-build
> > I have linked dist-f12-build to external repos in mirrors.kernel.org.
> >     - what does this do you me? I this just the place where any rpm needed
> > to satisfy a build request get pulled from?
> >
> > I regen-repo and everything I think is ok, so far.
> >
> > For testing, I download the src rpm for bc.
> > I did koji import dist-f12 bc*src.rpm
>
> koji import is a way of importing a pre built .src.rpm and binaries into koji.
>
> Instead you want to build the package.
>
> koji build dist-f12 yourrpm.src.rpm
> > via web interface, it looks ok.
> > Why does this show up as a build? The bc package shows up under builds. I
> > guess a build is any rpm, src or binary correct?
> >
> > How do I trigger a build of this rpm?
> > koji build dist-f12 bc*src*rpm - complains has it tries to do an import
> > again.
> > Using --scratch option works or doesn't fail. but I don't know what that
> > does.
>
> When you imported it you effectivly built it. You can never build the
> same thing again.
> > How do I just say build everything under a tag, for example dist-f12?
> > Is there a  I way to trigger this via web interface?
>
> Again once built you cannot build again so the question does not make sense.
> You have to increase the release number at least and then they can be built.
> > How does a user, via koji cli, checkout src package, make changes, checkin,
> > build, ...?
> >
> > Thanks!
> >
> > Doug
> >
> > --
> > buildsys mailing list
> > [e-mail]
> > https://admin.fedoraproject.org/mailman/listinfo/buildsys
>
> --
> Steve Traylen
> --
> buildsys mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/buildsys

[Michael Cronenworth]

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.

No. You do not want to "import" anything. You want to "build" packages. 
You do not use "koji import". You want to use "koji build".
> 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.

Fedora uses a CVS tree (soon git?) for holding all the specs and source 
code. When a packager issues "make package" the koji system pulls the 
spec and source and builds from that, instead of an SRPM. This is part 
of the ServerHowTo.

[Doug Reiland]

The SeverHowTo does have a link to bootstrapping the server, but
that's where I got the import idea from.

Can you give me an example?
I have done fedora-package-setup
How would I checkout and build "bc"?

I saw some language about "make package" but didn't understand the tie
in. Should I have done:
1) fedora-package-setup
2) cvs co cvs.fedoraproject.org:/cvs/pkgs
4) cd some package directory
5) make build

#5 will interact with whatever koji build server is configured.

Also, should I get rid of everything I imported? If so, how..

Doug

On Mon, Feb 22, 2010 at 9:33 AM, Michael Cronenworth  wrote:
> 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.
>
> No. You do not want to "import" anything. You want to "build" packages.
> You do not use "koji import". You want to use "koji build".
> > 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.
>
> Fedora uses a CVS tree (soon git?) for holding all the specs and source
> code. When a packager issues "make package" the koji system pulls the
> spec and source and builds from that, instead of an SRPM. This is part
> of the ServerHowTo.
> --
> buildsys mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/buildsys

[Michael Cronenworth]

Doug Reiland wrote:
> Can you give me an example?
> I have done fedora-package-setup
> How would I checkout and build "bc"?

Steve Traylen gave you a good example. You can start a build from a SRPM 
without needing the CVS setup.

$ koji build filename.srpm.rpm

I do not have first hand experience with fedora packaging Makefiles, but 
if you check out an existing package and follow it you should have 
something useful to work off of.

You don't need to get rid of what you imported, but you will have to 
submit a package with a higher version in order to replace it.

[Steve Traylen]

On Mon, Feb 22, 2010 at 5:00 PM, Michael Cronenworth  wrote:
> Doug Reiland wrote:
> > Can you give me an example?
> > I have done fedora-package-setup
> > How would I checkout and build "bc"?
>
> Steve Traylen gave you a good example. You can start a build from a SRPM
> without needing the CVS setup.
>
> $ koji build filename.srpm.rpm
>
> I do not have first hand experience with fedora packaging Makefiles, but
> if you check out an existing package and follow it you should have
> something useful to work off of.

If you want to build out of your own cvs repo your toplevel Makefile has to
support

make sources

and at the end of that there has to be a

whatever.spec
yoursource-forwhatever.spec

There is some documentation for how we do things here:
https://twiki.cern.ch/twiki/bin/view/EGEE/EGEESA1KojiClient#Submit_a_SCM_URL...

We don't work like fedora in that we just put the .spec files in with
the code being developed
so make sources is effectively make dist. In Fedora's layout (which is
better I might add)
the make sources just wgets the source tar ball.

You can follow the example svn urls to look at our source trees e.g.

http://www.sysadmin.hep.ac.uk/svn/grid-monitoring/trunk/msg/egee-backbone-co...
> You don't need to get rid of what you imported, but you will have to
> submit a package with a higher version in order to replace it.
> --
> buildsys mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/buildsys

[Mike McLean]

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.

[Doug Reiland]

Ok, thanks everybody. I am going to digest all this.
If there a command or some sql steps to cleanup/undo my imports,
please point me to them.

I thought I can across a page with some various helpful koji sql
macros a couple of days ago, but I can't find it now.

Doug

On Mon, Feb 22, 2010 at 12:02 PM, Mike McLean  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
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/buildsys

[Mike McLean]

On 02/22/2010 12:11 PM, Doug Reiland wrote:
> Ok, thanks everybody. I am going to digest all this.
> If there a command or some sql steps to cleanup/undo my imports,
> please point me to them.
>
> I thought I can across a page with some various helpful koji sql
> macros a couple of days ago, but I can't find it now.

Depending on the extent of mistaken imports, it may be easiest to reset 
the db and /mnt/koji.

If we're only talking about a few mistaken imports, I wouldn't worry 
about it. Just leave them, bump the release and move on.

[Doug Reiland]

I imported the whole f12 source repo. I guess I will reinitialize.

On Mon, Feb 22, 2010 at 12:19 PM, Mike McLean  wrote:
> On 02/22/2010 12:11 PM, Doug Reiland wrote:
> > Ok, thanks everybody. I am going to digest all this.
> > If there a command or some sql steps to cleanup/undo my imports,
> > please point me to them.
> >
> > I thought I can across a page with some various helpful koji sql
> > macros a couple of days ago, but I can't find it now.
>
> Depending on the extent of mistaken imports, it may be easiest to reset
> the db and /mnt/koji.
>
> If we're only talking about a few mistaken imports, I wouldn't worry
> about it. Just leave them, bump the release and move on.
> --
> buildsys mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/buildsys

[Doug Reiland]

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  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
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/buildsys

[Doug Reiland]

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  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  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
> > [e-mail]
> > https://admin.fedoraproject.org/mailman/listinfo/buildsys

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 
To:
Discussion of Fedora build system 
Date:
23/02/2010 13:49
Subject:
Re: workflow help
Sent by:
[e-mail]

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  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  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:
> > build it in koji (koji build)
> > 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
> > [e-mail]
> > https://admin.fedoraproject.org/mailman/listinfo/buildsys

--
buildsys mailing list
[e-mail]
https://admin.fedoraproject.org/mailman/listinfo/buildsys