This bug was fixed in the package libvirt - 1.3.1-1ubuntu10.13
---
libvirt (1.3.1-1ubuntu10.13) xenial; urgency=medium
* d/libvirt-bin.postinst: call apparmor_parser with options to
ignore the apparmor cache and rebuild it, otherwise old apparmor
rules are used and this
This bug was fixed in the package libvirt - 1.2.2-0ubuntu13.1.21
---
libvirt (1.2.2-0ubuntu13.1.21) trusty; urgency=medium
* d/libvirt-bin.postinst: call apparmor_parser with options to
ignore the apparmor cache and rebuild it, otherwise old apparmor
rules are used and this
Hi @bpick
the verification was done already, but if you want to continue (and you
are welcome to!), what you missed above is enabling the proposed
repository, as 1.3.1-1ubuntu10.12 is the version currently in xenial-
updates. Maybe you just missed an "sudo apt update" call?
Check what "apt-cache
Hi @bpick
the verification was done already, but if you want to continue (and you
are welcome to!), what you missed above is enabling the proposed
repository, as 1.3.1-1ubuntu10.12 is the version currently in xenial-
updates. Maybe you just missed an "sudo apt update" call?
Check what "apt-cache
I have followed what steps I can follow, and when I tried to install
libvert, it was already at current release:
user@user1:~/Desktop/libvirt-1.2.2$ sudo apt install libvirt-bin
Reading package lists... Done
Building dependency tree
Reading state information... Done
libvirt-bin is already
Tested xenial:
TL;DR working as it should now - properly regenerating "over" the cache and
thereby working correctly.
$ lxc launch ubuntu-daily:x xenial-bug-1707400 --profile default --profile kvm
Creating xenial-bug-1707400
Starting xenial-bug-1707400
[✓]─[paelzer@lap:~]──[60422]──[19:10 Mi Aug
I attached the full logs for further confidence.
Trusty as well as Xenial correctly exposed the bug with the testcase (to be
sure to actually verify the fix) and with the solution from -proposed the
reinstall worked correctly.
Setting verification tags accordingly.
Still any further testing is
Detailed instructions on how to use -proposed are here:
https://wiki.ubuntu.com/Testing/EnableProposed
To help testing, you could follow the [test case] from the bug in the first
comment, confirm the error, and then repeat it fresh but using the package from
proposed, and confirm it's fixed.
Detailed instructions on how to use -proposed are here:
https://wiki.ubuntu.com/Testing/EnableProposed
To help testing, you could follow the [test case] from the bug in the first
comment, confirm the error, and then repeat it fresh but using the package from
proposed, and confirm it's fixed.
Tested trusty:
TL;DR working as it should now - properly regenerating "over" the cache and
thereby working correctly.
$ lxc launch ubuntu-daily:t trusty-bug-1707400 --profile default --profile kvm
Creating trusty-bug-1707400
Starting
I followed the instructions in #22 above. I followed the INSTALL
directions from the package.
I am not a super Ubuntu user. I'm just following directions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@bpick, any particular reason you tried to build from source? You should
grab the binary package that's in the proposed repository. Or at least
the source package and build that: it would have told you which
dependencies are needed to perform a build.
--
You received this bug notification
@bpick, any particular reason you tried to build from source? You should
grab the binary package that's in the proposed repository. Or at least
the source package and build that: it would have told you which
dependencies are needed to perform a build.
--
You received this bug notification
During ./configure, this is how it ended:
checking for yajl_parse_complete in -lyajl... no
checking for yajl_tree_parse in -lyajl... no
configure: error: You must install the libyajl library & headers to compile
libvirt
user@user1:~/Desktop/libvirt-1.2.2$
If this helps.
--
You received this
Hello Bob, or anyone else affected,
Accepted libvirt into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libvirt/1.3.1-1ubuntu10.13 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Excellent work in tracking this down!
> Since the change is simple, I included it for Trusty as well and will
leave it up to the SRU team to decide if it's worth fixing there or not.
I would perfectly understand if it is deemed not worthy for Trusty at
this time.
Seems to me that if a security
Reviewed and Approved.
I sponsored the uploads into [TX]-unapproved.
You already had a sufficient SRU Template.
So now this is ready for the SRU Team to evaluate it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks Andreas for working on this while I was away.
I'm now reviewing the changes that you proposed and would move them to the
right repo (libvirt packaging is in a git repo of its own).
FWIW - not only did we start to use dh_apparmor in yakkety, in artful we
also dropped a lot more of the
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/libvirt/+git/libvirt/+merge/328425
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/libvirt/+git/libvirt/+merge/328426
--
You received this bug notification because you are a
** Description changed:
[Impact]
TL;DR
libvirt-bin stops working after a release upgrade from Trusty to Xenial.
Other scenarios possible.
Workaround after it breaks:
sudo touch /etc/apparmor.d/{usr.lib.libvirt.virt-aa-helper,usr.sbin.libvirtd}
sudo apt -f install
The
** Description changed:
[Impact]
TL;DR
libvirt-bin stops working after a release upgrade from Trusty to Xenial.
Other scenarios possible.
Workaround after it breaks:
sudo touch /etc/apparmor.d/{usr.lib.libvirt.virt-aa-helper,usr.sbin.libvirtd}
sudo apt -f install
The
** Description changed:
[Impact]
+ TL;DR
+ libvirt-bin stops working after a release upgrade from Trusty to Xenial.
Other scenarios possible.
- * An explanation of the effects of the bug on users and
+ Workaround after it breaks:
+ sudo touch
22 matches
Mail list logo
