When I installed 9.3 last week and ran online update, there were 5 packages that had signature errors. In the past, with 8.1, these errors eventually just cleared themselves up. I have run Online Update every day since then and those updates still won't come through. There have been a couple of new updates and the downloaded and installed fine. Will these others eventually clear up, or do you now have to take some sort of manual intervention step to fix them? The patches are for -- Samba Rpm Java_1_4_3_sum MozillFirefox Adobe Reader for PDF Files As always, any help greatly appreciated. Thanks, Greg Wallace
On Wednesday, September 07, 2005 @ 8:44 PM, I wrote:
When I installed 9.3 last week and ran online update, there were 5 packages that had signature errors. In the past, with 8.1, these errors eventually just cleared themselves up. I have run Online Update every day since then and those updates still won't come through. There have been a couple of new updates and the downloaded and installed fine. Will these others eventually clear up, or do you now have to take some sort of manual intervention step to fix them? The patches are for --
Samba Rpm Java_1_4_3_sum MozillFirefox Adobe Reader for PDF Files
As always, any help greatly appreciated.
Thanks, Greg Wallace
I went to the archives and found the following from last month (the previous entry in the thread describes the same problem I'm having) --
On Tuesday 23 August 2005 22:43, Carl Hartung wrote: On Tuesday 23 August 2005 16:16, steve wrote:
Hi and thanks for the ideas. I've tried three alternative YOU servers without success. Is there anything else I could try?
Hi Steve,
Two things you can try:
a) check the contents of YOU's local repository where it stores downloaded items (/var/lib/YaST2/you/mnt/i386/update/9.x...) and delete the errant/corrupted rpm and try running YOU again. Maybe it's not smart enough to download the file again even though it later finds the local copy is corrupted.
b) navigate via Konqueror browser to the mirror, through the update branch, locate the update rpm and click on it. You should then be able to click the "Install with YaST" button from within Konqueror.
regards,
- Carl
Thanks Carl.
Method (a) worked fine. Steve
I would like to try this approach myself. However, I need a little more detail (being pretty ignorant in this area). When I go to (/var/lib/YaST2/you/mnt/i386/update/9.3, I see three directories (deltas, patches, and rpm) with subdirectories in each. Do I go in and start deleting from all of these or is there a particular one I need to focus on. I don't want to cut any "lean" here, just fat. Greg Wallace
On Wednesday, September 07, 2005 @ 8:44 PM, I wrote:
When I installed 9.3 last week and ran online update, there were 5
On Wednesday, September 07, 2005 @ 11:28 PM, I wrote: packages
that had signature errors. In the past, with 8.1, these errors eventually just cleared themselves up. I have run Online Update every day since then and those updates still won't come through. There have been a couple of new updates and the downloaded and installed fine. Will these others eventually clear up, or do you now have to take some sort of manual intervention step to fix them? The patches are for --
Samba Rpm Java_1_4_3_sum MozillFirefox Adobe Reader for PDF Files
As always, any help greatly appreciated.
Thanks, Greg Wallace
<snip> I selected the YOU option "Reload All Patches From Server". YaST downloaded all of my patches again, found the 5 that hadn't been installed, and applied them. All available patches now installed! Greg Wallace
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2005-09-07 at 23:28 -0800, Greg Wallace wrote:
a) check the contents of YOU's local repository where it stores downloaded items (/var/lib/YaST2/you/mnt/i386/update/9.x...) and delete the errant/corrupted rpm and try running YOU again. Maybe it's not smart enough to download the file again even though it later finds the local copy is corrupted.
Method (a) worked fine. Steve
I would like to try this approach myself. However, I need a little more detail (being pretty ignorant in this area). When I go to (/var/lib/YaST2/you/mnt/i386/update/9.3, I see three directories (deltas, patches, and rpm) with subdirectories in each. Do I go in and start deleting from all of these or is there a particular one I need to focus on. I don't want to cut any "lean" here, just fat.
As a) above says, delete the rpm, ie, /var/lib/YaST2/you/mnt/i386/update/9.3/rpm/*/whatever.rpm - there will be only one copy of the offending rpm. However, as what was downloaded was probably a delta, you have to delete the delta file as well to force downloading it again. Or tell Yast to download everything... as you did. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDIExYtTMYHG2NR9URAu+yAJ9l8C7Rzy3YicDH26alSkZdE9eFMwCeJaPo MKIOo/KsmtnV5f4GwsGtmmY= =X6sW -----END PGP SIGNATURE-----
On Thursday, September 08, 2005 @ 6:36, Carlos Robinson wrote:
The Wednesday 2005-09-07 at 23:28 -0800, Greg Wallace wrote:
a) check the contents of YOU's local repository where it stores downloaded items (/var/lib/YaST2/you/mnt/i386/update/9.x...) and delete the errant/corrupted rpm and try running YOU again. Maybe it's not smart enough to download the file again even though it later finds the local copy is corrupted.
Method (a) worked fine. Steve
I would like to try this approach myself. However, I need a little more detail (being pretty ignorant in this area). When I go to (/var/lib/YaST2/you/mnt/i386/update/9.3, I see three directories (deltas, patches, and rpm) with subdirectories in each. Do I go in and start deleting from all of these or is there a particular one I need to focus on. I don't want to cut any "lean" here, just fat.
As a) above says, delete the rpm, ie, /var/lib/YaST2/you/mnt/i386/update/9.3/rpm/*/whatever.rpm - there will be only one copy of the offending rpm.
However, as what was downloaded was probably a delta, you have to delete the delta file as well to force downloading it again.
Or tell Yast to download everything... as you did.
Thanks for the info. Doing it the brute force way as I did is fine except it takes a while to reload all of those packages. As more patches come though, there will be more to download. I'll save off this not for future reference. So just to confirm, I would delete the offending packages from .../rpm and .../deltas but not .../patches, is that right? Thanks, Greg Wallace
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2005-09-08 at 13:15 -0800, Greg Wallace wrote:
Thanks for the info. Doing it the brute force way as I did is fine except it takes a while to reload all of those packages. As more patches come though, there will be more to download.
It will not download those already updated; only those needing update, but already downloaded.
I'll save off this not for future reference. So just to confirm, I would delete the offending packages from .../rpm and .../deltas but not .../patches, is that right?
It would not hurt to delete it as well. It a small text file, and YOU should download it fast. Only that it did not complain about that file, so, strictly speaking, no need to delete the .../patches/whatever file. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDIMV5tTMYHG2NR9URAmOyAJ4or+kD6DkI7j8jK+FE2RO3/tMkNQCffc8B VIsce9cauQ7V0AZPCQQTg0U= =J2uk -----END PGP SIGNATURE-----
On Thursday, September 08, 2005 @ 3:13 PM, Carlos Robinson wrote: -----Original Message-----
The Thursday 2005-09-08 at 13:15 -0800, Greg Wallace wrote:
Thanks for the info. Doing it the brute force way as I did is fine except it takes a while to reload all of those packages. As more patches come though, there will be more to download.
It will not download those already updated; only those needing update, but already downloaded.
I'll save off this not for future reference. So just to confirm, I would delete the offending packages from .../rpm and .../deltas but not .../patches, is that right?
It would not hurt to delete it as well. It a small text file, and YOU should download it fast. Only that it did not complain about that file, so, strictly speaking, no need to delete the .../patches/whatever file.
- -- Cheers, Carlos Robinson
Thanks for he info. I'll save this note off for future reference. Greg W
participants (2)
-
Carlos E. R. -
Greg Wallace