Search Criteria
Package Details: forgejo-runner-bin 5.0.2-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/forgejo-runner-bin.git (read-only, click to copy) |
---|---|
Package Base: | forgejo-runner-bin |
Description: | Continuous integration for Forgejo |
Upstream URL: | https://code.forgejo.org/forgejo/runner |
Licenses: | MIT |
Conflicts: | forgejo-runner |
Provides: | forgejo-runner |
Submitter: | Rubonnek |
Maintainer: | tippfehlr |
Last Packager: | tippfehlr |
Votes: | 3 |
Popularity: | 0.031944 |
First Submitted: | 2023-10-27 00:52 (UTC) |
Last Updated: | 2024-11-23 12:18 (UTC) |
Latest Comments
tippfehlr commented on 2024-11-11 13:45 (UTC)
Alright. Sorry for bothering you.
Rubonnek commented on 2024-11-11 12:47 (UTC)
@tippfehlr that's a non-sequitur, I don't really use this package and you are quite motivated. I've disowned the package. You can maintain it now.
tippfehlr commented on 2024-11-11 12:14 (UTC)
Thanks. I overlooked the architecture in the file name, you could have used the same name there of course.
And even if official packages are built in chroots sources should still be unique [1].
[1] https://wiki.archlinux.org/title/PKGBUILD#source
Rubonnek commented on 2024-11-11 11:57 (UTC)
@tippfehlr there's no issue with the PKGBUILD, you are building the package on a dirty filesystem. While this PKGBUILD is not official, official PKGBUILDs do require a clean chroot and users are expected to build them within such. See https://wiki.archlinux.org/title/Arch_build_system#Toolchain.
For your convenience, I've updated this PKGBUILD to build under a dirty filesystem but don't expect every other package out there to support this.
tippfehlr commented on 2024-11-11 09:12 (UTC)
updating fails for me because the cached source file doesn’t have the version in the name. The original file name should be fine so you can just remove the
${_pkgname}::
. Thanks!Fijxu commented on 2024-04-28 00:31 (UTC)
Thanks for keeping this updated <3