[Craft] [Bug 484633] Craft was unable to find alkimia
https://bugs.kde.org/show_bug.cgi?id=484633 --- Comment #7 from Thomas Baumgart --- 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-0extragear/alkimia/alkimia.py [from: extragear/libalkimia/libalkimia.py - 100% similarity] M +1-1extragear/kmymoney/kmymoney.py https://invent.kde.org/packaging/craft-blueprints-kde/-/commit/3a3e2ab518773cb786410c34a3a781fd70b9e3cd -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 484633] Craft was unable to find alkimia
https://bugs.kde.org/show_bug.cgi?id=484633 --- Comment #6 from Ralf Habacker --- 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 -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 484633] Craft was unable to find alkimia
https://bugs.kde.org/show_bug.cgi?id=484633 --- Comment #5 from Ingo Klöcker --- (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. -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 484633] Craft was unable to find alkimia
https://bugs.kde.org/show_bug.cgi?id=484633 --- Comment #4 from Ralf Habacker --- (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 -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 484633] Craft was unable to find alkimia
https://bugs.kde.org/show_bug.cgi?id=484633 --- Comment #3 from Ralf Habacker --- (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? -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 484633] Craft was unable to find alkimia
https://bugs.kde.org/show_bug.cgi?id=484633 Ralf Habacker changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/pack ||aging/craft-blueprints-kde/ ||-/commit/6edcad1d52573d6c31 ||1eb105434f1e63fb4a8836 Resolution|--- |FIXED --- Comment #2 from Ralf Habacker --- 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-0extragear/alkimia/alkimia.py [from: extragear/libalkimia/libalkimia.py - 100% similarity] M +1-1extragear/kmymoney/kmymoney.py https://invent.kde.org/packaging/craft-blueprints-kde/-/commit/6edcad1d52573d6c311eb105434f1e63fb4a8836 -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 484633] Craft was unable to find alkimia
https://bugs.kde.org/show_bug.cgi?id=484633 Ingo Klöcker changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||kloec...@kde.org --- Comment #1 from Ingo Klöcker --- 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. -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 484633] Craft was unable to find alkimia
https://bugs.kde.org/show_bug.cgi?id=484633 Ralf Habacker changed: What|Removed |Added Product|libalkimia |Craft Component|CI |Blueprints Assignee|kmymoney-de...@kde.org |vonr...@kde.org CC||kde-wind...@kde.org -- You are receiving this mail because: You are watching all bug changes.
