Re: [SLE] SuSE Online Update not looking at RPM database
I have a work around to this problem: If you update your system with a patch using RPM -U ..., you need to fool YaST2 into thinking it was installed. Problem: Performing YaST2 Online Update, Internet connection times out before all patches downloaded. You want to install the the rpms that you got before you lost the internet connection but YaST2 Online Update thinks it needs to re-download all those patches again. example: if you had gone ahead and performed an upgrade by hand of Sax2: cd /var/lib/YaST/patches/i386/update/7.2/x1 rpm -U sax2.rpm you need to fool YaST2 Online Update into thinking it has installed the patch as it is not smart enough to look at the RPM database. cd /var/lib/YaST/patches/i386/update/7.2/patches mv sax2-1.20010901.new sax2-1.20010901.installed the next time your run YaST2 Online Update it will think that it has already installed the patch for Sax2, even though you did it yourself. Sean
From: Ben Rosenberg
To: SLE Subject: Re: [SLE] SuSE Online Update not looking at RPM database Date: Mon, 3 Sep 2001 01:15:50 -0700 Well, since this has been a big topic as of late. I remind people that YOU's 1st version is in 7.2..so don't expect it to be perfect. If you want a bug fixed like this submit the bug.
Hey LenZ..anyone. Is there a fix coming down the pipe for this. I've counted at least 15 people who have mentioned this.
* Seán Ó Ceallaigh (sean0cea11aigh_@hotmail.com) [010903 01:08]: ->I have a problem with SuSE Online Update using Yast2 and ->SuSE version 7.2. I have installed by hand ( RPM -U ... ) several patches ->from the SuSE ftp site. However, when I run Yast2's online ->update from the Yast2 control center, it tells me that I need to ->download and install those very same patches!? It even says ->that the version on disk is the same as the version on the ftp ->site and it still says I need to update with that patch? What gives? ->Shouldn't Yast2 be comparing the patches in the SuSE ftp site ->with the current RPM database? -> ->Thanks, -> ->Sean -> ->_________________________________________________________________ ->Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp -> -> ->-- ->To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com ->For additional commands send e-mail to suse-linux-e-help@suse.com -> ->Also check the FAQ at http://www.suse.com/support/faq and the ->archives at http://lists.suse.com ->
-- Ben Rosenberg mailto:ben@whack.org cat CE|ME|NT|XP > /dev/null
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
_________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
* Seán Ó Ceallaigh (sean0cea11aigh_@hotmail.com) [010903 09:34]: -> ->I have a work around to this problem: -> -> If you update your system with a patch using RPM -U ..., -> you need to fool YaST2 into thinking it was installed. -> -> Problem: -> -> Performing YaST2 Online Update, Internet connection times -> out before all patches downloaded. You want to install the -> the rpms that you got before you lost the internet connection -> but YaST2 Online Update thinks it needs to re-download all those -> patches again. -> If you are using ftp.suse.com I think this is also a problem with the amount of time that's set before the connection times out and your disconnected. When I use gFTP and I am tagging the files for downloaded it make take a few minutes to go through what I want and what I don't want (ie..KDE2's apps directory) and the connection can time out before I'm 1/2 way through deciding what I need and don't. This is a problem. My solution..although a stupid solution is to just use ncftp in 3 xterms connected at the same time and instead of going through the directories for just what I want. I download all the RPM's .. I just set and forget. That way I don't have to keep reconnecting. I know SuSE doesn't want people hanging out on the ftp site and taking up one of the max connections..but the short timeout on the ftp server is just wrong and a pain in the ass. If your on a modem I bet this is why it dies before you get the whole list. Regards, -- Ben Rosenberg mailto:ben@whack.org cat CE|ME|NT|XP > /dev/null
On Monday 03 September 2001 19.40, Ben Rosenberg wrote:
* Seán Ó Ceallaigh (sean0cea11aigh_@hotmail.com) [010903 09:34]: -> ->I have a work around to this problem: -> -> If you update your system with a patch using RPM -U ..., -> you need to fool YaST2 into thinking it was installed. -> -> Problem: -> -> Performing YaST2 Online Update, Internet connection times -> out before all patches downloaded. You want to install the -> the rpms that you got before you lost the internet connection -> but YaST2 Online Update thinks it needs to re-download all those -> patches again. ->
If you are using ftp.suse.com I think this is also a problem with the amount of time that's set before the connection times out and your disconnected. When I use gFTP and I am tagging the files for downloaded it make take a few minutes to go through what I want and what I don't want (ie..KDE2's apps directory) and the connection can time out before I'm 1/2 way through deciding what I need and don't. This is a problem. My solution..although a stupid solution is to just use ncftp in 3 xterms connected at the same time and instead of going through the directories for just what I want. I download all the RPM's .. I just set and forget. That way I don't have to keep reconnecting. I know SuSE doesn't want people hanging out on the ftp site and taking up one of the max connections..but the short timeout on the ftp server is just wrong and a pain in the ass.
If your on a modem I bet this is why it dies before you get the whole list.
Regards,
There is another problem with downloading large files. The control connection times out while a large file downloads. Apparently, the ftp implementations don't send keep_alive:s or ping:s or whatever ftp uses to tell the server that the client is still there. I've had this happen with Yast, but also with command line ftp. So when then file is done, there is no control connection to send back a new request for the next file. mget fails almost always with this. The only 'solution' I've found is to use wget, which is smart enough to open a new control connection if the first one dies. Anders
participants (3)
-
Anders Johansson
-
Ben Rosenberg
-
Se�n � Ceallaigh