[Rpm-maint] [rpm-software-management/rpm] Try to continue despite missing %include files on forced spec parse (#684)

[Panu Matilainen]

On forced spec parse (spec query or --force'd build) we already allow
sources and patches to be missing. %include differs from sources and
patches in that a missing include might make the spec unparseable,
but then we lose nothing by trying, as quite often the spec is parseable
enough to get at least some info out of it. Doesn't seem any worse
than allowing build without sources present...

Helps a bit in cases like RhBug:1658292 and RhBug:1547897.
You can view, comment on, or merge this pull request online at:

  https://github.com/rpm-software-management/rpm/pull/684

-- Commit Summary --

  * Try to continue despite missing %include files on forced spec parse

-- File Changes --

    M build/parseSpec.c (20)
    M tests/Makefile.am (1)
    A tests/data/SPECS/inctest.spec (11)
    M tests/rpmbuild.at (23)

-- Patch Links --

https://github.com/rpm-software-management/rpm/pull/684.patch
https://github.com/rpm-software-management/rpm/pull/684.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/684
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20190426/8d6a74c5/attachment.html>