Source: pybind11
Followup-For: Bug #890364
For testing proposes I ran the ratt tool in my system to check if
something would be broken with the update.
- 8< -
jrivero@nium tmp $ ratt pybind11_2.2.1-1_source.changes
2018/02/21 23:07
I depend on this as well. As a stop-gap measure, I've set of a PPA [1].
Cheers,
Nico
[1] https://launchpad.net/~nschloe/+archive/ubuntu/pybind11-backports/
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman
Hi Ghis,
Thank you!
What is the likelihood of migration before March 1st (date of ubuntu Bionic
Debian import freeze)?
Cheers,
Shane
On Wed, Feb 14, 2018 at 1:34 AM, Ghislain Vaillant
wrote:
> Hi Shane, thanks for reaching out,
>
> On Wed, 14 Feb 2018 00:48:14 + Shane Loretz rg> wrote:
Hi Shane, thanks for reaching out,
On Wed, 14 Feb 2018 00:48:14 + Shane Loretz wrote:
> Would the maintainer be willing to migrate 2.2.1 from experimental to
unstable? I'm a user of a distribution based on debian unstable. I have
been using pybind11 from pip previously. The package in experim
Package: pybind11-dev
Version: 2.2.1-1
Severity: wishlist
Dear Maintainer,
Would the maintainer be willing to migrate 2.2.1 from experimental to unstable?
I'm a user of a distribution based on debian unstable. I have been using
pybind11 from pip previously. The package in experimental appears t