Bug 1424075 - php-pear-XML-Serializer: FTBFS in rawhide
Summary: php-pear-XML-Serializer: FTBFS in rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: php-pear-XML-Serializer
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Remi Collet
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F26FTBFS
TreeView+ depends on / blocked
 
Reported: 2017-02-17 15:49 UTC by Fedora Release Engineering
Modified: 2017-02-22 11:21 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-22 11:20:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (8.51 KB, text/plain)
2017-02-17 15:49 UTC, Fedora Release Engineering
no flags Details
root.log (89.94 KB, text/plain)
2017-02-17 15:49 UTC, Fedora Release Engineering
no flags Details
state.log (687 bytes, text/plain)
2017-02-17 15:49 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2017-02-17 15:49:19 UTC
Your package php-pear-XML-Serializer failed to build from source in current rawhide.

https://koji.fedoraproject.org/koji/taskinfo?taskID=17781303

For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild

Comment 1 Fedora Release Engineering 2017-02-17 15:49:23 UTC
Created attachment 1253532 [details]
build.log

Comment 2 Fedora Release Engineering 2017-02-17 15:49:26 UTC
Created attachment 1253533 [details]
root.log

Comment 3 Fedora Release Engineering 2017-02-17 15:49:28 UTC
Created attachment 1253534 [details]
state.log

Comment 4 Remi Collet 2017-02-22 11:20:44 UTC
Test broken by XML_Util 1.4.1 (in php-pear)

Fixed by http://pkgs.fedoraproject.org/cgit/php-pear.git/commit/?h=master&id=708a4a047a772197ae408333a2d74302898de0af

Comment 5 Remi Collet 2017-02-22 11:21:13 UTC
Package:    php-pear-XML-Serializer-0.21.0-2.fc26
Status:     complete
Built by:   remi
ID:         852817


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