Bug 983140 - FTBS: rpmbuild -bp qt.spec fails applying qt-4.8-CVE-2013-0254.patch
FTBS: rpmbuild -bp qt.spec fails applying qt-4.8-CVE-2013-0254.patch
Status: CLOSED WORKSFORME
Product: Fedora
Classification: Fedora
Component: qt (Show other bugs)
19
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Ngo Than
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-10 11:33 EDT by Ian Pilcher
Modified: 2013-10-09 12:18 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-10-09 12:18:38 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ian Pilcher 2013-07-10 11:33:35 EDT
Fully updated Fedora 19, with all build dependencies installed via yum-builddep.  'rpmbuild -bp qt.spec' gives:

...
Patch #501 (qt-4.8-CVE-2013-0254.patch):
+ /usr/bin/cat /home/pilcher/rpmbuild/SOURCES/qt-4.8-CVE-2013-0254.patch
+ /usr/bin/patch -p1 -b --suffix .qsharedmemory-security --fuzz=0
patching file src/corelib/kernel/qsharedmemory_unix.cpp
patching file src/corelib/kernel/qsystemsemaphore_unix.cpp
patching file src/gui/image/qnativeimage.cpp
patching file src/gui/image/qpixmap_x11.cpp
patching file src/plugins/platforms/xcb/qxcbwindowsurface.cpp
patching file src/plugins/platforms/xlib/qxlibwindowsurface.cpp
can't find file to patch at input line 125
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/tests/auto/qtipc/qsharedmemory/tst_qsharedmemory.cpp b/tests/auto/qtipc/qsharedmemory/tst_qsharedmemory.cpp
|index 9e77af6..e92a030 100644
--------------------------
File to patch:
Comment 1 Rex Dieter 2013-10-09 12:18:38 EDT
It's obviously building fine for us,

http://koji.fedoraproject.org/koji/packageinfo?packageID=374

hard to say what your problem was...

Note You need to log in before you can comment on or make changes to this bug.