Mailinglist Archive: opensuse-autoinstall (27 mails)

["Andreas Taschner" <ataschner@xxxxxxxxxx>]

Hi

I have created a YaST client module that snaps into the AutoYaST workflow for 
running displaying the progress of custom scripts 
(http://www.novell.com/communities/node/8961/) and a part of this game is to 
modify <instsrc>/control.xml.

While this works fine for SLES 10, SLES 11 is more careful.
First it gave me an error like this :
  <instsrc>/control.xml : SHA1 sum wrong.
  If you really trust your repository, you may continue in an insecure mode.
  (OK/Back)

Hmm ... OK fair enough - naively I entered a new SHA1 sum in <instsrc>/content 
hoping that would be it.
:(
Now I get a less friendly popup saying :
  <instsrc>/content: Invalid signature
  Aborting installation

I see there is a content.key file, but since I don't know the password to it, 
it guess it is useless to try to generate a new content.asc.

Is there any way around this, or do we not want customer's to port their 
customizations to SLE 11 ?

Thanks.

Best regards
Andreas Taschner

--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-autoinstall+help@xxxxxxxxxxxx