f10.src.rpm koji results in dist-5E-epel target:
http://koji.fedoraproject.org/koji/taskinfo?taskID=1476599

x86_64 cli version appears to work fine.

> I need lshw in EPEL, do you want to package it or should i take care of it?  

I don't do EPEL packages of any package at the moment.


> or should i take care of it? 

Yes, please :-)


 - Terje

(In reply to comment #3)
> > I need lshw in EPEL, do you want to package it or should i take care of it?  
> > or should i take care of it? 
> 
> Yes, please :-)

Okay :)

Package Change Request
======================
Package Name: lshw
New Branches: EL-4 EL-5
Owners: terjeros tuju

One thing what needs to be resolved, that how can we prevent that sub-package from appearing in EPEL? I really don't think it's worth of dragging all those gui dependencies into server platform, especially when all changes in the future should be kept in minimal. 

http://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies
> have a mostly stable set of packages that normally does not change 
> at all and only changes if there are good reasons for changes.

sure the gui stuff remains as such too, but perhaps we could do some %if magic in spec for EL versions? What do you think?

CVS done.

lshw-B.02.12.01-1.el5 has been submitted as an update for Fedora EPEL 5.
http://admin.fedoraproject.org/updates/lshw-B.02.12.01-1.el5

lshw-B.02.12.01-1.el5 has been pushed to the Fedora EPEL 5 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update lshw'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/EL-5/FEDORA-EPEL-2009-0105

(In reply to comment #6)
> CVS done.  

Tibbs, btw, did you notice that cvs request was for EL-4 too?

cvs done.

lshw-B.02.12.01-1.el5 has been pushed to the Fedora EPEL 5 stable repository.  If problems still persist, please make note of it in this bug report.