Since the issue is non-fatal and not a super-high-prio-feature to be needed I
refuse to do an SRU of this into Yakkety without anybody explicitly requesting
that.
Pre-Yakkety the issue was not existing (came in upstream in 2.x)
I add a task for Yakkety and flag it so that this state is clear.
This bug was fixed in the package libvirt - 2.1.0-1ubuntu13
---
libvirt (2.1.0-1ubuntu13) zesty; urgency=medium
* drop d/p/ubuntu/fix-ftbfs-for-gnutls-3-5-6.patch as the offending change
in gnutls has been reverted (LP: #1641615)
* Build depend on gnutls >= 3.5.6-4ubuntu2 to
FYI - this is still waiting to migrate, so while the fix is committed
you can not get it via an apt-get update, so it is expected to still
fail atm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
What worked last week doesn't have to this week - I ran into an FTBFS -
please wait a bit until resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615550
Title:
FYI - Fix pushed to Zesty
Since it is non fatal I did not consider an SRU so far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615550
Title:
STC860:Tuleta-L:KVM:iap01:Ubuntu 16.10 KVM logs
** Changed in: libvirt (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615550
Title:
STC860:Tuleta-L:KVM:iap01:Ubuntu 16.10 KVM logs apparmor="DENIED"
Hi Simon,
as stated in the other bug I can only agree!
Thanks - I made a new version ready to test for Yakkety available in the
ppa.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615550
Title:
The attachment "aa-libvirt-qemu.patch" seems to be a patch. If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
Hi Christian,
While looking at LP: #1546674 I ran into this bug as well. Your PPA
package patches the usr.sbin.libvirtd profile but I think the right
place to add the rule is in the abstraction/libvirt-qemu profile
extract.
I added a similar but slightly more restrictive rule in the attached
Hi,
sometimes the verification of this bug seems to elude me.
So I made a test build available for you to test if the package in
https://launchpad.net/~paelzer/+archive/ubuntu/libvirt-
bug-1546674-1615550/+packages would help you to get rid of the reported
issue.
--
You received this bug
** Changed in: libvirt (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => ChristianEhrhardt
(paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615550
Title:
Checking the code I'd expect that this kind of access is from:
static void qemu_thread_set_name(QemuThread *thread, const char *name)
{
#ifdef CONFIG_PTHREAD_SETNAME_NP
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libvirt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615550
Title:
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615550
Title:
STC860:Tuleta-L:KVM:iap01:Ubuntu 16.10 KVM logs apparmor="DENIED"
To
Confirmed by SMB
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615550
Title:
STC860:Tuleta-L:KVM:iap01:Ubuntu 16.10 KVM logs apparmor="DENIED"
To manage notifications about this bug go to:
15 matches
Mail list logo
