Adding own/custom rpms
Hi there, I have trouble adding my own rpms for an automated installation. Has anyone succeded with this and can post the necesserary steps? - I've tried + adding my own directory besides i586/i686/noarch, named "sven" or "custom" + adding my rpms to the directories above + adding a i386 directory with my rpms - I've called /usr/lib/YaST2/bin/create_package_descr + packages, packages.DU get updated and I can see my packages in there But when I create an ISO-Image not a single rpm is copied to the generated structure in /tmp/YaST.... I'm using autoyast2-installation-2.6.40-0 and autoyast2-2.6.40-0. Where's my fault? Sven
* Sven Thomsen <sven@tumelum.de> [Feb 04. 2003 18:51]:
Hi there,
I have trouble adding my own rpms for an automated installation.
Has anyone succeded with this and can post the necesserary steps?
- I've tried + adding my own directory besides i586/i686/noarch, named "sven" or "custom" + adding my rpms to the directories above + adding a i386 directory with my rpms
- I've called /usr/lib/YaST2/bin/create_package_descr + packages, packages.DU get updated and I can see my packages in there
But when I create an ISO-Image not a single rpm is copied to the generated structure in /tmp/YaST....
I'm using autoyast2-installation-2.6.40-0 and autoyast2-2.6.40-0.
Where's my fault?
when creating the ISO yast2 looks only in arch directories, i.e. i386, i586 etc. so other directories are skipped. Put all your RPMs in the respective arch dir and try again. Anas
Sven
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
-- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
Hi,
when creating the ISO yast2 looks only in arch directories, i.e. i386, i586 etc. so other directories are skipped. Put all your RPMs in the respective arch dir and try again.
OK, seems like my rpm isn't copied to the iso: <software> <addons config:type="list"/> <base>Minimal</base> <packages config:type="list"> <package>vnc</package> <package>harden_suse</package> <package>daemontools</package> </packages> </software> As you can see, for this example I'm using a minimal-installation and adding vnc, harden_suse (both from the 8.1 CDs) and daemontools (derived from a rpm --rebuild ....src.rpm). The daemontools-rpm ist located in i386: # ls -l dr-xr-xr-x 9 root root 102 2003-02-05 09:22 . drwxr-xr-x 14 root root 4096 2003-02-04 17:23 .. -r--r--r-- 1 root root 92 2002-09-14 01:20 TRANS.TBL drwxr-xr-x 2 root root 40 2003-02-05 09:22 i386 dr-xr-xr-x 2 root root 106496 2003-02-04 18:12 i586 dr-xr-xr-x 2 root root 67 2002-09-14 00:49 i686 dr-xr-xr-x 2 root root 16384 2002-09-14 00:51 noarch dr-xr-xr-x 2 root root 4096 2002-09-14 00:54 nosrc dr-xr-xr-x 4 root root 88 2002-09-14 00:49 setup dr-xr-xr-x 2 root root 6 2002-11-05 19:36 src # ls -l i386 insgesamt 48 drwxr-xr-x 2 root root 40 2003-02-05 09:22 . dr-xr-xr-x 9 root root 102 2003-02-05 09:22 .. -rw-r--r-- 1 root root 42689 2003-02-05 09:22 daemontools-0.70-3.i386.rpm Now I'm calling create_package_descr # /usr/lib/YaST2/bin/create_package_descr -d /export/media/suse_8.1/suse -l english -l german using settings: datadirs: /export/media/suse_8.1/suse languages: english,german output dir: ./setup/descr/ is not a directory: ignoring extra_provides: /usr/share/autoinstall/EXTRA_PROV ................ (dots deleted :-) done processed 2845 packages now recoding to UTF-8: packages packages.DU packages.en packages.de Ok, looking in packages, I see: # grep -A 10 -B 10 daemontools setup/descr/packages =Ver: 2.0 ##---------------------------------------- =Pkg: daemontools 0.70 3 i386 +Req: ld-linux.so.2 libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.2) -Req: =Grp: Utilities/System =Lic: See djb@pobox.com =Src: daemontools 0.70 3 src =Tim: 1039954306 =Loc: 1 daemontools-0.70-3.i386.rpm =Siz: 42689 152400 ##---------------------------------------- =Pkg: 3d_chess 0.8.1 687 i586 +Req: ld-linux.so.2 libICE.so.6 libSM.so.6 libX11.so.6 libXaw3d.so.7 libXext.so.6 Seems OK to me. Now, I create an iso-image with the yast2-GUI and mount it via loopback: # ls /mnt . ARCHIVES.gz COPYING.tex COPYRIGHT.yast INDEX.gz LIESMICH.DOS README.DOS TRANS.TBL autorun.inf boot.cat ls-lR.gz pubring.gpg .. COPYING COPYRIGHT ChangeLog LIESMICH README SuSEgo.ico autoinst.xml boot content media.1 suse # ls /mnt/suse . .. TRANS.TBL i386 i586 i686 noarch setup As one sees, there is an i386 directroy, but... # ls /mnt/suse/i386 . .. ...it's empty. All other packages, including vnc and harden_suse are in their correct directories on the image. So, looking in the log (/var/log/YaST2/y2log) I see: # grep harden_suse y2log 2003-02-05 10:31:42 <1> tigerente(12748) [YCP] autoinstall/packageMgmt.ycp(autoi nstPackages):81 package list needed during auto-installation: ["vnc", "harden_su se", "daemontools", "k_deflt", "k_athlon", "k_smp"] 2003-02-05 10:31:42 <1> tigerente(12748) [YCP] autoinstall/packageMgmt.ycp(creat eISO):283 install ["SuSEfirewall2 3.1 9 noarch", "acl 2.0.19 7 i586", <a long line, containing harden_suse, vnc but NOT daemontools> 2003-02-05 10:31:52 <1> tigerente(12748) [YCP] autoinstall/packageMgmt.ycp(creat eISO):325 Package to be copied: /export/media/suse_8.1//./suse/noarch/harden_sus e-3.5-219.noarch.rpm # grep daemontools y2log 2003-02-05 10:31:42 <1> tigerente(12748) [YCP] autoinstall/packageMgmt.ycp(autoinstPackages):81 package list needed during auto-installation: ["vnc", "harden_suse", "daemontools", "k_deflt", "k_athlon", "k_smp"] That's it, my package doesn't get copied... Any ideas? Sven
* Sven Thomsen <sven@tumelum.de> [Feb 05. 2003 10:58]:
Hi,
when creating the ISO yast2 looks only in arch directories, i.e. i386, i586 etc. so other directories are skipped. Put all your RPMs in the respective arch dir and try again.
OK, seems like my rpm isn't copied to the iso:
<software> <addons config:type="list"/> <base>Minimal</base> <packages config:type="list"> <package>vnc</package> <package>harden_suse</package> <package>daemontools</package> </packages> </software>
As you can see, for this example I'm using a minimal-installation and adding vnc, harden_suse (both from the 8.1 CDs) and daemontools (derived from a rpm --rebuild ....src.rpm).
The daemontools-rpm ist located in i386:
# ls -l dr-xr-xr-x 9 root root 102 2003-02-05 09:22 . drwxr-xr-x 14 root root 4096 2003-02-04 17:23 .. -r--r--r-- 1 root root 92 2002-09-14 01:20 TRANS.TBL drwxr-xr-x 2 root root 40 2003-02-05 09:22 i386 dr-xr-xr-x 2 root root 106496 2003-02-04 18:12 i586 dr-xr-xr-x 2 root root 67 2002-09-14 00:49 i686 dr-xr-xr-x 2 root root 16384 2002-09-14 00:51 noarch dr-xr-xr-x 2 root root 4096 2002-09-14 00:54 nosrc dr-xr-xr-x 4 root root 88 2002-09-14 00:49 setup dr-xr-xr-x 2 root root 6 2002-11-05 19:36 src
# ls -l i386 insgesamt 48 drwxr-xr-x 2 root root 40 2003-02-05 09:22 . dr-xr-xr-x 9 root root 102 2003-02-05 09:22 .. -rw-r--r-- 1 root root 42689 2003-02-05 09:22 daemontools-0.70-3.i386.rpm
Now I'm calling create_package_descr
# /usr/lib/YaST2/bin/create_package_descr -d /export/media/suse_8.1/suse -l english -l german
using settings: datadirs: /export/media/suse_8.1/suse languages: english,german output dir: ./setup/descr/ is not a directory: ignoring extra_provides: /usr/share/autoinstall/EXTRA_PROV ................ (dots deleted :-) done processed 2845 packages now recoding to UTF-8: packages packages.DU packages.en packages.de
Ok, looking in packages, I see:
# grep -A 10 -B 10 daemontools setup/descr/packages =Ver: 2.0 ##---------------------------------------- =Pkg: daemontools 0.70 3 i386 +Req: ld-linux.so.2 libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.2) -Req: =Grp: Utilities/System =Lic: See djb@pobox.com =Src: daemontools 0.70 3 src =Tim: 1039954306 =Loc: 1 daemontools-0.70-3.i386.rpm =Siz: 42689 152400 ##---------------------------------------- =Pkg: 3d_chess 0.8.1 687 i586 +Req: ld-linux.so.2 libICE.so.6 libSM.so.6 libX11.so.6 libXaw3d.so.7 libXext.so.6
Seems OK to me.
Did you replace the package source with the new one? You have to do that using the yast2 control center Software->Change source ....
Now, I create an iso-image with the yast2-GUI and mount it via loopback:
# ls /mnt . ARCHIVES.gz COPYING.tex COPYRIGHT.yast INDEX.gz LIESMICH.DOS README.DOS TRANS.TBL autorun.inf boot.cat ls-lR.gz pubring.gpg .. COPYING COPYRIGHT ChangeLog LIESMICH README SuSEgo.ico autoinst.xml boot content media.1 suse
# ls /mnt/suse . .. TRANS.TBL i386 i586 i686 noarch setup
As one sees, there is an i386 directroy, but...
# ls /mnt/suse/i386 . ..
...it's empty. All other packages, including vnc and harden_suse are in their correct directories on the image.
So, looking in the log (/var/log/YaST2/y2log) I see:
# grep harden_suse y2log
2003-02-05 10:31:42 <1> tigerente(12748) [YCP] autoinstall/packageMgmt.ycp(autoi nstPackages):81 package list needed during auto-installation: ["vnc", "harden_su se", "daemontools", "k_deflt", "k_athlon", "k_smp"]
2003-02-05 10:31:42 <1> tigerente(12748) [YCP] autoinstall/packageMgmt.ycp(creat eISO):283 install ["SuSEfirewall2 3.1 9 noarch", "acl 2.0.19 7 i586", <a long line, containing harden_suse, vnc but NOT daemontools>
2003-02-05 10:31:52 <1> tigerente(12748) [YCP] autoinstall/packageMgmt.ycp(creat eISO):325 Package to be copied: /export/media/suse_8.1//./suse/noarch/harden_sus e-3.5-219.noarch.rpm
# grep daemontools y2log
2003-02-05 10:31:42 <1> tigerente(12748) [YCP] autoinstall/packageMgmt.ycp(autoinstPackages):81 package list needed during auto-installation: ["vnc", "harden_suse", "daemontools", "k_deflt", "k_athlon", "k_smp"]
That's it, my package doesn't get copied...
Any ideas?
Yeah, you are using the old source. Try adding it and let us know if it works. Anas
Sven
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com -- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
Hi,
Did you replace the package source with the new one? You have to do that using the yast2 control center Software->Change source ....
OK, that's the problem: The package source already pointed to that specific directory before. I had to remove this entry and generate a new identical one. Now it works. So there's something happening upon adding a new package source, like updating YaST2 internal data structures. Is it possible to add a script to YaST2 ("update_XXX") or autoinst that does this? Thanks and greetings, Sven
Hello Anas, I just did an AutoYast2-Installation, Upgrade from SuSE-7.1 to SuSE-8.1. This is the most important server for our customer. I'm doing remote administration, so I cannot access the machine directly. The installation worked - but instead of performing the installation on '/dev/sda', as defined in the control file, this *§$%&# thing installed SuSE-8.1 on the data disk '/dev/sdb'. So now I can still boot SuSE-7.3, but all data of all users has been substituted by SuSE-8.1. How could this happen?! I'm really getting nervous now about using AutoYast at all. Please help me. Here's part of the control file: ------------------------------------------------------------------------ <general> <mode><confirm config:type="boolean">false</confirm></mode> <hwclock>localtime</hwclock> <keyboard> <keymap>german</keymap> </keyboard> <language>en_US</language> <mouse>probe</mouse> <timezone>Europe/Berlin</timezone> </general> <partitioning config:type="list" > <drive> <device>/dev/sda</device> <partitions config:type="list" > <partition> <crypt_fs config:type="boolean" >false</crypt_fs> <crypt_key></crypt_key> <filesystem config:type="symbol" >swap</filesystem> <filesystem_id config:type="integer" >131</filesystem_id> <format config:type="boolean" >true</format> <mount>swap</mount> <size>1gb</size> <type>Linux native</type> </partition> <partition> <crypt_fs config:type="boolean" >false</crypt_fs> <crypt_key></crypt_key> <filesystem config:type="symbol" >ext3</filesystem> <filesystem_id config:type="integer" >131</filesystem_id> <format config:type="boolean" >true</format> <mount>/</mount> <size>max</size> <type>Linux native</type> </partition> </partitions> <use>all</use> </drive> </partitioning> ------------------------------------------------------------------------ :-(Erik. --
* Erik Soyez <soyez@science-computing.de> [Feb 05. 2003 13:24]:
Hello Anas,
I just did an AutoYast2-Installation, Upgrade from SuSE-7.1 to SuSE-8.1. This is the most important server for our customer. I'm doing remote administration, so I cannot access the machine directly.
The installation worked - but instead of performing the installation on '/dev/sda', as defined in the control file, this *§$%&# thing installed SuSE-8.1 on the data disk '/dev/sdb'. So now I can still boot SuSE-7.3, but all data of all users has been substituted by SuSE-8.1.
How could this happen?! I'm really getting nervous now about using AutoYast at all. Please help me.
The only explaination would be that during installation /dev/sda was replaced by /dev/sdb, but this is only an assumption. I will need the u2log files to know exactly what went wrong. This is the first time such a thing happens and I checked the code again and there is no reson why this should happen. Can you please provide logs? Anas -- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
Hello Anas, this is NOT an AutoYast problem. It's a "Transtec Megaraid" problem. It's even not possible to install this machine manually, because during installation "/dev/sda" and "/dev/sdb" get switched internally. According to Transtec you have to take away the entire SCSI Controller in order to perform an installation - works as designed. Cool feature. Sorry for bothering you, Erik. On Thu, 6 Feb 2003, Anas Nashif wrote:
* Erik Soyez <soyez@science-computing.de> [Feb 05. 2003 13:24]:
Hello Anas,
I just did an AutoYast2-Installation, Upgrade from SuSE-7.1 to SuSE-8.1. This is the most important server for our customer. I'm doing remote administration, so I cannot access the machine directly.
The installation worked - but instead of performing the installation on '/dev/sda', as defined in the control file, this *§$%&# thing installed SuSE-8.1 on the data disk '/dev/sdb'. So now I can still boot SuSE-7.3, but all data of all users has been substituted by SuSE-8.1.
How could this happen?! I'm really getting nervous now about using AutoYast at all. Please help me.
The only explaination would be that during installation /dev/sda was replaced by /dev/sdb, but this is only an assumption. I will need the u2log files to know exactly what went wrong. This is the first time such a thing happens and I checked the code again and there is no reson why this should happen.
Can you please provide logs?
Anas -- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
--
participants (3)
-
Anas Nashif -
Erik Soyez -
Sven Thomsen