Package Details: gnome-shell-extension-gtile-git 53.r0.g138a98c-1

Git Clone URL: https://aur.archlinux.org/gnome-shell-extension-gtile-git.git (read-only, click to copy)
Package Base: gnome-shell-extension-gtile-git
Description: A window tiling extension for GNOME
Upstream URL: https://github.com/gTile/gTile
Keywords: extension gnome tiling
Licenses: GPL-2.0-or-later
Conflicts: gnome-shell-extension-gtile
Provides: gnome-shell-extension-gtile
Submitter: Revelation60
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 8
Popularity: 0.164390
First Submitted: 2020-02-16 17:28 (UTC)
Last Updated: 2024-02-29 15:03 (UTC)

Latest Comments

1 2 3 Next › Last »

zed123 commented on 2023-03-05 08:32 (UTC)

Ok. This worked. Also with AUR helper pikaur. Just need to execute it twice and update the PKGBUILD before the second build.

yochananmarqos commented on 2023-02-20 22:31 (UTC)

@zed123: It's just a hacky workaround for now. The hash apparently won't be the same as I used in the PKGBUILD. Check your bazel-cache folder. Edit the PKGBUILD as follows to match the folder name indicated by <change me>:

  # Temporary workaround for tarball not being copied properly from cache
  bsdtar -xvf "$srcdir/bazel-cache/<change me>/execroot/_main/bazel-out/k8-fastbuild/bin/dist.tar.gz" -C \
    "$pkgdir/usr/share/gnome-shell/extensions/gTile@vibou/"

Either way, for now you can install gtile from the Arch community repository until the issue with Bazel 6 is sorted upstream. The upstream "fix" doesn't seem to apply here.

zed123 commented on 2023-02-20 21:48 (UTC)

Still doesn't work for me:

==> Starting build()... Starting local Bazel server and connecting to it... INFO: Analyzed target //:install-extension (68 packages loaded, 407 targets configured). INFO: Found 1 target... Target //:install-extension up-to-date: bazel-bin/install-extension INFO: Elapsed time: 28.886s, Critical Path: 1.01s INFO: 1 process: 1 internal. INFO: Build completed successfully, 1 total action ==> Entering fakeroot environment... ==> Starting package()... bsdtar: Error opening archive: Failed to open '/home/fubar/.cache/pikaur/build/gnome-shell-extension-gtile-git/src/bazel-cache/0b5fc7d4bbd34f8962010e75d3c172c0/execroot/_main/bazel-out/k8-fastbuild/bin/dist.tar.gz' ==> ERROR: A failure occurred in package(). Aborting...

zed123 commented on 2023-02-20 03:53 (UTC)

Is someone able to install the package?

==> Starting build()... Extracting Bazel installation... Starting local Bazel server and connecting to it... DEBUG: Rule 'aspect_rules_js~override' indicated that a canonical reproducible form can be obtained by modifying arguments shallow_since = "1673821223 -0800" DEBUG: Repository aspect_rules_js~override instantiated at: callstack not available Repository rule git_repository defined at: /home/fubar/.cache/pikaur/build/gnome-shell-extension-gtile-git/src/bazel-cache/1f4b54fc4e03eceeb380509f564bcf57/external/bazel_tools/tools/build_defs/repo/git.bzl:176:33: in <toplevel> INFO: Analyzed target //:install-extension (68 packages loaded, 407 targets configured). INFO: Found 1 target... INFO: From Rollup bundle.js:

entry.js → bundle.js... created bundle.js in 331ms Target //:install-extension up-to-date: bazel-bin/install-extension INFO: Elapsed time: 56.809s, Critical Path: 5.96s INFO: 77 processes: 35 internal, 13 linux-sandbox, 19 local, 10 worker. INFO: Build completed successfully, 77 total actions ==> Entering fakeroot environment... ==> Starting package()... bsdtar: Error opening archive: Failed to open 'bazel-bin/install-extension.runfiles/gtile/dist.tar.gz' ==> ERROR: A failure occurred in package(). Aborting...

It should be fixed, but I still get the error:

https://github.com/gTile/gTile/issues/314

yochananmarqos commented on 2022-04-12 16:32 (UTC)

@clfarron4: Aha, build_tar is indeed a Python script.

clfarron4 commented on 2022-04-11 19:32 (UTC) (edited on 2022-04-11 19:33 (UTC) by clfarron4)

Please could 'python' be added to the makedepends? I just received the below.

Extracting Bazel installation... Starting local Bazel server and connecting to it... Loading: Loading: 0 packages loaded Loading: 0 packages loaded Loading: 0 packages loaded Loading: 0 packages loaded Loading: 0 packages loaded Loading: 0 packages loaded Loading: 0 packages loaded Loading: 0 packages loaded Loading: 0 packages loaded Loading: 0 packages loaded Analyzing: target //:install-extension (1 packages loaded, 0 targets configured) INFO: Analyzed target //:install-extension (85 packages loaded, 1040 targets configured). INFO: Found 1 target... [0 / 43] [Prepa] Symlinking //:install-extension ... (9 actions, 0 running) INFO: From Bundling JavaScript bundle.js [rollup]:

bazel-out/k8-fastbuild/bin/entry.mjs → bazel-out/k8-fastbuild/bin/bundle.js... created bazel-out/k8-fastbuild/bin/bundle.js in 211ms ERROR: /build/gnome-shell-extension-gtile-git/src/gnome-shell-extension-gtile/BUILD.bazel:26:8: PackageTar dist.tar.gz failed: (Exit 127): build_tar failed: error executing command bazel-out/host/bin/external/bazel_tools/tools/build_defs/pkg/build_tar --flagfile bazel-out/k8-fastbuild/bin/dist.args

Use --sandbox_debug to see verbose messages from the sandbox /usr/bin/env: 'python3': No such file or directory Target //:install-extension failed to build Use --verbose_failures to see the command lines of failed build steps. INFO: Elapsed time: 34.834s, Critical Path: 2.15s INFO: 77 processes: 56 internal, 2 linux-sandbox, 19 worker. FAILED: Build did NOT complete successfully FAILED: Build did NOT complete successfully ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Build failed, check /ccm/buildroot/claire/build

Many Thanks,

Claire

nonshankus commented on 2022-03-25 20:42 (UTC) (edited on 2022-03-25 20:43 (UTC) by nonshankus)

@Revelation60: Wow, that was fast. Thank you very much! Your changes did the trick and the installation now works flawlessly.

Also thanks for pointing out the "flagging out of date of VCS packages". I actually read the hint when flagging the package out of date, but after reading it again I think I finally got it.

yochananmarqos commented on 2022-03-25 19:31 (UTC)

@nonshankus: Sorry, thought I tested it the last time I updated this. It's fixed now.

FYI, "VCS packages are not considered out of date when the pkgver changes, do not flag them as the maintainer will merely unflag the package and ignore you." See Flagging packages out of date

nonshankus commented on 2022-03-25 19:17 (UTC)

Hey @Revelation60,

Thank you for maintaining this package. I just wanted to point out, that with the latest commit (50898a8f4df3) and the changes to the install locations of the schemes I get the same error as the previous commenter. I could only work around the issue by building the package manually from the previous revision. I guess it comes down to this change:

@@ -30,9 +30,10 @@ package() {
   cd "$srcdir/${pkgname%-git}"
   install -d "$pkgdir/usr/share/gnome-shell/extensions/gTile@vibou"
   bsdtar -xvf bazel-bin/install-extension.runfiles/gtile/dist.tar.gz -C \
-    "$pkgdir/usr/share/gnome-shell/extensions/gTile@vibou"
+    "$pkgdir/usr/share/gnome-shell/extensions/gTile@vibou/"

-  install -d "$pkgdir/usr/share/glib-2.0/schemas"
-  ln -s /usr/share/gnome-shell/extensions/gTile@vibou/schemas/org.gnome.shell.extensions.gtile.gschema.xml \
-    "$pkgdir/usr/share/glib-2.0/schemas"
+  install -Dm644 schemas/org.gnome.shell.extensions.gtile.gschema.xml -t \
+    "$pkgdir/usr/share/glib-2.0/schemas/"
+
+  rm -rf "$pkgdir/usr/share/gnome-shell/extensions/gTile@vibou/schemas/"
 }

Any fixes for this would be highly appreciated.

Cheers

falstaff_ch commented on 2022-01-13 09:29 (UTC)

After updating the package today, the extension did not load anymore. The settings of extension gTile@vibou had an error:

GLib.FileError: Failed to open file “/usr/share/gnome-shell/extensions/gTile@vibou/schemas/gschemas.compiled”: open() failed: No such file or directory

Stack trace:

get@/usr/share/gnome-shell/extensions/gTile@vibou/settings.js:13:43
buildPrefsWidget@/usr/share/gnome-shell/extensions/gTile@vibou/prefs.js:436:29
_init@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:219:40
OpenExtensionPrefsAsync/<@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:128:33
asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:115:22
run@resource:///org/gnome/Shell/Extensions/js/dbusService.js:177:20
main@resource:///org/gnome/Shell/Extensions/js/main.js:19:13
run@resource:///org/gnome/gjs/modules/script/package.js:206:19
start@resource:///org/gnome/gjs/modules/script/package.js:190:8
@/usr/share/gnome-shell/org.gnome.Shell.Extensions:1:17