similar to: Bug#606589: marked as done (xen-linux-system-2.6.32-5-xen-amd64 doesn't upgrade from xen-linux-system-2.6.26-2-xen-amd64)

Your message dated Wed, 13 Sep 2006 10:34:57 +0200 with message-id <20060913083457.GA11942@wavehammer.waldi.eu.org> and subject line fixed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB:

Your message dated Sat, 10 Dec 2011 20:00:59 +0100 with message-id <20111210190059.GG15557 at wavehammer.waldi.eu.org> and subject line no bug has caused the Debian Bug report #649141, regarding xen-hypervisor-4.0-amd64: live migration fails with invalid opcode due to nonstop_tsc to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Your message dated Sat, 06 Apr 2013 13:00:07 +0000 with message-id <E1UOSj1-0002As-63 at franck.debian.org> and subject line Bug#693137: fixed in swift-plugin-s3 1.7-1 has caused the Debian Bug report #693137, regarding ITP: swift-plugin-s3 -- swift3 (S3 compatibility) middleware plugin for swift to be marked as done. This means that you claim that the problem has been dealt with. If this

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: serious Tags: squeeze Hi there! Upgrading from Lenny to Squeeze left my box with xen-hypervisor-3.2-1-amd64 installed, and I had to "apt-get install xen-hypervisor-4.0-amd64" manually to have it installed after a dist-upgrade. This for sure, isn't the expected behavior. Also, after the dist-upgrade, I did: apt-get

Your message dated Fri, 06 Sep 2013 09:09:48 +0100 with message-id <1378454988.3057.2.camel at dagon.hellion.org.uk> and subject line Re: [Pkg-xen-devel] Bug#710522: Problem found has caused the Debian Bug report #710522, regarding xen-hypervisor-4.1-amd64: Boot hang with Linux 3.2+Xen, works with linux 2.6.32+Xen or 3.2 raw to be marked as done. This means that you claim that the problem

Processing commands for control at bugs.debian.org: > severity 606589 important Bug #606589 [xen-linux-system-2.6.32-5-xen-amd64] xen-linux-system-2.6.32-5-xen-amd64 doesn't upgrade from xen-linux-system-2.6.26-2-xen-amd64 Severity set to 'important' from 'serious' > reassign 606589 xen-hypervisor-4.0-amd64 Bug #606589 [xen-linux-system-2.6.32-5-xen-amd64]

On 12/10/2010 11:37 PM, Ian Campbell wrote: > severity 606589 important > reassign 606589 xen-hypervisor-4.0-amd64 > merge 606590 606589 > thanks > > At the core this is the same issue as 606590. I think a single report is > enough to allow this to be fixed in the relevant place, if the kernel > ends up being the place to fix then the bug can be reassigned as >

Your message dated Fri, 29 Aug 2014 13:26:07 +0000 with message-id <20140829132607.GD4202 at shell.waldi.eu.org> and subject line Xen 3.0 unsupported has caused the Debian Bug report #728295, regarding xen: Issues with Networking on virtual hosts with Xen.3.0.3-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Your message dated Fri, 29 Aug 2014 13:33:00 +0000 with message-id <20140829133300.GB4246 at shell.waldi.eu.org> and subject line xend support gone has caused the Debian Bug report #491660, regarding xen-utils-common: should allow local unix connections to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility

Your message dated Sun, 10 Aug 2014 12:00:17 +0000 with message-id <E1XGRnN-0007ak-6G at franck.debian.org> and subject line Bug#718898: fixed in xen 4.4.0-1 has caused the Debian Bug report #718898, regarding coreutils: cut no longer works with newline as delimiter to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Your message dated Fri, 28 May 2010 10:02:57 +0000 with message-id <E1OHwP3-0007aW-JR at ries.debian.org> and subject line Bug#583283: fixed in xen-3 3.4.3-1 has caused the Debian Bug report #583283, regarding udev - Weird behaviour with device names including a slash to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Your message dated Sun, 02 Mar 2014 18:42:06 +0000 with message-id <E1WKBKw-0004SD-Mw at franck.debian.org> and subject line Bug#740517: Removed package(s) from unstable has caused the Debian Bug report #710650, regarding xen-api: FTBFS: gcc: error: /home/blank/debian/xen/releases/xen/xen-4.2.1/debian/build/build-utils_amd64/tools/ocaml/libs/xc/../../../../tools/libxc/libxenctrl.so: No such

xm save lenny3 /tmp/lenny3.save The guest console says: Suspending xenbus... and detaches. Restore the guest (paused to attach its console before continuing): xm restore -p /tmp/lenny3.save xm console lenny3 xm unpause lenny3 The console starts spewing out "BUG: recent printk recursion" and the domain spins until destroyed. The same thing happens on (live or not) migration. The

Your message dated Thu, 08 Sep 2011 14:48:50 +0000 with message-id <E1R1fuM-0008SF-9f at franck.debian.org> and subject line Bug#639839: fixed in logcheck 1.3.14 has caused the Debian Bug report #639839, regarding amavisd-new: logcheck "Passed: CLEAN|SPAM" doesn't work because mail-id can contain "-" to be marked as done. This means that you claim that the problem

Your message dated Sun, 31 Aug 2008 19:32:06 +0000 with message-id <E1KZsec-00064d-FQ at ries.debian.org> and subject line Bug#474239: fixed in logcheck 1.3.0 has caused the Debian Bug report #474239, regarding spamassassin: spamd logcheck file doesn't work with shortcircuit enabled to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Your message dated Tue, 24 Jun 2008 20:13:35 +0100 with message-id <20080624191335.GA18136 at lapse.rw.madduck.net> and subject line closed ages ago has caused the Debian Bug report #252165, regarding postfix: Messages from queuemanager flood logcheck to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility

Hi, On 23 Jun 2014, at 09:53, Thomas Goirand <zigo at debian.org> wrote: > On 04/19/2014 03:15 AM, Ian Campbell wrote: >> On Thu, 2014-03-06 at 14:05 +0000, Ian Campbell wrote: >>> Hi waldi, >>> >>> Are you planning to update the Xen package too 4.4 soon? Upstream have >>> released 4.4-rc6 and AIUI are planning to release the final version next

On 04/19/2014 03:15 AM, Ian Campbell wrote: > On Thu, 2014-03-06 at 14:05 +0000, Ian Campbell wrote: >> Hi waldi, >> >> Are you planning to update the Xen package too 4.4 soon? Upstream have >> released 4.4-rc6 and AIUI are planning to release the final version next >> week (I've been out of the office for a bit, so I don't know the precise >> state,

On 08 ??? 2014, at 22:31, Thomas Goirand <zigo at debian.org> wrote: > On 09/08/2014 04:59 PM, Chrysostomos Nanakos wrote: >> On 2014-09-08 10:07, Thomas Goirand wrote: >>> On 09/07/2014 01:44 AM, Chrysostomos Nanakos wrote: >>>> dget -x >>>> >>>> http://mentors.debian.net/debian/pool/main/b/blktap/blktap_2.0.90-3.dsc >>>

On 09/09/2014 05:15 AM, Nanakos Chrysostomos wrote: > On 08 ??? 2014, at 22:31, Thomas Goirand <zigo at debian.org> wrote: > >> On 09/08/2014 04:59 PM, Chrysostomos Nanakos wrote: >>> On 2014-09-08 10:07, Thomas Goirand wrote: >>>> On 09/07/2014 01:44 AM, Chrysostomos Nanakos wrote: >>>>> dget -x >>>>> >>>>>