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

Bug#805386: marked as done (RFS: arrayfire/3.2.0+dfsg1-1)



Your message dated Tue, 17 Nov 2015 16:41:30 +0000 (UTC)
with message-id <2027611116.9969937.1447778490993.JavaMail.yahoo@mail.yahoo.com>
and subject line Re: Bug#805386: RFS: arrayfire/3.2.0+dfsg1-1
has caused the Debian Bug report #805386,
regarding RFS: arrayfire/3.2.0+dfsg1-1
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.)


-- 
805386: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805386
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-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-doc - Common documentation 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-1.dsc

Changes since the last upload:

  * New upstream release.
  * d/gbp.conf: use submodules with buildpackage.
  * d/gbp.conf: disable patch numbering with pq.
  * Refresh patch queue:
    - Drop bugfix-in-assign.patch, applied upstream.
    - Rename remaining patches to their corresponding commit message,
      following switch to gbp-pq.
  * d/control: add gtest to build dependencies.
  * Add patch allowing build of testsuite with Debian gtest.
  * Disable build of unified backend.
  * d/{*.install,rules}: use more specific regexes.
    Reason: in anticipation of other backends being packaged.
  * d/rules: move nocheck filter inside autotest-arch target.
  * d/copyright: add missing copyright information.

Regards,
Ghislain Vaillant

--- End Message ---
--- Begin Message ---
Hi,

Built&Signed&Uploaded, thanks for your contribution to Debian!


cheers,

G.






Il Martedì 17 Novembre 2015 16:51, 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-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-doc - Common documentation 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-1.dsc

Changes since the last upload:

   * New upstream release.
   * d/gbp.conf: use submodules with buildpackage.
   * d/gbp.conf: disable patch numbering with pq.
   * Refresh patch queue:
     - Drop bugfix-in-assign.patch, applied upstream.
     - Rename remaining patches to their corresponding commit message,
       following switch to gbp-pq.
   * d/control: add gtest to build dependencies.
   * Add patch allowing build of testsuite with Debian gtest.
   * Disable build of unified backend.
   * d/{*.install,rules}: use more specific regexes.
     Reason: in anticipation of other backends being packaged.
   * d/rules: move nocheck filter inside autotest-arch target.
   * d/copyright: add missing copyright information.

Regards,
Ghislain Vaillant

--- End Message ---

Reply to: