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

Proposed fix with breaks / replaces



On 19/12/15 10:49, Ghislain Vaillant wrote:
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

Would the following diff work:

diff --git a/debian/control b/debian/control
index 372e3d1..b111754 100644
--- a/debian/control
+++ b/debian/control
@@ -29,7 +29,7 @@ Section: libdevel
 Architecture: any
 Multi-Arch: same
 Depends: libarrayfire-cpu3 (= ${binary:Version}),
-         libarrayfire-dev,
+         libarrayfire-dev (>= 3.2.1+dfsg1-6),
          ${misc:Depends}
 Description: Development files for ArrayFire (CPU backend)
  ArrayFire is a high performance software library for parallel computing
@@ -92,6 +92,8 @@ Architecture: any
 Multi-Arch: same
 Depends: ${misc:Depends}
 Suggests: libarrayfire-doc
+Replaces: libarrayfire-cpu-dev (<< 3.2.1+dfsg1-6)
+Breaks: libarrayfire-cpu-dev (<< 3.2.1+dfsg1-6)
 Description: Common development files for ArrayFire
  ArrayFire is a high performance software library for parallel computing
  with an easy-to-use API. Its array based function set makes parallel


Reply to: