Bug 1423306 - conky: FTBFS in rawhide
Summary: conky: FTBFS in rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: conky
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Lichvar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F26FTBFS
TreeView+ depends on / blocked
 
Reported: 2017-02-17 03:33 UTC by Fedora Release Engineering
Modified: 2017-02-20 15:57 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-02-20 15:57:51 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (168.12 KB, text/plain)
2017-02-17 03:33 UTC, Fedora Release Engineering 		no flags Details
root.log (110.83 KB, text/plain)
2017-02-17 03:33 UTC, Fedora Release Engineering 		no flags Details
state.log (615 bytes, text/plain)
2017-02-17 03:33 UTC, Fedora Release Engineering 		no flags Details
View All

Description Fedora Release Engineering 2017-02-17 03:33:46 UTC 
Your package conky failed to build from source in current rawhide.

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

For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild
Comment 1 Fedora Release Engineering 2017-02-17 03:33:51 UTC 
Created attachment 1251669 [details]
build.log
Comment 2 Fedora Release Engineering 2017-02-17 03:33:55 UTC 
Created attachment 1251670 [details]
root.log
Comment 3 Fedora Release Engineering 2017-02-17 03:33:57 UTC 
Created attachment 1251671 [details]
state.log
Comment 4 Ralf Corsepius 2017-02-20 08:03:38 UTC 
This FTBFS seems to be caused by a missing include:

diff -Naur conky-1.10.4.orig/src/luamm.hh conky-1.10.4/src/luamm.hh
--- conky-1.10.4.orig/src/luamm.hh      2016-07-20 18:53:48.000000000 +0200
+++ conky-1.10.4/src/luamm.hh   2017-02-20 08:40:13.196709403 +0100
@@ -26,6 +26,7 @@
 #include <memory>
 #include <mutex>
 #include <stdexcept>
+#include <functional>

 #include <lua.hpp>
Comment 5 Miroslav Lichvar 2017-02-20 15:57:51 UTC 
It should be fixed now. Thanks for the patch, Ralf.
Note You need to log in before you can comment on or make changes to this bug.