On Wednesday 13 September 2006 23:01, Lee Mayes wrote:
Hi Oliver,
On Wed, 2006-09-13 at 18:48 +0200, Oliver Schweikert wrote:
Instead of the 1.3 Gbyte from SLES sources, YaST claims to have only about 47 Mbyte to install and the first package (grub) fails to install at the %post script.
I have seen this as well (SLES10, using the SDK as an addon during install). It appears that between 2 different sources you can choose a selection of patterns that YaST cannot resolve correctly. When that happens, I see the symptom you describe. Here's a screen shot:
http://mayeses.com/temp/sles10.png
Here's the XML (it's an ugly set of patterns, I chose a bunch to force the error):
http://mayeses.com/temp/autoyast.xml17822.txt
Any idea, why YaST gets confused?
I really don't, but the ways I can force it imply that while the different sources resolved OK rpm-wise, the union of the two did not due to conflicts between the rpms.
Double check the dependencies and conflicts of the 2 sources and make sure one doesn't step on the other.
I also got the impression that it somehow makes a difference if I specify a certain package in a selection (or pattern) or in a <package></package> statement. I could reproduce the behavior you described if I specify "ksh" in a package statement but if I put it in a selection file it worked. Very strange. This is with SUSE Pro 10.1 and my two sources are the DVD copy and the official updates (created with the create_update_source script). The ksh package is in both sources with the newer rpm in the update source of course. Karsten. -- Pick another fortune cookie.