This bug was fixed in the package qemu - 1:2.8+dfsg-3ubuntu2.3
---
qemu (1:2.8+dfsg-3ubuntu2.3) zesty; urgency=medium
* debian/rules: fix installation of /etc/default/qemu-kvm (LP: #1692530)
This was inadvertently dropped on 2.8 merge.
-- Christian Ehrhardt Mon, 22 May
2017
As I expected all but one test were transient and fixed on retry.
The remaining issue seems to be perma-fails in systemd dep8 tests on zesty.
Armhf [1] seems to never work. And s390x [2] doesn't seem to be much better.
I tried to get s390x good by re-triggering, but it becomes a waste of test
ress
Found that there are test issues - should not be releated, retriggered
them now and will look deeper if they are not transient.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692530
Title:
/etc/defa
** Tags removed: verification-done
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692530
Title:
/etc/default/qemu-kvm inadvertently dropped from packaging in q
Verified in zesty-proposed - working fine now on upgrades and on new installs.
Saw now related conffile conflict, package ownership and all that is fine.
Setting v-d
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a mem
Hello ChristianEhrhardt, or anyone else affected,
Accepted qemu into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:2.8+dfsg-
3ubuntu2.3 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. S
Ah this was a week were I was stupid, I had another case like this -
grml my fault :-/.
I set to Fix committed as it was ready for review but according to the
SRU Process [1] it should have been "In Progress" - maybe that made it
being skipped - fixed the status and looking forward to a SRU check
Hmm, no update why it might be blocked on SRU in unapproved for so long ...
Asking in #ubuntu-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692530
Title:
/etc/default/qemu-kvm inadvertently
Artful is released and working, pushed the matching fix for Zesty into
the SRU unapproved queue and waiting for review now.
** Changed in: qemu (Ubuntu Zesty)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
This bug was fixed in the package qemu - 1:2.8+dfsg-3ubuntu4
---
qemu (1:2.8+dfsg-3ubuntu4) artful; urgency=medium
* debian/rules: fix installation of /etc/default/qemu-kvm (LP: #1692530)
This was inadvertently dropped on 2.8 merge.
-- Christian Ehrhardt Mon, 22 May
2017 15:
** Description changed:
+ [Impact]
+
+ * Users installing fresh on Zesty or later will lack the
+/etc/default/qemu-kvm file to control the convenience features of the
+qemu-kvm init script. They have to "guess" what to set in there if they
+want to use it.
+
+ [Test Case]
+
+ *
Given the change that was to be assumed, but all tests look good so far.
Pushing to Artful now and prepping for Zesty then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692530
Title:
/etc/default/
** Description changed:
- While clearing out the sysv and upstart bits this got inadvertently as
- well.
+ While clearing out the sysv and upstart bits this got inadvertently
+ dropped as well.
The reason it wasn't realized for so long is that:
a) it is a conffile which was not autoremoved
13 matches
Mail list logo
