search for: libxenevtchn1

...8 19:38:52 +0100 Source: xen Binary: xenstore-utils xen-utils-common xen-hypervisor-common xen-doc xen-utils-4.11 xen-hypervisor-4.11-amd64 xen-system-amd64 xen-hypervisor-4.11-arm64 xen-system-arm64 xen-hypervisor-4.11-armhf xen-system-armhf libxen-dev libxenmisc4.11 libxencall1 libxendevicemodel1 libxenevtchn1 libxenforeignmemory1 libxengnttab1 libxenstore3.0 libxentoolcore1 libxentoollog1 Architecture: all amd64 source Version: 4.11.1~pre.20180911.5acdd26fdc+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Xen Team <pkg-xen-devel at lists.alioth.debian.org> Changed-By: Ian Jackson...

...5/debian/control 2024-02-05 22:37:18.000000000 +0000 @@ -212,16 +212,16 @@ Section: libdevel Architecture: amd64 arm64 armhf Depends: ${shlibs:Depends}, ${misc:Depends}, - libxenmisc4.17 (= ${binary:Version}), - libxencall1 (= ${binary:Version}), - libxendevicemodel1 (= ${binary:Version}), - libxenevtchn1 (= ${binary:Version}), - libxenforeignmemory1 (= ${binary:Version}), - libxengnttab1 (= ${binary:Version}), - libxenstore4 (= ${binary:Version}), - libxentoolcore1 (= ${binary:Version}), - libxentoollog1 (= ${binary:Version}), - libxenhypfs1 (= ${binary:Version}), + libxenmisc4.17t64 (= ${bi...

...rsion 4.8 produces libraries with 4.8 in the soname. A qemu compiled against this version has Depends: libxen-4.8 3. libxen-dev version 4.11 produces libraries with no version number in the soname (except those in libxenmisc). A qemu compiled against this version has Depends: libxendevicemodel1, libxenevtchn1, libxenforeignmemory1, libxengnttab1, libxenmisc4.11 There doesn't seem to be a way by which qemu could be packaged to work with *either* 4.8 or 4.11: If you have a qemu that was compiled against libxen-dev=4.8, your qemu will *only* use the libxen-4.8 files. If you have a qemu that was compi...

Source-only uploads to NEW are not allowed. binary:libxencall1 is NEW. binary:libxendevicemodel1 is NEW. binary:libxenevtchn1 is NEW. binary:libxenforeignmemory1 is NEW. binary:libxengnttab1 is NEW. binary:libxenhypfs1 is NEW. binary:libxenstore4 is NEW. binary:libxentoolcore1 is NEW. binary:libxentoollog1 is NEW. === Please feel free to respond to this email if you don't understand why your files were rejected, or...

...dev_4.20.0~rc2+1-gfcde5e0de8-1~exp1_amd64.deb libxencall1-dbgsym_4.20.0~rc2+1-gfcde5e0de8-1~exp1_amd64.deb libxencall1_4.20.0~rc2+1-gfcde5e0de8-1~exp1_amd64.deb libxendevicemodel1-dbgsym_4.20.0~rc2+1-gfcde5e0de8-1~exp1_amd64.deb libxendevicemodel1_4.20.0~rc2+1-gfcde5e0de8-1~exp1_amd64.deb libxenevtchn1-dbgsym_4.20.0~rc2+1-gfcde5e0de8-1~exp1_amd64.deb libxenevtchn1_4.20.0~rc2+1-gfcde5e0de8-1~exp1_amd64.deb libxenforeignmemory1-dbgsym_4.20.0~rc2+1-gfcde5e0de8-1~exp1_amd64.deb libxenforeignmemory1_4.20.0~rc2+1-gfcde5e0de8-1~exp1_amd64.deb libxengnttab1-dbgsym_4.20.0~rc2+1-gfcde5e0de8-1~exp1_...

...important/urgent one. Having this dependency means that users of backports cannot use HVM, or that there also need to be qemu backports. When redoing the packaging in Q3 2018, all libraries with upstream stable ABI were split off into packages with its own version number, like libxendevicemodel1, libxenevtchn1, etc. We think there's technically no reason that qemu has to depend on libxenmisc4.11, so maybe it's the shlibs machinery that is confused. Task here: find out why this is happening and see if the dependency can be removed. Apparently collectd and libvirt have a similar problem.

...AGE=en_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_CA.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xen-utils-4.11 depends on: ii  libc6             2.27-6 ii  libncurses6       6.1+20181013-1 ii  libtinfo6         6.1+20181013-1 pn  libxenevtchn1     <none> pn  libxengnttab1     <none> pn  libxenmisc4.11    <none> pn  libxenstore3.0    <none> pn  libxentoolcore1   <none> pn  libxentoollog1    <none> pn  libyajl2          <none> ii  python            2.7.15-3 pn  xen-utils-common  <none> Versi...