[RFC] Make koji a complete rpmfind replacement

Mike Bonnet mikeb at redhat.com
Wed May 16 14:35:38 UTC 2007


On Thu, 2007-05-17 at 00:30 +1200, Nigel Jones wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Nicolas Mailhot wrote:
> > Hi,
> > 
> > With the rawhide sync down and packages stuck on various non-mirrored
> > state I couldn't help noticing the retro rpmfind-ish experience of koji
> > (go to the web site, select the right package letter, open the package
> > info page, click on the download link, repeat for deps…)
> > 
> > While I'm sure the yum repo situation will correct itself soon I
> > couldn't help wondering if koji could not serve the same purpose as
> > rpmfind for fly-by users (typically users of another distro/release
> > version that just want to look at how something was done in Fedora X to
> > provide feedback or adapt)
> > 
> > Right now it only needs:
> > 1. a search field
> Well there is the search section (top menu bar)
> > 2. resolving dependency links

Not sure what you mean by this.  You want the web interface to perform
the same functions as yum?

> > 3. displaying of rpm metadata

Like http://koji.fedoraproject.org/koji/rpminfo?rpmID=69779 for example?
(follow the (info) link next to the RPM list on the buildinfo page)

What other metadata would you like displayed here?

> Yes I agree on the 2nd two points, it'd be quite handy.
> 
> I also think having koji to show BR trees would be useful people can
> then look at it and say "right if I rebuild libxyz now, rpmx rpmy and
> rpmz need to be rebuilt, maybe I should contact those maintainers".

http://koji.fedoraproject.org/koji/rpmlist?buildrootID=2540&type=component
(from the taskinfo page click Buildroot -> Component RPMs)

Every RPM with a check mark in the "Update" column was pulled in as a
BuildRequires or a dependency of a BuildRequires.  RPMs without a check
mark in the "Update" column were pulled in as part of the minimal
buildroot.  Note that there is usually overlap in these sets.

> I have yet to really find a decent way for handling those sorts of issues.
> 
> N.J.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
> 
> iD8DBQFGSvlapldg9bRmG6kRAoI8AJ9SHHlIktqA5ugRiKJOV9ov745m7gCfeR5d
> 44uHlSsmQKOdXjWJii6U3EI=
> =iehS
> -----END PGP SIGNATURE-----
> 




More information about the fedora-devel-list mailing list