This bug was fixed in the package qemu - 1.5.0+dfsg-3ubuntu5.1
---
qemu (1.5.0+dfsg-3ubuntu5.1) saucy-proposed; urgency=low
* debian/control: qemu-utils must Replace: qemu-kvm as it did in raring,
to prevent lts-to-lts updates from breaking. (LP: #1243403)
-- Serge HallynW
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1243403
Title:
Upgrade from qemu 1.0+noroms-0ubuntu14.11 fails
To
Hello!
Unfortunately, I destroyed the vm I was testing on, but there was
definitely an issue with my sources or the mirror (kernel.org) I was
using, as I was able to successfully upgrade from precise's qemu to
saucy's qemu with no issues. I do see ipxe-qemu in the saucy main repo
now.
The qemu u
> root@wilk-aio3:~# apt-cache policy ipxe-qemu
> ipxe-qemu:
> Installed: (none)
> Candidate: (none)
> Version table:
Can you please show your /etc/apt/sources.list and any files
under /etc/apt/sources.list.d? My saucy box says:
$ apt-cache policy ipxe-qemu
ipxe-qemu:
Installed: 1.0.0+git
Hello Serge,
I am sorry for the slow response on this. I had a chance to test the
packages, and it appears that they have been broken by a change to
another package: qemu-system-x86 deps on ipxe-qemu, which appears to
have been superceded by ipxe.
The packages are uninstallable in proposed.
roo
@Jacob,
once someone verifies the fix in saucy, and the fix is promoted to
saucy-updates, then it will show up in the cloud archive.
(To put it another way - the bug is not in precise; it is in the
version in cloud archive, which will be pulled into the cloud archive
from saucy when that is upda
This bug is also present in Precise when using the Cloud Archive. To
workaround, qemu-kvm and qemu-common must be removed via dpkg.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1243403
** Branch linked: lp:ubuntu/saucy-proposed/qemu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1243403
Title:
Upgrade from qemu 1.0+noroms-0ubuntu14.11 fails
To manage notifications
Hello William, or anyone else affected,
Accepted qemu into saucy-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/qemu/1.5.0+dfsg-
3ubuntu5.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
** Changed in: qemu (Ubuntu Saucy)
Status: New => Triaged
** Changed in: qemu (Ubuntu Saucy)
Importance: Undecided => High
** Description changed:
+ =
+ SRU Justification
+ 1. Impact: cloud archive users cannot upgrade cleanly
+ 2. Development fix: properly mark qem
** Branch linked: lp:ubuntu/qemu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1243403
Title:
Upgrade from qemu 1.0+noroms-0ubuntu14.11 fails
To manage notifications about this bug
This bug was fixed in the package qemu - 1.6.0+dfsg-2ubuntu2
---
qemu (1.6.0+dfsg-2ubuntu2) trusty; urgency=low
* debian/control: qemu-utils must Replace: qemu-kvm as it did in raring,
to prevent lts-to-lts updates from breaking. (LP: #1243403)
-- Serge HallynWed, 23 Oct 2
Thanks, Serge!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1243403
Title:
Upgrade from qemu 1.0+noroms-0ubuntu14.11 fails
To manage notifications about this bug go to:
https://bug
Hi,
If this only affected the cloud archive updates then the bug would
probably belong against the cloud archive itself (if that exists
as a project), since normally you must update from p to q to r to
s, which works fine. However it IS valid against the ubuntu qemu packages
because, once trusty
Hello Serge,
I am sorry! I put this bug in on the saucy package, because I believe
it is what the cloud archive repository is using to provide openstack
packages for precise. I should have been more clear, and I apologize if
this bug is filed against the wrong project -- the packaging situation
** Changed in: qemu (Ubuntu)
Importance: Undecided => High
** Changed in: qemu (Ubuntu)
Status: Confirmed => In Progress
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) => Serge Hallyn (serge-hallyn)
** Also affects: qemu (Ubuntu Saucy)
Importance: Undecided
Status:
16 matches
Mail list logo
