Package Details: extension-manager 0.4.2-1

Git Clone URL: (read-only, click to copy)
Package Base: extension-manager
Description: A native tool for browsing, installing, and managing GNOME Shell Extensions
Upstream URL:
Licenses: GPL3
Submitter: igor-dyatlov
Maintainer: igor-dyatlov
Last Packager: igor-dyatlov
Votes: 41
Popularity: 1.31
First Submitted: 2022-01-09 15:20 (UTC)
Last Updated: 2023-06-29 14:45 (UTC)

Latest Comments

1 2 3 4 Next › Last »

doppelhelix commented on 2023-12-02 17:37 (UTC)

Just in case you update this package to 0.4.3

libbacktrace is now optional.

Just extend build() from

arch-meson $pkgname-$pkgver build


arch-meson $pkgname-$pkgver build -Dbacktrace=false


redw0rm commented on 2023-06-01 09:13 (UTC)

@Maybelline Thankyou so much. I dont know why , but removing the python-argparse package did solve the issue.

Maybelline commented on 2023-05-17 23:27 (UTC)

I cannot be defeated! I resorted to debugging with print() statements, and it turns out that I needed to remove python-argparse for some reason. Once I removed that package, it ran just fine. @dmark04 you might try that. Many thanks to you, @duffydack.

duffydack commented on 2023-05-17 21:10 (UTC) (edited on 2023-05-17 21:10 (UTC) by duffydack)

Yours seems to fail around the blueprint part. Mine succeeds,

Build targets in project: 39

extension-manager 0.4.0

  User defined options
    auto_features: enabled
    buildtype    : plain
    libexecdir   : lib
    prefix       : /usr
    sbindir      : bin
    wrap_mode    : nodownload
    b_lto        : true
    b_pie        : true

Found ninja-1.11.1 at /usr/bin/ninja
INFO: autodetecting backend as ninja                                                                
INFO: calculating backend command to run: /usr/bin/ninja -C /home/dd/extension-manager/src/build
ninja: Entering directory `/home/dd/extension-manager/src/build'
[33/68] Generating src/blueprints with a custom command
upgrade: Use type syntax here (introduced in blueprint 0.8.0)
at ../extension-manager-0.4.1/src/exm-window.blp line 4 column 10:
   4 |template ExmWindow : Adw.ApplicationWindow {
     |         ^

upgrade: Use the '$' extern syntax introduced in blueprint 0.8.0
at ../extension-manager-0.4.1/src/exm-window.blp line 43 column 16:
  43 |                        child: .ExmInstalledPage installed_page {};
     |               ^

What version of blueprint-compiler do you have? Generally, if you can't build something, you try another system or a clean chroot to rule out your system. Something on your system is problematic.

Maybelline commented on 2023-05-17 20:54 (UTC) (edited on 2023-05-17 20:57 (UTC) by Maybelline)

@duffydack Thanks, I think that's the culprit. Correct me if I'm mistaken, but I believe these are the steps you tried:

  1. cd /tmp
  2. git clone
  3. cd /tmp/extension-manager
  4. makepkg -sr

When I do the above, the output looks like this so I'm just struggling to see where my process differs from yours. I see interesting parts like extension-manager 0.4.0 (when I'm expecting 0.4.1) but it doesn't seem to bother the compilation until it looks for that exm-window.ui file, and I can't seem to put my finger on where that comes from.

I realize I've burdened you quite a bit, but maybe this will help shine a light for others to see a difference that I'm failing to see.

duffydack commented on 2023-05-17 19:40 (UTC) (edited on 2023-05-17 19:42 (UTC) by duffydack)

@Maybelline I have the file.

❯ find . -iname 'exm-window.ui' 
❯ grep -R exm-window.ui
src/extension-manager-0.4.1/src/exm.gresource.xml:    <file>exm-window.ui</file>
src/extension-manager-0.4.1/src/exm-window.c:    gtk_widget_class_set_template_from_resource (widget_class, "/com/mattjakeman/ExtensionManager/exm-window.ui");
grep: src/build/src/extension-manager: binary file matches
grep: src/build/.ninja_deps: binary file matches
grep: pkg/extension-manager/usr/bin/extension-manager: binary file matches

That's just a basic git clone and makepkg -sr

Maybelline commented on 2023-05-17 18:46 (UTC)

@duffydack or @pezz could you confirm that after you build in your chroot you're seeing the same contents that I am? Namely, after you build, could you run find ./extension-manager -iname 'exm-window.ui' and then also grep -R exm-window.ui to see if you're also seeing references to exm-window.ui, but do not have the file? I think that's the missing piece for my build, so I'm trying to narrow down where our paths diverge.

I'm sorry to keep nagging, but I'm worried that this isn't going to resolve itself naturally. Appreciated!

duffydack commented on 2023-05-13 09:13 (UTC) (edited on 2023-05-13 09:15 (UTC) by duffydack)

@all, It builds fine in a chroot (I use aurutils), I also just did a build in my gnome VM. Needed to install gcc and pkgconf, makepkg -sc built ok. ¯\_(ツ)_/¯

dmark04 commented on 2023-05-13 09:03 (UTC)

@pezz for me the error of being unable to locate "exm-window.ui" persists even after manually installing text-engine and libbacktrace-git Both using yay and manually makepkg -si

pezz commented on 2023-05-13 01:35 (UTC) (edited on 2023-05-13 01:36 (UTC) by pezz)

makepkg doesn't install AUR dependencies, so perhaps your system is missing something.

I'd check if you have text-engine and libbacktrace-git installed before trying makepkg.

The culprit still could be yay not resolving and installing deps properly.