> IMHO the best solution is to adopt Julian's patch for blosc disabling
> and upload the new package to allow migration to testing.
> Just let me know how to proceed.
I guess that would indeed be the best resolution for now
> I don't know if there is some special protocol/procedure for importing
Hi Yaroslav, hi Julian,
Il 03/03/2012 22:01, Yaroslav Halchenko ha scritto:
> what would not work? disabling blosc? it would work I bet and thanks
> for testing on a sparc64 system
>
> I just hoped that someone (upstream?) could find a chance to
> resolve it "properly" ;)
>
Yaroslav, I doubt
what would not work? disabling blosc? it would work I bet and thanks
for testing on a sparc64 system
I just hoped that someone (upstream?) could find a chance to
resolve it "properly" ;)
> On 03/03/2012 09:47 PM, Yaroslav Halchenko wrote:
> > are "going" across platforms? or should we may be
On 03/03/2012 09:47 PM, Yaroslav Halchenko wrote:
> Hi Antonio and Julian,
>
> Sorry for being silent/disconnected
>
> so -- what is the status -- should we meanwhile upload to see how things
> are "going" across platforms? or should we may be adopt blosc
> disabling patches from Julian first..
Hi Antonio and Julian,
Sorry for being silent/disconnected
so -- what is the status -- should we meanwhile upload to see how things
are "going" across platforms? or should we may be adopt blosc
disabling patches from Julian first
sparc issue is still not resolved AFAIK
I have pushed a tin
5 matches
Mail list logo
