Package Details: extension-manager 0.5.1-5

Git Clone URL: https://aur.archlinux.org/extension-manager.git (read-only, click to copy)
Package Base: extension-manager
Description: A native tool for browsing, installing, and managing GNOME Shell Extensions
Upstream URL: https://github.com/mjakeman/extension-manager
Licenses: GPL-3.0-or-later
Submitter: igor-dyatlov
Maintainer: bill88t
Last Packager: bill88t
Votes: 51
Popularity: 1.90
First Submitted: 2022-01-09 15:20 (UTC)
Last Updated: 2024-09-16 16:23 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

DenalB commented on 2024-03-19 13:11 (UTC) (edited on 2024-03-19 13:12 (UTC) by DenalB)

Just wanted to install this package and got the following error messages:

Fehler: Der Vorgang konnte nicht durchgeführt werden (In Konflikt stehende Dateien)
gobject-introspection-runtime: /usr/lib/girepository-1.0/GLib-2.0.typelib existiert im Dateisystem (gehört zu glib2)
gobject-introspection-runtime: /usr/lib/girepository-1.0/GModule-2.0.typelib existiert im Dateisystem (gehört zu glib2)
gobject-introspection-runtime: /usr/lib/girepository-1.0/GObject-2.0.typelib existiert im Dateisystem (gehört zu glib2)
gobject-introspection-runtime: /usr/lib/girepository-1.0/Gio-2.0.typelib existiert im Dateisystem (gehört zu glib2)
gobject-introspection: /usr/share/gir-1.0/GLib-2.0.gir existiert im Dateisystem (gehört zu glib2)
gobject-introspection: /usr/share/gir-1.0/GModule-2.0.gir existiert im Dateisystem (gehört zu glib2)
gobject-introspection: /usr/share/gir-1.0/GObject-2.0.gir existiert im Dateisystem (gehört zu glib2)
gobject-introspection: /usr/share/gir-1.0/Gio-2.0.gir existiert im Dateisystem (gehört zu glib2)
Fehler sind aufgetreten, keine Pakete wurden aktualisiert.
 -> error installing repo packages
error installing repo packages

Any idea what I could do now?

nikelborm commented on 2023-12-29 04:12 (UTC)

Errors are being thrown. That's the word I've learned from typescript programming language. I know nothing more.

doppelhelix commented on 2023-12-28 19:58 (UTC) (edited on 2023-12-28 20:00 (UTC) by doppelhelix)

@nikelborm: Fixed in upstream. Try the git version (see https://github.com/mjakeman/extension-manager/pull/534 )

P.S. Usually they "trow" themself very violently in your face!

yochananmarqos commented on 2023-12-28 19:38 (UTC)

@nikelborm: That's an upstream issue, not a packaging issue.

P.S. How do errors "throw"?

nikelborm commented on 2023-12-28 18:18 (UTC)

During build it throws an error when running tests:

[69/69] Linking target src/extension-manager
==> Starting check()...
ninja: Entering directory `/home/nikel/.cache/yay/extension-manager/src/build'
ninja: no work to do.
1/3 Validate desktop file          OK              0.02s
2/3 Validate schema file           OK              0.01s
3/3 Validate appstream file        FAIL            0.01s   exit status 1
>>> ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=248 /sbin/appstreamcli validate --nonet --explain data/com.mattjakeman.ExtensionManager.metainfo.xml
―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― ✀  ――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
stdout:
Unknown option --nonet
stderr:
Run 'appstreamcli --help' to see a list of available commands and options, and 'appstreamcli validate --help' to see a list of options specific for this subcommand.
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――


Summary of Failures:

3/3 Validate appstream file FAIL            0.01s   exit status 1

Ok:                 2   
Expected Fail:      0   
Fail:               1   
Unexpected Pass:    0   
Skipped:            0   
Timeout:            0   

Full log written to /home/nikel/.cache/yay/extension-manager/src/build/meson-logs/testlog.txt
==> Entering fakeroot environment...

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

to

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

see

https://github.com/mjakeman/extension-manager/pull/434#pullrequestreview-1513582623

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 https://aur.archlinux.org/extension-manager.git
  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.

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »