Package Details: looking-glass-host-git 2:B6.r51.g53525847-1

Git Clone URL: https://aur.archlinux.org/looking-glass-git.git (read-only, click to copy)
Package Base: looking-glass-git
Description: Linux host application for pushing frame data to the LookingGlass IVSHMEM device
Upstream URL: https://looking-glass.io/
Licenses: GPL2
Conflicts: looking-glass-host
Provides: looking-glass-host
Submitter: Omar007
Maintainer: Omar007
Last Packager: Omar007
Votes: 14
Popularity: 0.22
First Submitted: 2017-12-14 09:38 (UTC)
Last Updated: 2023-05-08 10:14 (UTC)

Latest Comments

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

Omar007 commented on 2023-04-28 13:37 (UTC)

@ipaqmaster; it should not. You getting that error suggests that you're not building in a clean environment/chroot (e.g. https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot ). That is fine but in that case any breakage is for you to deal with.

Fwiw, adding -v is not going to change anything. You might be thinking of -p maybe? But in that case be aware that it will create parent directories and it does not fail (exit code always 0). That means if any expected dir in the path is missing, it'll fail somewhere later on with no indication this is actually where it failed (failure here would've told you the file structure is not as expected). But again, that's all for you to deal with if you choose to not build in a clean environment.

ipaqmaster commented on 2023-04-27 00:59 (UTC) (edited on 2023-04-28 13:40 (UTC) by ipaqmaster)

Subsequent builds fail due to line 55 in PKGBUILD.

mkdir: cannot create directory ‘client/build’: File exists
==> ERROR: A failure occurred in build().
    Aborting...

The mkdir "${b}" in PKGBUILD line 55 should have -p added.

(E: Corrected -v to -p)

Omar007 commented on 2022-10-26 13:20 (UTC)

Probably because the latest PKGBUILD is still the same PKGBUILD as before. I see something went wrong with the mirroring/pushing to the AUR. Different git issue i.c.w. CI pipeline (repository ownership) so the PKGBUILD was never included. I'll fix that in a bit.

quietvoid commented on 2022-10-26 12:17 (UTC)

I'm still unable to build after cloning the latest PKGBUILD.

Cloning into 'looking-glass-git/src/looking-glass/repos/PureSpice'...
fatal: transport 'file' not allowed
fatal: clone of '/home/nark/Downloads/looking-glass-git/src/PureSpice' into submodule path 'looking-glass-git/src/looking-glass/repos/PureSpice' failed

Omar007 commented on 2022-10-26 08:56 (UTC)

@gutash; it's not advisable to use internal/private git commands. There's no telling when those may change or break.

Due to CVE-2022-39253, the flag protocol.file.allow was changed to default to 'user', which disallows the use of file:// clones. The proper way to deal with this is to set the config flag to re-allow file:// clones instead. I've updated the package to explicitly provide this config flag for the submodule update commands.

gustash commented on 2022-10-22 23:17 (UTC)

A recent git update broke some -git packages using submodules. I've seen a common fix between other packages for this, so here's a patch that enables this package to properly build again:

diff --git a/PKGBUILD b/PKGBUILD
index 4506fdd..b83be57 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -7,7 +7,7 @@ pkgname=("${_pkgname}-git"
          "${_pkgname}-host-git"
          "obs-plugin-${_pkgname}-git")
 epoch=2
-pkgver=B5.r242.g35bf3091
+pkgver=B6rc1.r0.g5b6095ad
 pkgrel=1
 pkgdesc="An extremely low latency KVMFR (KVM FrameRelay) implementation for guests with VGA PCI Passthrough"
 url="https://looking-glass.io/"
@@ -41,12 +41,12 @@ prepare() {
    git config submodule.repos/LGMP.url "${srcdir}/LGMP"
    git config submodule.repos/PureSpice.url "${srcdir}/PureSpice"
    git config submodule.repos/cimgui.url "${srcdir}/cimgui"
-   git submodule update
+   git submodule--helper update

    cd "repos/cimgui"
    git submodule init
    git config submodule.imgui.url "${srcdir}/imgui"
-   git submodule update
+   git submodule--helper update
 }

 build() {

Omar007 commented on 2022-07-02 12:14 (UTC)

The project already did back in August. Under the default build options, it's not a new dependency for the client. It is now only additionally being used in the client's X11 displayserver component but it's not a new dependency.

Unless you've manually made changes to the PKGBUILD to change the build options to exclude anything and everything libxkbcommon, nothing changed.

Netboy3 commented on 2022-07-02 12:03 (UTC)

Sorry, my bad. The project just added this dependency officially so I just passed along the message. I should have looked at PKGBUILD

Omar007 commented on 2022-07-02 11:55 (UTC)

@NetBoy3: It already has since August last year.

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