Hi all: It's posible to specify several sources to autoinstall a machine? I've two repositories, the first with stock suse 10.1 and the second with my own repository and I want to install machines using pacakges from both repositories... It's posible? Greetings.
On Tuesday 14 November 2006 12:19, Antonio Beamud Montero wrote:
I've two repositories, the first with stock suse 10.1 and the second with my own repository and I want to install machines using pacakges from both repositories...
http://www.suse.de/~ug/AutoYaST_FAQ.html#b9 -- 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 Diorama - Light
El mar, 14-11-2006 a las 12:21 +0100, Uwe Gansert escribió:
On Tuesday 14 November 2006 12:19, Antonio Beamud Montero wrote:
I've two repositories, the first with stock suse 10.1 and the second with my own repository and I want to install machines using pacakges from both repositories...
Hi Uwe: I've follow all the steps to create a repository with my own packets. The problem is when from a machine a configure a source via http with: http yastserver.linkend.net /packages/repo2/updates/ When try to install a package a message like this appears: http://yastserver/packages/repo2/updates/: Can't open /var/lib/zypp/cache/Source.08MaOg/DATA/descr/packages And this is the repo2 tree: -------------------------------------------- . ./yast ./yast/order ./yast/instorder ./setup ./setup/descr ./setup/descr/packages ./setup/descr/packages.DU ./setup/descr/packages.en ./setup/descr/packages.es ./updates ./updates/suse ./updates/suse/i386 ./updates/suse/i386/divx4linux-20020418.i386.rpm ./updates/suse/i386/cx_Oracle-4.2-9i-py24-1.i386.rpm ./updates/suse/i586 ./updates/suse/i586/mad_0.15.1b-1.pm.3_i586.rpm ./updates/suse/i586/gdmodule-0.56-1.i586.rpm ./updates/suse/i586/ZODB3-3.2-1.i586.rpm ./updates/suse/setup ./updates/suse/setup/descr ./updates/suse/setup/descr/directory.yast ./updates/suse/setup/descr/packages ./updates/suse/setup/descr/packages.DU ./updates/suse/setup/descr/packages.en ./updates/suse/setup/descr/packages.es ./updates/suse/setup/descr/EXTRA_PROV ./updates/suse/noarch ./updates/suse/noarch/SOAPpy-0.11.6-1.noarch.rpm ./updates/directory.yast ./updates/content ./updates/media.1 ./updates/media.1/directory.yast ./updates/media.1/media ./updates/media.1/products I have created manually the updates/suse/setup/descr/EXTRA_PROV file to avoid the warning: ------------------------------ extra_provides: file /usr/share/repo2/updates/suse/setup/descr/EXTRA_PROV not found! What I'm doing wrong? Greetings.
On Wednesday 15 November 2006 19:58, Antonio Beamud Montero wrote:
When try to install a package a message like this appears: http://yastserver/packages/repo2/updates/: Can't open /var/lib/zypp/cache/Source.08MaOg/DATA/descr/packages
I have never seen that message
And this is the repo2 tree:
if repo1 is your original SUSE installation source, then your "updates" addon directory must be in the repo1 directory. Not in a self created parallel repo2 directory. Does your installation source look like the tree in the FAQ? -- 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 Faderhead - Vanish (Extended Version)
What should I do, if I do not want to have a "update "directory, but a XYZ
installation source, which is NOT connect/related to the original SLED10
installation source. I tried this manually, but at the end it's all messing
up. I found that the "installation source system" is one of the worst
repository systems, I've ever seen. It's completely unlogic and
everchanging between the SLES releases.
Please can you give me a hint, how to create external installation sources
for SLED/SLES10 without the need of having it related to the SLES/SLED10
installation source.
And how can I avoid to put 10 media.x directories if we're running more
than one architecture (i385/i586/noarch/x86_64/ppc64/ppc).
I have the impression that this is a bug in Code10.
Do you have some "magic script" that builds a default installation source,
where I just have to put my RPM's in the architecture directory and rerun
make_package_descr to reindex the repository.
Kind Regards
marco
Uwe Gansert
When try to install a package a message like this appears: http://yastserver/packages/repo2/updates/: Can't open /var/lib/zypp/cache/Source.08MaOg/DATA/descr/packages
I have never seen that message
And this is the repo2 tree:
if repo1 is your original SUSE installation source, then your "updates" addon directory must be in the repo1 directory. Not in a self created parallel repo2 directory. Does your installation source look like the tree in the FAQ? -- 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 Faderhead - Vanish (Extended Version) -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
Try custom post install scripts using wget etc.
-----Original Message-----
From: Marco Hoehle [mailto:MHO@zurich.ibm.com]
Sent: Thursday, November 16, 2006 6:18 AM
To: Uwe Gansert
Cc: suse-autoinstall@suse.com
Subject: Re: [suse-autoinstall] several sources
What should I do, if I do not want to have a "update "directory, but a
XYZ
installation source, which is NOT connect/related to the original SLED10
installation source. I tried this manually, but at the end it's all
messing
up. I found that the "installation source system" is one of the worst
repository systems, I've ever seen. It's completely unlogic and
everchanging between the SLES releases.
Please can you give me a hint, how to create external installation
sources
for SLED/SLES10 without the need of having it related to the SLES/SLED10
installation source.
And how can I avoid to put 10 media.x directories if we're running more
than one architecture (i385/i586/noarch/x86_64/ppc64/ppc).
I have the impression that this is a bug in Code10.
Do you have some "magic script" that builds a default installation
source,
where I just have to put my RPM's in the architecture directory and
rerun
make_package_descr to reindex the repository.
Kind Regards
marco
Uwe Gansert
When try to install a package a message like this appears: http://yastserver/packages/repo2/updates/: Can't open /var/lib/zypp/cache/Source.08MaOg/DATA/descr/packages
I have never seen that message
And this is the repo2 tree:
if repo1 is your original SUSE installation source, then your "updates" addon directory must be in the repo1 directory. Not in a self created parallel repo2 directory. Does your installation source look like the tree in the FAQ? -- 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 Faderhead - Vanish (Extended Version) -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
Todd,
we do this - I have yum based repository backends to manage our add-on
software, but I wanted to give the installation sources yet another try
after the disasters with SLES8 and SLES9 but it looks like @ novell nobody
learned something and they're still using the same ugly mechanisms....
(sometimes I have the impression that this system is maybe a legacy from
pre-novell times and the people that worked on it are no more in the
company)
In my opinion it's not the intention of the installation system to build a
second repository infrastructure (beside the yast / installation source
system) for additional packages. This makes no sense and does not reduce
administrative work.
At the moment we're starting the installation with the yast2 installation
sources and we're finishing the package installation with yum repositories
which costs a lot of disk space (ok symlinks can help there) and is really
bad to administrate.
Sometimes I got the impression, that maybe I missed something in the
documentation - but no ... there must be magic in building a installation
source like they're on the CD ...
Also I wanted to avoid a lot of my postinstall scripts (which in the latest
SLES9 were about 14 scripts) and try using that what Novell provides to us.
I think Novell / SuSE should have a look at this issue and maybe in code 11
bring out something better and more consistent than the installation source
system. With the ZEN framework, they're now supporting a lot of other
repository types - so please get rid of the installation source system, or
do something that makes it better to handle, more easy to understand, more
easy to administrate and more easy to customize. (maybe have a deeper look
at yum or apt-get to adopt their repository techniques).
Regards
marco
P.S.: Still, I am really interested in a script which builds a plain
installation source structure that I can just put in my RPM's and point to
it during installation.
"Ness, Todd"
When try to install a package a message like this appears: http://yastserver/packages/repo2/updates/: Can't open /var/lib/zypp/cache/Source.08MaOg/DATA/descr/packages
I have never seen that message
And this is the repo2 tree:
if repo1 is your original SUSE installation source, then your "updates" addon directory must be in the repo1 directory. Not in a self created parallel repo2 directory. Does your installation source look like the tree in the FAQ? -- 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 Faderhead - Vanish (Extended Version) -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
participants (4)
-
Antonio Beamud Montero -
Marco Hoehle -
Ness, Todd -
Uwe Gansert