Description of problem: If there is a compelling reason, please tell it here and if it is really compelling, a comment should be added in the spec file. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
To be more precise, depending on the -devel subpackages corresponds with the intention to link against the library, while depending on the -static subpackage means that nget needs the uulib static libraries which I think is not true. This is not a very problematic bug, since the end result is the same, but I think that it is important to be consistent and have meaningful requires, not only correct requires. Also it is implied by the guidelines (though in that sort of areas I don't think that guidelines should necessarily be followed to the letter): "This way other packages which will link against a dynamic library when your package starts providing one can BuildRequire: foo-devel and packages which explicitly need to link against the static version can BuildRequire: foo-static"
uulib-static comes from the uudeview package, which only provides static archives and no dynamic library. I see that you have changed the package name to uulib-devel, which has 'Provides: uulib-static', after filing this bug. The reason I preferred -static over -devel is that I did not want to slip in a dependency on some static library in the garb of of yet another -devel package.
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Ping?
I am closing this as WONTFIX. Please feel free to reopen if you have further doubts or issues. Thanks for the report.