Summary: | postgresql virtual/jdk dependency | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dave Lee <bigd> |
Component: | New packages | Assignee: | Karl Trygve Kalleberg (RETIRED) <karltk> |
Status: | RESOLVED INVALID | ||
Severity: | major | CC: | esigra |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dave Lee
2002-04-11 13:42:01 UTC
What version of portage are you using? I'm using 1.8.19 and I can't replicate this problem. I am now using portage 1.8.19 but wasd using 1.8.16 when I filed this bug. I didnt state that it is postgresql-7.2-r1 that I am getting this error with. when I try to emerge postgresql-7.2-r2 portage attempts to download sun-jdk-1.3.1-r3 to fill the =virtual/jdk-1.3* dependency. I already have ibm-jdk-1.3.1 that should fill the =virtual/jdk-1.3* dependency need. so the lastest postgresql ebuild doesnt seem to have this bug, but instead seems to be encountering another bug that is not recognizing my ibm-jdk as a virtual/jdk. I think postgresql-7.2-r1 may be failing due to the fact the dependency is listed as =virtual/jdk-1.3 and not =virtual/jdk-1.3* since my jdk is ibm-jdk-1.3.1 >=virtual/jdk-1.3 is incorrect. Postgresql-7.2 will only work with the 1.3
series of JDKs. This appears to work like a charm in Portage 1.8.8-r1.
|