Bug#890364: pybind11-dev: Request migration to unstable

[Jose Luis Rivero]

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:51 Loading changes file
"pybind11_2.2.1-1_source.changes"
2018/02/21 23:07:51  - 4 binary packages: pybind11-dev pybind11-doc
python-pybind11 python3-pybind11
2018/02/21 23:07:51  - corresponding .debs (will be injected when
building):
2018/02/21 23:07:51 Figuring out reverse build dependencies using
dose-ceve(1). This might take a while
2018/02/21 23:07:51 dose-ceve(1) failed (exec: "dose-ceve": executable
file not found in $PATH), falling back to interpreting Sources directly
2018/02/21 23:07:51 Loading sources index
"/var/lib/apt/lists/ftp.us.debian.org_debian_dists_sid_main_source_Sources"
2018/02/21 23:07:53 Setting -sbuild_dist=experimental (from .changes
file)
2018/02/21 23:07:53 Building ovito_2.9.0+dfsg1-5 (commandline: [sbuild
--arch-all --dist=experimental --nolog ovito_2.9.0+dfsg1-5])
2018/02/21 23:12:16 building ovito_2.9.0+dfsg1-5 failed: exit status 2
2018/02/21 23:12:16 Building psi4_1:1.1-5 (commandline: [sbuild
--arch-all --dist=experimental --nolog psi4_1:1.1-5])
2018/02/22 00:10:01 Building xtensor-python_0.12.4-1 (commandline:
[sbuild --arch-all --dist=experimental --nolog xtensor-python_0.12.4-1])
2018/02/22 00:12:22 Build results:
2018/02/22 00:12:22 PASSED: psi4_1:1.1-5
2018/02/22 00:12:22 PASSED: xtensor-python_0.12.4-1
2018/02/22 00:12:22 FAILED: ovito_2.9.0+dfsg1-5 (see
buildlogs/ovito_2.9.0+dfsg1-5)
- 8< -

Ovito failed and log displays this problem:

- 8< -
-- Found Libav: /usr/lib/x86_64-linux-gnu  
-- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.8") 
-- Found OpenGL: /usr/lib/x86_64-linux-gnu/libOpenGL.so   
-- Found PythonInterp: /usr/bin/python3 (found version "3.6.4") 
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.6m.so (found version 
"3.6.4+") 
CMake Error at 
/usr/share/cmake-3.10/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
  Could NOT find QScintilla (missing: QSCINTILLA_LIBRARY)
Call Stack (most recent call first):
  /usr/share/cmake-3.10/Modules/FindPackageHandleStandardArgs.cmake:378 
(_FPHSA_FAILURE_MESSAGE)
  cmake/FindQScintilla.cmake:13 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
  src/plugins/pyscript/gui/CMakeLists.txt:22 (FIND_PACKAGE)


-- Configuring incomplete, errors occurred!
- 8< -

Which I think it is unrelated to the upgrade of pybind and was reported in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885644

If there is any other test that we can help with, please let us know.
Thanks!

Bug#890364: pybind11-dev: Request migration to unstable

[Shane Loretz]

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:
> > 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 to be working flawlessly for my usecase and has some nice new
> features not in the version currently in unstable.
>
> There are a few rdpends I have got to test first to guarantee a smooth
> upgrade. But yes, I intend to migrate the new version to unstable soon.
>
> Cheers,
> Ghis
>

Bug#890364: pybind11-dev: Request migration to unstable

[Ghislain Vaillant]

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 experimental
appears to be working flawlessly for my usecase and has some nice new
features not in the version currently in unstable.

There are a few rdpends I have got to test first to guarantee a smooth
upgrade. But yes, I intend to migrate the new version to unstable soon.

Cheers,
Ghis

Bug#890364: pybind11-dev: Request migration to unstable

[Shane Loretz]

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 to be working 
flawlessly for my usecase and has some nice new features not in the version 
currently in unstable.


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.13.0-26-generic (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

pybind11-dev depends on no packages.

pybind11-dev recommends no packages.

Versions of packages pybind11-dev suggests:
pn  libeigen3-dev  
pn  pybind11-doc   

-- no debconf information