similar to: xen_4.1.2-6_amd64.changes ACCEPTED into unstable

Accepted: libxen-4.1_4.1.2-4_amd64.deb to main/x/xen/libxen-4.1_4.1.2-4_amd64.deb libxen-dev_4.1.2-4_amd64.deb to main/x/xen/libxen-dev_4.1.2-4_amd64.deb libxen-ocaml-dev_4.1.2-4_amd64.deb to main/x/xen/libxen-ocaml-dev_4.1.2-4_amd64.deb libxen-ocaml_4.1.2-4_amd64.deb to main/x/xen/libxen-ocaml_4.1.2-4_amd64.deb libxenstore3.0_4.1.2-4_amd64.deb to

libxen-4.1_4.1.2-2_amd64.deb to main/x/xen/libxen-4.1_4.1.2-2_amd64.deb libxen-dev_4.1.2-2_amd64.deb to main/x/xen/libxen-dev_4.1.2-2_amd64.deb (new) libxen-ocaml-dev_4.1.2-2_amd64.deb optional ocaml OCaml libraries for controlling Xen (devel package) This package contains the ocaml findlib packages for compiling applications that are designed to control the Xen hypervisor. (new)

Accepted: libxen-4.1_4.1.2-1_amd64.deb to main/x/xen/libxen-4.1_4.1.2-1_amd64.deb libxen-dev_4.1.2-1_amd64.deb to main/x/xen/libxen-dev_4.1.2-1_amd64.deb libxenstore3.0_4.1.2-1_amd64.deb to main/x/xen/libxenstore3.0_4.1.2-1_amd64.deb xen-docs-4.1_4.1.2-1_all.deb to main/x/xen/xen-docs-4.1_4.1.2-1_all.deb xen-hypervisor-4.1-amd64_4.1.2-1_amd64.deb to

(new) libxen-4.1_4.1.2-1_amd64.deb optional libs Public libs for Xen This package contains the shared libraries for Xen. libxen-dev_4.1.2-1_amd64.deb to main/x/xen/libxen-dev_4.1.2-1_amd64.deb libxenstore3.0_4.1.2-1_amd64.deb to main/x/xen/libxenstore3.0_4.1.2-1_amd64.deb xen-docs-4.1_4.1.2-1_all.deb to main/x/xen/xen-docs-4.1_4.1.2-1_all.deb xen-hypervisor-4.1-amd64_4.1.2-1_amd64.deb to

Package: libxen-dev,libxs-dev Version: libxen-dev/4.1.2-3 Version: libxs-dev/1.0.1-1 Severity: serious User: treinen at debian.org Usertags: edos-file-overwrite Date: 2012-04-12 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem:

Package: xcp-xapi Version: 1.3.2-6 Severity: important Looks like on Wheezy, /etc/default/xen is not created by xen-utils-common. Since xcp-xapi depends on its existence and further declaration of the toolstack in it, it should take extra care to ensure that it is present. root at debian:~# aptitude install xcp-xapi The following NEW packages will be installed: blktap-dkms{a} blktap-utils{a}

Package: xen-utils-common Version: 4.1.2-4 Severity: serious Upgrading xen-utils-common from 4.1.2-2 to 4.1.2-4 fails with the following output: root at node4407:~# dpkg -i xen-utils-common_4.1.2-4_all.deb (Reading database ... 64228 files and directories currently installed.) Preparing to replace xen-utils-common 4.1.2-1 (using xen-utils-common_4.1.2-4_all.deb) ... insserv: Service xend has to

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Thu, 11 Dec 2014 15:56:08 +0100 Source: xen Binary: libxen-4.4 libxenstore3.0 libxen-dev xenstore-utils xen-utils-common xen-utils-4.4 xen-hypervisor-4.4-amd64 xen-system-amd64 xen-hypervisor-4.4-arm64 xen-system-arm64 xen-hypervisor-4.4-armhf xen-system-armhf Architecture: source all amd64 Version: 4.4.1-6 Distribution:

Package: xen-utils-common Version: 4.1.2-1 Severity: important User: debian-qa at lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts

Source: xen Version: 4.1.2-3 Severity: serious Tags: wheezy sid User: debian-qa at lists.debian.org Usertags: qa-ftbfs-20120321 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[7]: Entering directory `/?PKGBUILDDIR?/debian/build/build-utils_amd64/tools/firmware' > /usr/bin/make -C etherboot

xen_4.4.1-6_amd64.changes uploaded successfully to localhost along with the files: xen_4.4.1-6.dsc xen_4.4.1-6.debian.tar.xz xen-utils-common_4.4.1-6_all.deb xen-hypervisor-4.4-amd64_4.4.1-6_amd64.deb xen-system-amd64_4.4.1-6_amd64.deb libxenstore3.0_4.4.1-6_amd64.deb libxen-4.4_4.4.1-6_amd64.deb libxen-dev_4.4.1-6_amd64.deb xen-utils-4.4_4.4.1-6_amd64.deb

Processing commands for control at bugs.debian.org: > severity 671750 important Bug #671750 [xen-utils-common] Configuration of domain save/restore broken Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 671750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671750 Debian Bug Tracking System Contact

On 12/22/2011 01:37 AM, Mike McClurg wrote: > Hi Thomas, Jon, > > I was hoping that you could both comment on this github pull request: > > https://github.com/jonludlam/xen-api/pull/12 > > Mike > In Debian, /etc/default/xen is there to select xm vs xl. So we could do: if ! [ -f /etc/default/xen ] ; then TOOLSTACK=xm else . /etc/default/xen if ! [

Package: xen-utils-common Version: 4.0.0-1 Severity: important When xen domUs are saved by running /etc/init.d/xendomains stop the memory images are saved world readable, so that every user on the system can read the memory dumps. The default mode of /var/lib/xen/save is 755, vm images are saved with mode 755. At least the save directory shoudn't be world readable. -- System Information:

Package: xen-utils-common Version: 4.1.2-5 Severity: grave Hi, Between 4.1.2-3 and 4.1.2-5, the sanity checks on the variables defined in /etc/default/xendomains (XENDOMAINS_SAVE, XENDOMAINS_RESTORE, etc.) was lost. I can't check exactly when because there's no Vcs defined for this package. 4.1.2-3 had in /etc/init.d/xendomains for restore: if [ "$XENDOMAINS_RESTORE" =

Processing commands for control at bugs.debian.org: > severity 503044 wishlist Bug #503044 [xen-utils-common] xen-utils-common: should make the loopback device default to supporting more nodes Severity set to 'wishlist' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator

Hi, i have a problem with samba3 (with ldapsam). I've set up my samba3 beta2 (also tried beta3) as a pdc, but it seems that samba does not anounce it's DOMAIN correctly. I don't see my JOCHENGROUP Domain from any Windows-Workstation. I can search for the name of my PDC using the 'Search Computer' Function and Windows will find it. I can doubleclick the PDC and login using

On 23 March 2016 at 09:35, Barnet Wagman wrote: | I am unable to install R on an up to date (i.e. apt upgraded) Ubuntu | 14.04 system. According to | https://cran.r-project.org/bin/linux/ubuntu/README (and many other sources), | R is available for this version of Ubuntu (which is a stable version). | | I currently have | | deb https://cran.cnr.berkeley.edu/bin/linux/ubuntu trusty/ | | in

Synaptic can show the origin of packages. The only thing I see from a backport is libcmanager0 I don't think this is relevant to R. Or is it. The only thing I've got installed from a ppa is mate (a desktop). I don't see anything related to mate that is related to R. FYI the ubunu I'm using came preinstalled from Dell (on a notebook; usually I install linux myself). On

It's a Dell XPS 13. Obviously I don't understand what's in libcmanager0. I wonder if I can safely replace it. I'm a bit uneasy about replacing things Dell installed. I gather there are some specialized drivers for the monitor on this system. On 03/23/2016 11:34 AM, Alex M wrote: > That could do it > http://packages.ubuntu.com/trusty-backports/libcgmanager0 > >