Hello,
I want to create a single installation DVD, that contains SLES10 and customer packages. The DVD shall also act as network installation source, when it is mounted.
When using SLES8 I put the customer packages among the SLES packages and update the package description, and all works fine.
Now i try to separate SUSE and customer rpms, but cannot get it to work (all while automatic installation process):
add-on product approach: YaST expects an URL in the add_on_product file, but i can only provide a relative path, because if the media is used from a drive the protocol is cd://, but when acting as network source it is ftp://.
Is there a way to specify the add-on product path relative to the media root?
multi-product approach: When I append my product to /media.1/products (*asc/*key removed and <signature-handling> adjusted to accept it), the meta data are read from YaST myprod/setup/descr/packages,...), but if i define a package from this product YaST messes up the package selection and the installation fails:
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.
Any idea, why YaST gets confused? Oliver
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.
Best Regards,
Lee
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.
Thanks for your help. I took your hint with the pattern and tried to use a pattern file instead of selecting single packages, but I could not get it to work. y2log just complained "Could not set patterns or selections:" :-(
BTW: Has anybody a description of the pattern file tags. Some meanings seem more obvious, other ones less (e.g. Ord. Prq vs.Prc)?
Although the multi-product stuff is available at least since SLES8 - where I have tested it without success ;-) - it feels still too experimental too me, to rely on it for productive usage.
I will do it the old way and merge different rpm sources to one single product media.
Regards Oliver
On Wednesday 13 September 2006 18:48, Oliver Schweikert wrote:
add-on product approach: YaST expects an URL in the add_on_product file, but i can only provide a relative path, because if the media is used from a drive the protocol is cd://, but when acting as network source it is ftp://.
Is there a way to specify the add-on product path relative to the media root?
no but have you tried to add ftp and cd to the file? I think it does not hurt if one is not available
autoinstall@lists.opensuse.org
-
Karsten Künne -
Lee Mayes -
Oliver Schweikert -
Uwe Gansert