sys-apps/hashboot
Check integrity of files in /boot
ChangeLog
commit 95ac54cfe230f4ce100632a8c4aba21838303201
Author: tea <tea+gentoo@cuddleslut.fr>
Date: Sun Nov 3 15:59:43 2024 +0100
*/*: update name and email
Signed-off-by: tea <tea+gentoo@cuddleslut.fr>
commit d065d6c380bd133392a002a4e2ef37e7c12e33e0
Author: tea <tea@tastytea.de>
Date: Tue May 28 20:42:03 2024 +0200
sys-apps/hashboot: update EAPI 7 -> 8, fix live ebuild
Signed-off-by: tea <tea@tastytea.de>
commit 009cf82ed5cba158f05e9e120f1480cf71301689
Author: tastytea <tastytea@tastytea.de>
Date: Tue Mar 14 13:33:53 2023 +0100
sys-apps/hashboot: update Manifest
Signed-off-by: tastytea <tastytea@tastytea.de>
commit 8bf89ef4089b5400be30d29d84694f656320042a
Author: tmweaver <tmweaver@xn--vafrnir-zza3gsb.is>
Date: Tue Mar 9 13:36:23 2021 +0000
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="$/$"`, which is what this commit
adds to the ebuild.
commit 684a21cc8ad058d3d2b7bfb6d71e2b108715543b
Author: tastytea <tastytea@tastytea.de>
Date: Tue Mar 9 08:38:39 2021 +0100
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: https://schlomp.space/tastytea/overlay/issues/12
commit 32836c6a0e46dc713fae065df01a8bd7b5defa90
Author: tastytea <tastytea@tastytea.de>
Date: Fri Sep 4 03:50:50 2020 +0200
Switch to thin manifests and don't sign them anymore.
Commits are still signed.
commit adfe955acaf62bc07c7531025f42c4747e365fdb
Author: tastytea <tastytea@tastytea.de>
Date: Thu Jun 20 22:23:34 2019 +0200
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
commit 1f3423eafa2bf9e3c7fe134860f30f231a9838a1
Author: tastytea <tastytea@tastytea.de>
Date: Thu Jun 20 14:55:50 2019 +0200
sys-apps/hashboot: Updated live ebuild.
Package-Manager: Portage-2.3.66, Repoman-2.3.11
Manifest-Sign-Key: 3555266864CA6D7FF45AA6E7CFC39497F1B26E07
commit 8393ed127124c12d08bd18dc8556784de80206b0
Author: tastytea <tastytea@tastytea.de>
Date: Sat Mar 30 09:49:02 2019 +0100
sys-apps/hashboot: Removed upstream maintainer address.
Package-Manager: Portage-2.3.62, Repoman-2.3.11
Manifest-Sign-Key: 3555266864CA6D7FF45AA6E7CFC39497F1B26E07
commit a0b885bd89ccb10131eb9f9903bcaf090e0626d3
Author: tastytea <tastytea@tastytea.de>
Date: Sat Mar 30 00:19:02 2019 +0100
sys-apps/hashboot: Version 0.9.13.
Package-Manager: Portage-2.3.62, Repoman-2.3.11
Manifest-Sign-Key: 3555266864CA6D7FF45AA6E7CFC39497F1B26E07
commit ff8d62db14505493edfaa804009e851c7d4983e2
Author: tastytea <tastytea@tastytea.de>
Date: Sat Mar 30 00:13:13 2019 +0100
sys-apps/hashboot: New init script location, added firmware flag.
Package-Manager: Portage-2.3.62, Repoman-2.3.11
Manifest-Sign-Key: 3555266864CA6D7FF45AA6E7CFC39497F1B26E07
commit 5c36381008c6149d484fcc60ef5683fdd6ef25e0
Author: tastytea <tastytea@tastytea.de>
Date: Sun Feb 24 15:37:27 2019 +0100
sys-apps/hashboot: Updated 9999.
Package-Manager: Portage-2.3.51, Repoman-2.3.11
Manifest-Sign-Key: 3555266864CA6D7FF45AA6E7CFC39497F1B26E07
commit 0bd0ae2cefa5787ca36bca44531055389561c7ea
Author: tastytea <tastytea@tastytea.de>
Date: Sun Feb 24 11:16:47 2019 +0100
sys-apps/hashboot: Updated 9999.
Package-Manager: Portage-2.3.51, Repoman-2.3.11
Manifest-Sign-Key: 3555266864CA6D7FF45AA6E7CFC39497F1B26E07
commit eba52562a16c6927c170048a2d43c0470bcd6a4b
Author: tastytea <tastytea@tastytea.de>
Date: Tue Feb 5 10:37:04 2019 +0100
sys-apps/hashboot: Updated to EAPI 7
Package-Manager: Portage-2.3.51, Repoman-2.3.11
Manifest-Sign-Key: 3555266864CA6D7FF45AA6E7CFC39497F1B26E07
commit b30a620bce012f6eff7005844108b45f5c84e439
Author: tastytea <tastytea@tastytea.de>
Date: Mon Jul 16 19:36:03 2018 +0200
signed manifests
commit cb6fa040cb9cf96111f5d0d1e6a384d8b9b047f9
Author: tastytea <tastytea@tastytea.de>
Date: Fri Jun 29 16:36:31 2018 +0200
Disabled thin manifests
commit e776d07ac944a0bca158bd1ff2e4d203467b4c62
Author: tastytea <tastytea@tastytea.de>
Date: Thu Jun 21 21:43:10 2018 +0200
Fixed QA issues in sys-apps
commit 9693ad0dc712e93b08305dc8a0b0e450c66a4ec8
Author: tastytea <tastytea@tastytea.de>
Date: Tue May 22 00:52:05 2018 +0200
changed hashboot-9999.ebuild
commit c42dccc9d50bb26d54bfba95431dbc1f0500bd9a
Author: tastytea <tastytea@tastytea.de>
Date: Tue May 8 06:50:18 2018 +0200
populate overlay
Author: tea <tea+gentoo@cuddleslut.fr>
Date: Sun Nov 3 15:59:43 2024 +0100
*/*: update name and email
Signed-off-by: tea <tea+gentoo@cuddleslut.fr>
commit d065d6c380bd133392a002a4e2ef37e7c12e33e0
Author: tea <tea@tastytea.de>
Date: Tue May 28 20:42:03 2024 +0200
sys-apps/hashboot: update EAPI 7 -> 8, fix live ebuild
Signed-off-by: tea <tea@tastytea.de>
commit 009cf82ed5cba158f05e9e120f1480cf71301689
Author: tastytea <tastytea@tastytea.de>
Date: Tue Mar 14 13:33:53 2023 +0100
sys-apps/hashboot: update Manifest
Signed-off-by: tastytea <tastytea@tastytea.de>
commit 8bf89ef4089b5400be30d29d84694f656320042a
Author: tmweaver <tmweaver@xn--vafrnir-zza3gsb.is>
Date: Tue Mar 9 13:36:23 2021 +0000
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="$/$"`, which is what this commit
adds to the ebuild.
commit 684a21cc8ad058d3d2b7bfb6d71e2b108715543b
Author: tastytea <tastytea@tastytea.de>
Date: Tue Mar 9 08:38:39 2021 +0100
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: https://schlomp.space/tastytea/overlay/issues/12
commit 32836c6a0e46dc713fae065df01a8bd7b5defa90
Author: tastytea <tastytea@tastytea.de>
Date: Fri Sep 4 03:50:50 2020 +0200
Switch to thin manifests and don't sign them anymore.
Commits are still signed.
commit adfe955acaf62bc07c7531025f42c4747e365fdb
Author: tastytea <tastytea@tastytea.de>
Date: Thu Jun 20 22:23:34 2019 +0200
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
commit 1f3423eafa2bf9e3c7fe134860f30f231a9838a1
Author: tastytea <tastytea@tastytea.de>
Date: Thu Jun 20 14:55:50 2019 +0200
sys-apps/hashboot: Updated live ebuild.
Package-Manager: Portage-2.3.66, Repoman-2.3.11
Manifest-Sign-Key: 3555266864CA6D7FF45AA6E7CFC39497F1B26E07
commit 8393ed127124c12d08bd18dc8556784de80206b0
Author: tastytea <tastytea@tastytea.de>
Date: Sat Mar 30 09:49:02 2019 +0100
sys-apps/hashboot: Removed upstream maintainer address.
Package-Manager: Portage-2.3.62, Repoman-2.3.11
Manifest-Sign-Key: 3555266864CA6D7FF45AA6E7CFC39497F1B26E07
commit a0b885bd89ccb10131eb9f9903bcaf090e0626d3
Author: tastytea <tastytea@tastytea.de>
Date: Sat Mar 30 00:19:02 2019 +0100
sys-apps/hashboot: Version 0.9.13.
Package-Manager: Portage-2.3.62, Repoman-2.3.11
Manifest-Sign-Key: 3555266864CA6D7FF45AA6E7CFC39497F1B26E07
commit ff8d62db14505493edfaa804009e851c7d4983e2
Author: tastytea <tastytea@tastytea.de>
Date: Sat Mar 30 00:13:13 2019 +0100
sys-apps/hashboot: New init script location, added firmware flag.
Package-Manager: Portage-2.3.62, Repoman-2.3.11
Manifest-Sign-Key: 3555266864CA6D7FF45AA6E7CFC39497F1B26E07
commit 5c36381008c6149d484fcc60ef5683fdd6ef25e0
Author: tastytea <tastytea@tastytea.de>
Date: Sun Feb 24 15:37:27 2019 +0100
sys-apps/hashboot: Updated 9999.
Package-Manager: Portage-2.3.51, Repoman-2.3.11
Manifest-Sign-Key: 3555266864CA6D7FF45AA6E7CFC39497F1B26E07
commit 0bd0ae2cefa5787ca36bca44531055389561c7ea
Author: tastytea <tastytea@tastytea.de>
Date: Sun Feb 24 11:16:47 2019 +0100
sys-apps/hashboot: Updated 9999.
Package-Manager: Portage-2.3.51, Repoman-2.3.11
Manifest-Sign-Key: 3555266864CA6D7FF45AA6E7CFC39497F1B26E07
commit eba52562a16c6927c170048a2d43c0470bcd6a4b
Author: tastytea <tastytea@tastytea.de>
Date: Tue Feb 5 10:37:04 2019 +0100
sys-apps/hashboot: Updated to EAPI 7
Package-Manager: Portage-2.3.51, Repoman-2.3.11
Manifest-Sign-Key: 3555266864CA6D7FF45AA6E7CFC39497F1B26E07
commit b30a620bce012f6eff7005844108b45f5c84e439
Author: tastytea <tastytea@tastytea.de>
Date: Mon Jul 16 19:36:03 2018 +0200
signed manifests
commit cb6fa040cb9cf96111f5d0d1e6a384d8b9b047f9
Author: tastytea <tastytea@tastytea.de>
Date: Fri Jun 29 16:36:31 2018 +0200
Disabled thin manifests
commit e776d07ac944a0bca158bd1ff2e4d203467b4c62
Author: tastytea <tastytea@tastytea.de>
Date: Thu Jun 21 21:43:10 2018 +0200
Fixed QA issues in sys-apps
commit 9693ad0dc712e93b08305dc8a0b0e450c66a4ec8
Author: tastytea <tastytea@tastytea.de>
Date: Tue May 22 00:52:05 2018 +0200
changed hashboot-9999.ebuild
commit c42dccc9d50bb26d54bfba95431dbc1f0500bd9a
Author: tastytea <tastytea@tastytea.de>
Date: Tue May 8 06:50:18 2018 +0200
populate overlay