[opensuse-autoinstall] Adding the SLES10 SDK to a repository?
So, as with several other oddities, I've found my standard SLES9
method of using Yast2 to import the SDK as an add-on product is no
longer possible. How would one go about adding SLES10's SDK to an
autoyast repository properly? I've attempted using yast2 to create an
installation source, and adding this (actually `yast autoyast` added
this) following xml to an autoinstall.xml, but with no luck:
<add-on>
On Monday 09 April 2007 23:46:45 Michael T. Halligan wrote:
So, as with several other oddities, I've found my standard SLES9 method of using Yast2 to import the SDK as an add-on product is no longer possible. How would one go about adding SLES10's SDK to an autoyast repository properly? I've attempted using yast2 to create an installation source, and adding this (actually `yast autoyast` added this) following xml to an autoinstall.xml, but with no luck:
<add-on>
<listentry> </add-on>ftp://10.1.100.9/SLES10SDK <product>SUSE-Linux-Enterprise-SDK-x86_64</product>/ </listentry>What am I doing wrong?
Hi Michael Without seeing your logs of the failed install it's pretty hard to say. I've had pretty good luck with quickly creating add on sources with the Addon Creator Yast package: http://developer.novell.com/wiki/index.php/Creating_Add-on_Media_with_YaST It's only a test/beta version but works pretty well. I've managed to create auto install repos of the HP PSP rpms, Tomcat 5.5 from the build service and more. Create the repo using that tool, signing it with your key and then use an sml snippet just like you have there to provice it to the profile. Don't forget the import key setting that Uwe pointed out if you are using your own signing key. Cheers Pete -- Peter Connolly Technical Specialist, Novell Consulting M: + 44 7712 487115. E: pconnolly@novell.com -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
On Apr 10, 2007, at 1:06 AM, Peter Connolly wrote:
On Monday 09 April 2007 23:46:45 Michael T. Halligan wrote:
So, as with several other oddities, I've found my standard SLES9 method of using Yast2 to import the SDK as an add-on product is no longer possible. How would one go about adding SLES10's SDK to an autoyast repository properly? I've attempted using yast2 to create an installation source, and adding this (actually `yast autoyast` added this) following xml to an autoinstall.xml, but with no luck:
<add-on>
<listentry> </add-on>ftp://10.1.100.9/SLES10SDK <product>SUSE-Linux-Enterprise-SDK-x86_64</product>/ </listentry>What am I doing wrong?
Hi Michael
Without seeing your logs of the failed install it's pretty hard to say. I've had pretty good luck with quickly creating add on sources with the Addon Creator Yast package:
Logs? What are these logs you speak of?
http://developer.novell.com/wiki/index.php/Creating_Add- on_Media_with_YaST
It's only a test/beta version but works pretty well. I've managed to create auto install repos of the HP PSP rpms, Tomcat 5.5 from the build service and more. Create the repo using that tool, signing it with your key and then use an sml snippet just like you have there to provice it to the profile. Don't forget the import key setting that Uwe pointed out if you are using your own signing key.
Should I have to go through all this trouble for a repository that SuSE created, the SDK? There must be an easier way. I've followed UWE's minimal instructions to the very last detail, and autoyast is clearly broken. If I can manually add an installation source to an existing system, there's no reason I shouldn't be able to add that to a server installing through autoyast, especially since all of the packages come directly from Novell.
Cheers
Pete
-- Peter Connolly Technical Specialist, Novell Consulting M: + 44 7712 487115. E: pconnolly@novell.com
-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall +help@opensuse.org
-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Hi Michael On Tuesday 10 April 2007 17:12:41 Michael T. Halligan wrote:
On Apr 10, 2007, at 1:06 AM, Peter Connolly wrote:
On Monday 09 April 2007 23:46:45 Michael T. Halligan wrote:
So, as with several other oddities, I've found my standard SLES9 method of using Yast2 to import the SDK as an add-on product is no longer possible. How would one go about adding SLES10's SDK to an autoyast repository properly? I've attempted using yast2 to create an installation source, and adding this (actually `yast autoyast` added this) following xml to an autoinstall.xml, but with no luck:
<add-on>
<listentry> </add-on>ftp://10.1.100.9/SLES10SDK <product>SUSE-Linux-Enterprise-SDK-x86_64</product>/ </listentry>What am I doing wrong?
Hi Michael
Without seeing your logs of the failed install it's pretty hard to say. I've had pretty good luck with quickly creating add on sources with the Addon Creator Yast package:
Logs? What are these logs you speak of?
Have a look at /var/log/YaST2 straight after installation on the target machine and you should see a collection of logs outlining what happened during the installation. The y2log(-?) files are the ones that should show how the installation sources were viewed and handled by autoyast.
http://developer.novell.com/wiki/index.php/Creating_Add- on_Media_with_YaST
It's only a test/beta version but works pretty well. I've managed to create auto install repos of the HP PSP rpms, Tomcat 5.5 from the build service and more. Create the repo using that tool, signing it with your key and then use an sml snippet just like you have there to provice it to the profile. Don't forget the import key setting that Uwe pointed out if you are using your own signing key.
Should I have to go through all this trouble for a repository that SuSE created, the SDK?
You are correct, the SDK should have its contents signed by a trusted key that autoyast will accept. Recently I've been working with a customer that required only packages signed by themselves to be accepted by autoyast for security reasons.
There must be an easier way. I've followed UWE's minimal instructions to the very last detail, and autoyast is clearly broken. If I can manually add an installation source to an existing system, there's no reason I shouldn't be able to add that to a server installing through autoyast, especially since all of the packages come directly from Novell.
Cheers
Pete
If you can send me the contents of the y3log, and the y2log-1 (etc.) I'll have a look through to see if I can spot anything. I've yet to try including the SDK as an installation source beside the main OS, but should be in a position to try this early next week. Probably too far away for you :( If the logs are too large for the list, mail directly. I'll try to help. Cheers Pete -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Michael T. Halligan wrote:
So, as with several other oddities, I've found my standard SLES9 method of using Yast2 to import the SDK as an add-on product is no longer possible. How would one go about adding SLES10's SDK to an autoyast repository properly? I've attempted using yast2 to create an installation source, and adding this (actually `yast autoyast` added this) following xml to an autoinstall.xml, but with no luck:
<add-on>
<listentry> </add-on>ftp://10.1.100.9/SLES10SDK <product>SUSE-Linux-Enterprise-SDK-x86_64</product>/ </listentry>What am I doing wrong? --To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Hi Michael,
Here's what relevant stuff that ends up in my autoyast.xml file:
<profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns">
<add-on>
participants (3)
-
Lee Mayes -
Michael T. Halligan -
Peter Connolly