[Libvir] RPM upgrades interaction with default networking

Daniel P. Berrange berrange at redhat.com
Wed Mar 14 03:02:32 UTC 2007

On Tue, Mar 13, 2007 at 07:48:11PM -0700, David Lutterkort wrote:
> On Tue, 2007-03-13 at 23:22 +0000, Daniel P. Berrange wrote:
> > When we build an RPM we also include the default.xml file in the 
> > /etc/libvirt/qemu/networks directory, as well as the autostart symlink.
> > So anyone installing the libvirt RPM gets the default network, whether
> > they're doing an upgrade or fresh install.  This is reasonable for the
> > new install, or the first time you upgrade to a new neworking-enabled
> > libvirt. If you subsequently delete the default network, or turn off
> > autostarting, then along comes the next libvirt RPM update and autostart
> > gets turned back on, and/or the default network recreated.
> Have you tried how rpm reacts to a %config(noreplace) for those files ?
> I am not sure how it deals with file deletions, but for files changed by
> the user, it properly creates the new file as .rpmnew (and some people
> actually have scripts to help them reconcile the rpmnew files with their
> changes, interactively, of course)

The deletion of files is unfortunately the most important bit - and as
far as my testing has seen, no matter what you annotate with, if you 
delete a file it will always get re-created upon upgrade :-(

|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

More information about the libvir-list mailing list