Summary: | dev-lang/jimtcl-0.81 always use jimsh0 to bootstrap | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Esteve Varela Colominas <esteve.varela> |
Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | esteve.varela |
Priority: | Normal | Keywords: | PullRequest |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://github.com/msteveb/jimtcl/issues/247 https://github.com/gentoo/gentoo/pull/34890 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 847148 |
Description
Esteve Varela Colominas
2023-05-02 19:27:43 UTC
Perhaps a USE=system-bootstrap instead. But really, this was kind of a specific issue which needed resolving, no? I think having different behavior between a clean install and an upgrade leads to hard to detect bugs like this one. Anyway, I'll be sending a PR in a bit. |