Bug 563285 - RFE: Yum repository for every "buildArch" task in Koji
Summary: RFE: Yum repository for every "buildArch" task in Koji
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-09 17:46 UTC by Dave Malcolm
Modified: 2018-07-18 21:33 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-07-18 21:30:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
script to download rpms from koji build and make yum metadata (808 bytes, text/plain)
2010-02-12 14:40 UTC, Tim Lauridsen
no flags Details

Description Dave Malcolm 2010-02-09 17:46:54 UTC
Description of problem:
I often perform scratch builds in Koji to test a particular feature, and these sometimes emit numerous sub-packages.

Currently I'm manually downloading each URL from the web UI, and installing them with rpm.

It would be useful when testing the builds to be able to have a yum repository for the build, so that I could write something like this:

  yum --with-koji-task=1972153 update python

and have yum "magically" grab the test build of python, python-libs etc (i.e synthesize a repository for the build: http://koji.fedoraproject.org/koji/taskinfo?taskID=1972153 and enable it for this command).

Potentially, multiple instances of --with-koji-task could be supplied.

How sane does this sound, and would other people find this useful?  (Probably a plugin, I guess)

Note that this introduces a singleton "koji" URL, could have a syntax like this:
  --with-repo=koji:1972153
and have some pluggable mechanism for generating repository info on the fly from a string like "koji:task:1972153", as opposed to say "koji:tag:dist-f14", with e.g. another string for people with their own instances of Koji.

Comment 1 seth vidal 2010-02-09 18:04:37 UTC
this is a variation on the tmprepo plugin.

or

a variation on createrepo -i http://url/pkg1 -i http://url/pkg2 etc


in either case it would be much simpler if koji, at the end of a build process just ran createrepo -d over the results.


if koji does the above first then yum just needs a url an the tmprepo plugin.

Comment 2 James Antill 2010-02-09 18:09:10 UTC
 I have:

% cat /etc/yum.repos.d/koji.repo
[koji]
name=Koji $basearch
baseurl=http://koji.fedoraproject.org/static-repos/dist-rawhide-current/$basearch/
gpgcheck = false
enabled=false

[koji-32]
name=Koji i386
baseurl=http://koji.fedoraproject.org/static-repos/dist-rawhide-current/i386/
gpgcheck = false
enabled=false

...which generally takes a couple of hours, and if I can't wait that long recent yum's allow you to paste URLs directonly on the cmd line.
 As Seth says, for us to do any better it'd be really nice for koji to do the createrepo run.

Comment 3 Tim Lauridsen 2010-02-12 14:40:37 UTC
Created attachment 390496 [details]
script to download rpms from koji build and make yum metadata

What about something like this :)

Comment 4 Karel Zak 2013-02-20 10:38:47 UTC
koji supports "download-build" command now, all you need is

   koji download-build <pkg-ver-rel> && createrepo -d .

to create a local repository from the build.

Comment 5 Daniel Mach 2018-07-18 21:30:09 UTC
yum and related packages are no longer actively developed.
They are being replaced with dnf, dnf-utils, etc.

I'm closing this bug because it's most likely never going to be fixed.
If you still consider your bug report important, reopen it, please.

Comment 6 Daniel Mach 2018-07-18 21:33:11 UTC
yum and related packages are no longer actively developed.
They are being replaced with dnf, dnf-utils, etc.

I'm closing this bug because it's most likely never going to be fixed.
If you still consider your bug report important, reopen it, please.


Note You need to log in before you can comment on or make changes to this bug.