dev-lang/ghc: Fixed symlink creation to non-existant directory

[jaakristioja]

Closes: https://bugs.gentoo.org/860276
Signed-off-by: Jaak Ristioja jaak@ristioja.ee

[gentoo-bot]

Pull Request assignment

Submitter: @jaakristioja
Areas affected: ebuilds
Packages affected: dev-lang/ghc

dev-lang/ghc: @gentoo/haskell

Linked bugs

Bugs linked: 860276

---

In order to force reassignment and/or bug reference scan, please append [please reassign] to the pull request title.

Docs: Code of Conduct ● Copyright policy (expl.) ● Devmanual ● GitHub PRs ● Proxy-maint guide

[matoro]

So this was my change...but the underlying cause of this is that the binpkg was built on a system which uses lib64, while you are building on one that doesn't. At least two users have reported this, but with different causes. The linked bug is due to being on a 17.0 profile, and there was another one due to being on a musl profile. At least in the musl case, the binpkg binary will NOT run then, so this will not help - it needs to be masked on musl. The question is, should we also be masking on 17.0?

CC @thesamesam

[gentoo-repo-qa-bot]

Pull request CI report

Report generated at: 2022-07-28 23:39 UTC
Newest commit scanned: 29f0ac1
Status: ✅ good

There are existing issues already. Please look into the report to make sure none of them affect the packages in question:
https://qa-reports.gentoo.org/output/gentoo-ci/4179424412/output.html

[thesamesam]

I'd really like to see individual bug reports from people hitting this to understand what their issue is and to debug it.

Some info in the commit message would be good. What case is this fixing for you exactly? It may work on 17.0 systems, but it won't work on musl for example, which was the original bug.

(If you are on 17.0, please get off it ASAP, as we're going to delete it shortly.)

[stikonas]

I'd really like to see individual bug reports from people hitting this to understand what their issue is and to debug it.

Some info in the commit message would be good. What case is this fixing for you exactly? It may work on 17.0 systems, but it won't work on musl for example, which was the original bug.

(If you are on 17.0, please get off it ASAP, as we're going to delete it shortly.)

I think the reason is that those people are using ghcbootstrap flag.

[thesamesam]

Thanks @stikonas - that makes sense!