Bug#797284: Info received (Bug#797284: Info received (Bug#797284: pytango ftbfs in unstable))

2015-09-13 Thread PICCA Frederic-Emmanuel
Here also a discussion about the problem on the gcc mailing list https://gcc.gnu.org/ml/gcc-help/2015-09/msg00057.html It seems that a abi_tag attribut should be added in tango to the problematic symbols in order to help gcc5 decide which ABI is expected. ifdef _GLIBCXX_USE_CXX11_ABI define TAN

Bug#797284: Info received (Bug#797284: pytango ftbfs in unstable)

2015-09-07 Thread PICCA Frederic-Emmanuel
I started a thread about this on debian-python mailing list. https://lists.debian.org/debian-python/2015/09/msg00028.html

Bug#797284: Info received (Bug#797284: pytango ftbfs in unstable)

2015-09-05 Thread PICCA Frederic-Emmanuel
:/usr/lib/i386-linux-gnu$ nm -D libtango.so.8.1.2 | grep ranges_type | c++filt 0045f258 D Tango::ranges_type2const::enu 00460dfc B Tango::ranges_type2const::str[abi:cxx11] 0045f280 D Tango::ranges_type2const::enu 00460fdc B Tango::ranges_type2const::str[abi:cxx11] 0045f27c D Tango::ranges_type2co

Bug#797284: pytango ftbfs in unstable

2015-09-05 Thread PICCA Frederic-Emmanuel
ok, so the missing symbols comes from attribute.o and wattribute.o

Bug#797284: pytango ftbfs in unstable

2015-09-04 Thread PICCA Frederic-Emmanuel
Ok, with the new tango,I get another symbols problem ImportError: /«PKGBUILDDIR»/build/lib.linux-i686-2.7/PyTango/_PyTango.so: undefined symbol: _ZN5Tango17ranges_type2constIsE3strE Tango::ranges_type2const::str so once again a problem with a string ???

Bug#797284: pytango ftbfs in unstable

2015-09-02 Thread PICCA Frederic-Emmanuel
ok, I just uploaded a tango package which fix the FTBFS with gcc5. I also made a libstdc++6 transition for tango. so now I think that after tango acceptation into unstable a simple binNMU should fix this issue.

Bug#797284: pytango ftbfs in unstable

2015-08-29 Thread PICCA Frederic-Emmanuel
> any libstdc++6 follow-up transition is waived. you can just upload to > unstable. ok, I will try to fix this issue next week. thanks

Bug#797284: pytango ftbfs in unstable

2015-08-29 Thread Matthias Klose
On 08/29/2015 08:51 PM, PICCA Frederic-Emmanuel wrote: > I am working on it with the upstream. > > once fixed,I will upload a tango with the v5 extension. then I will ask for a > transition > right ? any libstdc++6 follow-up transition is waived. you can just upload to unstable.

Bug#797284: pytango ftbfs in unstable

2015-08-29 Thread PICCA Frederic-Emmanuel
I am working on it with the upstream. once fixed,I will upload a tango with the v5 extension. then I will ask for a transition right ?

Bug#797284: pytango ftbfs in unstable

2015-08-29 Thread Matthias Klose
On 08/29/2015 06:45 PM, PICCA Frederic-Emmanuel wrote: > ok, when I unmangle the symbol, I get this > > c++filt _ZN5Tango11DeviceProxy14get_corba_nameB5cxx11Eb > > Tango::DeviceProxy::get_corba_name[abi:cxx11](bool) > > so it seems that this FTBFS is about a cxx11 ABi change. > > during this bu

Bug#797284: pytango ftbfs in unstable

2015-08-29 Thread PICCA Frederic-Emmanuel
: Bug#797284: pytango ftbfs in unstable Package: src:pytango Version: 8.1.5-1 Severity: serious Tags: sid stretch pytango ftbfs in unstable: creating /scratch/packages/tmp/pytango-8.1.5/build/sphinx/html Running Sphinx v1.3.1 Traceback (most recent call last): File "setup.py", li

Bug#797284: pytango ftbfs in unstable

2015-08-29 Thread Matthias Klose
Package: src:pytango Version: 8.1.5-1 Severity: serious Tags: sid stretch pytango ftbfs in unstable: creating /scratch/packages/tmp/pytango-8.1.5/build/sphinx/html Running Sphinx v1.3.1 Traceback (most recent call last): File "setup.py", line 528, in main() File "setup.py", line 525, in