Summary: | =dev-libs/icu-58*: Too specific subslot | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | octoploid <octoploid> |
Component: | Current packages | Assignee: | Gentoo Office Team <office> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | jouni.kosonen, mgorny, octoploid |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
octoploid
2016-12-19 22:43:38 UTC
This mistake was introduced in dev-libs/icu-58.1 which was setting SLOT="0/${PV}" and this mistake is present in newer ebuilds. SLOT="0/${PV%%.*}" should be used. After changing to the correct SLOT and ebuilding icu-58.2, you can use something like: find . -type f -exec sed -i 's/58\.1=/58/g' {} \; in /etc/pkg to avoid the costly rebuilds. This is NOT a mistake, and all bugs filed will be closed INVALID. Upstream explicitly specifies that even minor upgrades require a rebuild of reverse dependencies. (In reply to Andreas K. Hüttel from comment #3) Could you give URL of this statement of upstream in upstream documentation or an e-mail in upstream mailing list for reference? (In reply to Andreas K. Hüttel from comment #3) > This is NOT a mistake, and all bugs filed will be closed INVALID. > > Upstream explicitly specifies that even minor upgrades require a rebuild of > reverse dependencies. This is totally crazy. What if all e.g. Libreoffice reverse dependencies would behave this way? See the problem? And their documentation is clear: »The second field is 1 for the initial release (e.g., 49.1). The second and sometimes third fields are incremented for binary compatible maintenance releases.« So you are wrong and no rebuild is required. And sorry, I mean "Libreoffice dependencies" of course. (In reply to Andreas K. Hüttel from comment #3) > This is NOT a mistake, and all bugs filed will be closed INVALID. > > Upstream explicitly specifies that even minor upgrades require a rebuild of > reverse dependencies. If this is indeed correct, then please update SONAME accordingly. |