[opensuse-autoinstall] post-packages sles vs sled
On 11.2 at least, it seems like post-packages works fine for sles, but is completely ignored on sled installs. I've done some testing and am seeing no mention of autoyast even looking at post-packages on the sled installs. Is this a known difference? I saw another thread mentioning a known issue with opensuse 11.4 but that wouldn't explain why sles works and not sled. We have a package that mostly creates links, fun stuff like: /usr/lib64/libXaw3d.so.7 -> libXaw3d.so.8.0 for issues with older tools we still need to support. Rather then deal with trying to make sure dependencies are listed in the rpm itself to ensure the installation order, we just use the post-packages bit. Otherwise it would sometimes install before even the paths existed and would get wiped out by later rpm installs. This problem didn't seem to exist with sles/sled 10.x (for sure 10.4 that I've gone back and tested). -- Mike Marion-Unix SysAdmin/Sr. Staff IT Engineer-http://www.qualcomm.com O'Neill: "I hope you like Guinness sir. I find it a refreshing substitute for... food." ==> Stargate SG-1 -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
Hi On Wed, Mar 20, Mike Marion wrote:
On 11.2 at least, it seems like post-packages works fine for sles, but is completely ignored on sled installs. I've done some testing and am seeing no mention of autoyast even looking at post-packages on the sled installs.
Is this a known difference? I saw another thread mentioning a known issue with opensuse 11.4 but that wouldn't explain why sles works and not sled.
We have a package that mostly creates links, fun stuff like: /usr/lib64/libXaw3d.so.7 -> libXaw3d.so.8.0
for issues with older tools we still need to support. Rather then deal with trying to make sure dependencies are listed in the rpm itself to ensure the installation order, we just use the post-packages bit. Otherwise it would sometimes install before even the paths existed and would get wiped out by later rpm installs.
This problem didn't seem to exist with sles/sled 10.x (for sure 10.4 that I've gone back and tested).
Strange, there is nothing in autoyast code that should behave different in SLES/SLED/openSUSE per se. Differences between SLES/SLED regarding installation are mostly in file control.xml on install medium that controls which yast modules are started in which order and provides defaults (e.g. for partition proposal) and of course list of installed packages. Are you sure the SLES and SLED versions you compare are the same service pack? There might be bugs e.g. on SP1 or GA that are fixed in SP2. It could also be possible that package dependencies influence installation on two different environments. If it does not work as expected in SLED best would most probably be to file a bug report via Novell Customer Center. Bye, Thomas Fehr -- Thomas Fehr, SuSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Tel: +49-911-74053-0, Fax: +49-911-74053-482, Email: fehr@suse.de GPG public key available. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
On Thu, Mar 21, 2013 at 12:06:40PM +0100, Thomas Fehr wrote:
Strange, there is nothing in autoyast code that should behave different in SLES/SLED/openSUSE per se. Differences between SLES/SLED regarding installation
Yeah, that was exactly my thought.
are mostly in file control.xml on install medium that controls which yast modules are started in which order and provides defaults (e.g. for partition proposal) and of course list of installed packages. Are you sure the SLES and SLED versions you compare are the same service pack? There might be bugs e.g. on SP1 or GA that are fixed in SP2. It could also be possible that package dependencies influence installation on two different environments.
They're definitely the same level, ISOs downloaded at the same time.
If it does not work as expected in SLED best would most probably be to file a bug report via Novell Customer Center.
That's my next step, figured I'd ask here just in case it was well known and there was a known fix. Thanks. -- Mike Marion-Unix SysAdmin/Sr. Staff IT Engineer-http://www.qualcomm.com Antonio: "It's no fair. Some men drink deep from the fountain of life, while Antonio takes one sip and it goes down the wrong pipe!" --Wings -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
Hi again, On Thu, Mar 21, Mike Marion wrote:
If it does not work as expected in SLED best would most probably be to file a bug report via Novell Customer Center.
That's my next step, figured I'd ask here just in case it was well known and there was a known fix.
In the meanwhile I got another report about with a xml file where I could reproduce this and it seems that indeed post-install packages on SLED do not work in SLESD 11 SP2. So far it seems to be a problem outside of autoyast itself but one with handling control.xml. Tschuess, Thomas Fehr -- Thomas Fehr, SuSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Tel: +49-911-74053-0, Fax: +49-911-74053-482, Email: fehr@suse.de GPG public key available. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
participants (2)
-
Mike Marion -
Thomas Fehr