Joachim, On Friday 30 December 2005 07:47, Joachim Schrod wrote:
Hi,
On some 10.0 systems, I use YOU for online updates. At 20 Dec, new Java packages appeared and got installed by me.
Now, package dependencies are broken, yast2 reports conflicts for *tomcat* and lots of java-1_4_2* packages.
This is because java-1_4_2-sun-src didn't got updated, too, and still has the dependency on the old java-1_4_2-sun package. Deleting java-1_4_2-sun-src does the job and restores consistency.
What is the nature of the inconsistency? How does it manifest itself? Nothing literally depends on the Java source code. It's provided as an aid to Java developers for things like debugging (being able to step into the source code of standard libraries with a source debugger, e.g.). While it would be best to have the latest version of the source, nothing will malfunction because of it. It's even possible that the difference in the newere release supplied by the YOU update did not originate in any changes in that source code (it could very well be in proprietary source that's not distributed by Sun). I'm frankly more concerned that SuSE Watcher did not alert me to the Java updates nor the Perl update nor the binutils update, all of which were available for my installation.
Anybody in the know, if those broken dependency will be resolved in the future, and a java-1_4_2-sun-src package will be released?
In my experience when the rare packaging error slips through it does get corrected fairly quickly.
Thanks in advance for any answer,
Joachim
Randall Schulz