Bug#805838: marked as done (RFS: arrayfire/3.2.0+dfsg1-3)
Your message dated Mon, 23 Nov 2015 09:10:31 +0000 (UTC)
with message-id <600667960.14447356.1448269831741.JavaMail.yahoo@mail.yahoo.com>
and subject line Re: Bug#805838: RFS: arrayfire/3.2.0+dfsg1-3
has caused the Debian Bug report #805838,
regarding RFS: arrayfire/3.2.0+dfsg1-3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
805838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805838
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "arrayfire"
* Package name : arrayfire
Version : 3.2.0+dfsg1-3
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-doc - Common documentation and examples for ArrayFire
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.2.0+dfsg1-3.dsc
Changes since the last upload:
* Remove jquery symlink in HTML documentation.
* d/rules: set build directory explicitly.
* d/rules: use correct cmake option for include install path.
* Add example source code to documentation package.
* d/rules: exclude examples and documentation from compression.
* Add patch enabling usage of custom compile flags in examples.
* Add autopkgtest testsuite.
* Add patch fixing build of examples.
* Use cmake options to inject documentation and example install paths.
* d/control: cme fixed, wrap and sort.
Regards,
Ghislain Vaillant
--- End Message ---
--- Begin Message ---
Hi, Built&Signed and Source-Only uploaded!
the Ubuntu Xenial build failure seems to be fixed now (at least I don't see this problem in a xenial amd64 pbuilder environment)
- I don't understand the force of build directory, but I don't care :)
- I don't understand the reason to specify usr/include as include path (isn't it a default?)
- the pre-depends can be dropped, useless after jessie (or was it wheezy?)
cheers,
thanks for your contribution to Debian!
(BTW I don't remember if you already applied as DM, I would like to grant you upload permissions for this package, I didn't have
to change anything in your packaging since a few uploads now :) )
G.
Il Lunedì 23 Novembre 2015 0:45, Ghislain Vaillant <ghisvail@gmail.com> ha scritto:
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "arrayfire"
* Package name : arrayfire
Version : 3.2.0+dfsg1-3
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-doc - Common documentation and examples for ArrayFire
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.2.0+dfsg1-3.dsc
Changes since the last upload:
* Remove jquery symlink in HTML documentation.
* d/rules: set build directory explicitly.
* d/rules: use correct cmake option for include install path.
* Add example source code to documentation package.
* d/rules: exclude examples and documentation from compression.
* Add patch enabling usage of custom compile flags in examples.
* Add autopkgtest testsuite.
* Add patch fixing build of examples.
* Use cmake options to inject documentation and example install paths.
* d/control: cme fixed, wrap and sort.
Regards,
Ghislain Vaillant
--- End Message ---
Reply to: