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

Bug#849014: marked as done (RFS: forge/0.9.2-1)

Your message dated Thu, 22 Dec 2016 10:04:56 +0000 (UTC)
with message-id <1369093177.294681.1482401096449@mail.yahoo.com>
and subject line Re: Bug#849014: RFS: forge/0.9.2-1
has caused the Debian Bug report #849014,
regarding RFS: forge/0.9.2-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.)


-- 
849014: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849014
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 "forge"

* Package name    : forge
  Version         : 0.9.2-1
  Upstream Author : ArrayFire
* URL             : https://github.com/arrayfire/forge
* License         : BSD
  Section         : libs

It builds those binary packages:

 forge-doc  - documentation for forge
 libforge-dev - development files for forge
 libforge0  - high-performance OpenGL visualization
To access further information about this package, please visit the following URL: 

  https://mentors.debian.net/package/forge

Alternatively, one can download the package with dget using this command:
dget -x https://mentors.debian.net/debian/pool/main/f/forge/forge_0.9.2-1.dsc 

Successful build on debomatic:


http://debomatic-amd64.debian.net/distribution#unstable/forge/0.9.2-1/buildlog

Changes since the last upload:

  * Switch to git-dpm.
  * New upstream release.
* Drop patch Fix-build-of-examples-with-the-system-cl2hpp.patch, applied upstream. 
  * New patch No-version-queries-with-Git.patch, avoid spurious "git not
    found" entries in the build log when the documentation is generated.
  * Drop gbp configuration in favor of git-dpm
  * Upgrade packaging to debhelper 10
  * Use architecture.mk to query DEB_HOST_MULTIARCH
  * Cosmetic fixup of rules file

Regards,
Ghislain Vaillant

--- End Message ---
--- Begin Message --- 

>I am looking for a sponsor for my package "forge"

seems already done

G.

--- End Message ---
Reply to: