| Summary: | Rpmdiff failure(s) for build rubygem-cloudfiles-1.4.17-2.el6 | ||
|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | John Eckersberg <jeckersb> |
| Component: | rubygem-cloudfiles | Assignee: | Steve Linabery <slinaber> |
| Status: | CLOSED ERRATA | QA Contact: | Rehana <redakkan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1.0.0 | CC: | cpelland, dajohnso, hbrock, whayutin |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-05-15 19:33:06 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
John Eckersberg
2012-03-13 16:53:45 UTC
This change is ok because the patches are being applied. These lines in the spec:
/usr/bin/patch -s -p0 -b --suffix --fuzz=0 test/cloudfiles_authentication_test.rb %{PATCH0}
/usr/bin/patch -s -p0 -b --suffix --fuzz=0 test/cloudfiles_connection_test.rb %{PATCH1}
/usr/bin/patch -s -p0 -b --suffix --fuzz=0 test/cloudfiles_storage_object_test.rb %{PATCH2}
result in this output in the build.log:
+ /usr/bin/patch -s -p0 -b --suffix --fuzz=0 test/cloudfiles_authentication_test.rb /builddir/build/SOURCES/disable_test_bad_hostname.patch
+ /usr/bin/patch -s -p0 -b --suffix --fuzz=0 test/cloudfiles_connection_test.rb /builddir/build/SOURCES/disable_faulty_connection_tests.patch
patch unexpectedly ends in middle of line
+ /usr/bin/patch -s -p0 -b --suffix --fuzz=0 test/cloudfiles_storage_object_test.rb /builddir/build/SOURCES/disable_storage_object_test.patch
patch unexpectedly ends in middle of line
Steve, Are these lines in comment 1 expected... ...patch unexpectedly ends in middle of line They make me nervous and just want to double check before marking this as verified. I just mocked it locally and installed the resulting rpm, and the patches are being correctly applied despite the warning. I believe it's ok to proceed. assigning to rehana This change is ok because the patches are being applied. These lines in the spec:
/usr/bin/patch -s -p0 -b --suffix --fuzz=0 test/cloudfiles_authentication_test.rb %{PATCH0}
/usr/bin/patch -s -p0 -b --suffix --fuzz=0 test/cloudfiles_connection_test.rb %{PATCH1}
/usr/bin/patch -s -p0 -b --suffix --fuzz=0 test/cloudfiles_storage_object_test.rb %{PATCH2}
result in this output in the build.log:
+ /usr/bin/patch -s -p0 -b --suffix --fuzz=0 test/cloudfiles_authentication_test.rb /builddir/build/SOURCES/disable_test_bad_hostname.patch
+ /usr/bin/patch -s -p0 -b --suffix --fuzz=0 test/cloudfiles_connection_test.rb /builddir/build/SOURCES/disable_faulty_connection_tests.patch
patch unexpectedly ends in middle of line
+ /usr/bin/patch -s -p0 -b --suffix --fuzz=0 test/cloudfiles_storage_object_test.rb /builddir/build/SOURCES/disable_storage_object_test.patch
patch unexpectedly ends in middle of line
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. http://rhn.redhat.com/errata/RHEA-2012-0600.html |