Summary: | dev-db/postgresql-8.2.7 / sys-apps/openrc-0.2.5 - problems stopping daemon | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Maciej Mrozowski <reavertm> |
Component: | [OLD] baselayout | Assignee: | PgSQL Bugs <pgsql-bugs> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Maciej Mrozowski
2008-07-13 04:26:16 UTC
It's a bad init script. Not an issue with s-s-d. right, removing --oknodo does the thing em, I'll probably close this as won't fix. Please use dev-db/postgresql-server instead of dev-db/postgresql If dev-db/postgresql (not splitted postgresql ebuild) going to be removed from portage soon? If not I guess it would be better to add baselayout-2 support (remove --oknodo from init.d script when baselayout-2 detected) just to avoid further problems when eventually baselayout-2 hits stable. I examined init script from dev-db/postgresql-server (splitted ebuild) and it seems that it intentionally deprecates the one from dev-db/postgresql - or it's just lack of cohesion? Going for splitted ebuild in anyway good idea. And I guess that all 8.x versions are keyword masked just to avoid being auto installed due to database cluster incompatibility with latest 'stable' - not for stability issues (I haven't encountered single crash). cheers (In reply to comment #4) > If dev-db/postgresql (not splitted postgresql ebuild) going to be removed from > portage soon? I hope so, yes. > If not I guess it would be better to add baselayout-2 support > (remove --oknodo from init.d script when baselayout-2 detected) just to avoid > further problems when eventually baselayout-2 hits stable. > I examined init script from dev-db/postgresql-server (splitted ebuild) and it > seems that it intentionally deprecates the one from dev-db/postgresql - or it's > just lack of cohesion? Intentional. A lot of bugs are solved with the new (splitted) ebuilds. > Going for splitted ebuild in anyway good idea. > And I guess that all 8.x versions are keyword masked just to avoid being auto > installed due to database cluster incompatibility with latest 'stable' - not > for stability issues (I haven't encountered single crash). > cheers > No, it's just lack of time that we didn't mark those stable. I'll do that as soon as I have time. The problem of the db cluster incompatibility is not a problem anymore with the splitted ebuilds since they're also slotted. Means you can install 7.4,8.{0,1,2,3} side-by-side and then do the pgdump/pgload. |