-----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-----