[opensuse-autoinstall] steps to create an update source
Hi, I have a few custom built RPMs that we would like to install on our SLES 11 and opensuse 11.1 machines via autoyast. I looked around the autoyast website and a few other lists and such and cant' quite get all the parts right to do this. For now I am simply trying to create the update source then I go to a SLES 11 machine and try to add that as a "Software Repository" just to test if the update source works. When I do this I get this error message: "No repository index in content file" Here are the steps I followed to create the update source:
create_update_source.sh dist/ mkdir -p dist/updates/suse/x86_64 cp *.rpm dist/updates/suse/x86_64/ cd dist/updates/suse/ create_package_descr -x setup/descr/EXTRA_PROV cd setup/descr/ create_directory.yast . create_md5sums .
last I edit the "dist/updates/content" file to look like this:
cat dist/updates/content VENDOR SuSE Linux AG CREATIONDATE 20090329125112 VERSION 1 LABEL My Software
Any ideas as to what I am missing in the creating of the update source that might cause the "No repository index in content file" error message? Thanks Rene -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
in case this helps here is what the directory structure looks like for the update source: dist/ |-- updates | |-- content | |-- directory.yast | |-- media.1 | | |-- directory.yast | | |-- media | | `-- products | |-- packages | |-- packages.DU | |-- packages.en | `-- suse | |-- ppc64 | | |-- mx-1.2.8-6.ppc64.rpm | | |-- panfs-2.6.27.19-5-ppc64-mp-3.4.0-381771.23.sles_11_ppc64.rpm | | |-- pdsh-2.17-1.ppc64.rpm | | |-- pdsh-rcmd-rsh-2.17-1.ppc64.rpm | | `-- pdsh-rcmd-ssh-2.17-1.ppc64.rpm | `-- setup | `-- descr | |-- MD5SUMS | |-- directory.yast | |-- packages | |-- packages.DU | `-- packages.en `-- yast |-- instorder `-- order -----Original Message----- From: Salmon, Rene [mailto:salmr0@bp.com] Sent: Sun 3/29/2009 1:18 PM To: opensuse-autoinstall@opensuse.org Subject: [opensuse-autoinstall] steps to create an update source Hi, I have a few custom built RPMs that we would like to install on our SLES 11 and opensuse 11.1 machines via autoyast. I looked around the autoyast website and a few other lists and such and cant' quite get all the parts right to do this. For now I am simply trying to create the update source then I go to a SLES 11 machine and try to add that as a "Software Repository" just to test if the update source works. When I do this I get this error message: "No repository index in content file" Here are the steps I followed to create the update source:
create_update_source.sh dist/ mkdir -p dist/updates/suse/x86_64 cp *.rpm dist/updates/suse/x86_64/ cd dist/updates/suse/ create_package_descr -x setup/descr/EXTRA_PROV cd setup/descr/ create_directory.yast . create_md5sums .
last I edit the "dist/updates/content" file to look like this:
cat dist/updates/content VENDOR SuSE Linux AG CREATIONDATE 20090329125112 VERSION 1 LABEL My Software
Any ideas as to what I am missing in the creating of the update source that might cause the "No repository index in content file" error message? Thanks Rene -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
On Sunday 29 March 2009 20:18:06 Salmon, Rene wrote:
I have a few custom built RPMs that we would like to install on our SLES 11 and opensuse 11.1 machines via autoyast. I looked around the autoyast website and a few other lists and such and cant' quite get all the parts
you should read the description of "create_update_source" on http://www.suse.de/~ug/ That should lead you to an add-on that you can add during a manual installation (try that first before you try to use it in autoyast, so you can be sure your add-on is okay). Use the create_update_source script that is delivered with SLES11/openSUSE11.1 Then you should read: http://ugansert.blogspot.com/2009/01/opensuse-111-sles11-and-add-ons.html
"No repository index in content file"
hm. I have never seen that. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
you should read the description of "create_update_source" on http://www.suse.de/~ug/ That should lead you to an add-on that you can add during a manual installation (try that first before you try to use it in autoyast, so you can be sure your add-on is okay). Use the create_update_source script that is delivered with SLES11/openSUSE11.1
Ok I am givin that a try thanks for the links. Here is what i get now. hpci6002:# create_update_source.sh dist/ hpci6002:# mkdir -p dist/updates/suse/ppc64 hpci6002:# cp *.rpm dist/updates/suse/ppc64/ hpci6002:# cd dist/updates/suse/ hpci6002:# create_package_descr -x setup/descr/EXTRA_PROV hpci6002:# cd setup/descr hpci6002:# ls > directory.yast hpci6002:# cd ../../.. hpci6002:# create_sha1sums -x -n . The "create_sh1sums" command modified my content file and now it looks like this: hpci6002:# cat content BASEARCHS ppc64 DATADIR suse DESCRDIR suse/setup/descr LABEL MY Software META SHA1 b13be3f545d68149e5cd9258ceb48dbc5edb627f packages META SHA1 41b1460da2116281f4bc63de26563210ff47c036 packages.DU META SHA1 118debabb5e3875c6d04ac6efb05627828dcf95a packages.en Now when i go add my software repository I on my sles 11 box I get this message: 'repo2solv.sh '-o-' '/var/cache/zypp/solv/My_software' /var/cache/zypp/raw/My_Software' repo_content 'content' incomplete, no product solvable created! I take it that means there is something wrong with my content file above. Any ideas as to what I am missing?
Then you should read: http://ugansert.blogspot.com/2009/01/opensuse-111-sles11-and-add-ons.html
"No repository index in content file"
hm. I have never seen that.
Read through the blog entry Thanks. Once I get this working I will
probably use the easy option which is to add something like this to my
auto yast:
<add-on>
On Monday 30 March 2009 19:57:37 Rene Salmon wrote:
hpci6002:# create_update_source.sh dist/
in "dist" is your real 11.1 installation source? Do you use the 11.1 inst-source-utils package? because ....
The "create_sh1sums" command modified my content file and now it looks like this:
hpci6002:# cat content BASEARCHS ppc64 DATADIR suse DESCRDIR suse/setup/descr LABEL MY Software
my updates/content file begins like this: CONTENTSTYLE 11 BASEARCHS i586 x86_64 DATADIR suse DESCRDIR suse/setup/descr DISTRIBUTION openSUSE FLAVOR dvd-biarch LABEL openSUSE 11.1 LINGUAS cs da de en en_GB en_US es fi fr hu it ja nb nl pl pt pt_BR ru sv zh zh_CN zh_TW NAME openSUSE REFERENCES openSUSE-release = 11.1 RELEASE 0 RELNOTESURL http://www.suse.com/relnotes/i386/openSUSE/11.1/release-notes- openSUSE.rpm SUMMARY openSUSE VENDOR openSUSE VERSION 11.1 -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug listening to: "Wahn!Sinn?" by Diary Of Dreams -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (3)
-
Rene Salmon -
Salmon, Rene
-
Uwe Gansert