[Debian-med-packaging] [Python-apps-team] cython for jessie-backports
Charles Plessy
plessy at debian.org
Tue Oct 13 12:13:35 UTC 2015
Le Tue, Oct 13, 2015 at 12:03:00AM -0700, Afif Elghraoui a écrit :
> On الإثنين 12 تشرين الأول 2015 23:47, Charles Plessy wrote:
> >> On الإثنين 12 تشرين الأول 2015 21:56, Charles Plessy wrote:
> >>> > > operations like changing the resolver affect all the
> >>> > > dependances, so one could imagine that a package would start to fail to build
> >>> > > because it needs python-foo from jessie-backports but can not use a cython
> >>> > > version higher than the one in jessie.
> >> >
> >> > Is this even if d/control says cython << 0.23?
> > Most likely not, but I was thinking of the packages that were uploaded up to
> > now, where such a version check may not be present.
>
> I thought it might just be a better move then to add that qualification
> into debian/control when backporting a package that would otherwise be
> affected.
Definitely, if cython is backported, it will be good to have "cython << 0.23"
in the backports that are not proven to work with Jessie's version.
My question was more about the existing backports, if they are not proven to
work with cython >= 0.23. But maybe there are no such packages ?
Cheers,
--
Charles
More information about the Debian-med-packaging
mailing list