Re: Bug#808320: fails to upgrade from 'testing'

[Ghislain Vaillant <ghisvail@gmail.com>]

Hi Andreas,

Thanks for reporting this bug.

I am not quite sure what the appropriate course of action is here. My 
thinking was the following:

libarrayfire-cpu-dev [3.0.2] shipped all CMake configuration files, 
since it was the only backend available at the time.

With the recent inclusion of new backends (OpenCL, unified), this 
package was split to:

libarrayfire-cpu-dev [3.2.x]
libarrayfire-dev [3.2.x]

whereby libarrayfire-dev now contains the files common to all backends, 
including the offending file you reported.

I thought about the upgrade path from libarrayfire-cpu-dev [3.0.2] to 
libarrayfire-cpu-dev [3.2.x] but probably forgot about someone who just 
wants to install libarrayfire-dev [3.2.x] with an existing 
libarrayfire-cpu-dev [3.0.2] in place. This is a very much a corner case 
though.

So I am guessing the appropriate course of action is to do something on 
the libarrayfire-dev. Can anyone confirm whether would this solution 
suffice:

Replaces: libarrayfire-cpu-dev (<< 3.2.1)
Breaks: libarrayfire-cpu-dev (<< 3.2.1)

Many thanks,
Ghis