| Summary: | slotted sun-jdk 1.5 not getting updated | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Anton Bolshakov <anton.bugs> |
| Component: | [OLD] Java | Assignee: | Java team <java> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | dev-portage |
| Priority: | High | ||
| Version: | 2008.0 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Anton Bolshakov
2008-08-16 01:34:27 UTC
(In reply to comment #0) > > I'm not sure if it's a portage problem, so file it under 'java' component > first. > It's not a problem at all. virtual/jdk:1.5 is not part of world because you have nothing pulling it for RDEPEND (see man emerge for with-bdeps). If you want world to update it you can for example add virtual/jdk:1.5 to the world file or upgrade to portage-2.2* and use the new @installed set. > It's not a problem at all.
The way how I see it is that my system might have an old (less supported/buggy?) java (and may be other) package, which won't be updated with universal "world" update and it could stay there for awhile. Hopefully, it'll covered with portage-2.2. Let it be an invalid for now, but at least you're aware. Thanks.
(In reply to comment #2) > The way how I see it is that my system might have an old (less > supported/buggy?) java (and may be other) package, which won't be updated with > universal "world" update and it could stay there for awhile. Run emerge --depclean after your updates and it will find and remove packages like those. > Run emerge --depclean after your updates and it will find and remove packages
> like those.
no, it won't.
run "emerge -pv tomcat" and you'll see that it still pulls both 1.5 and 1.6
I don't know exactly why.
(In reply to comment #2) > > It's not a problem at all. > > The way how I see it is that my system might have an old (less > supported/buggy?) java (and may be other) package, which won't be updated with > universal "world" update and it could stay there for awhile. You don't understand world. It's not universal. It's what gets pulled in by the world file and their runtime dependencies. Earlier version of Portage considered all slots but now it's only the latest. > Hopefully, it'll > covered with portage-2.2. Let it be an invalid for now, but at least you're > aware. Thanks. > It will not be if you continue using just world. (In reply to comment #4) > > Run emerge --depclean after your updates and it will find and remove packages > > like those. > You would probably need emerge --depclean --with-bdeps=n for this to happen. > no, it won't. > run "emerge -pv tomcat" and you'll see that it still pulls both 1.5 and 1.6 > I don't know exactly why. > Because java is only ABI backwards compatible. So you need to build things with 1.5 although you can run them with 1.6. In general if you need more information please ask on one of our IRC support channels http://www.gentoo.org/main/en/irc.xml as bugzilla is not a support medium. (In reply to comment #4) > run "emerge -pv tomcat" and you'll see that it still pulls both 1.5 and 1.6 > I don't know exactly why. In addition to what Petteri already mentioned, there are also some known inconsistencies between update and depclean dependency calculations in portage-2.1.4.4. These inconsistencies are fixed in current portage-2.2_rc releases. |
