Hi! On Friday 04 August 2006 15:44, Frank Steiner wrote:

after failing to integrate own packages into the standard SuSE sources (see my former mail), I tried the way described for SuSE 10.1.

I created a file add_on_products in the SuSE source directory, with content nfs:///rpm-export/i586/10.1/addons

In this directory I added a i586/ subdirectory, containing my own packages, and called create_package_descr, so that the addons subdir now contains i586/ setup/

But autoyast still fails to add e.g. the kernelbio-source rpm that I include in the <packages> list. Looking at y2log I see that AY mounts the addons directory and tries to identify it as some sort of source:

First it tries to find /repodata/repomd.xml and concludes it's not a YUM source. Then it fails to find /media/media.1, so it's also not a "SUSE tags source", then AY says "No next type of source" and fails to add the addons/ directory.

What's wrong? What else do I need to do? The online HOWTO and the FAQ don't mention anything else...

It looks like the HOWTO is lacking the media.1 directory description. For the SUSE tags source, this directory is a must. You have to create one, hopefully the example from the SL10.1 CD are sufficient to create such directory for your media... -- Regards, Jiri Srain YaST2 developer --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 2 9654 2373 190 00 Praha 9 fax: +420 2 9654 2374 Czech Republic http://www.suse.cz

Uwe Gansert wrote

On Friday 04 August 2006 15:44, Frank Steiner wrote:

...

What's wrong? What else do I need to do? The online HOWTO and the FAQ don't mention anything else...

did you follow these: http://www.suse.de/~ug/AutoYaST_FAQ.html#b9 instructions?

I misunderstood the functionality of the create_update_source.sh script and tried to create the update source manually. Sorry, my fault! Works now! -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

On Monday 07 August 2006 13:35, Frank Steiner wrote:

I put this in my profile:

<general> <signature-handling> true </signature-handling> ... </general>

and in y2log I can see it's parsed. But I still get the warning about the content file in this update source not being signed. So the automatic installation stops because I have to answer the question manually :-(

10.1 or SLES10? If it's 10.1 -> ftp://ftp.suse.com/pub/people/ug/autoyast use the 10.1 root fix V0.2 -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Business: http://www.suse.de/~ug now playing Agonoize - chains of love

Uwe Gansert wrote

On Monday 07 August 2006 13:40, Uwe Gansert wrote:

...

10.1 or SLES10?

10.1

...

If it's 10.1 -> ftp://ftp.suse.com/pub/people/ug/autoyast use the 10.1 root fix V0.2

I knew I wrote something about that a while ago. Here it is: http://lists.suse.com/archive/suse-autoinstall/2006-Jun/0109.html

Ok, sorry I missed that! It solves the problem. However, two issues remain: 1) You write that for x86_64 systems, the bugfix script should be executed on an x86_64 system. But we plan to use the sources forinstalling both architectues, x86 and x86_64, with autoyast. So where should we execute the script? Will it work for x86 systems if we run it on x86_64 systems? If we need two different driverupdate files, can we handle that somehow via pxelinux? We have specific tftpboot directories for x86 and x86_64 with the according initrd and kernel files. Can we send a specific driverupdate file, too? 2) As soon as I use my additional source via add_on_products, AY ignores all files from the base selection. My profile looks like this: <software> <base>Minimal</base> <packages config:type="list"> <package>sendmail</package> <package>lilo</package> <package>kernelbio-source</package> <package>texinfo</package> </packages> <remove-packages config:type="list"> <package>kernel-source</package> <package>postfix</package> <package>grub</package> </remove-packages> </software> The "kernelbio-source" is a package in my additional source. This works and installs all packages from the Minimal selection and the addon packages as long as I have no add_on_products file. When I use it, AY doesn't complain anymore about the kernelbio-source file, but it *only* installs sendmail, lilo, kernelbio-source and texinfo. Of course, each of these packages fails because bash etc. is missing. Have you seen sth. like that before? cu, Frank P.S.: Really great fotos :-) -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *