#167 Empty file list handing incorrect (Was:"No built package" error when there is no base package)
Closed: Fixed Opened by leamas.

If a spec file does not define a base package, f-r runs into problems after completed build looking for a non-existing base-package.

Testcase: https://bugzilla.redhat.com/show_bug.cgi?id=852330#c10


Fixed in 997b0f4c698899774ec36e4

The fix is broken. Problem is that it does not differ the case when there's an empty %files section from a not-existing section. An empty section is valid, indicating an empty (e. g., meta) package, whereas a not-existing section will not generate any binary package.

Fixed, again, inf51f7fcd66aa6672945

Metadata