RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1415547 - Rebuilding tigervnc SRPM stops at applying Patch101
Summary: Rebuilding tigervnc SRPM stops at applying Patch101
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tigervnc
Version: 7.3
Hardware: All
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Jan Grulich
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1393395
TreeView+ depends on / blocked
 
Reported: 2017-01-23 02:56 UTC by Tsukahara Ken
Modified: 2017-08-01 20:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 20:50:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2000 0 normal SHIPPED_LIVE Moderate: tigervnc and fltk security, bug fix, and enhancement update 2017-08-01 18:33:08 UTC

Description Tsukahara Ken 2017-01-23 02:56:22 UTC 
Description of problem:
Rebuilding tigervnc SRPM stops at applying Patch101(0001-rpath-hack.patch).

Version-Release number of selected component (if applicable):
tigervnc-1.3.1-9.el7.src.rpm
xorg-x11-server-source-1.17.2-22.el7.noarch.rpm

How reproducible:
Always

Steps to Reproduce:
1. rpm -ivh tigervnc-1.3.1-9.el7.src.rpm
2. rpmbuild -bp tigervnc.spec

Actual results:
# rpmbuild -bp tigervnc.spec
>> snip <<
+ echo 'Patch #101 (0001-rpath-hack.patch):'
Patch #101 (0001-rpath-hack.patch):
+ /usr/bin/cat /root/rpmbuild/SOURCES/0001-rpath-hack.patch
+ /usr/bin/patch -p1 -b --suffix .rpath --fuzz=0
patching file configure.ac
Reversed (or previously applied) patch detected!  Assume -R? [n]
>> stop <<

Expected results:
# rpmbuild -bp tigervnc.spec
>> snip <<
Patch #15002 (tigervnc-pullrequest-402.patch):
+ /usr/bin/cat /root/rpmbuild/SOURCES/tigervnc-pullrequest-402.patch
+ /usr/bin/patch -p1 -b --suffix .leakage --fuzz=0
patching file vncviewer/X11PixelBuffer.cxx
Hunk #1 succeeded at 195 (offset 8 lines).
Hunk #2 succeeded at 225 (offset 8 lines).
+ exit 0

Additional info:
Patch101 has already been applied to xorg-x11-server-source-1.17.2-22(maybe since 1.17.2-18). Patch101 should be dropped from tigervnc, and add BuildRequires: xorg-x11-server-source >= 1.17.2-18.
Comment 1 Jan Grulich 2017-01-23 06:49:29 UTC 
Will be fixed with the next tigervnc update.
Comment 2 Tsukahara Ken 2017-01-23 09:00:25 UTC 
OK, I see. Thanks!
Comment 7 errata-xmlrpc 2017-08-01 20:50:05 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:2000
Note You need to log in before you can comment on or make changes to this bug.