Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#44018 - [libvirt] avoid re-enabling default network on upgrade

Attached to Project: Community Packages
Opened by Matthew Monaco (dgbaley27) - Monday, 02 March 2015, 16:17 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 03 March 2015, 10:06 GMT
Task Type General Gripe
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I don't feel too strongly about this, but it is annoying and contrary to how Arch handles config changes in general. I make a habit of removing the symlink /etc/libvirt/qemu/networks/autostart/default.xml. Can the maintainer please consider removing this symlink from the package and adding it via the install script, post_install, which already exists?
This task depends upon

Closed by  Sergej Pupykin (sergej)
Tuesday, 03 March 2015, 10:06 GMT
Reason for closing:  Not a bug
Comment by Sergej Pupykin (sergej) - Monday, 02 March 2015, 21:11 GMT
Will it work if you leave symlink but edit /etc/libvirt/qemu/networks/default.xml removing these settings?

default.xml is in backup array and should not be overwritten by upgrade.
Comment by Matthew Monaco (dgbaley27) - Tuesday, 03 March 2015, 08:26 GMT
I symlinked networks/default.xml to /dev/null. There are some complaints by libvirtd, but it moves on.
Comment by Sergej Pupykin (sergej) - Tuesday, 03 March 2015, 10:06 GMT
Ok, it should also work if you edit default.xml. Symlink created by upstream "make install", so I mark it as "not a bug".

Loading...