In #slforum today lewellyn mentioned that yum-builddep doesn't seem to work on SL the same way it does on CentOS and upstream.
A command like:
yum-builddep [package]
fails like this:
> [root@tortilla opt]# yum-builddep openssh
> Loaded plugins: refresh-packagekit
> Enabling epel-source repository
> Enabling tao-dev-source repository
> No source RPM found for openssh-5.3p1-70.el6.x86_64
> No uninstalled build requires
> [root@tortilla opt]# yum-builddep samba
> Loaded plugins: refresh-packagekit
> Enabling epel-source repository
> Enabling tao-dev-source repository
> No source RPM found for samba-3.5.10-114.el6.x86_64
> No source RPM found for samba-3.5.10-116.el6_2.x86_64
> No source RPM found for samba-3.5.10-115.el6_2.x86_64
> No uninstalled build requires
It seems like yum-builddep isn't used by a huge number of folks these days (myself
included), but it is useful for people who do local builds outside of mock. The problem appears to be that the repodata indicates a flat directory structure, but within SRPMS/ there is a nested structure which clearly segregates the packages by origin.
Any ideas?