Master Branch Status

Sun Nov 27 23:00:24 GMT 2022

Looks like that file was added  after 8.0.4 was released, so you  
probably need 8.1, and I wonder if the minimum version requirement in  
CMakeLists.txt doesn't need updating.  (I may well misunderstand  
things, but that's what it looks like to me.)

On 2022.11.27 17:41, Brendan Coupe via KMyMoney-devel wrote:
> No sign of the required file in the RPM.
> 
> https://fedora.pkgs.org/37/fedora-x86_64/libalkimia-qt5-devel-8.0.3-9.fc37.x86_64.rpm.html
> 
> On 11/27/22 3:32 PM, Brendan Coupe wrote:
>> I don't see alkversion.h
>> 
>> ls -l /usr/include/alkimia/Qt5/alkimia/
>> total 52K
>> -rw-r--r-- 1 root root 2.7K Jul 21 11:56 alkcompany.h
>> -rw-r--r-- 1 root root  939 Jul 21 11:56 alk_export.h
>> -rw-r--r-- 1 root root 2.6K Jul 21 11:56 alkfinancequoteprocess.h
>> -rw-r--r-- 1 root root 4.4K Jul 21 11:56 alkonlinequote.h
>> -rw-r--r-- 1 root root 3.5K Jul 21 11:56 alkonlinequotesource.h
>> -rw-r--r-- 1 root root 2.9K Jul 21 11:56 alkonlinequotesprofile.h
>> -rw-r--r-- 1 root root 2.2K Jul 21 11:56  
>> alkonlinequotesprofilemanager.h
>> -rw-r--r-- 1 root root 2.2K Jul 21 11:56 alkonlinequoteswidget.h
>> -rw-r--r-- 1 root root  11K Jul 21 11:56 alkvalue.h
>> -rw-r--r-- 1 root root 3.0K Jul 21 11:56 alkwebpage.h
>> 
>> On 11/27/22 2:26 PM, Jack via KMyMoney-devel wrote:
>>> Check the content of the libalkimia-dev package for alkversion.h.   
>>> It might be in an unexpected location.  My libalkimia 8.1.1 has it  
>>> in /usr/include/alkimia/Qt5/alkimia/alkversion.h.  However, it  
>>> looks like KMM requires libalkimia > 5.0, so you should be ok in  
>>> terms of version.
>>> 
>>> (sorry for the other resend.  I has sent this from the wrong  
>>> address and then resent that one thinking I was fixing this one.)
>>> 
>>> On 11/27/22 15:51, Brendan Coupe via KMyMoney-devel wrote:
>>>> qtkeychain-qt5.x86_64 was installed.
>>>> 
>>>> qtkeychain-qt5-devel was not installed. It is now.
>>>> 
>>>> That fixed that problem.
>>>> 
>>>> Then it failed at 15%:
>>>> 
>>>> ==============================================
>>>> 
>>>> [ 15%] Building CXX object  
>>>> kmymoney/mymoney/CMakeFiles/kmm_mymoney.dir/mymoneytransactionfilter.cpp.o
>>>> /usr/local/src/kmm/kmymoney-2022.11.27-13.44.21-GIT-MASTER/kmymoney/mymoney/mymoneymoney.cpp:20:10:  
>>>> fatal error: alkimia/alkversion.h: No such file or directory
>>>>    20 | #include <alkimia/alkversion.h>
>>>>       |          ^~~~~~~~~~~~~~~~~~~~~~
>>>> compilation terminated.
>>>> 
>>>> ==============================================
>>>> 
>>>> dnf list installed | grep alkimia
>>>> libalkimia-doc.noarch 8.0.3-6.fc35 @fedora
>>>> libalkimia-qt5.x86_64 8.0.3-9.fc37 @fedora
>>>> ibalkimia-qt5-devel.x86_64 8.0.3-9.fc37 @fedora
>>>> 
>>>> 
>>>> *Brendan Coupe*
>>>> *3 at Coupe7.com*
>>>> 
>>>> 
>>>> On 2022-11-27 1:09 PM, Jack via KMyMoney-devel wrote:
>>>>> Check for a package for qt5-keychain, perhaps qt5keychain-dev.    
>>>>> The Fedora package name might be different.
>>>>> 
>>>>> On 2022.11.27 14:55, Brendan Coupe via KMyMoney-devel wrote:
>>>>>> I just upgraded to Fedora 37. The 5.1 branch compiles without a  
>>>>>> problem.
>>>>>> 
>>>>>> When I try to compile the Master branch I get the following  
>>>>>> error (I did a test compile before the upgrade to Fedora 37  
>>>>>> which seemed to work fine. I never installed it / ran it so I  
>>>>>> can't be sure it would run).
>>>>>> 
>>>>>> CMake Error at CMakeLists.txt:141 (find_package):
>>>>>>   Could not find a package configuration file provided by  
>>>>>> "Qt5Keychain" with
>>>>>>   any of the following names:
>>>>>> 
>>>>>>     Qt5KeychainConfig.cmake
>>>>>>     qt5keychain-config.cmake
>>>>>> 
>>>>>>   Add the installation prefix of "Qt5Keychain" to  
>>>>>> CMAKE_PREFIX_PATH or set
>>>>>>   "Qt5Keychain_DIR" to a directory containing one of the above  
>>>>>> files.  If
>>>>>>   "Qt5Keychain" provides a separate development package or SDK,  
>>>>>> be sure it
>>>>>>   has been installed.
>>>>>> 
>>>>>> **
>>>>>> *Brendan Coupe*
>>>>>> *3 at Coupe7.com*
>>>>>> 
>>>>>> 
>>>>>> On 11/14/22 2:57 PM, Jack via KMyMoney-devel wrote:
>>>>>>> On 2022.11.14 07:25, Thomas Baumgart via KMyMoney-devel wrote:
>>>>>>>> On Samstag, 12. November 2022 16:48:15 CET Jack via  
>>>>>>>> KMyMoney-devel wrote:
>>>>>>>> > On 11/12/22 09:27, Thomas Baumgart via KMyMoney-devel wrote:
>>>>>>>> > > [snip ...]
>>>>>>>> >
>>>>>>>>> What's the best way to report these issues?  I've put some in  
>>>>>>>>> Issue 61 in invent.kde.org and sent some to the mailing list.  
>>>>>>>>> Do we want to broaden that issue to track all bugs in master,  
>>>>>>>>> or keep that to Ledger related issues and open a separate  
>>>>>>>>> issue for other bugs?
>>>>>>>> 
>>>>>>>> My preference would be to use separate issues for areas, e.g.  
>>>>>>>> ledger, home page (which we both already have) and others. Not  
>>>>>>>> sure what we can do if someone adds a b.k.o entry that rather  
>>>>>>>> fits an issue on invent. Maybe close it on b.k.o and keep a  
>>>>>>>> reference to it in the issue.
>>>>>>> 
>>>>>>> I know of issue 61 for ledger issues.  Issues 16 and 18 (New  
>>>>>>> home screen and New Welcome Page) are more about how things  
>>>>>>> should look that tracking issues with what has already been  
>>>>>>> implemented in master.  So, I don't see any issue for other  
>>>>>>> areas of master development, although I agree that would be a  
>>>>>>> good way to handle this.  Should I start by creating a new  
>>>>>>> issue "New issues with master branch"  which can be for  
>>>>>>> anything that doesn't fit other issues, and then create new  
>>>>>>> issues of specific areas that have more than one item in the  
>>>>>>> general issue?