On Thu, 14 Mar 2013 14:44:48 +0002 Alex Lourie <[email protected]> wrote:
> Hi Jiri > > On Thu, Mar 14, 2013 at 4:30 PM, Jiri Belka <[email protected]> wrote: > > I'll talk about RHEVM but it's probably related to oVirt too. > > > > As rhevm installs all deps, I'm curious why versionlock.list is > > populated after rhevm-setup and _not_dirrectly during installation > > (maybe because you would need to hardcode versions into rhevm > > package?). It took me tens of minutes to figure out why is upgrade > > working differently now, just because I did _NOT_ do rhevm-setup after > > clean install because I was thinking I know what files are important > > and was restoring them from a tarball. > > > > I think running rhevm-setup if you just want to restore is stupid. If > > we would know 100% which files are involved, just install, restore > > from > > backup, restore DB should be sufficient, without loosing time with > > rhevm-setup which just writes there and here... :) > > > > I don't really follow you here. What are you restoring with rhevm-setup? My previous (wrong) procedure to restore old version was: rhevm-cleanup, yum remove rhevm\*, rm -rf $dirs, yum install rhevm\*, tar xvzpf /backup.tgz, ./restore.sh for DB... which was not fully correct as I haven't known /etc/yum/plugin.d/versionlock.list is touched by rhevm-setup as well and thus yum was working very strange during next normal upgrade. _______________________________________________ Engine-devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/engine-devel
