Bug 1735411

Summary: CPUFreqUtility: FTBFS in Fedora rawhide/f31
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: CPUFreqUtilityAssignee: Fl@sh <alex.mail.1534>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: alex.mail.1534
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-10 09:42:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1700317, 1732841    
Attachments:
Description Flags
build.log
none
root.log
none
state.log none

Description Fedora Release Engineering 2019-07-31 21:16:30 UTC 
CPUFreqUtility failed to build from source in Fedora rawhide/f31

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
Please fix CPUFreqUtility at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
CPUFreqUtility will be orphaned. Before branching of Fedora 32,
CPUFreqUtility will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://fedoraproject.org/wiki/Fails_to_build_from_source
Comment 1 Fedora Release Engineering 2019-07-31 21:16:33 UTC 
Created attachment 1596636 [details]
build.log

file build.log too big, will only attach last 32768 bytes
Comment 2 Fedora Release Engineering 2019-07-31 21:16:35 UTC 
Created attachment 1596637 [details]
root.log

file root.log too big, will only attach last 32768 bytes
Comment 3 Fedora Release Engineering 2019-07-31 21:16:42 UTC 
Created attachment 1596638 [details]
state.log
Comment 4 Fl@sh 2019-08-02 18:47:42 UTC 
Strange behavior on the building...
At F30 building was success:

/usr/bin/cmake -P cmake_install.cmake
-- Install configuration: ""
-- Installing: /builddir/build/BUILDROOT/CPUFreqUtility-1.4.5-7.fc30.x86_64/usr/share/applications/CPUFreqUtility.desktop
-- Installing: /builddir/build/BUILDROOT/CPUFreqUtility-1.4.5-7.fc30.x86_64/usr/bin/CPUFreqUtility
-- Installing: /builddir/build/BUILDROOT/CPUFreqUtility-1.4.5-7.fc30.x86_64/usr/share/knotifications5/CPUFreqUtility.notifyrc
-- Installing: /builddir/build/BUILDROOT/CPUFreqUtility-1.4.5-7.fc30.x86_64/usr/libexec/kf5/kauth/cpu_freq_helper
-- Installing: /builddir/build/BUILDROOT/CPUFreqUtility-1.4.5-7.fc30.x86_64/etc/dbus-1/system.d/org.freedesktop.auth.cpufrequtility.conf
-- Installing: /builddir/build/BUILDROOT/CPUFreqUtility-1.4.5-7.fc30.x86_64/usr/share/dbus-1/system-services/org.freedesktop.auth.cpufrequtility.service
-- Installing: /builddir/build/BUILDROOT/CPUFreqUtility-1.4.5-7.fc30.x86_64/usr/share/polkit-1/actions/org.freedesktop.auth.cpufrequtility.policy
+ popd

At F31 is fail:

Install the project...
/usr/bin/cmake -P cmake_install.cmake
-- Install configuration: ""
-- Installing: /builddir/build/BUILDROOT/CPUFreqUtility-1.4.5-8.fc31.x86_64/usr/share/applications/CPUFreqUtility.desktop
-- Installing: /builddir/build/BUILDROOT/CPUFreqUtility-1.4.5-8.fc31.x86_64/usr/bin/CPUFreqUtility
-- Installing: /builddir/build/BUILDROOT/CPUFreqUtility-1.4.5-8.fc31.x86_64/usr/share/knotifications5/CPUFreqUtility.notifyrc
-- Installing: /builddir/build/BUILDROOT/CPUFreqUtility-1.4.5-8.fc31.x86_64/usr/libexec/kf5/kauth/cpu_freq_helper
-- Installing: /builddir/build/BUILDROOT/CPUFreqUtility-1.4.5-8.fc31.x86_64/usr/share/dbus-1/system.d/org.freedesktop.auth.cpufrequtility.conf
-- Installing: /builddir/build/BUILDROOT/CPUFreqUtility-1.4.5-8.fc31.x86_64/usr/share/dbus-1/system-services/org.freedesktop.auth.cpufrequtility.service
-- Installing: /builddir/build/BUILDROOT/CPUFreqUtility-1.4.5-8.fc31.x86_64/usr/share/polkit-1/actions/org.freedesktop.auth.cpufrequtility.policy
~/build/BUILD/CPUFreqUtility-1.4.5

The changes in path for */dbus-1/system.d/org.freedesktop.auth.cpufrequtility.conf  

In first case %{_sysconfdir} is equal the /etc? but in second is /usr

What is happen?
Comment 5 Fl@sh 2019-08-02 18:48:46 UTC 
Sorry:
...is equal the /etc, but in second is /usr .
Comment 6 Ben Cotton 2019-08-13 16:50:27 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.
Comment 7 Ben Cotton 2019-08-13 17:58:43 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.
Comment 8 Fedora Release Engineering 2019-09-22 04:27:10 UTC 
Dear Maintainer,

your package has not been built successfully in 31. Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. Following the latest policy for such packages [2], your package
can be orphaned if this bug remains in NEW state more than 8 weeks.

A week before the mass branching of Fedora 32 according to the schedule [3],
any packages which still have open FTBFS bugs from Fedora 31 will be retired.

[1] https://fedoraproject.org/wiki/Updates_Policy
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedoraproject.org/wiki/Releases/32/Schedule
Comment 9 Fedora Release Engineering 2019-09-29 04:26:47 UTC 
Dear Maintainer,

your package has not been built successfully in 31. Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. Following the latest policy for such packages [2], your package
can be orphaned if this bug remains in NEW state more than 8 weeks.

A week before the mass branching of Fedora 32 according to the schedule [3],
any packages which still have open FTBFS bugs from Fedora 31 will be retired.

[1] https://fedoraproject.org/wiki/Updates_Policy
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedoraproject.org/wiki/Releases/32/Schedule
Comment 10 Fedora Release Engineering 2019-10-06 04:23:52 UTC 
Dear Maintainer,

your package has not been built successfully in 31. Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. Following the latest policy for such packages [2], your package
can be orphaned if this bug remains in NEW state more than 8 weeks.

A week before the mass branching of Fedora 32 according to the schedule [3],
any packages which still have open FTBFS bugs from Fedora 31 will be retired.

[1] https://fedoraproject.org/wiki/Updates_Policy
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedoraproject.org/wiki/Releases/32/Schedule
Comment 11 Fl@sh 2019-10-10 09:42:28 UTC 
not have a time... orphaned.