Bug 484633 - Craft was unable to find alkimia
Summary: Craft was unable to find alkimia
Status: RESOLVED FIXED
Alias: None
Product: Craft
Classification: Developer tools
Component: Blueprints (show other bugs)
Version: master
Platform: Other Other
: NOR normal
Target Milestone: ---
Assignee: Hannah von Reth
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-27 22:35 UTC by Ralf Habacker
Modified: 2024-04-14 13:41 UTC (History)
2 users (show)

See Also:
Latest Commit: https://invent.kde.org/packaging/craft-blueprints-kde/-/commit/6edcad1d52573d6c311eb105434f1e63fb4a8836
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ralf Habacker 2024-03-27 22:35:58 UTC 
SUMMARY

On CI the job https://invent.kde.org/habacker/alkimia/-/jobs/1689986#L114  failed to build.

STEPS TO REPRODUCE
1. inspect https://invent.kde.org/habacker/alkimia/-/jobs/1689986#L114 

OBSERVED RESULT
The last executed command: 

$ Run-CraftMaster -c --install-deps --options "[CodeSigning]Enabled=False" $env:CI_PROJECT_NAME
CraftMaster Arguments: craftmaster/CraftMaster.py --config ci-utilities/craft/qt5/CraftConfig.ini --config-override C:\builds\habacker\alkimia/src/.craft.ini --target windows-msvc2019_64-cl -c --install-deps --options [CodeSigning]Enabled=False alkimia

used 'alkimia' as package name, but the actual name is libalkimia as mentioned in the log.

Craft was unable to find alkimia, similar packages are:
extragear/libalkimia
    Name: libalkimia
    BlueprintPath: C:\gitlab\craft\blueprints\craft-blueprints-kde\extragear\libalkimia\libalkimia.py
    Homepage: 
    Description: A library with common classes and functionality used by finance applications for the KDE SC.
    Tags: 
    Options: args=, branch=(str), buildStatic=(bool), buildTests=True, buildType=RelWithDebInfo, featureArguments=, ignored=(bool), patchLevel=(int), revision=(str), srcDir=(str), version=(str)
    Latest version: 8.1.2
    Installed versions: None
    Installed revision: None
    Available versions: master, 7.0.2, 8.0.4, 8.1.1, 8.1.2

EXPECTED RESULT
The build should not fail

SOFTWARE/OS VERSIONS
Linux: KDE-CI System
Comment 1 Ingo Klöcker 2024-03-28 07:27:59 UTC 
The CI templates expect that the project name "alkimia" matches the name of the Craft blue print. (How else should they know the name of the blue print?) Unfortunately, the blue print is named "libalkimia" (probably for historic reasons). You have to rename the blue print and all references to it to make the the CI templates work for alkimia.
Comment 2 Ralf Habacker 2024-03-28 07:57:07 UTC 
Git commit 6edcad1d52573d6c311eb105434f1e63fb4a8836 by Ralf Habacker.
Committed on 28/03/2024 at 07:56.
Pushed by habacker into branch 'master'.

[alkimia] Fix bug that CI templates cannot find alkimia

The CI templates determine the blueprint name from the project name,
which did not match.

R  +0    -0    extragear/alkimia/alkimia.py [from: extragear/libalkimia/libalkimia.py - 100% similarity]
M  +1    -1    extragear/kmymoney/kmymoney.py

https://invent.kde.org/packaging/craft-blueprints-kde/-/commit/6edcad1d52573d6c311eb105434f1e63fb4a8836
Comment 3 Ralf Habacker 2024-03-28 08:01:12 UTC 
(In reply to Ingo Klöcker from comment #1)
> You have to rename the blue print and all references to it to make the the CI templates work for alkimia.

Thanks for your investigation

I still have a question about the next steps: How do the updated blueprints get into the CI images that are used for building?
Comment 4 Ralf Habacker 2024-03-28 08:03:25 UTC 
(In reply to Ralf Habacker from comment #3)
> I still have a question about the next steps: How do the updated blueprints
> get into the CI images that are used for building?

I ask because I had the case in another ticket that they are not updated by default, https://bugs.kde.org/show_bug.cgi?id=484507
Comment 5 Ingo Klöcker 2024-03-28 08:12:53 UTC 
(In reply to Ralf Habacker from comment #3)
> (In reply to Ingo Klöcker from comment #1)
> > You have to rename the blue print and all references to it to make the the CI templates work for alkimia.
> 
> Thanks for your investigation
> 
> I still have a question about the next steps: How do the updated blueprints
> get into the CI images that are used for building?

(In reply to Ralf Habacker from comment #4)
> (In reply to Ralf Habacker from comment #3)
> > I still have a question about the next steps: How do the updated blueprints
> > get into the CI images that are used for building?

Automatically.

> I ask because I had the case in another ticket that they are not updated by
> default, https://bugs.kde.org/show_bug.cgi?id=484507

I think in this case the problem was/is that a patch was added to the blueprint of kdevelop, but the patch level of kdevelop wasn't set/increased. Craft uses the patch level to determine if a build can be taken from the cache or if it needs to be rebuilt.
Comment 6 Ralf Habacker 2024-03-28 08:34:10 UTC 
Git commit d7f3720d28e8456e465180e5a567a60da207fd28 by Ralf Habacker.
Committed on 28/03/2024 at 08:33.
Pushed by habacker into branch 'master'.

Adjust project name for alkimia

The renaming was necessary to meet the expectations of the CI templates

M  +2    -2    .craft.ini

https://invent.kde.org/office/kmymoney/-/commit/d7f3720d28e8456e465180e5a567a60da207fd28
Comment 7 Thomas Baumgart 2024-04-14 13:41:45 UTC 
Git commit 3a3e2ab518773cb786410c34a3a781fd70b9e3cd by Thomas Baumgart.
Committed on 14/04/2024 at 13:41.
Pushed by tbaumgart into branch 'qt5-lts'.

[alkimia] Fix bug that CI templates cannot find alkimia

The CI templates determine the blueprint name from the project name,
which did not match.
(cherry picked from commit 6edcad1d52573d6c311eb105434f1e63fb4a8836)

R  +0    -0    extragear/alkimia/alkimia.py [from: extragear/libalkimia/libalkimia.py - 100% similarity]
M  +1    -1    extragear/kmymoney/kmymoney.py

https://invent.kde.org/packaging/craft-blueprints-kde/-/commit/3a3e2ab518773cb786410c34a3a781fd70b9e3cd