I've just triggered the builds for the dual-build package to be uploaded to the stable PPA for 18.04, 18.10, and 19.04. They should be available in about 2 hours.
Next up, getting the builds for 14.04 and 16.04 working.
In debian/control, it looks like you were the one who added the version requirement for this dependency. However it seems like the patch associated with this change is no longer being used. Can you say a bit about what motivated this change? It's blocking builds for Ubuntu 14.04.
Code: Select all
/<<BUILDDIR>>/freecad-0.18+dfsg1~201903280210~ubuntu16.04.1/src/Gui/DownloadManager.cpp:37:24: fatal error: QWebSettings: No such file or directory
Code: Select all
CMake Error at CMakeLists.txt:1 (cmake_minimum_required):
CMake 3.3 or higher is required. You are running version 2.8.12.2
Code: Select all
[ 66%] Building CXX object src/Mod/Fem/App/CMakeFiles/Fem.dir/FemConstraintInitialTemperature.cpp.o
cd "/<<BUILDDIR>>/freecad-0.18+dfsg1~201903280126~ubuntu18.10.1/debian/build-py3/src/Mod/Fem/App" && /usr/bin/c++ -DFC_USE_VTK -DFem_EXPORTS -DHAVE_CONFIG_H -DHAVE_LIMITS_H -DQT_CORE_LIB -DQT_NO_DEBUG -DQT_XML_LIB -D_OCC64 -I"/<<BUILDDIR>>/freecad-0.18+dfsg1~201903280126~ubuntu18.10.1/debian/build-py3" -I"/<<BUILDDIR>>/freecad-0.18+dfsg1~201903280126~ubuntu18.10.1/debian/build-py3/src" -I"/<<BUILDDIR>>/freecad-0.18+dfsg1~201903280126~ubuntu18.10.1/src" -I"/<<BUILDDIR>>/freecad-0.18+dfsg1~201903280126~ubuntu18.10.1/debian/build-py3/src/Mod/Fem/App" -I/usr/include/occt -I/usr/include/python3.6m -I"/<<BUILDDIR>>/freecad-0.18+dfsg1~201903280126~ubuntu18.10.1/src/3rdParty/salomesmesh/inc" -I/usr/include/vtk-7.1 -I/usr/include/x86_64-linux-gnu -I/usr/include/hdf5/openmpi -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/include/jsoncpp -I/usr/include/freetype2 -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem /usr/include/x86_64-linux-gnu/qt5/QtXml -Wall -Wextra -Wno-write-strings -Wall -DHAVE_SWIG=1 -fpermissive -g -O2 -fdebug-prefix-map=/<<BUILDDIR>>/freecad-0.18+dfsg1~201903280126~ubuntu18.10.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -D_OCC64 -Wno-overloaded-virtual -O2 -g -DNDEBUG -fPIC -I/usr/include/openmpi -I/usr/include/hdf5/openmpi -pthread -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -fPIC -std=gnu++11 -o CMakeFiles/Fem.dir/FemConstraintInitialTemperature.cpp.o -c "/<<BUILDDIR>>/freecad-0.18+dfsg1~201903280126~ubuntu18.10.1/src/Mod/Fem/App/FemConstraintInitialTemperature.cpp"
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libshiboken2-python2.7.x86_64-linux-gnu.so: undefined reference to `PyBuffer_FromMemory'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libshiboken2-python2.7.x86_64-linux-gnu.so: undefined reference to `PyString_FromStringAndSize'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libshiboken2-python2.7.x86_64-linux-gnu.so: undefined reference to `_Py_ZeroStruct'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libshiboken2-python2.7.x86_64-linux-gnu.so: undefined reference to `PyInstance_Type'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libshiboken2-python2.7.x86_64-linux-gnu.so: undefined reference to `PyString_Concat'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libshiboken2-python2.7.x86_64-linux-gnu.so: undefined reference to `PyUnicodeUCS4_Compare'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libshiboken2-python2.7.x86_64-linux-gnu.so: undefined reference to `PyUnicodeUCS4_Concat'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libshiboken2-python2.7.x86_64-linux-gnu.so: undefined reference to `PyString_FromString'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libshiboken2-python2.7.x86_64-linux-gnu.so: undefined reference to `PyCObject_AsVoidPtr'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libshiboken2-python2.7.x86_64-linux-gnu.so: undefined reference to `PyInt_Type'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libshiboken2-python2.7.x86_64-linux-gnu.so: undefined reference to `PyInt_FromLong'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libshiboken2-python2.7.x86_64-linux-gnu.so: undefined reference to `PyInt_AsLong'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libshiboken2-python2.7.x86_64-linux-gnu.so: undefined reference to `PyString_AsString'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libshiboken2-python2.7.x86_64-linux-gnu.so: undefined reference to `PyString_FromFormat'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libshiboken2-python2.7.x86_64-linux-gnu.so: undefined reference to `PyCObject_Type'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libpyside2-python2.7.x86_64-linux-gnu.so: undefined reference to `PyString_ConcatAndDel'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libshiboken2-python2.7.x86_64-linux-gnu.so: undefined reference to `PyUnicodeUCS4_AsUTF8String'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libshiboken2-python2.7.x86_64-linux-gnu.so: undefined reference to `PyClass_Type'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libshiboken2-python2.7.x86_64-linux-gnu.so: undefined reference to `PyUnicodeUCS4_FromString'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libpyside2-python2.7.x86_64-linux-gnu.so: undefined reference to `PyCObject_FromVoidPtr'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libshiboken2-python2.7.x86_64-linux-gnu.so: undefined reference to `Py_InitModule4_64'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libshiboken2-python2.7.x86_64-linux-gnu.so: undefined reference to `PyString_FromFormatV'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libshiboken2-python2.7.x86_64-linux-gnu.so: undefined reference to `PyBuffer_FromReadWriteMemory'
/usr/bin/ld: /usr/lib/x86_64-linux-gnu/libshiboken2-python2.7.x86_64-linux-gnu.so: undefined reference to `PyString_Type'
FYI the former freecad-0.17.13541 package was showing the document icon properly.kkremitzki wrote: ↑Thu Mar 28, 2019 3:37 amYep, I've seen the icon issue mentioned a few places but not sure if a fix was ever found or even if a bug report has been created.
Short answer: It should work with upstream just fine by removing the spec.kkremitzki wrote: ↑Thu Mar 28, 2019 1:20 amIn debian/control, it looks like you were the one who added the version requirement for this dependency. However it seems like the patch associated with this change is no longer being used. Can you say a bit about what motivated this change? It's blocking builds for Ubuntu 14.04.
Hi Kurt
Yeah, I was thinking the same, so I don't want to spend much effort on it, but I figured it would be worth trying at least.jmaustpc wrote: ↑Thu Mar 28, 2019 1:57 pmHi Kurt
Just a thought, why bother with 14.04? Its end of life in a few days, 30 April 2019 according to Google search.
This is just a link to the Ubuntu release cycle page
https://www.ubuntu.com/about/release-cycle
Just a thought.
Jim