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

Bug#819463: marked as done (RFS: python-arrayfire/3.3.20160328-1 [ITP])

Your message dated Tue, 29 Mar 2016 11:08:02 +0000
with message-id <20160329110802.GB5329@chase.mapreri.org>
and subject line Re: Bug#819463: RFS: python-arrayfire/3.3.20160328-1 [ITP]
has caused the Debian Bug report #819463,
regarding RFS: python-arrayfire/3.3.20160328-1 [ITP]
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.)


-- 
819463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819463
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

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

It builds those binary packages:

  python-arrayfire - Python wrappers for the ArrayFire library (Python 2)
  python-arrayfire-doc - examples for the ArrayFire Python wrappers
  python3-arrayfire - Python wrappers for the ArrayFire library (Python 3)
To access further information about this package, please visit the following URL: 

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

Alternatively, one can download the package with dget using this command:
dget -x http://mentors.debian.net/debian/pool/main/p/python-arrayfire/python-arrayfire_3.3.20160328-1.dsc 

Or by checking out the upstream repository at:


https://anonscm.debian.org/git/debian-science/packages/python-arrayfire.git

You can find the successful build logs on debomatic at:
[amd64] http://debomatic-amd64.debian.net/distribution#unstable/python-arrayfire/3.3.20160328-1/buildlog [i386] http://debomatic-i386.debian.net/distribution#unstable/python-arrayfire/3.3.20160328-1/buildlog 

Changes since the last upload:

  * Initial release. (Closes: #799001)

Regards,
Ghislain Vaillant

--- End Message ---
--- Begin Message --- 
On Tue, Mar 29, 2016 at 11:17:02AM +0100, Ghislain Vaillant wrote:
> On 29/03/16 11:11, Mattia Rizzolo wrote:
> >The package looks ok, but the tarball I get with pristine-tar is
> >different than the one I can download with uscan.  how so?
> 
> The tarball was committed with a call to:
> 
>   gbp buildpackage --git-no-pristine-tar --git-pristine-tar-commit
> 
> Which generated the tarball out of the upstream tag.

ok, thats's fine by me.

> >a nitpick: in the DEP-8 test instead of listing all 3 binaries in
> >the example test you could have just used '@', or even leave out the
> >Depends: field entirely (in that case the deps on @ is implied).
> 
> Interesting. I did not know that. Does it mean it would look like this:
> 
> Tests: examples
> Depends: @
> 
> or even just:
> 
> Tests: examples
> 
> ?

yes, exactly.  See
https://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/tree/doc/README.package-tests.rst#n92

I uploaded this, just stage it for the next upload if you feel like to
do so (also, you already tagged this realease, so changing it now would
be unconvinient.)

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  http://mapreri.org                              : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: