[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#842919: transition: xen



Emilio Pozuelo Monfort writes ("Re: Bug#842919: transition: xen"):
> On 02/11/16 11:47, Ian Jackson wrote:
...
> > All that is needed from the build-rdeps is a rebuild.  That is, of:
> >   libvirt qemu xenwatch python-pyxenstore collectd grub2
> > 
> > I have checked that they all build against the new libxen{-4.8,-dev},
> > at least on amd64.  I don't anticipate trouble on other architectures.
> 
> The ben tracker only lists qemu and libvirt as rdeps of the binaries
> that are removed in the new version. Why do the other packages need
> a rebuild? Do any of them statically link libxen or something?

(Hi.  Thanks for your attention.  I am somewhat full of wine right
now, so my answers may be wrong.  It seemed better to reply sooner.
My work hat can produce more sober replies tomorrow:)

I got the list from "build-rdeps".  Is it wrong ?  It's the list of
things which have libxen-dev as a build-dep.

Hrm.  I looked at xenwatch and python-pyxenstore and though the source
packages Build-Depend on libxen, the binaries Depend only libxenstore
whose ABI version and package name have not changed.  So I think,
then, that there is actually no need to recompile those two, although
it would probably be best to do so as a precaution (in case the ABI
has unwittingly changed, in which case it would be somewhat better for
stretch to be internally consistent).

In my test rebuild, collectd.deb Depends libxen-4.8.  My apt-cache
show thinks that sid's current collectd Depends libxen-4.6.  I'm not
sure why a collectd rebuild would not be needed.

grub2 is more complicated.  I am going to reply separately about that,
CC grub2@p.d.o.

Thanks,
Ian.

-- 
Ian Jackson <ijackson@chiark.greenend.org.uk>   These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.


Reply to: