Bug#933848: FTBFS if cmake is installed or if built twice in a row

2019-08-13 Thread Drew Parsons 
Source: pygalmesh
Followup-For: Bug #933848
Control: severity -1 important
Control: tags -1 + moreinfo,unreproducible


There is no cmake-related FTBFS for me.

Fixing the tags for moreinfo,unreproducible

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#933848: FTBFS if cmake is installed or if built twice in a row

2019-08-08 Thread Joachim Reichel 
It seems to be that the cmake-related FTBFS was not addressed?

Bug#933848: FTBFS if cmake is installed or if built twice in a row

2019-08-04 Thread Joachim Reichel 
Source: pygalmesh
Version: 0.3.6-1
Severity: serious

1) pygalmesh FTBFS if cmake is installed. Actually the build succeeds, but the
resulting binary package is almost empty.

With cmake installed:

 fakeroot debian/rules clean
dh clean --with python3 --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: dh_auto_clean --buildsystem=cmake
   dh_autoreconf_clean -O--buildsystem=pybuild
   dh_clean -O--buildsystem=pybuild
[...]
 fakeroot debian/rules binary
dh binary --with python3 --buildsystem=pybuild
   dh_testroot -O--buildsystem=pybuild
   dh_prep -O--buildsystem=pybuild
   dh_auto_install -O--buildsystem=pybuild
I: pybuild base:217: dh_auto_install --buildsystem=cmake 
--builddirectory="/mnt/debian/packages/pygalmesh/pygalmesh-0.3.6/.pybuild/cpython3_3.7_pygalmesh/build"
 
--destdir="/mnt/debian/packages/pygalmesh/pygalmesh-0.3.6/debian/python3-pygalmesh"
 -- 
   dh_installdocs -O--buildsystem=pybuild

Without cmake installed:

 fakeroot debian/rules clean
dh clean --with python3 --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py clean 
running clean
removing '/build/pygalmesh-0.3.6/.pybuild/cpython3_3.7_pygalmesh/build' (and 
everything under it)
'build/bdist.linux-amd64' does not exist -- can't clean it
'build/scripts-3.7' does not exist -- can't clean it
[...]
 fakeroot debian/rules binary
dh binary --with python3 --buildsystem=pybuild
   dh_testroot -O--buildsystem=pybuild
   dh_prep -O--buildsystem=pybuild
   dh_auto_install -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3 setup.py install --root 
/build/pygalmesh-0.3.6/debian/python3-pygalmesh 
running install
[... many more lines following ...]
   dh_installdocs -O--buildsystem=pybuild

I don't understand why the bare existence of cmake causes the build process to
behave differently. At least, the package should declare a Build-Conflicts: on
cmake.


2) pygalmesh FTBFS when built twice in a row. This can be fixed by putting

pygalmesh-from-inr.1
pygalmesh-volume-from-surface.1

in debian/clean.


Best regards,
  Joachim


-- System Information:
Debian Release: 10.0
  APT prefers stable-debug
  APT policy: (800, 'stable-debug'), (800, 'stable'), (700, 'testing-debug'), 
(700, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)