How do I force the package manager to re-install a package? Such as Development - > Development Tools -> G77 Or the entire Development tools package? The G77 Is missing - and when I ask it to install - it states that is already installed. Thanks Dan A. Dansereau -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20070909/a65c6df5/attachment.html>
On Sun, 2007-09-09 at 11:49 -0700, Dan Dansereau wrote:> The G77 Is missing ? and when I ask it to install ? it states that is > already installed.Why do you think it's missing? -- Ignacio Vazquez-Abrams <ivazqueznet at gmail.com> PLEASE don't CC me; I'm already subscribed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.centos.org/pipermail/centos/attachments/20070909/9a0384f2/attachment.sig>
On Sun, 2007-09-09 at 11:49 -0700, Dan Dansereau wrote:> How do I force the package manager to re-install a package? > > > > Such as Development - > Development Tools -> G77 > > > > Or the entire Development tools package? > > The G77 Is missing ? and when I ask it to install ? it states that is > already installed.Assuming you have satisfied the concerns Ignacio Vazquez-Abrams raised and still want to proceed... Change to the directory containing the package[s] and do: rpm -Uvh --force <package1> <package2> ... <packageN> Note that this is pretty ugly and should only be necessary if things are messed up badly, such as when files have been manually removed outside the package management system, or when failed updates leave the RPM database corrupted. Phil
Possibly Parallel Threads
- How to refer to my package from another package DESCRIPTION
- Problem understanding behaviour of versionCheck for loadNamespace (and when versions for Imports packages are checked)
- Problem understanding behaviour of versionCheck for loadNamespace (and when versions for Imports packages are checked)
- Problem understanding behaviour of versionCheck for loadNamespace (and when versions for Imports packages are checked)
- problem with a repo