Arch Linux User Repository

@yochananmarqos sorry this seems to be more a blueprint-compiler issue. I tried installing blueprint-compiler seperately and installation worked but not execution.

@Scotty_Trees: That info is for application developers, not packagers.

@jonas-w: I can't reproduce it with blueprint-compiler 0.2.0-1.

Can't get it to build. Something with blueprint-compiler, maybe this has something to do with that in the previous comment? [10/56] Generating src/blueprints with a custom command FAILED: src /sbin/blueprint-compiler batch-compile src/. ../extension-manager-0.3.1/src ../extension-manager-0.3.1/src/exm-window.blp ../extension-manager-0.3.1/src/exm-installed-page.blp ../extension-manager-0.3.1/src/exm-browse-page.blp ../extension-manager-0.3.1/src/exm-extension-row.blp ../extension-manager-0.3.1/src/exm-search-row.blp ../extension-manager-0.3.1/src/exm-detail-view.blp ../extension-manager-0.3.1/src/exm-screenshot.blp ../extension-manager-0.3.1/src/exm-comment-tile.blp ../extension-manager-0.3.1/src/exm-comment-dialog.blp ../extension-manager-0.3.1/src/exm-rating.blp ../extension-manager-0.3.1/src/exm-release-notes-dialog.blp Traceback (most recent call last): File "/sbin/blueprint-compiler", line 35, in <module> from blueprintcompiler import main ModuleNotFoundError: No module named 'blueprintcompiler' [19/56] Generating src/exm-enums.h with a custom co...cause command contains newlines, to capture output ninja: build stopped: subcommand failed. ==> ERROR: A failure occurred in build(). Aborting... -> error making: extension-manager

From upstream James Westman announces:

I’ve released blueprint-compiler v0.2.0, the first tagged release! If you’re using blueprint in a project, I highly recommend using this tag instead of the main branch, to avoid any breakage as the language develops toward 1.0. You can do this with "tag": "v0.2.0" in your flatpak manifest and revision = v0.2.0 in blueprint-compiler.wrap.

Just build this on arm (m1 macbook) by adding aarch64 as supported, so it would be nice if you could change arch=('x86_64') to arch=('x86_64' 'aarch64')

@Scotty_Trees: This is not an application build error. Upstream bug (conflicts with cozy-audiobooks, they use the settings-symbolic.svg icon)

Today's update (v0.3.0-1) fails to build. I hope this can be fixed, I tried to cleanbuild, but still got the following error, would appreciate any help, thank you kindly:

error: failed to commit transaction (conflicting files)
extension-manager: /usr/share/icons/hicolor/scalable/actions/settings-symbolic.svg exists in filesystem (owned by cozy-audiobooks)
Errors occurred, no packages were upgraded.
 -> exit status 1

Failed installation, need to install package blueprint-compiler-git first. Then works fine.

Building v0.2.1-1 fails:

FAILED: src /usr/bin/blueprint-compiler batch-compile src/. ../extension-manager-0.2.1/src ../extension-manager-0.2.1/src/gtk/help-overlay.blp ../extension-manager-0.2.1/src/exm-window.blp ../extension-manager-0.2.1/src/exm-installed-page.blp ../extension-manager-0.2.1/src/exm-browse-page.blp ../extension-manager-0.2.1/src/exm-extension-row.blp ../extension-manager-0.2.1/src/exm-search-row.blp ../extension-manager-0.2.1/src/exm-detail-view.blp ../extension-manager-0.2.1/src/exm-screenshot.blp
error: Cannot assign Gtk.StringList to Gio.ListModel
at ../extension-manager-0.2.1/src/exm-browse-page.blp line 31 column 8: 31 | model: StringList {
| ^
ninja: build stopped: subcommand failed.
==> FEHLER: Ein Fehler geschah in build().

I'm waiting for the new update :)