Bug#862507: marked as done (RFS: pybind11/2.1.0-1 [experimental])
Your message dated Mon, 15 May 2017 06:19:29 +0000 (UTC)
with message-id <413002550.1912201.1494829169035@mail.yahoo.com>
and subject line Re: Bug#862507: RFS: pybind11/2.1.0-1 [experimental]
has caused the Debian Bug report #862507,
regarding RFS: pybind11/2.1.0-1 [experimental]
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.)
--
862507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862507
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 the following package:
* Package name : pybind11
Version : 2.1.0
Upstream Author : Wenzel Jakob <wenzel.jakob@epfl.ch>
* URL : https://github.com/pybind/pybind11
* License : BSD
Section : libs
One can check out the package by visiting the following URL
(experimental branch):
https://anonscm.debian.org/git/debian-science/packages/pybind11.git
Changes since last upload:
* Switch from git-dpm to gbp
* New upstream version 2.1.0
* Refresh
the patch queue
* Fixup the Vcs-Browser URI
* Simplify the rules file
* Update the packaging of the documentation
- Use the Python 3
version of Sphinx and the RTD theme
- Add new dependency on the
breathe Sphinx extension
- Call the upstream Makefile for the
documentation
- Install from and clean the docs build directory
*
Add DEP-8 tests for clang
Note: I am aware there is a new upstream release available (2.1.1) but
the update is marginal (1 commit) and concerns Windows only.
Best regards,
Ghis
--- End Message ---
--- Begin Message ---
hello, doing it soon
G.
--- End Message ---
Reply to: