What I do is copy all of the folders except the patches in the patches/8.0/ onto the other machine. Then I use YOU to do the update. It goes and checks the patches when you install, if it is already on the disk it will skip the download and install the packages. Art -----Original Message----- From: Basil Chupin [mailto:blchupin@tpg.com.au] Sent: Tuesday, August 06, 2002 4:00 AM To: suse-linux-e@suse.com Subject: [SLE] "Reusing" RPM patches I update my system almost on a daily basis with YOU on-line feature. The RPM patches end up in the /var/lib/....../8.0/<various> sub-directories (I think :-)). I want to apply these patches to another copy of the SuSE V8.0 system (my testbed) and not have to go thru the whole on-line update process again. Could someone please point me to the place where I can find information on how I can achieve this or give me an outline of how to do this. I've looked in the SDB but can't even find what the command line to apply one of these patches looks like (eg, is it rpm -Uvh --nodeps <name>.rpm or is it without the --nodeps?). I can see in the sub-directories that the patches are dated (according to the date they were downloaded and applied) so I guess that one condition for applying the patches would be in date order otherwise an earlier patch may overwrite a later patch which corrected the first one - or am I misunderstanding things? Or can i put all the patches into the one directory and then apply (say) RPM -Uvh *.rpm to the lot? Any help gratefully appreciated (as I would like to re-install v8.0, recompile the kernel and then apply the patches). Cheers. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
Art Fore wrote:
hat I do is copy all of the folders except the patches in the patches/8.0/ onto the other machine. Then I use YOU to do the update. It goes and checks the patches when you install, if it is already on the disk it will skip the download and install the packages.
Art
-----Original Message----- From: Basil Chupin [mailto:blchupin@tpg.com.au] Sent: Tuesday, August 06, 2002 4:00 AM To: suse-linux-e@suse.com Subject: [SLE] "Reusing" RPM patches
I update my system almost on a daily basis with YOU on-line feature. The RPM patches end up in the /var/lib/....../8.0/<various> sub-directories (I think :-)). I want to apply these patches to another copy of the SuSE V8.0 system (my testbed) and not have to go thru the whole on-line update process again.
Could someone please point me to the place where I can find information on how I can achieve this or give me an outline of how to do this. I've looked in the SDB but can't even find what the command line to apply one of these patches looks like (eg, is it rpm -Uvh --nodeps <name>.rpm or is it without the --nodeps?).
I can see in the sub-directories that the patches are dated (according to the date they were downloaded and applied) so I guess that one condition for applying the patches would be in date order otherwise an earlier patch may overwrite a later patch which corrected the first one - or am I misunderstanding things? Or can i put all the patches into the one directory and then apply (say) RPM -Uvh *.rpm to the lot?
Any help gratefully appreciated (as I would like to re-install v8.0, recompile the kernel and then apply the patches).
Cheers.
Thank you for this information. I'll try it ASAP. Cheers.
Art Fore wrote:
hat I do is copy all of the folders except the patches in the patches/8.0/ onto the other machine. Then I use YOU to do the update. It goes and checks the patches when you install, if it is already on the disk it will skip the download and install the packages.
Art
-----Original Message----- From: Basil Chupin [mailto:blchupin@tpg.com.au] Sent: Tuesday, August 06, 2002 4:00 AM To: suse-linux-e@suse.com Subject: [SLE] "Reusing" RPM patches
I update my system almost on a daily basis with YOU on-line feature. The RPM patches end up in the /var/lib/....../8.0/<various> sub-directories (I think :-)). I want to apply these patches to another copy of the SuSE V8.0 system (my testbed) and not have to go thru the whole on-line update process again.
Could someone please point me to the place where I can find information on how I can achieve this or give me an outline of how to do this. I've looked in the SDB but can't even find what the command line to apply one of these patches looks like (eg, is it rpm -Uvh --nodeps <name>.rpm or is it without the --nodeps?).
I can see in the sub-directories that the patches are dated (according to the date they were downloaded and applied) so I guess that one condition for applying the patches would be in date order otherwise an earlier patch may overwrite a later patch which corrected the first one - or am I misunderstanding things? Or can i put all the patches into the one directory and then apply (say) RPM -Uvh *.rpm to the lot?
Any help gratefully appreciated (as I would like to re-install v8.0, recompile the kernel and then apply the patches).
Cheers.
Further to my earlier reply, and the following is also addressed to Jon
whose response was along the same lines as yours.
I admit I am no rocket scientist but following these instructions seems
to be beyond my limited capabilities because I cannot get the updates to
work! :-) I tried running them 'everyway but loose' but all I get is an
error message, "No SuSE=-patch-CD or SuSE path found".
I copy all the files/folders for
/var/lib/YaST/patches/i386/update/8.0/<various> [without and without
/patches] then run YOU as either auto or manual with the HD path set to
the /var/lib/YaST/patches/i386/update/8.0/
* Basil Chupin;
Art Fore wrote:
to be beyond my limited capabilities because I cannot get the updates to work! :-) I tried running them 'everyway but loose' but all I get is an error message, "No SuSE=-patch-CD or SuSE path found".
I copy all the files/folders for /var/lib/YaST/patches/i386/update/8.0/<various> [without and without /patches] then run YOU as either auto or manual with the HD path set to the /var/lib/YaST/patches/i386/update/8.0/
First use a different directory as /var/lib/Yast will be used by YaST2 ie the eay I do it is via rsync every night I am updating /usr/local/update/i386/update/8.0 directory. When using YaST2 online Update module select expert and then choose harddisk and enter the path as follows /usr/local/update ( YaST2 will find the remaining parts depending on your SuSE version) and then you will be able to apply the pathces via harddisk. If you want to make a Patch CD the important point is use of "graft-points" option of mkisofs for example -graft-points i386/update/8.0=/usr/local/update/i386/update/8.0 This way you can use the CD as a patch CD and YaST2 will happly accept it. HTH -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx
Togan Muftuoglu wrote:
* Basil Chupin;
on 08 Aug, 2002 wrote: Art Fore wrote:
to be beyond my limited capabilities because I cannot get the updates to work! :-) I tried running them 'everyway but loose' but all I get is an error message, "No SuSE=-patch-CD or SuSE path found".
I copy all the files/folders for /var/lib/YaST/patches/i386/update/8.0/<various> [without and without /patches] then run YOU as either auto or manual with the HD path set to the /var/lib/YaST/patches/i386/update/8.0/
First use a different directory as /var/lib/Yast will be used by YaST2 ie the eay I do it is via rsync every night I am updating /usr/local/update/i386/update/8.0 directory.
When using YaST2 online Update module select expert and then choose harddisk and enter the path as follows
/usr/local/update ( YaST2 will find the remaining parts depending on your SuSE version) and then you will be able to apply the pathces via harddisk. If you want to make a Patch CD the important point is use of "graft-points" option of mkisofs for example -graft-points i386/update/8.0=/usr/local/update/i386/update/8.0
This way you can use the CD as a patch CD and YaST2 will happly accept it.
HTH
Thank you for this information. I shall try it out later on today after I have re-installed SuSE on the testbed (after my earlier attempts to install the patches YOU suddenly won't even boot-up so I guess the executable got corrupted in the process. Life wan't meant to be easy. Cheers.
Togan Muftuoglu wrote:
* Basil Chupin;
on 08 Aug, 2002 wrote: Art Fore wrote:
to be beyond my limited capabilities because I cannot get the updates to work! :-) I tried running them 'everyway but loose' but all I get is an error message, "No SuSE=-patch-CD or SuSE path found".
I copy all the files/folders for /var/lib/YaST/patches/i386/update/8.0/<various> [without and without /patches] then run YOU as either auto or manual with the HD path set to the /var/lib/YaST/patches/i386/update/8.0/
First use a different directory as /var/lib/Yast will be used by YaST2 ie the eay I do it is via rsync every night I am updating /usr/local/update/i386/update/8.0 directory.
When using YaST2 online Update module select expert and then choose harddisk and enter the path as follows
/usr/local/update ( YaST2 will find the remaining parts depending on your SuSE version) and then you will be able to apply the pathces via harddisk. If you want to make a Patch CD the important point is use of "graft-points" option of mkisofs for example -graft-points i386/update/8.0=/usr/local/update/i386/update/8.0
This way you can use the CD as a patch CD and YaST2 will happly accept it.
HTH
Oh dear, but I am definitely doing something wrong because I have tried all the suggestions made so far by all - except for the option of creating a mirror of the ftp source - and am getting nowhere very fast :-(. When I try what you suggest above I end up with an error message of "No SuSE=pathc-CD or SuSE path found" and then, when I actually gave the fulll path to the patches, I got Cannot download patch descriptons (or words to this effect). This led me to thinking that on the patched system there is a folder called "patches" which contains the name of available patches and at the end of each name thre is a description which states "new" or "installed" and that if I removed the "installed" at the end of the name then the YOU would work correctly. So I renamed all the files (patches). I then ran YOU and what I now got was the error messages (for each patch), "Could not copy patch-information". After trying a number of variations around this scenario, and having got nowhere, I was forced to give up because - once again! - the YOU application disappeared from the system. After some 6 unsuccessful attempts at running YOU in AUTOMATIC/HD/path-to-patches, YOU disappears off the screen and one cannot re-activate it again :-(. YOU is gone :-(. The only way I know of bringing it back is to re-install SuSE. The other suggestin I tried was the one about placing all the patches into the one directory and running rpm -Fvh *.rpm in the directory. Well, all I got was screens and screens of error messages. I then decided to see what would happen of I applied this in each of sub-directories holding the patches- this worked for all but the patches in sub-directories kde7, kde8, xwm1, and yast1. So, this approach doesn't work for me :-(. At this point in time my mind is boggling. I'll take a 10-minute break - and see if someone can come up with that small detail that I am missing in order for this to work for me. To be honest, I am surprised that SuSE haven't written into the SDB the method(s) of updating a system using existing patches rathen than having people download them again (and tying up their server). Cheers.
Hi Basil and all! It was me suggesting to mirror a FTP-site. The reasons is that I had (like you are having now) a lot of trouble to get YOU to understand where te update files are. It seems that YOU is coded to have a certain path to the update files. I found that copying that path from a FTP-site would be the easiest thing to do. Wget with the mirror option does this automaticly. One more reason is that even if you copy all already downloaded files from an other machine you still have You to connect to a FTP-site to read the patch file information in order to decide which files to download. This will also take time and create a lot of traffic. My method do create a big download the first time you run wget but if you riun it twice a week it's not that much the following times. I also need to host a lot of files (for the moment 1GB). But downloading is fully automatic and updating each computer on the network dont need many clicks with the mouse. Regards /Nils-Olov
On Thursday 08 August 2002 14:52, Basil Chupin wrote:
I admit I am no rocket scientist but following these instructions seems to be beyond my limited capabilities because I cannot get the updates to work! :-) I tried running them 'everyway but loose' but all I get is an error message, "No SuSE=-patch-CD or SuSE path found".
I copy all the files/folders for /var/lib/YaST/patches/i386/update/8.0/<various> [without and without /patches] then run YOU as either auto or manual with the HD path set to the /var/lib/YaST/patches/i386/update/8.0/
Where am I going wrong?
Don't change your source of installation. Keep it pointed at ftp.gwdg.de or wherever is good for you. Go for automatic or manual as you prefer. All that copying the files over does is to save you from having to download them all over again. Yast2 will see that you already have the files that match the versions on the servers, so will only download newer files. Jon
Jon Lim wrote:
On Thursday 08 August 2002 14:52, Basil Chupin wrote:
I admit I am no rocket scientist but following these instructions seems to be beyond my limited capabilities because I cannot get the updates to work! :-) I tried running them 'everyway but loose' but all I get is an error message, "No SuSE=-patch-CD or SuSE path found".
I copy all the files/folders for /var/lib/YaST/patches/i386/update/8.0/<various> [without and without /patches] then run YOU as either auto or manual with the HD path set to the /var/lib/YaST/patches/i386/update/8.0/
Where am I going wrong?
Don't change your source of installation.
Keep it pointed at ftp.gwdg.de or wherever is good for you. Go for automatic or manual as you prefer.
All that copying the files over does is to save you from having to download them all over again. Yast2 will see that you already have the files that match the versions on the servers, so will only download newer files.
Jon
Aaah, that's the secret! Many thanks for this. Cheers.
participants (5)
-
Art Fore
-
Basil Chupin
-
Jon Lim
-
Nils-Olov Fransson
-
Togan Muftuoglu