Search Criteria
Package Details: surfer-waveform-git-bin 0.3.0.r738.1df1df84-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/surfer-waveform.git (read-only, click to copy) |
---|---|
Package Base: | surfer-waveform |
Description: | A waveform viewer with a focus on a snappy usable interface, and extensibility. |
Upstream URL: | https://gitlab.com/surfer-project/surfer |
Keywords: | surfer waveform |
Licenses: | EUPL |
Provides: | surfer-waveform |
Submitter: | xusine |
Maintainer: | xusine |
Last Packager: | xusine |
Votes: | 0 |
Popularity: | 0.000000 |
First Submitted: | 2024-02-25 10:11 (UTC) |
Last Updated: | 2024-11-18 20:11 (UTC) |
Latest Comments
xusine commented on 2024-10-23 17:29 (UTC)
@TheZoq2 Sure, let's add the publishing process to CI. Let me know if there is anything I can help.
TheZoq2 commented on 2024-10-23 11:58 (UTC)
o/ Surfer author here, thanks for packaging this! We could add the publishing to CI if you want, another option is to change the link from an absolute file to https://gitlab.com/api/v4/projects/42073614/jobs/artifacts/main/raw/surfer_linux.zip?job=linux_build though I assume that that would break checksuming
leuko commented on 2024-06-12 16:01 (UTC)
You should use
provides
so that surfer-waveform-git{,-bin} clash with each other.xusine commented on 2024-06-02 19:38 (UTC) (edited on 2024-06-02 19:41 (UTC) by xusine)
@leuko Thanks for letting me know. I updated the package and now it should be OK.
This repository contains a
update.py
which automatically fetches the latest commit and its artifact. It might be more promising if we put this script as part of the official CI/CD flow so that this repo is automatically updated every time there is a new commit.leuko commented on 2024-06-02 15:01 (UTC)
https://gitlab.com/surfer-project/surfer/-/jobs/6890676473/artifacts/download?file_type=archive leads to 404.
leuko commented on 2024-03-20 17:02 (UTC)
@xusine, you use
pkgbase
even you have only a single package. Is this intended?xusine commented on 2024-03-14 09:10 (UTC)
@delta Aha, sorry for my late reply.
The problem is caused by the link. The link in the PKGBUILD always points to the latest release version, so if I forget to follow the commit and update the PKGBUILD, we will see the validity check failure.
I have fixed the link now. Thanks for your feedback.
delta64 commented on 2024-03-04 21:16 (UTC) (edited on 2024-03-04 21:16 (UTC) by delta64)
The validity check fails for me: