[Rpm-maint] [PATCH] fix %autopatch when patch do not exist

[Thierry Vignaud]

On 18 September 2015 at 11:50, Dimitri John Ledkov
<dimitri.j.ledkov at intel.com> wrote:
> So this %autopatch thing is a bit useless to me at the moment,
> specifically because of the requirement to have patches in
> rpmbuild/SOURCES/.

Uh?
Patches can be anywhere.
They're found where %patch is looking for them.
There's nothing changed there.
It can be anywhere...

> And it's not nice to operate against packaging committed to git.

Uh?
What?
You've the choice. You can use git or not.
Both are supported. And more.

It works nicely for Mageia. It has been tested by lots of packages in
lots of different locations
(rpmbuild/SOURCES, <pkg_name>/SOURCES, ...)
It works nicely with either manual rpmbuild or with iurt (~~mock for Mageia).

> I have a git tree with foo.spec & foo.patch. And use mock to build it:
>
> $ mock --buildsrpm --source=./ --spec=foo.spec --results=results/
>
> %autopatch / %autosetup then looks for patches in the wrong location.
> Am I missing something to use both %autopatch and patches from the
> same location as the spec file?

I think you needs to show your spec up.
But I bet that mock --buildsrpm works smoothly.
Are you sure mock --spec/--sources works for your foo.spec with
regular plain %patch macros?
I've never used --spec/--sources but maybe there's a regression and it
doesn't set right the path macros (eg: %_sourcedir).

But please open a __new mail thread__ for that.
Thanks :-)