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 <ug@suse.de> To 11/16/06 01:53 PM suse-autoinstall@suse.com cc Subject Re: [suse-autoinstall] several sources 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) -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com