427c46dbf9
In the lifecycle of vX.Y.Z, all tests are run against vX.Y-test before it is published, including when the tag is pushed because the automated release process now runs end-to-end before pushing the release to forgejo-experimental. Running end-to-end against vX.Y-dev is therefore redundant with at least two other runs with exactly the same SHA (the one before the tag is pushed and the one when the tag is pushed). There would be value in doing that if it allowed to detect race conditions in Forgejo. But such races were not found in the past six months and there is a lot more scrutiny on commits merged in Forgejo which makes it even less likely than it was before. Running the tests on vX.Y instead of also including the built version provide the same coverage and reduces the workload.
26 lines
957 B
Text
26 lines
957 B
Text
# -*- mode: Shell-script; eval: (setq indent-tabs-mode 't); eval: (setq tab-width 4) -*-
|
|
# Maintainer: Dominic Meiser <git@msrd0.de>
|
|
pkgname=forgejo-2174
|
|
pkgver=1.0
|
|
pkgrel=0
|
|
pkgdesc="Forgejo #2174 Reproduction"
|
|
url="https://msrd0.dev/msrd0/$pkgname"
|
|
arch="x86_64"
|
|
license="custom"
|
|
|
|
# using x86_64 instead of noarch as a workaround of
|
|
# https://codeberg.org/forgejo/forgejo/issues/2173
|
|
subpackages="$pkgname-openrc::x86_64"
|
|
|
|
source="forgejo_2174 forgejo_2174.init"
|
|
builddir="$srcdir"
|
|
|
|
package() {
|
|
install -D -m755 "$srcdir/forgejo_2174" "$pkgdir"/usr/bin/forgejo_2174
|
|
install -D -m755 "$srcdir/forgejo_2174.init" "$pkgdir"/etc/init.d/forgejo_2174
|
|
}
|
|
|
|
sha512sums="
|
|
651c2a816510a18981bcd45077eb5acd6e58511d641949ddc690e326b81018d851eb7f1c88e2336eada2f216606ce2aa0569eb2d02d7c423c80705cc00acf838 forgejo_2174
|
|
b1cba77139cdaf9e0cdd78de93becbb3891ec59646e8d2cb40620b230bd798d51e6d9c58e65b584812a6bb8eb2b9c9f89262a8700a39c62af8ec8ea09aee4e29 forgejo_2174.init
|
|
"
|