sys-apps/hashboot: Fix incorrect source variable #13

tmweaver · 2021-03-09T14:41:47+01:00

tmweaver commented

2021-03-09 14:41:47 +01:00

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.

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.

💖 1

tmweaver added 1 commit 2021-03-09 14:41:51 +01:00

sys-apps/hashboot: Fix incorrect source variable

continuous-integration/drone/pr Build is failing

Details

8bf89ef408

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.

tastytea commented

2021-03-09 15:22:13 +01:00

Thanks! I confirmed the issue with 0.9.14, but the 9999 ebuild does use […]/hashboot-9999/work/hashboot-9999, right?

Thanks! I confirmed the issue with 0.9.14, but the 9999 ebuild does use `[…]/hashboot-9999/work/hashboot-9999`, right?

tastytea commented

2021-03-09 15:32:38 +01:00

Ah, git-r3 just clones into ${S}.

Ah, `git-r3` just clones into `${S}`.

tastytea merged commit a4a205a544 into master

2021-03-09 15:32:52 +01:00

tastytea referenced this issue from a commit

2021-03-09 15:32:52 +01:00