@xiota: sounds like a good plan to me!
Search Criteria
Package Details: beeper-latest-bin 3.110.1-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/beeper-latest-bin.git (read-only, click to copy) |
---|---|
Package Base: | beeper-latest-bin |
Description: | A unified messaging app |
Upstream URL: | https://beeper.com/ |
Licenses: | LicenseRef-beeper |
Conflicts: | beeper |
Provides: | beeper |
Submitter: | xiota |
Maintainer: | xiota (sundbp) |
Last Packager: | xiota |
Votes: | 7 |
Popularity: | 0.94 |
First Submitted: | 2023-07-28 06:12 (UTC) |
Last Updated: | 2024-11-12 21:47 (UTC) |
Dependencies (2)
Required by (0)
Sources (1)
sundbp commented on 2023-07-28 06:06 (UTC)
sundbp commented on 2023-07-28 06:00 (UTC)
@blaxpot: exactly, I've asked them if they can consider version specific files but no luck so far :(
@xiota: The downloading etc seems an automated part of the pkgbuild/makepkg setup. I don't know how to tweak it to check the filename upfront. Do you?
blaxpot commented on 2023-07-28 02:08 (UTC)
AFAICT Beeper doesn't provide a way to download a specific version of their AppImage (or publish a checksum or sign it either)... So that explains what's going on I guess.
I've been using this package for months without noticing this problem FWIW. Thanks for keeping on top of updating it so well!
blaxpot commented on 2023-07-28 01:33 (UTC)
heh it would help if I could read properly... apparently I'm getting a newer version there...
blaxpot commented on 2023-07-28 01:31 (UTC) (edited on 2023-07-28 01:31 (UTC) by blaxpot)
I'm getting errors re: a failed validity check when updating this package.
I get a different checksum than what's in the PKGBUILD when I download the source file:
# sha256sum beeper-3.66.24.AppImage
e3c5518e119520a76632c7a96e64e287c2dbe2f25e088029e84d427c3d3a4f1f beeper-3.66.24.AppImage
dimfred commented on 2023-07-20 16:50 (UTC)
New package available Version: 3.65.19 Hash: 38fb69d255e8e17c342d0391f42b8e68375ddbe621681323be05a5bdb3d4d9c3
shtrophic commented on 2023-07-20 05:06 (UTC)
this package requires fuse2
Pinned Comments
xiota commented on 2024-05-05 02:26 (UTC) (edited on 2024-05-05 02:33 (UTC) by xiota)
Switching back to the system electron because of reported issues with the packaged electron. Also, fixed pkgver issue.
Build options by setting environment variables (or editing pkgbuild):
_system_electron=false
– Use the packaged electron_electron_version=29
– Use a specific system electron version (when default version has problems)/usr/bin/beeper
after install._install_path=usr/lib
– Use a different install path. Default isopt
. (Do not include leading/
and trailing/beeper
.)xiota commented on 2023-07-28 06:41 (UTC) (edited on 2024-02-29 23:18 (UTC) by xiota)
This is a self-updating package. It always downloads the latest available AppImage and applies the correct version number.
Please wait until over a month has passed since the last update before requesting version bumps.