Commit Graph

17 Commits

Author SHA1 Message Date
009cf82ed5
sys-apps/hashboot: update Manifest
Signed-off-by: tastytea <tastytea@tastytea.de>
2023-03-14 13:33:53 +01:00
8bf89ef408 sys-apps/hashboot: Fix incorrect source variable
When downloading the hashboot tarball, e.g. `hashboot-0.9.14.tar.gz` it
extracts to a folder without the version name, so `hashboot`.

This breaks when trying to `emerge hashboot` because the ebuild is
looking for the source code in
`/var/tmp/portage/sys-apps/hashboot-0.9.14/work/hashboot-0.9.14` when
it's actually located at
`/var/tmp/portage/sys-apps/hashboot-0.9.14/work/hashboot`.

In the ebuild that the `P` variable resolves to `hashboot-0.9.14`
and by default `S` and `P` are the same. `S` is what Portage uses to
figure out where the source is, which is why it's trying to find it in
`/var/tmp/portage/sys-apps/hashboot-0.9.14/work/hashboot-0.9.14`.

I managed to get it to build by editing the ebuild to set the `S`
variable as so: `S="${WORKDIR}/${PN}"`, which is what this commit
adds to the ebuild.
2021-03-09 13:40:10 +00:00
684a21cc8a
sys-apps/hashboot: Fix SRC_URI; re-generate Manifest.
When SRC_URI changed from GitHub to schlomp.space I forgot to
re-generate the manifest.

Fixes: tastytea/overlay#12
2021-03-09 08:38:39 +01:00
32836c6a0e
Switch to thin manifests and don't sign them anymore.
Commits are still signed.
2020-09-04 03:50:50 +02:00
adfe955aca
sys-apps/hashboot: Version bump 0.9.14 and repo location change.
Package-Manager: Portage-2.3.66, Repoman-2.3.11
Manifest-Sign-Key: 3555266864CA6D7FF45AA6E7CFC39497F1B26E07
2019-06-20 22:23:34 +02:00
1f3423eafa
sys-apps/hashboot: Updated live ebuild.
Package-Manager: Portage-2.3.66, Repoman-2.3.11
Manifest-Sign-Key: 3555266864CA6D7FF45AA6E7CFC39497F1B26E07
2019-06-20 14:55:50 +02:00
8393ed1271
sys-apps/hashboot: Removed upstream maintainer address.
Package-Manager: Portage-2.3.62, Repoman-2.3.11
Manifest-Sign-Key: 3555266864CA6D7FF45AA6E7CFC39497F1B26E07
2019-03-30 09:49:02 +01:00
a0b885bd89
sys-apps/hashboot: Version 0.9.13.
Package-Manager: Portage-2.3.62, Repoman-2.3.11
Manifest-Sign-Key: 3555266864CA6D7FF45AA6E7CFC39497F1B26E07
2019-03-30 00:19:02 +01:00
ff8d62db14
sys-apps/hashboot: New init script location, added firmware flag.
Package-Manager: Portage-2.3.62, Repoman-2.3.11
Manifest-Sign-Key: 3555266864CA6D7FF45AA6E7CFC39497F1B26E07
2019-03-30 00:13:34 +01:00
5c36381008
sys-apps/hashboot: Updated 9999.
Package-Manager: Portage-2.3.51, Repoman-2.3.11
Manifest-Sign-Key: 3555266864CA6D7FF45AA6E7CFC39497F1B26E07
2019-02-24 15:37:27 +01:00
0bd0ae2cef
sys-apps/hashboot: Updated 9999.
Package-Manager: Portage-2.3.51, Repoman-2.3.11
Manifest-Sign-Key: 3555266864CA6D7FF45AA6E7CFC39497F1B26E07
2019-02-24 11:16:47 +01:00
eba52562a1
sys-apps/hashboot: Updated to EAPI 7
Package-Manager: Portage-2.3.51, Repoman-2.3.11
Manifest-Sign-Key: 3555266864CA6D7FF45AA6E7CFC39497F1B26E07
2019-02-05 10:37:04 +01:00
b30a620bce
signed manifests 2018-07-16 19:36:03 +02:00
cb6fa040cb
Disabled thin manifests 2018-06-29 16:36:31 +02:00
e776d07ac9
Fixed QA issues in sys-apps 2018-06-21 21:43:10 +02:00
9693ad0dc7
changed hashboot-9999.ebuild 2018-05-22 00:52:05 +02:00
c42dccc9d5
populate overlay 2018-05-08 06:50:18 +02:00