Custom Package Selection
Hi, I'm trying to load a target with a customized minimal set of packages. I followed the instructions on Config and Installation Options 5.2 but I get to the Configure Software Selections part and a window pops up saying "Cannot set base selection", and when I ok that I get "Error while configuring software selections". I'm suspicious of the examples 4.20 and 4.21 because it seems like the =Sel should be 'My' and the category should be Base-System and not addon in order to be picked up in 4.21 by the <base>My</base>. I've tried the examples and variations and I always get the same errors. Here's what it looks like <software> <addons config:type="list"> <addon>Base-System</addon> <addon>YaST2</addon> </addons> <base>My</base> </software> If I replace My with Minimal it works fine. What am I missing? Is there some way to know in greater detail what is going wrong? The My.sel has a large list of packages from a previous inhouse installation. Could that be interacting in a bad way so that I would see the errors I'm getting? Maybe I need to cull out any overlap between My and Base-System? One more easy one, how do I select a valid =Ord value for my Selection? Thanks a lot, Brian
OK, I cut down the My.sel to hardly anything just for testing. And yes I did add the My.sel to the files selections and directory.yast. # My linux package selection 1.1 =Ver: 1.1 =Sel: My =Sum: My installation selection of packages =Cat: addon =Vis: true =Ord: 108 +Ins acroread susehelp_en howtoenh mozilla minicom -Ins: I left out the <base> selection, and added the My to the addons. Now I get "Could not set add-on selections". I verified that there was no overlap with My package list and the others. So what do I need to do? Brian On Wednesday 01 December 2004 4:09 pm, Brian Corriveau wrote:
Hi,
I'm trying to load a target with a customized minimal set of packages. I followed the instructions on Config and Installation Options 5.2 but I get to the Configure Software Selections part and a window pops up saying "Cannot set base selection", and when I ok that I get "Error while configuring software selections". I'm suspicious of the examples 4.20 and 4.21 because it seems like the =Sel should be 'My' and the category should be Base-System and not addon in order to be picked up in 4.21 by the <base>My</base>. I've tried the examples and variations and I always get the same errors. Here's what it looks like <software> <addons config:type="list"> <addon>Base-System</addon> <addon>YaST2</addon> </addons> <base>My</base> </software>
If I replace My with Minimal it works fine. What am I missing? Is there some way to know in greater detail what is going wrong? The My.sel has a large list of packages from a previous inhouse installation. Could that be interacting in a bad way so that I would see the errors I'm getting? Maybe I need to cull out any overlap between My and Base-System?
One more easy one, how do I select a valid =Ord value for my Selection?
Thanks a lot, Brian
It depends on the release you are installing. Take one of the selection files from the release as reference. Anas Brian Corriveau wrote:
OK, I cut down the My.sel to hardly anything just for testing. And yes I did add the My.sel to the files selections and directory.yast.
# My linux package selection 1.1 =Ver: 1.1
=Sel: My
=Sum: My installation selection of packages
=Cat: addon
=Vis: true
=Ord: 108
+Ins acroread susehelp_en howtoenh mozilla minicom -Ins:
I left out the <base> selection, and added the My to the addons. Now I get "Could not set add-on selections". I verified that there was no overlap with My package list and the others. So what do I need to do?
Brian
On Wednesday 01 December 2004 4:09 pm, Brian Corriveau wrote:
Hi,
I'm trying to load a target with a customized minimal set of packages. I followed the instructions on Config and Installation Options 5.2 but I get to the Configure Software Selections part and a window pops up saying "Cannot set base selection", and when I ok that I get "Error while configuring software selections". I'm suspicious of the examples 4.20 and 4.21 because it seems like the =Sel should be 'My' and the category should be Base-System and not addon in order to be picked up in 4.21 by the <base>My</base>. I've tried the examples and variations and I always get the same errors. Here's what it looks like <software> <addons config:type="list"> <addon>Base-System</addon> <addon>YaST2</addon> </addons> <base>My</base> </software>
If I replace My with Minimal it works fine. What am I missing? Is there some way to know in greater detail what is going wrong? The My.sel has a large list of packages from a previous inhouse installation. Could that be interacting in a bad way so that I would see the errors I'm getting? Maybe I need to cull out any overlap between My and Base-System?
One more easy one, how do I select a valid =Ord value for my Selection?
Thanks a lot, Brian
On Wednesday 01 December 2004 5:13 pm, Anas Nashif wrote:
It depends on the release you are installing. Take one of the selection files from the release as reference. I am using SLES 9.
From looking at Minimal .sel it is hard to know exactly what is going on. Maybe you could describe how the following works: +Req: Base-System YaST2 -Req: +Con: Minimal+X11 default Standard Alles -Con: What does Req mean? What does Con mean? When I install the Minimal I didn't think I got any X11 packages so it almost looks like Req brings in other Selection files and Con is being used to satisfy some requirements from other Selection files, though I don't understand why Minimal+X11 is there. Is =Ord just a unique number among the selection files? Thanks, Brian
Install yast2-packagemanager-devel and take a look at /usr/share/doc/packages/yast2-packagemanager/selection-descr.html Anas Brian Corriveau wrote:
On Wednesday 01 December 2004 5:13 pm, Anas Nashif wrote:
It depends on the release you are installing. Take one of the selection files from the release as reference.
I am using SLES 9.
From looking at Minimal .sel it is hard to know exactly what is going on. Maybe you could describe how the following works:
+Req: Base-System YaST2 -Req:
+Con: Minimal+X11 default Standard Alles -Con:
What does Req mean? What does Con mean? When I install the Minimal I didn't think I got any X11 packages so it almost looks like Req brings in other Selection files and Con is being used to satisfy some requirements from other Selection files, though I don't understand why Minimal+X11 is there.
Is =Ord just a unique number among the selection files?
Thanks, Brian
The problem was that my version was not 3.0. From the documentation it sounds like version could be a local product, but I guess it relates to the EXACT suse version 3.0 for the autoyast product as only 3.0 seems to work. On Friday 03 December 2004 11:52 am, Anas Nashif wrote:
Install yast2-packagemanager-devel and take a look at
/usr/share/doc/packages/yast2-packagemanager/selection-descr.html
Anas
participants (2)
-
Anas Nashif -
Brian Corriveau