Still unclear on adding additional packages with SLES9-SP2
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 First off, I've read through the list archives, and there are so many conflicting methods for doing this, I'm back to square one. In redhat, all I would do is symlink my packages into my main RPM directory, then run genhdlist. My understanding from Novell's very spares documentation is that I would do something similar, but it does not work, and breaks in a rather ugly way each time. My source tree looks like this : rwxr-xr-x 6 root root 456 Nov 3 17:17 . drwxr-xr-x 5 root root 152 Nov 3 16:20 .. drwxr-xr-x 7 root root 168 Nov 3 10:17 SUSE-CORE-Version-9 drwxr-xr-x 5 root root 120 Nov 3 10:42 SUSE-SLES-9-Service-Pack- Version-2 drwxr-xr-x 3 root root 72 Nov 3 10:11 SUSE-SLES-Version-9 lrwxrwxrwx 1 root root 28 Nov 3 10:58 boot -> SUSE-SLES- Version-9/CD1/boot lrwxrwxrwx 1 root root 31 Nov 3 10:58 content -> SUSE-SLES- Version-9/CD1/content lrwxrwxrwx 1 root root 35 Nov 3 11:07 control.xml -> SUSE-SLES- Version-9/CD1/control.xml lrwxrwxrwx 1 root root 51 Nov 3 11:07 driverupdate -> SUSE- SLES-9-Service-Pack-Version-2/CD1/driverupdate lrwxrwxrwx 1 root root 44 Nov 3 10:58 linux -> SUSE-SLES-9- Service-Pack-Version-2/CD1/linux lrwxrwxrwx 1 root root 31 Nov 3 11:02 media.1 -> SUSE-SLES- Version-9/CD1/media.1 - -rw-r--r-- 1 root root 5081 Nov 3 16:41 part.xml drwxr-xr-x 2 root root 104 Nov 3 10:18 yast I've tried adding packages to: SUSE-CORE-Version-9/CD1/suse/x86_64 SUSE-CORE-Version-9/CD1/suse/addons SUSE-CORE-Version-9/CD1/suse/updates SUSE-SLES-9-Service-Pack-Version-2/CD1/suse/x86_64 SUSE-SLES-9-Service-Pack-Version-2/CD1/suse/addons SUSE-SLES-9-Service-Pack-Version-2/CD1/suse/updates SUSE-SLES-Version-9/CD1/suse/x86_64 SUSE-SLES-Version-9/CD1/suse/addons SUSE-SLES-Version-9/CD1/suse/updates From the "suse" directory all of those above paths, I've tried: create_package_descr -x ./setup/descr/EXTRA_PROV -d . create_package_descr -x ./setup/descr/EXTRA_PROV -d addons create_package_descr -x ./setup/descr/EXTRA_PROV -d updates The effect is the same, either errors during the autoyast, which is unable to find the added rpms, or a newly created depdency hell where autoyast tries installing conflicting versions of packages like lvm, and becomes unusable (only fixable by rebuilding my source-tree). Does anybody have a good answer to a working way, that doesn't involve "please look back through the archives"? I'd be really grateful! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDaxHZwjCqooJyNAMRAsw2AJ9BkXwIpNdKEKY3KrDJRrlNMZ009QCeOv3T Ma10UO+eSKx1032vvTvEXwA= =nl2K -----END PGP SIGNATURE-----
On Friday 04 November 2005 08:46, Michael T. Halligan wrote:
First off, I've read through the list archives, and there are so many conflicting methods for doing this, I'm back to square one. In redhat, all I would do is symlink my packages into my main RPM directory, then run genhdlist.
I'm not an expert on this but can you try the following? change to this directory:
My source tree looks like this :
rwxr-xr-x 6 root root 456 Nov 3 17:17 . drwxr-xr-x 5 root root 152 Nov 3 16:20 .. drwxr-xr-x 7 root root 168 Nov 3 10:17 SUSE-CORE-Version-9
use the create_update_source.sh from www.suse.de/~ug Start the script like this: create_update_source.sh . a directory "updates" should appear. Copy your RPM to that directory like this: cp myRPM-1.23-4.5.i586.rpm updates/suse/i586/ cd updates/suse create_package_descr -x setup/descr/EXTRA_PROV -l english -l spanish -l french -l german -l czech -l hungarian -l italian I hope that's it. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
On Friday 04 November 2005 12:19, Uwe Gansert wrote: sorry, lame self reply but what I wrote could be missunderstood
:
My source tree looks like this :
rwxr-xr-x 6 root root 456 Nov 3 17:17 . drwxr-xr-x 5 root root 152 Nov 3 16:20 .. drwxr-xr-x 7 root root 168 Nov 3 10:17 SUSE-CORE-Version-9
by "change to this directory" I did not mean the "SUSE-CORE-Version-9" directory but the directory that contains the SUSE-CORE-Version-9 directory. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Uwe, You're awesome. That worked perfectly. I was trying to follow the directions from Novell telling me to put them in the normal path, which was causing all sorts of lovely depdency errors.. like not installing DMAPI or LVM2, making my lvm root group unbootable :) That worked great. I owe you one! Michael On Nov 4, 2005, at 3:22 AM, Uwe Gansert wrote:
On Friday 04 November 2005 12:19, Uwe Gansert wrote:
sorry, lame self reply but what I wrote could be missunderstood
:
My source tree looks like this :
rwxr-xr-x 6 root root 456 Nov 3 17:17 . drwxr-xr-x 5 root root 152 Nov 3 16:20 .. drwxr-xr-x 7 root root 168 Nov 3 10:17 SUSE-CORE-Version-9
by "change to this directory" I did not mean the "SUSE-CORE-Version-9" directory but the directory that contains the SUSE-CORE-Version-9 directory.
-- ciao, Uwe Gansert
Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDa/IzwjCqooJyNAMRAsoEAJ9zCapjW+mvTkuHd308Vk7XYPNp6ACfUTZn O5B2erkA+4fg+ZfaypgJHgs= =puN5 -----END PGP SIGNATURE-----
participants (2)
-
Michael T. Halligan -
Uwe Gansert