For odd reasons I got an email about Software Freedom Day Event over at unc next week. I emailed some folks and I think we’re going to have a talk by Max Spevack – our fearless leader of the Fedora Project and hopefully a table/booth for fedora schwag (livecds, dvds, etc). I’ll update more here as I know more but it sure seems like a cool thing to go to and UNC campus is really nice. If you’re in the area and want to learn more about linux and other open-source-y/free culture things you should stop by. If you’re a linux company/project/lug in the area contact the people in charge to see if you can help!


I was talking to luke today and he said he needed an easy way of querying data out of a repository that he just had on disk or available at a url but didn’t actually have set up in his yum configuration. So I took a little time and sifted through repoquery in yum-utils to add support for arbitrary repository paths.

So if you take this version of repoquery and you run it like this:

repoquery –repofrompath=/url/or/path/to/myrepo  \ –repoid=myrepo -q -a

then you’ll get a list of all the pkgs in that repository.

It was very simple to implement but it should expedite a lot of random lookups that people may want to do against arbitrary repositories – especially often-remade koji repos.

Here’s the full excerpt from the man page:

Specify  a  path  or  url  to  a  repository  (same path as in a
baseurl) to add to the repositories for this query. This  option
can  be  used  multiple times. If you want to view only the pkgs
from this repository combine this with –repoid. The  repoid  of
the  paths  specified are the last directory path segment. So if
the path you specified  was:  ’/some/place/named/my_repo/’  then
the    repoid   would   be   ’my_repo’.   If   the   path   was:
’http://server/path/my_repo’  then  the  repoid  would  also  be           ‘my_repo’.


Assuming Google translate hasn’t horribly mangled your intent, could you file a bug about what is happening there? Specifically if you have  diskspacecheck turned off in your yum.conf? B/C as it is rpm should be erroring about there being insufficient disk space well before the transaction is ever run.