Automatically upgrade a package installed after the bundle is assigned

Question

Hi All,
I am trying out ZLM 7.3 and thanks also the helpful posts here I feel
quite confident with the tool.
Mirrored the channel, assigned the bundle and the catalog for the oss
packages and done, the installed package are upgraded with the patches
available with the bundle.
What I did not understand is the way to automatically upgrade a oss
package which is installed by YaST after the bundle is assigned. My
guess is, assign the catalog with patches to the device and whenever I
try to install a new package I automatically install the newest one. Is
this correct? Is there any other way to do this?
Thanks,
Jan

Answer 1

On 11/16/2009 09:36 PM, brunold wrote:
>
>> I see the new package installed and marked with status "v" which
>> according with the man pages means the bundle is installed but is of a
>> different version compared to the one displayed in the list. Now, I
>> would aspect it is automatically updated, instead it is not.
>
> I does not update the package installed by yast immediately after
> installing it. It should recognize that there is a updated version
> available the next time the zlm client refreshes.
>
You are right, after refreshing the client with rug the new package is
installed.
Thanks,
Jan
>> As said above, rug would solve the problem but I would like to use a
>> different approach if it is possible.
>
> Thinking about this situation might bring up a few other ideas but I
> have not checked if they work. When you mirror updates to your local zlm
> server, on the zlm server there is in the package repository a folder
> created for each bundle. If you mirror the updates for each different
> architecture into a different local bundle and therefor a different
> folder, you might be able to export that directory via nfs and mount it
> on the system and then add it as a local directory in the installation
> sources. The problem here is that yast might not be able to identify the
> packages in a local folder if they are for this architecture or not.
> Therefor you should create different bundles for different architectures
> and use them.
>
> Another option might be to copy the bundles from that zlm mirror to a
> different folder and create a installation source like the installation
> dvd is. We did that when we updated our remote oes 1 sp2 systems to oes
> 2 sp1 because we wanted to update them to a specific level we have a t
> the zlm server but we do not want to distribute it after the update
> accross the wire. We wanted to distribute it before we run the update
> and then run the update from a local source. That takes some time till
> you have the process to create such a installation source. therefor I
> don't know if that is of interest for you. You can script it of course
> ..
>
> Rainer
>
>