Closed #1592.
--
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/issues/1592#event-5161889493___
Rpm-maint mailing list
Rpm-maint@lists.r
Not sure if the example above is really helping in clearing this up. But the
basic reason is that Spec files are turing complete and can do all kind of
things. This includes things depending on the sources. So not having them can
change the result - with or without a visible error. So we require
To illustrate the problem (even without rebase-helper):
```bash
$ rhpkg clone -a cronie
$ cd cronie && git checkout rhel-8.5.0
$ cat cronie.spec
...
%prep
%setup -q
%patch0 -p1
%patch1 -p1
%patch2 -p1
%patch3 -p1
...
```
```bash
$ python3 -c 'import os, rpm; rpm.addMacro("_sourcedir", os.getcwd()
Original report: https://github.com/rebase-helper/rebase-helper/issues/848
I have a specfile which is being parsed by the rpm python bindings. The parsing
fails on the fact that primary `Source0` archive is not present so
rebase-helper retries with `RPMSPEC_FORCE` which results into ignoring pat
