FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor


 
 
LinkBack Thread Tools
 
Old 02-22-2010, 11:01 AM
"Doug Reiland"
 
Default workflow help

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
*
*
*
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 02-22-2010, 11:51 AM
Steve Traylen
 
Default workflow help

On Mon, Feb 22, 2010 at 1:01 PM, Doug Reiland <dreiland@gmail.com> 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
> buildsys@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/buildsys
>



--
Steve Traylen
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 02-22-2010, 01:27 PM
Doug Reiland
 
Default workflow help

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 <steve.traylen@cern.ch> wrote:
> On Mon, Feb 22, 2010 at 1:01 PM, Doug Reiland <dreiland@gmail.com> 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
>> buildsys@lists.fedoraproject.org
>> https://admin.fedoraproject.org/mailman/listinfo/buildsys
>>
>
>
>
> --
> Steve Traylen
> --
> buildsys mailing list
> buildsys@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/buildsys
>
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 02-22-2010, 01:33 PM
Michael Cronenworth
 
Default workflow help

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
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 02-22-2010, 02:32 PM
Doug Reiland
 
Default workflow help

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 <mike@cchtml.com> 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
> buildsys@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/buildsys
>
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 

Thread Tools




All times are GMT. The time now is 03:57 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org