similar to: Bug#740515: Removed package(s) from unstable

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: xcp-storage-managers | 0.1.1-3.1 | source, amd64, i386 ------------------- Reason ------------------- ROM; non maintained upstream ---------------------------------------------- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: libxenapi-ocaml-dev | 1.3.2-15 | amd64, i386 python-xenapi | 1.3.2-15 | all xcp-networkd | 1.3.2-15 | amd64, i386 xcp-squeezed | 1.3.2-15 | amd64, i386 xcp-v6d | 1.3.2-15 | amd64, i386 xcp-xapi | 1.3.2-15 | amd64, i386 xcp-xapi-debug | 1.3.2-15 | amd64, i386 xcp-xe |

Version: 0.1-4+rm Dear submitter, as the package guest-templates has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/738322 The version of this package that was in Debian prior to this removal can still be found using

Version: 1.3.2-15+rm Dear submitter, as the package xen-api has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/740517 The version of this package that was in Debian prior to this removal can still be found using

Version: 0.5.2-3.1+rm Dear submitter, as the package xen-api-libs has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/740518 The version of this package that was in Debian prior to this removal can still be found using

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: xen-common | 4.1.2-1 | source xen-utils-common | 4.1.2-1 | all ------------------- Reason ------------------- RoQA; obsoleted by xen ---------------------------------------------- Note that the package(s) have simply been removed from the tag database and may (or may not) still be

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: guest-templates | 0.1-4 | source xcp-guest-templates | 0.1-4 | amd64, i386 ------------------- Reason ------------------- ROM; non maintained upstream ---------------------------------------------- Note that the package(s) have simply been removed from the tag database and may

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: libxcp-ocaml | 0.5.2-3.1 | amd64, i386 libxcp-ocaml-dev | 0.5.2-3.1 | amd64, i386 xcp-fe | 0.5.2-3.1 | amd64, i386 xen-api-libs | 0.5.2-3.1 | source ------------------- Reason ------------------- ROM; non maintained upstream ---------------------------------------------- Note

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: xcp-eliloader | 0.1-4 | source, all ------------------- Reason ------------------- ROM; non maintained upstream ---------------------------------------------- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: xcp-vncterm | 0.1-2.1 | source, amd64, i386 ------------------- Reason ------------------- ROM; non maintained upstream ---------------------------------------------- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool;

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: xen-3 | 3.4.3-1 | source xen-docs-3.4 | 3.4.3-1 | all xen-hypervisor-3.4-amd64 | 3.4.3-1 | amd64, i386 xen-hypervisor-3.4-i386 | 3.4.3-1 | i386 xen-utils-3.4 | 3.4.3-1 | amd64, i386 ------------------- Reason ------------------- ROM; Superseeded by xen

Package: xcp-storage-managers Version: 0.1.1-3 Severity: normal This was already reported in the archived bug 691805 but I sent an e-mail and I received back permanent delivery failure because this bugs has been archieved. Still the path of "pidof" in the file /usr/lib/xcp/sm/iscsilib.py is wrong on Wheezy. It should be /bin/pidof instead of /sbin/pidof root at xcpcompute2:~# cat

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Sun, 04 Nov 2012 18:54:52 +0000 Source: xcp-storage-managers Binary: xcp-storage-managers Architecture: source amd64 Version: 0.1.1-3 Distribution: unstable Urgency: low Maintainer: PKG-Xen Devel <pkg-xen-devel at lists.alioth.debian.org> Changed-By: Thomas Goirand <zigo at debian.org> Description:

Package: xcp-storage-managers Version: 0.1.1-3.1 Severity: normal User: mayhem at forallsecure.com Usertags: mayhem tp crashes with exit status 139. We confirmed the crash by re-running it in a fresh debian unstable installation. The attachment [1] contains a testcase (under ./crash) crashing the program. It ensures that you can easily reproduce the bug. Additionally, under ./crash_info/, we

Package: xcp-storage-managers Version: 0.1.1-3 Severity: normal XCP cannot use iscsi block devices. Fails with iscsiadm: No active sessions. I ran the following commands trying to diagnose the problem: First introducing a SR and then creating a PBD with the needed configuration for the iscsi block device. These steps work fine but when I tried to plug the PBD I got the error: root at

Package: xcp-xapi Version: 1.3.2-6 Severity: important Configuration: Two xcp-xapi hosts (default sid/xcp-xapi installation) in single pool. Network backend is bridge. After migration of 'idle' (doning nothing) virtual machine it stops to reply to ping for long time. AFAIK that caused by mac-learning table on upper level (hardware) switch, which route all frames to wrong port

Package: xcp-storage-managers Version: 0.1.1-2ubuntu1 Severity: normal This bug prevents CDROM VDIs from being hotplugged into guest VMs. The issue is that the NFS ISO SR configures the ISO VDIs to be 'file' types, which it should configure them to by 'phy' types. This breaks on Debian's Xen because the Debian hotplug scripts are more robuse than the ones on XenServer, and

Processing commands for control at bugs.debian.org: > # bugs with submitter debian at abeckmann.de > submitter 479445 ! Bug #479445 [gnuplot] gnuplot: wrong line numbers for missing files reported during replot Changed Bug submitter to 'Andreas Beckmann <anbe at debian.org>' from 'Andreas Beckmann <debian at abeckmann.de>' > submitter 681568 ! Bug #681568

Package: xcp-xapi Version: 1.3.2-8 Severity: minor During upgrade from 1.3.2-7 to 1.3.2-8 got follwing message on slave host (upgrade was simulatanious on slave and master): ... Setting up xcp-xapi (1.3.2-8) ... The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: INTERNAL_ERROR: [

Package: xcp-xapi Version: 1.3.2-6 Severity: important Tags: upstream xe vm-memory-target-set does not write new target to /local/domain/ID/memory/target. Balloon in guest domain is expecting this value to be changed to do selfballooning. This breaks 'dynamic memory control' feature. Steps to reproduce: 1) Setup any PV virtual machine with static-memory-min < static-memory-max 2)