Arch Linux User Repository

Thanks, kgs. Fixed.

sha256sums are outdated. new one is:

sha256sums_x86_64=('1af3e53480705c6349523b16481fc5b62e94734a91ff5b72c2154582d8a91dcb')

You can get around this by doing a clean build

yay -S openlens-bin                                                                                                                                                                                                                                                                                                                      
AUR Explicit (1): openlens-bin-6.4.15-2
:: PKGBUILD up to date, skipping download: openlens-bin
  1 openlens-bin                             (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==>A

Hi beliys, the release files on https://github.com/beliys/OpenLens/releases/tag/v6.4.15 have been changed. Now the checksums are invalid. Here the changes for PKGBUILD:

- sha256sums_x86_64=('b6708fd0f5404898497e8b2c1f5f726977a2901322082aa4a8fd86a3a1d4f8d8')
- sha256sums_aarch64=('2caec249ea59a27c743d280bb1817f5dc35ce217048b8732d84340a59b9cf528')

+ sha256sums_x86_64=('37341e8e7db585fbbfa03ea7a00fa488dc6bbcfc5ab6d82bf22327d4b0732e78')
+ sha256sums_aarch64=('de0f4405714dc2d72892485a8ca8932251c540937e9525ffdb95468e797a60a7')

Hi, can you please fix the checksums for the appimages as they seems not correct. The sums from the openlens repo with PKGBUILD are different

Are you using conda?

https://bbs.archlinux.org/viewtopic.php?pid=2061695

RESOLVED by disable conda.

I got the following error

==> Creating package "openlens-bin"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Generating .MTREE file...
  -> Compressing package...
bsdtar: Option --no-read-sparse is not supported
Usage:
  List:    bsdtar -tf <archive-filename>
  Extract: bsdtar -xf <archive-filename>
  Create:  bsdtar -cf <archive-filename> [filenames...]
  Help:    bsdtar --help
==> ERROR: Failed to create package file.
 -> error making: openlens-bin

Currently there are 2 problems:

1) with each build, the checksum changes

2) sometimes the GITHUB API does not return what it should. That is why 2 days ago the API returned 6.3.0 as the latest version, although it should have returned 6.4.0-alpha.3, and because of this, the package was rebuilt and the checksum changed.

This can be fixed in 2 ways:

1) just ignore the checksum check

2) make changes to minimize problems in the future.

I don’t really like the first option, but those who are more suitable for it can skip the checksum check during installation and there will be no problems.

But I try to go the second way doing it in my free time. If someone knows how to do better, then patches are welcome. In the MuhammedKalkan repository, the problem of rebuilding and changing checksums is much more common, at least due to the fact that receiving an empty response from the github api is not validated there.

==> Validating source files with sha256sums...
    OpenLens.desktop ... Passed
==> Validating source_x86_64 files with sha256sums...
    OpenLens-6.3.0-x86_64.AppImage ... FAILED
==> ERROR: One or more files did not pass the validity check!

I checked the sha256sum: ef6ab3b301e54a4df7ccf50dd566bbbdc1187370844550008c6b0896153a0253 OpenLens-6.3.0.x86_64.AppImage

And unfortunately even though your releases might be automateable, the new version is pretty buggy and theother release-repo has therefore removed it. This package is just not reliable like this.

In short, it saves my time as a maintainer and allows future PKGBUILD updates to be fully automated.