Bug 1678932 - Error rebuilding rh-dotnet22-curl in CentOS
Summary: Error rebuilding rh-dotnet22-curl in CentOS
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: dotNET
Classification: Red Hat
Component: rh-dotnet22
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ga
: 2.2
Assignee: Omair Majid
QA Contact: Radka Gustavsson
Les Williams
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-19 23:08 UTC by Omair Majid
Modified: 2019-05-15 21:54 UTC (History)
5 users (show)

Fixed In Version: rh-dotnet22-curl-7.61.1-2.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-15 21:54:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:1236 0 None None None 2019-05-15 21:54:49 UTC

Description Omair Majid 2019-02-19 23:08:44 UTC
Description of problem:

The rh-dotnet22-curl RPM can't be rebuilt by CentOS folks.

The error message is: 

error: /builddir/build/BUILDROOT/curl-7.61.1-1.el7.x86_64/usr/include/curl/curlbuild.h': No such file or directory

Turns out curlbuild.h was removed in curl 7.55. Our RPM is still incorrectly looking for it. Worse, instead of failing, the RPM build in our offical build system continues as if nothing bad happened. The built RPM is incomplete and missing files.

(In our case, this is not *too* bad, because we just skip packaging one pkg-config file.)

This was originally reported on #centos-devel by hughesjr

Version-Release number of selected component (if applicable):
rh-dotnet22-curl-7.61.1-1.el7

Comment 1 Omair Majid 2019-02-19 23:37:00 UTC
The fix is two fold:

1. Use a `set -ex` at the start of the %install section to make sure we fail the build if any build step fails

2. Do not try and patch, modify or install a non-existant curlbuild.h file. This file was removed in curl 7.55.0: https://curl.haxx.se/changes.html

Comment 5 errata-xmlrpc 2019-05-15 21:54:39 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-2019:1236


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