This bug was fixed in the package xen - 4.2.2-0ubuntu0.13.04.1
---
xen (4.2.2-0ubuntu0.13.04.1) raring-proposed; urgency=low
* Updating to latest upstream stable release (LP: #1180397).
- Security patches included which replace existing changes:
* CVE-2012-5634 / XSA-33, C
Adding the test results as an attachment to keep the formatting sane.
Note on the one occasional failure of the security QRT run: one of the
tests for /proc//maps turns out to be racy at least (I need to talk
to the security team about it). But failing or not failing is only
depending on execution
Hi Brian,
not formally yet as I wanted to write that down here as comments with
results. Need to see how much effort it will be to leverage some or more
of the regression testing that xen upstram does on the git repos. But
since I am travelling right now it will get delayed till next week.
--
Yo
Hello Stefan, or anyone else affected,
Accepted xen into raring-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/xen/4.2.2-0ubuntu0.13.04.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
The provisional micro-release exception for Xen includes the following
caveat:
Xen, first SRU needs to define a formal regression test procedure, such
as "boot the last N releases/LTS default install and verify some list of
things (networking, file system test suite, etc.)" (2013-07-22)
Where has
** Summary changed:
- Xen stable update to 4.2.2
+ [MRE] Xen stable update to 4.2.2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xen in Ubuntu.
https://bugs.launchpad.net/bugs/1180397
Title:
[MRE] Xen stable update to 4.2.2
To m