Bug 1270291 - [epel7s390x] php-pecl-solr2 SRPM does not build correctly on s390x
Summary: [epel7s390x] php-pecl-solr2 SRPM does not build correctly on s390x
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: php-pecl-solr2
Version: epel7
Hardware: s390x
OS: Linux
high
medium
Target Milestone: ---
Assignee: Remi Collet
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: epel7s390x
TreeView+ depends on / blocked
 
Reported: 2015-10-09 14:13 UTC by IBM Bug Proxy
Modified: 2015-12-02 17:20 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-12-02 17:20:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
php-pecl-solr2 build log (63.95 KB, text/plain)
2015-10-09 14:13 UTC, IBM Bug Proxy
no flags Details


Links
System ID Private Priority Status Summary Last Updated
IBM Linux Technology Center 131556 0 None None None Never

Description IBM Bug Proxy 2015-10-09 14:13:16 UTC

Comment 1 IBM Bug Proxy 2015-10-09 14:13:18 UTC
The EPEL 7 SRPM for php-pecl-solr2 
https://dl.fedoraproject.org/pub/epel/7/SRPMS/p/php-pecl-solr2-2.1.0-1.el7.src.rpm
does not build correctly in Mock on s390x.

Build fails due to a singular test program, does not specify reason or line number.

FAIL SolrUtils::escapeQueryChars() - Testing Lucene Reserved Characters [tests/080.solrutils_escapequerychars.phpt]

Comment 2 IBM Bug Proxy 2015-10-09 14:13:22 UTC
Created attachment 1081350 [details]
php-pecl-solr2 build log

Comment 3 Remi Collet 2015-10-09 14:24:28 UTC
Please version 2.2.0-2 in epel-testing which have some "bigendian" fix.

Comment 4 Remi Collet 2015-12-02 09:22:47 UTC
@joseph: can you check with 2.3.0 ?

Comment 5 IBM Bug Proxy 2015-12-02 17:10:58 UTC
------- Comment From hannsj_uhl.com 2015-12-02 17:07 EDT-------
Comment from  Mohammad Zaman 2015-12-02 11:57:19 EST

Tested with php-pecl-solr2-2.3.0-1.el7.src.rpm. Package built successfully.

Comment 6 Remi Collet 2015-12-02 17:20:02 UTC
Fixed, so I close


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