Okay, I tried running the same command as you, and the same thing
happened.
I also made sure the patch is in the right place ...
[rpmbuilder@biggusgazzus SPECS]$ ls ../SOURCES/ | grep scar
scarlett.patch
It seems like we're doing the same thing, but mind doesn't work.
Any other ideas? Anyone?
On Thu, 11 Sep, 2014 at 6:27 PM, Biggus Gazus <earthwormgaz(a)gmail.com>
wrote:
I ran this command ...
[rpmbuilder@biggusgazzus SPECS]$ rpmbuild -bb --with baseonly
--without debuginfo --target=`uname -m` kernel.spec
That's from the SPECS folder.
On Wed, 10 Sep, 2014 at 11:38 PM, Prarit Bhargava <prarit(a)redhat.com>
wrote:
> On 09/10/2014 06:06 PM, Josh Boyer wrote:
>> On Wed, Sep 10, 2014 at 5:22 PM, Biggus Gazus
>> <earthwormgaz(a)gmail.com> wrote:
>>> Hi,
>>>
>>> Here's the output ...
>>>
>>>
http://fpaste.org/132598/38399914/
>>>
>>> Here's the spec ...
>>>
>>>
http://fpaste.org/132600/41038420/
>>>
>>> If you search it for "focusrite" you'll find the three changes
I
>>> made.
>>>
>>> Thanks again for any help!
>>
>> Your changes appear to be correct to me. Are you sure you invoked
>> rpmbuild with the kernel.spec file you fpasted? Typically you get
>> that error message when you don't have the PatchXXXXX: field added.
>> You can alternatively hit this if you've renamed the package, but
>> that
>> doesn't appear to be the case here.
>>
>
> Hmm ... seems to work for me.
>
> Applied your 3 kernel.spec changes and then did:
>
> rpmbuild -bp kernel.spec
>
> to build the patched kernel ... I see the following in the log:
>
> + case "$patch" in
> + patch -p1 -F1 -s
> + ApplyPatch scarlett.patch
> + local patch=scarlett.patch
> + shift
> + '[' '!' -f /root/rpmbuild/SOURCES/scarlett.patch ']'
> Patch74912: scarlett.patch
>
> so it did apply AFAICT. I'm assuming you did put the patch in
>
> ~/rpmbuild/SOURCES/scarlett.patch
>
> P.