https://bugzilla.redhat.com/show_bug.cgi?id=833462 --- Comment #3 from Ales Kozumplik <akozumpl@xxxxxxxxxx> --- (In reply to comment #1) > (In reply to comment #0) > Ales, > > The .spec as-is produces a binary python-hawkey package that can't be > installed due to a missing requires on "libhawkey.so.0()(64bit)". This is\ Sorry about that. I didn't test the final package after adding the provides filtering on the python binary libs (something else that rpmlint complained about). > caused by _hawkey_testmodule.so having a DT_NEEDED entry (i.e. is linked > with) _hawkeymodule.so and RPM automatically generating a requires from that. > We can stop RPM from generating that requires by adding this snippet: It is strange the regular 'hawkey' python module doesn't cause the same thing. > > %global gitrev 04ecf00 > %global libsolv_version 0.0.0-11 > > +# filter out _hawkey_testmodule.so DT_NEEDED _hawkeymodule.so > +%{?filter_setup: > +%filter_requires_in %{python_sitearch}/hawkey/test/.*\.so$ > +%filter_setup > +} > + > Name: hawkey > > to the .spec file per > http://fedoraproject.org/wiki/Packaging: > AutoProvidesAndRequiresFiltering#Removing_items_from_the_requires_stream_. > 28post-scan_filtering.29 > b > > But I must ask do you _REALLY_ want to ship the "hawkey.test" package in the > RPM? Is it really useful? I would like to avoid this if at all possible: hawkey.test is useful for building python unit tests for the library and for components using it, so if it's in the .rpm people won't have to build hawkey from source (and set PYTHONPATH) to unit test DNF for instance. Let me think about how to unef this for a while. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review