Germán A. Racca, Em 16-12-2011 22:47, "Germán A. Racca" escreveu: > On 12/16/2011 09:34 PM, Reindl Harald wrote: >> >> >> Am 17.12.2011 00:17, schrieb Erik P. Olsen: >>> On 16/12/11 23:54, Reindl Harald wrote: >>>> >>>> >>>> Am 16.12.2011 23:50, schrieb Erik P. Olsen: >>>>> I have installed VirtualBox-4.0-4.0.14_74382_fedora14-1.x86_64 and >>>>> have been running it for quite some time. I have >>>>> now noticed that a new version >>>>> VirtualBox-4.1-4.1.6_74713_fedora14-1.x86_64 is available but not >>>>> as an update only >>>>> as a new install. Is it safe to remove the current package and >>>>> install the new one? Will my virtual machines be >>>>> automatically picked up by the installation process? >>>> >>>> this is linux not windows >>>> rpm -Uvh "package.rpm" or better "yum --nogpgcheck update package.rpm" >>>> to update downloaded packages >>> >>> My question had nothing to do with windows. I have never run windows >>> except as virtual machines. and "yum update >>> VirtualBox*" gets "No Packages marked for Update" so a clean install >>> is needed. >> >> * download the rpm >> * go in the folder with the rpm >> * type "yum --nogpgcheck update filename.rpm" >> >> yum is not limited to repos >> if something is installed as rpm a "clean install" is not needed >> why? because for a rpm a "clean install" does not exist >> a rpm-package knows which files are form the apckages, which are >> new and which are obsoleted to remove, that is why a package-manager >> exists >> >> your user-data has nothing to do with the rpm/software/package >> a virtual machine for vbox/vmware whatever is the same as a doc for >> openoffice >> it is yur data and has nothing to do with install/update/uninstall >> the software >> > > It has to be a "clean install" from my point of view, because he has > to remove one package and then install the other. Why? Because the > newer one has a different name. In the format of > name-version-release.arch, this is: > > Old package: VirtualBox-4.0-4.0.14_74382_fedora14-1.x86_64 > New package: VirtualBox-4.1-4.1.6_74713_fedora14-1.x86_64 I did exaclty this and "BOOTMGR is Compressed", Winvista64 doesn't boot anymore. Help? > > so the old one is called VirtualBox-4.0 and the newer is VirtualBox-4.1. > > (BTW, Erik, take into account that F14 is EOL. We are in F16, and the > same versio of VirtualBox is available). This was the reason of the update. > > HTH, > Germán. > -- Lucélio Gomes de Freitas ETFCSF-> U.G.F.-> P.U.C.(RJ) Engº, Analista Suporte(Free Mind). Email: aa.lucelio@xxxxxxxxx Tel: 55 0XX 21 85964911 -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
