Bug 1307850 - perl-Gtk3: FTBFS in rawhide
Summary: perl-Gtk3: FTBFS in rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Gtk3
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Pisar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1303926
Blocks: F24FTBFS
TreeView+ depends on / blocked
 
Reported: 2016-02-13 22:00 UTC by Fedora Release Engineering
Modified: 2016-02-18 07:56 UTC (History)
4 users (show)

Fixed In Version: perl-Gtk3-0.025-2.fc24
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-18 07:56:14 UTC
Type: ---

Attachments (Terms of Use)
build.log (7.62 KB, text/plain)
2016-02-13 22:00 UTC, Fedora Release Engineering 		no flags Details
root.log (114.90 KB, text/plain)
2016-02-13 22:00 UTC, Fedora Release Engineering 		no flags Details
state.log (629 bytes, text/plain)
2016-02-13 22:00 UTC, Fedora Release Engineering 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Fedora Release Engineering 2016-02-13 22:00:18 UTC 
Your package perl-Gtk3 failed to build from source in current rawhide.

http://koji.fedoraproject.org/koji/taskinfo?taskID=12850260

For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild
Comment 1 Fedora Release Engineering 2016-02-13 22:00:21 UTC 
Created attachment 1125611 [details]
build.log
Comment 2 Fedora Release Engineering 2016-02-13 22:00:23 UTC 
Created attachment 1125612 [details]
root.log
Comment 3 Fedora Release Engineering 2016-02-13 22:00:25 UTC 
Created attachment 1125613 [details]
state.log
Comment 4 Mamoru TASAKA 2016-02-18 04:57:24 UTC 
Now koji has gtk3-3.19.9-1.fc24 and scratch build of perl-Gtk3 seems okay:
http://koji.fedoraproject.org/koji/taskinfo?taskID=13029980
Comment 5 Upstream Release Monitoring 2016-02-18 07:53:54 UTC 
ppisar's perl-Gtk3-0.025-2.fc24 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=726188
Note You need to log in before you can comment on or make changes to this bug.