Package Details: looking-glass-host 2:B6-3

Git Clone URL: (read-only, click to copy)
Package Base: looking-glass
Description: Linux host application for pushing frame data to the LookingGlass IVSHMEM device
Upstream URL:
Licenses: GPL2
Submitter: Omar007
Maintainer: Omar007
Last Packager: Omar007
Votes: 26
Popularity: 0.92
First Submitted: 2017-12-22 16:49 (UTC)
Last Updated: 2023-01-31 16:50 (UTC)

Latest Comments

1 2 3 4 5 6 .. 8 Next › Last »

Omar007 commented on 2023-02-27 08:42 (UTC)

@dvalter: I did consider that and if it had changed again within a few days I would've changed over. It hadn't happened again though so it seems that whatever was going on has been fixed/changed. The checksum has been stable for about a month now (knocks on wood).

dvalter commented on 2023-02-26 19:30 (UTC)

With this repackaging insanity on the part of, could you consider using Github as a source of the tarball?

xiretza commented on 2023-01-29 19:42 (UTC) (edited on 2023-01-29 19:43 (UTC) by xiretza)

The only difference between 8b7a4b6d33380299512bef103331635c9e9855ae0712cbe4d9ccbec2c2499c77318502aa3e0259451ef32c414ef5c8fbc103513bcd924570097dd866934cbe10 (PKGBUILD) and 558981d6b32098076ef0775a748da349941551352cbef836e37310e43e5cd6072df3dec6fa2418a9abecc7729ef0c1c6869e3168d05a3d76bea46c6eb8c4e82c (upstream) is yet again a modification time update of the VERSION file.

MacGyver commented on 2023-01-24 17:00 (UTC) (edited on 2023-01-24 17:01 (UTC) by MacGyver)

I'm now seeing 558981d6b32098076ef0775a748da349941551352cbef836e37310e43e5cd6072df3dec6fa2418a9abecc7729ef0c1c6869e3168d05a3d76bea46c6eb8c4e82c for looking-glass-B6.tar.gz. It doesn't help that they don't publish the expected checksum themselves anywhere.

harrego commented on 2023-01-20 21:45 (UTC) (edited on 2023-01-20 21:45 (UTC) by harrego)

Currently fails to build, downgrading binutils to 2.39 on Arch worked ($ downgrade binutils). Issue is related to a change with libbfd.a that binutils made in 2.40.

Related GitHub issue:

Omar007 commented on 2023-01-16 08:48 (UTC)

@xiretza: So far I've not. It only happened twice over the whole lifespan thus far afaik so I haven't bothered. I don't know about others.

That said, checking the artifact now, the checksum still seems to be the same. I downloaded the artifact fresh (twice to confirm) and it still matches the checksum of PKGBUILD 2:B6-2. It seems it hasn't changed at the moment. Can you recheck on your end?

xiretza commented on 2023-01-15 19:19 (UTC)

Looks like it changed again, now it's 25d720c7dd2711c86ebde73c6f4db990b60d4015d075ca4b33b60e16937bf700... Has anyone complained to upstream about this yet?

Omar007 commented on 2023-01-10 19:23 (UTC) (edited on 2023-01-10 19:24 (UTC) by Omar007)

I have compared the website artifact against the sourcecode and I've been unable to find any differences (maybe the artifact VERSION file changed but that isn't relevant/dangerous here) so I have updated the checksum. The update should be pushed to the AUR shortly.

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.