On Fri, Oct 2, 2009 at 20:53, Jason Babicka
Thank you for your suggestion. I took your snippet and altered it so that it would be applicable to my add-on product and placed it in the autoinst.xml file that I have been using. Unfortunately, the results that I got were the same as to what I originally reported experiencing.
My apologies, I overlooked you use SLES10.2, so it might not be possible to use per-add-on-product gpg settings. If that is the case, try putting them in the global settings in <general><signature-handling> (if you didn't already do that in your alterations).
I checked the /var/log/YaST2/y2log script after the installation had completed. Using grep with your suggested keywords (throw and fail) did not yield any results surprisingly. I manually reviewed the entire log. Unfortunately again this did not yield any further information as nothing that I read through seemed to be related to the error message encountered, reference my add-on product rpm or add-on product name.
Stepping back to you original error message containing "Source rejected by the user", I would assume two possible cases: First, it might be you're still missing some gpg setting (maybe because the above changes where made on a per-addon basis and where ignored by autoyast). Another thing to look for in the logs is something like "user decision on <something like import>: 0", which indicates something went wrong with your import settings. I guess you have to at least use bioth accept_non_trusted_gpg_key and import_gpg_key, maybe even accept_unknown_gpg_key if your key is from a local/unknown CA. Second, it might be the case that the path to your addon is invalid. The only reference on device names I could find in the context of the old add_on_product file is (see further down below http://www.suse.de/~ug/AutoYaST_FAQ.html#b9) to use something like this: hd:/updates?device=/dev/your-dvd-device / It might be easier to use <add-on>, maybe with a relative path (as described in http://forgeftp.novell.com/yast/doc/SL11.1/tdg/installation_features.html) if that is supported in 10.2... In any case, the latter error message about the resolver happens because the add-on does not work and hence not all packages can be found. To help find the cause of the problem, try reading y2log during install: When the first error message appears, don't confirm it, but switch to the second terminal and read the last few dozen lines of the file, your problem hides there. tty, 686f6c6d -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org