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

Bug#819356: RFS: arrayfire/3.3.1+dfsg1-1



Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "arrayfire"

* Package name    : arrayfire
  Version         : 3.3.1+dfsg1-1
  Upstream Author : ArrayFire Development Group
* URL             : http://arrayfire.com/
* License         : BSD
  Section         : science

It builds those binary packages:

  libarrayfire-cpu-dev - Development files for ArrayFire (CPU backend)
  libarrayfire-cpu3 - High performance library for parallel computing
(CPU backend)
  libarrayfire-cpu3-dbg - Debugging symbols for ArrayFire (CPU backend)
  libarrayfire-dev - Common development files for ArrayFire
  libarrayfire-doc - Common documentation and examples for ArrayFire
  libarrayfire-opencl-dev - Development files for ArrayFire (OpenCL
backend)
  libarrayfire-opencl3 - High performance library for parallel
computing (OpenCL backend)
  libarrayfire-opencl3-dbg - Debugging symbols for ArrayFire (OpenCL
backend)
  libarrayfire-unified-dev - Development files for ArrayFire (unified
backend)
  libarrayfire-unified3 - High performance library for parallel
computing (unified backend)
  libarrayfire-unified3-dbg - Debugging symbols for ArrayFire (unified
backend)

To access further information about this package, please visit the
following URL:

  http://mentors.debian.net/package/arrayfire

Alternatively, one can download the package with dget using this command:

dget -x http://mentors.debian.net/debian/pool/main/a/arrayfire/arrayfire_3.3.1+dfsg1-1.dsc

Successful build logs on debomatic:

[amd64] http://debomatic-amd64.debian.net/distribution#unstable/arrayfire/3.3.1+dfsg1-1/buildlog

Changes since the last upload:

  * Release to unstable.
  * d/gbp.conf: use recommended packaging repository layout (DEP-14):
    - change upstream branch from dfsg-clean to upstream/latest.
    - change debian branch from debian/sid to debian/master.

Regards,
Ghislain Vaillant


Reply to: