Package Details: looking-glass-host 2:B7-1

Git Clone URL: https://aur.archlinux.org/looking-glass.git (read-only, click to copy)
Package Base: looking-glass
Description: Linux host application for pushing frame data to the LookingGlass IVSHMEM device
Upstream URL: https://looking-glass.io/
Licenses: GPL-2.0-or-later
Submitter: Omar007
Maintainer: Omar007
Last Packager: Omar007
Votes: 42
Popularity: 1.53
First Submitted: 2017-12-22 16:49 (UTC)
Last Updated: 2025-03-08 14:17 (UTC)

Latest Comments

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

Omar007 commented on 2023-01-07 18:21 (UTC) (edited on 2023-01-07 18:21 (UTC) by Omar007)

@untwisted; that is possible if the upstream artifact has changed. This should generally never just randomly happen and if it does, it can be an indication of a malicious actor having been able to either change the artifact or intercept yours somehow.

Now I highly doubt that has actually happened, this seems way to niche of an item to target so that means upstream probably repackaged it for some reason on another. That said, I will not just blindly update the checksum without verifying the new artifact but I'm going to have to do that later.

untwisted commented on 2023-01-07 16:15 (UTC) (edited on 2023-01-07 16:15 (UTC) by untwisted)

Looks like the sha512sum is incorrect? Installation was failing so I downloaded the package from the Looking Glass site and ran a sha512 manually and got 8b7a4b6d33380299512bef103331635c9e9855ae0712cbe4d9ccbec2c2499c77318502aa3e0259451ef32c414ef5c8fbc103513bcd924570097dd866934cbe10.

Modifying the PKGBUILD to this SHA value enabled the build to work.

Excalibur commented on 2022-12-23 12:28 (UTC) 

diff --git a/PKGBUILD b/PKGBUILD
index 299d696..b8a340d 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -6,8 +6,8 @@ pkgname=("${pkgbase}"
          "${pkgbase}-host"
          "obs-plugin-${pkgbase}")
 epoch=2
-pkgver=B5.0.1
-pkgrel=3
+pkgver=B6
+pkgrel=1
 pkgdesc="An extremely low latency KVMFR (KVM FrameRelay) implementation for guests with VGA PCI Passthrough"
 url="https://looking-glass.io/"
 arch=('x86_64')
@@ -15,7 +15,7 @@ license=('GPL2')
 makedepends=('cmake' 'fontconfig' 'spice-protocol' 'wayland-protocols'
              'libxss' 'libxi' 'libxpresent' 'obs-studio')
 source=("looking-glass-${pkgver}.tar.gz::https://looking-glass.io/artifact/${pkgver}/source")
-sha512sums=('2600722fba5a9b794556391a636df09d284dc5460c5e9b4718bc2c044e6ece68890893c18c30780245207c0e92194f9691269bdcd590f118a616417d1e74bbd6')
+sha512sums=('402729dc51a6e8995a64384de6e9549861a0db6a87c9627e5832ea548b4ab6b49f538cf12ae510caa360c39806671785ce7560aaf07e7c46532fe0271884f2cb')

 _lgdir="${pkgbase}-${pkgver}"

sk21 commented on 2022-09-05 10:40 (UTC)

The DKMS module reports error exit 10, for linux-xanmod-edge kernel, but works with my other kernels. Is there a way to fix this?

Swamp commented on 2022-08-27 17:11 (UTC)

Oh, my bad. When I first tried to install obs-plugin-looking-glass there was a conflict warning somewhere so I thought that installing looking-glass had already installed all 4 packages by itself. Thanks for the info.

Omar007 commented on 2022-08-27 16:06 (UTC)

@Swamp: Did you install the OBS plugin package? If you use this PKGBUILD as-is, it will result in 4 separate packages you can install; the client application, the DKMS modules, the host application and the OBS plugin.

Swamp commented on 2022-08-26 17:14 (UTC)

I'm not sure if it's my mistake but liblooking-glass-obs.so isn't being installed to /usr/lib/obs-plugins I copied it manually from the cache after building.

xiretza commented on 2022-07-09 16:06 (UTC)

Thanks for not blindly updating the hash like many others would have. I just compared the two tarballs, they seem to be identical except for timestamp differences, weird.

Omar007 commented on 2022-07-04 15:44 (UTC)

I no longer had the other artifact so instead I've compared the original git repository with the release artifact and looks like everything is good. VERSION file seems to be the only changed thing as of the July artifact.

Will update the checksums later.

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

The upstream file has changed as of this month (July) apparently. I'm not sure why so my initial gut reaction is to not just blindly update things, especially since the site page itself does not mention a newly packaged date/upload for it.

With a bit of luck I might have the previous build artifacts still somewhere so I can make a comparison.

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