Bug#1083992: xmds2: (build-)depends on deprecated module python3-pkg-resources
Package: src:xmds2 Version: 3.1.0+dfsg2-8 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083977: ufl: (build-)depends on deprecated module python3-pkg-resources
Package: src:ufl Version: 1:2022.3.0-1 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083791: symfit: (build-)depends on deprecated module python3-pkg-resources
Package: src:symfit Version: 0.5.6-3 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083781: spyder: (build-)depends on deprecated module python3-pkg-resources
Package: src:spyder Version: 5.5.1+ds-2 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083756: ros-vcstool: (build-)depends on deprecated module python3-pkg-resources
Package: src:ros-vcstool Version: 0.3.0-2 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083761: sasview: (build-)depends on deprecated module python3-pkg-resources
Package: src:sasview Version: 5.0.6-4 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083755: ros-rosdistro: (build-)depends on deprecated module python3-pkg-resources
Package: src:ros-rosdistro Version: 0.9.1-2 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083753: ros-bloom: (build-)depends on deprecated module python3-pkg-resources
Package: src:ros-bloom Version: 0.12.0-2 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083754: ros-catkin-tools: (build-)depends on deprecated module python3-pkg-resources
Package: src:ros-catkin-tools Version: 0.9.4+ds-1 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083752: ros-catkin-pkg: (build-)depends on deprecated module python3-pkg-resources
Package: src:ros-catkin-pkg Version: 1.0.0-2 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083735: pyzo: (build-)depends on deprecated module python3-pkg-resources
Package: src:pyzo Version: 4.15.0-1 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083734: pyzoltan: (build-)depends on deprecated module python3-pkg-resources
Package: src:pyzoltan Version: 1.0.1-11 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083720: python-thinc: (build-)depends on deprecated module python3-pkg-resources
Package: src:python-thinc Version: 9.0.0-2 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083672: python-opcodes: (build-)depends on deprecated module python3-pkg-resources
Package: src:python-opcodes Version: 0.0~git20180424.6e2b0cd-3 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083586: pysph: (build-)depends on deprecated module python3-pkg-resources
Package: src:pysph Version: 1.0~b1-8 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083575: pyfr: (build-)depends on deprecated module python3-pkg-resources
Package: src:pyfr Version: 1.5.0-3 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083569: pybtex: (build-)depends on deprecated module python3-pkg-resources
Package: src:pybtex Version: 0.24.0-4 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083523: pandas: (build-)depends on deprecated module python3-pkg-resources
Package: src:pandas Version: 2.2.3+dfsg-1 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083504: neuron: (build-)depends on deprecated module python3-pkg-resources
Package: src:neuron Version: 8.2.2-7 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083506: nmodl: (build-)depends on deprecated module python3-pkg-resources
Package: src:nmodl Version: 0.6-2 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083505: nmodl: (build-)depends on deprecated module python3-pkg-resources
Package: src:nmodl Version: 0.6-2 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083444: joblib: (build-)depends on deprecated module python3-pkg-resources
Package: src:joblib Version: 1.3.2-3 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083391: fenics-dolfinx: (build-)depends on deprecated module python3-pkg-resources
Package: src:fenics-dolfinx Version: 1:0.8.0-11 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083386: fasttext: (build-)depends on deprecated module python3-pkg-resources
Package: src:fasttext Version: 0.9.2+ds-7 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083395: fiat: (build-)depends on deprecated module python3-pkg-resources
Package: src:fiat Version: 2019.2.0~git20210419.7d418fa-4 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083393: fenics-ufl: (build-)depends on deprecated module python3-pkg-resources
Package: src:fenics-ufl Version: 2024.1.0-1 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083390: fenics-ffcx: (build-)depends on deprecated module python3-pkg-resources
Package: src:fenics-ffcx Version: 1:0.8.0-1 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083389: feff85exafs: (build-)depends on deprecated module python3-pkg-resources
Package: src:feff85exafs Version: 0.2+dfsg-2 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083371: dolfin: (build-)depends on deprecated module python3-pkg-resources
Package: src:dolfin Version: 2019.2.0~legacy20240219.1c52e83-10 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083361: dijitso: (build-)depends on deprecated module python3-pkg-resources
Package: src:dijitso Version: 2019.2.0~git20190418.c92dcb0-2 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083348: cyarray: (build-)depends on deprecated module python3-pkg-resources
Package: src:cyarray Version: 1.1-8 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1083302: apertium-apy: (build-)depends on deprecated module python3-pkg-resources
Package: src:apertium-apy Version: 0.11.7-2.2 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1081057: xsimd builds with -march=native
Package: src:xsimd Version: 13.0.0-1 Severity: serious Tags: sid trixie xsimd builds with -march=native, at least on amd64 and arm64. This is a policy violation. and even if you build multiple variants, -march=native never is the correct configuration to build packages for, assuming that the user's machine have at least the same baseline as the build machine. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1080464: Fix feature check for clang-19+
Package: src:xtensor Version: 0.25.0-1 Severity: important Tags: sid trixie patch Fix feature check for clang-19+, taken from upstream. Patch at https://launchpadlibrarian.net/747418683/xtensor_0.25.0-1_0.25.0-1ubuntu1.diff.gz -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1079756: setuptools test command is removed
Package: src:symfit Version: 0.5.6-3 Severity: serious Tags: sid trixie setuptools test command is removed, the package at least uses this command in it's autopkg tests. setuptools v72.0.0: Deprecations and Removals - - The test command has been removed. Users relying on 'setup.py test' will need to migrate to another test runner or pin setuptools before this version. (#931) [...] 46s autopkgtest [04:08:35]: test command1: [--- 47s /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning: Unknown distribution option: 'tests_require' 47s warnings.warn(msg) 47s /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning: Unknown distribution option: 'test_suite' 47s warnings.warn(msg) 47s usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] 47sor: setup.py --help [cmd1 cmd2 ...] 47sor: setup.py --help-commands 47sor: setup.py cmd --help 47s 47s error: invalid command 'test' -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1077978: package assumes that the default JVM is the server VM
Package: src:vtk9 Version: 9.3.0+dfsg1-1 Severity: serious Tags: sid trixie The package assumes that the default JVM is the server VM. Please don't make such an assumption. Failing autopkg tests on all architectures where zero is the default JVM. [...] 228s -- Build files have been written to: /tmp/tmp.NbT6UegYOq/build 228s [ 50%] Building CXX object CMakeFiles/demo.dir/demo.cpp.o 229s make[2]: *** No rule to make target '/usr/lib/jvm/default-java/lib/server/libjvm.so', needed by 'demo'. Stop. 229s make[1]: *** [CMakeFiles/Makefile2:83: CMakeFiles/demo.dir/all] Error 2 -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1076130: slepc's autopkg tests fail on armhf and i386, triggered by gcc-13
Source: slepc Version: 3.20.2+dfsg1-2 Severity: serious Tags: sid trixie slepc's autopkg tests fail on armhf and i386, triggered by gcc-13, see https://ci.debian.net/packages/s/slepc/testing/armhf/48828710/ https://ci.debian.net/packages/s/slepc/testing/i386/48834824/ -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1075701: yorick-hdf5: ftbfs with GCC-14
Package: src:yorick-hdf5 Version: 0.8.0-8 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/yorick-hdf5_0.8.0-8_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] SCHROOT_CHROOT_NAME=sid-amd64-sbuild SCHROOT_COMMAND=env SCHROOT_GID=1001 SCHROOT_GROUP=user42 SCHROOT_SESSION_ID=sid-amd64-sbuild-2e7521ba-224a-4d59-a6a0-afdac4399d9a SCHROOT_UID=1001 SCHROOT_USER=user42 SHELL=/bin/sh USER=user42 dpkg-buildpackage - Command: dpkg-buildpackage --sanitize-env -us -uc -b -rfakeroot dpkg-buildpackage: info: source package yorick-hdf5 dpkg-buildpackage: info: source version 0.8.0-8 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Thibaut Paumard dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 fakeroot debian/rules clean dh clean dh: warning: Compatibility levels before 10 are deprecated (level 9 in use) debian/rules override_dh_auto_clean make[1]: Entering directory '/<>' [ ! -f /usr/lib/yorick/Make.cfg ] || /usr/bin/make Y_MAKEDIR=/usr/lib/yorick Y_EXE=/usr/bin/yorick clean make[2]: Entering directory '/<>' rm -f *~ '#'* core* *.core a.out yinit.* ywrap.* *.dep so_locations Make.tmp rm -f Y_HOME.txt rm -f hdf5.o yorick libhdf5.a hdf5.so hdf5.def rm -rf binaries make[2]: Leaving directory '/<>' make[1]: Leaving directory '/<>' dh_clean dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in use) debian/rules build dh build dh: warning: Compatibility levels before 10 are deprecated (level 9 in use) dh_update_autotools_config dh_auto_configure dh_auto_configure: warning: Compatibility levels before 10 are deprecated (level 9 in use) debian/rules override_dh_auto_build make[1]: Entering directory '/<>' /usr/bin/make COPT_DEFAULT="" \ Y_CFLAGS="-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/hdf5/serial" \ Y_LDFLAGS="-Wl,-z,relro -Wl,-z,now -Wl,-L/usr/lib/x86_64-linux-gnu/hdf5/serial" make[2]: Entering directory '/<>' cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/hdf5/serial -D H5_USE_16_API -fPIC -DPLUG_IN -I. -I/usr/lib/yorick/include -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/hdf5/serial -c -o hdf5.o hdf5.c hdf5.c: In function ‘Y__H5Gopen’: hdf5.c:253:6: error: type of ‘nArgs’ defaults to ‘int’ [-Wimplicit-int] 253 | void Y__H5Gopen(nArgs) | ^~ hdf5.c: In function ‘Y__H5Gclose’: hdf5.c:263:6: error: type of ‘nArgs’ defaults to ‘int’ [-Wimplicit-int] 263 | void Y__H5Gclose(nArgs) | ^~~ hdf5.c: In function ‘Y__H5Gcreate’: hdf5.c:273:6: error: type of ‘nArgs’ defaults to ‘int’ [-Wimplicit-int] 273 | void Y__H5Gcreate(nArgs) | ^~~~ hdf5.c: In function ‘Y__H5Gget_num_objs’: hdf5.c:285:6: error: type of ‘nArgs’ defaults to ‘int’ [-Wimplicit-int] 285 | void Y__H5Gget_num_objs(nArgs) | ^~ make[2]: *** [: hdf5.o] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:15: override_dh_auto_build] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:12: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1075702: yorick-gy: ftbfs with GCC-14
Package: src:yorick-gy
Version: 0.0.5-2
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/yorick-gy_0.0.5-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
71 | fprintf(stderr, "single linked list", 0);
| ^~~~
gy_object.c: In function ‘gy_Object_extract’:
gy_object.c:159:24: error: initialization of ‘GList *’ {aka ‘struct _GList *’}
from incompatible pointer type ‘GObject *’ {aka ‘struct _GObject *’}
[-Wincompatible-pointer-types]
159 | GList* lst = o->object;
|^
gy_object.c:165:18: warning: suggest parentheses around assignment used as
truth value [-Wparentheses]
165 | while (lst=lst->next) ++sz;
| ^~~
gy_object.c:192:27: error: assignment to ‘GObject *’ {aka ‘struct _GObject *’}
from incompatible pointer type ‘GList *’ {aka ‘struct _GList *’}
[-Wincompatible-pointer-types]
192 | out -> object = ((GList*) o->object) -> next;
| ^
gy_object.c:194:27: error: assignment to ‘GObject *’ {aka ‘struct _GObject *’}
from incompatible pointer type ‘GList *’ {aka ‘struct _GList *’}
[-Wincompatible-pointer-types]
194 | out -> object = ((GList*) o->object) -> prev;
| ^
gy_object.c:327:23: warning: duplicate ‘const’ declaration specifier
[-Wduplicate-decl-specifier]
327 | static const char const * sigprefix = "signal_";
| ^
gy_object.c: In function ‘gy_Object_eval’:
gy_object.c:395:18: error: initialization of ‘GList *’ {aka ‘struct _GList *’}
from incompatible pointer type ‘GObject *’ {aka ‘struct _GObject *’}
[-Wincompatible-pointer-types]
395 | GList* lst = o->object;
| ^
gy_object.c:440:9: warning: ‘GParameter’ is deprecated
[-Wdeprecated-declarations]
440 | GParameter *parameters=NULL;
| ^~
In file included from /usr/include/glib-2.0/gobject/gobject.h:28,
from /usr/include/glib-2.0/gobject/gbinding.h:31,
from /usr/include/glib-2.0/glib-object.h:24,
from /usr/include/gobject-introspection-1.0/girepository.h:26,
from gy.h:20,
from gy_object.c:20:
/usr/include/glib-2.0/gobject/gparam.h:278:8: note: declared here
278 | struct _GParameter /* auxiliary structure for _setv() variants */
|^~~
gy_object.c:442:11: warning: ‘GParameter’ is deprecated
[-Wdeprecated-declarations]
442 | parameters=g_new0(GParameter, n_parameters);
| ^~
/usr/include/glib-2.0/gobject/gparam.h:278:8: note: declared here
278 | struct _GParameter /* auxiliary structure for _setv() variants */
|^~~
gy_object.c:442:11: warning: ‘GParameter’ is deprecated
[-Wdeprecated-declarations]
442 | parameters=g_new0(GParameter, n_parameters);
| ^~
/usr/include/glib-2.0/gobject/gparam.h:278:8: note: declared here
278 | struct _GParameter /* auxiliary structure for _setv() variants */
|^~~
gy_object.c:455:73: warning: passing argument 2 of
‘gy_base_info_find_property_info’ discards ‘const’ qualifier from pointer
target type [-Wdiscarded-qualifiers]
455 | cur = gy_base_info_find_property_info(o->info,
parameters[p].name);
|
~^
gy.h:114:56: note: expected ‘char *’ but argument is of type ‘const gchar *’
{aka ‘const char *’}
114 | char * name);
| ~~~^~~~
gy_object.c:469:11: warning: ‘g_object_newv’ is deprecated: Use
'g_object_new_with_properties' instead [-Wdeprecated-declarations]
469 |
Bug#1075704: yorick-yeti: ftbfs with GCC-14
Package: src:yorick-yeti Version: 6.4.0-1.1 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/yorick-yeti_6.4.0-1.1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] 710 | uint16 orientation; | ^~ yeti_tiff.c:711:3: warning: ‘uint16’ is deprecated [-Wdeprecated-declarations] 711 | uint16 sampleFormat; | ^~ yeti_tiff.c:712:3: warning: ‘uint16’ is deprecated [-Wdeprecated-declarations] 712 | uint16 samplesPerPixel; | ^~ yeti_tiff.c:713:3: warning: ‘uint16’ is deprecated [-Wdeprecated-declarations] 713 | uint16 bitsPerSample; | ^~ yeti_tiff.c:714:3: warning: ‘uint16’ is deprecated [-Wdeprecated-declarations] 714 | uint16 planarConfig; | ^~ yeti_tiff.c:715:3: warning: ‘uint16’ is deprecated [-Wdeprecated-declarations] 715 | uint16 photometric; | ^~ yeti_tiff.c:716:3: warning: ‘uint32’ is deprecated [-Wdeprecated-declarations] 716 | uint32 width, height, depth; | ^~ yeti_tiff.c:716:3: warning: ‘uint32’ is deprecated [-Wdeprecated-declarations] yeti_tiff.c:716:3: warning: ‘uint32’ is deprecated [-Wdeprecated-declarations] yeti_tiff.c:717:3: warning: ‘uint32’ is deprecated [-Wdeprecated-declarations] 717 | uint32 rowsPerStrip; | ^~ yeti_tiff.c:718:3: warning: ‘uint32’ is deprecated [-Wdeprecated-declarations] 718 | uint32 stripSize; | ^~ yeti_tiff.c:719:3: warning: ‘uint32’ is deprecated [-Wdeprecated-declarations] 719 | uint32 x, y, y1, y0, rowLength, rowSize; | ^~ yeti_tiff.c:719:3: warning: ‘uint32’ is deprecated [-Wdeprecated-declarations] yeti_tiff.c:719:3: warning: ‘uint32’ is deprecated [-Wdeprecated-declarations] yeti_tiff.c:719:3: warning: ‘uint32’ is deprecated [-Wdeprecated-declarations] yeti_tiff.c:719:3: warning: ‘uint32’ is deprecated [-Wdeprecated-declarations] yeti_tiff.c:719:3: warning: ‘uint32’ is deprecated [-Wdeprecated-declarations] yeti_tiff.c:837:9: warning: ‘uint32’ is deprecated [-Wdeprecated-declarations] 837 | uint32 n = (rowLength/8)*8; | ^~ yeti_tiff.c:858:9: warning: ‘uint32’ is deprecated [-Wdeprecated-declarations] 858 | uint32 n = (rowLength/4)*4; | ^~ yeti_tiff.c:875:9: warning: ‘uint32’ is deprecated [-Wdeprecated-declarations] 875 | uint32 n = (rowLength/2)*2; | ^~ yeti_tiff.c:895:2: warning: #warning "take orientation into account..." [-Wcpp] 895 | #warning "take orientation into account..." | ^~~ yeti_tiff.c:948:5: warning: ‘uint32’ is deprecated [-Wdeprecated-declarations] 948 | uint32 i, number = width*height*samplesPerPixel; | ^~ yeti_tiff.c:948:5: warning: ‘uint32’ is deprecated [-Wdeprecated-declarations] yeti_tiff.c:959:7: warning: ‘uint16’ is deprecated [-Wdeprecated-declarations] 959 | case 16: REVERSE(uint16,0x) break; | ^~~~ yeti_tiff.c:959:7: warning: ‘uint16’ is deprecated [-Wdeprecated-declarations] yeti_tiff.c:959:7: warning: ‘uint16’ is deprecated [-Wdeprecated-declarations] yeti_tiff.c:960:7: warning: ‘uint32’ is deprecated [-Wdeprecated-declarations] 960 | case 32: REVERSE(uint32,0x) break; | ^~~~ yeti_tiff.c:960:7: warning: ‘uint32’ is deprecated [-Wdeprecated-declarations] yeti_tiff.c:960:7: warning: ‘uint32’ is deprecated [-Wdeprecated-declarations] make[3]: *** [: yeti_tiff.o] Error 1 make[3]: Leaving directory '/<>/tiff' make[2]: *** [Makefile:43: all] Error 2 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:20: override_dh_auto_build] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:9: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https:/
Bug#1075703: yorick-ml4: ftbfs with GCC-14
Package: src:yorick-ml4
Version: 0.6.0-4
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/yorick-ml4_0.6.0-4_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
debian/rules override_dh_auto_clean
make[1]: Entering directory '/<>'
/usr/bin/make Y_MAKEDIR=/usr/lib/yorick Y_EXE=/usr/bin/yorick clean
make[2]: Entering directory '/<>'
rm -f *~ '#'* core* *.core a.out yinit.* ywrap.* *.dep so_locations Make.tmp
rm -f Y_HOME.txt
rm -f ml4.o yorick libml4.a ml4.so ml4.def
rm -rf binaries
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
dh_clean
debian/rules build
dh build
dh_update_autotools_config
dh_autoreconf
dh_auto_configure
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
/usr/bin/make COPT_DEFAULT="" \
Y_CFLAGS="-g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
-Wdate-time -D_FORTIFY_SOURCE=2" \
Y_LDFLAGS="-Wl,-z,relro"
make[2]: Entering directory '/<>'
cc -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
-Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DPLUG_IN -I. -I/usr/lib/yorick/include
-Wdate-time -D_FORTIFY_SOURCE=2 -c -o ml4.o ml4.c
ml4.c: In function ‘Y_ml4read’:
ml4.c:379:17: error: initialization of ‘int *’ from incompatible pointer type
‘long int *’ [-Wincompatible-pointer-types]
379 | int *data = a->value.l;
| ^
ml4.c:415:33: warning: format ‘%d’ expects argument of type ‘int’, but argument
2 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]
415 | if (DEBUG) printf("strlen: %d\n",strlen((void *)a->value.q[0]));
|~^~
| ||
| int size_t {aka long unsigned int}
|%ld
ml4.c:312:3: warning: ignoring return value of ‘fread’ declared with attribute
‘warn_unused_result’ [-Wunused-result]
312 | fread(&mrows,sizeof(int),1,fs);
| ^~
ml4.c:313:3: warning: ignoring return value of ‘fread’ declared with attribute
‘warn_unused_result’ [-Wunused-result]
313 | fread(&mcols,sizeof(int),1,fs);
| ^~
ml4.c:314:3: warning: ignoring return value of ‘fread’ declared with attribute
‘warn_unused_result’ [-Wunused-result]
314 | fread(&imagf,sizeof(int),1,fs);
| ^~
ml4.c:316:3: warning: ignoring return value of ‘fread’ declared with attribute
‘warn_unused_result’ [-Wunused-result]
316 | fread(&namelen,sizeof(int),1,fs);
| ^~~~
ml4.c:337:3: warning: ignoring return value of ‘fread’ declared with attribute
‘warn_unused_result’ [-Wunused-result]
337 | fread(tempvarname,(unsigned int)namelen,1,fs);
| ^
ml4.c: In function ‘matskip’:
ml4.c:456:3: warning: ignoring return value of ‘fread’ declared with attribute
‘warn_unused_result’ [-Wunused-result]
456 | fread(&mrows,sizeof(long),1,fs);
| ^~~
ml4.c:457:3: warning: ignoring return value of ‘fread’ declared with attribute
‘warn_unused_result’ [-Wunused-result]
457 | fread(&mcols,sizeof(long),1,fs);
| ^~~
ml4.c:458:3: warning: ignoring return value of ‘fread’ declared with attribute
‘warn_unused_result’ [-Wunused-result]
458 | fread(&imagf,sizeof(long),1,fs);
| ^~~
ml4.c:460:3: warning: ignoring return value of ‘fread’ declared with attribute
‘warn_unused_result’ [-Wunused-result]
460 | fread(&namelen,size
Bug#1075700: yorick: ftbfs with GCC-14
Package: src:yorick Version: 2.2.04+dfsg1-12 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/yorick_2.2.04+dfsg1-12_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -I../play -Wdate-time -D_FORTIFY_SOURCE=2 -c -o cfftf.o cfftf.c cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -I../play -Wdate-time -D_FORTIFY_SOURCE=2 -c -o cffti.o cffti.c cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -I../play -Wdate-time -D_FORTIFY_SOURCE=2 -c -o roll2.o roll2.c touch libyor make[2]: Leaving directory '/<>/fft' make[2]: Entering directory '/<>/yorick' make[3]: Entering directory '/<>/play' make[4]: Entering directory '/<>/play/hacks' make[4]: Nothing to be done for 'all'. make[4]: Leaving directory '/<>/play/hacks' make[4]: Entering directory '/<>/play/unix' make[4]: Nothing to be done for 'all'. make[4]: Leaving directory '/<>/play/unix' make[4]: Entering directory '/<>/play/x11' make[4]: Nothing to be done for 'all'. make[4]: Leaving directory '/<>/play/x11' make[4]: Entering directory '/<>/play/any' make[4]: Nothing to be done for 'all'. make[4]: Leaving directory '/<>/play/any' cd any; make numfmt make[4]: Entering directory '/<>/play/any' cc -g -o numfmt numfmt.c make[4]: Leaving directory '/<>/play/any' make[3]: Leaving directory '/<>/play' ../play/any/numfmt prmtyp.h cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I. -I../play -I../gist -Wdate-time -D_FORTIFY_SOURCE=2 -c -o opsv.o opsv.c cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I. -I../play -I../gist -o task.o -c task.c cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I. -I../play -I../gist -o yorick.o -c yorick.c cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I. -I../play -I../gist -Wdate-time -D_FORTIFY_SOURCE=2 -c -o yinput.o yinput.c cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I. -I../play -I../gist -Wdate-time -D_FORTIFY_SOURCE=2 -c -o parse.o parse.c cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I. -I../play -I../gist -Wdate-time -D_FORTIFY_SOURCE=2 -c -o ydata.o ydata.c cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I. -I../play -I../gist -Wdate-time -D_FORTIFY_SOURCE=2 -c -o yapi.o yapi.c cc -Wdate-time -D_FO
Bug#1075623: virtuoso-opensource: ftbfs with GCC-14
Package: src:virtuoso-opensource
Version: 7.2.12+dfsg-0.2
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/virtuoso-opensource_7.2.12+dfsg-0.2_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
1373 | last_len_chars = virt_mbsnrtowcs (NULL, &ptr,
ses->dks_out_fill, 0, &mb);
| ^~~~
| |
| unsigned char **
../../libsrc/util/utf8funs.h:52:68: note: expected ‘const unsigned char **’ but
argument is of type ‘unsigned char **’
52 | extern size_t virt_mbsnrtowcs (wchar_t *dst, const unsigned char **src,
size_t nmc, size_t len, virt_mbstate_t *ps);
| ~~^~~
Dksesstr.c:1374:30: warning: comparison of integer expressions of different
signedness: ‘long int’ and ‘long unsigned int’ [-Wsign-compare]
1374 | if (last_len_chars == (size_t) - 1)
| ^~
Dksesstr.c: In function ‘read_wides_from_utf8_file’:
Dksesstr.c:1461:58: error: passing argument 2 of ‘virt_mbsnrtowcs’ from
incompatible pointer type [-Wincompatible-pointer-types]
1461 | converted = virt_mbsnrtowcs ((wchar_t *) dest, &data_ptr,
readed, nchars, &mb);
| ^
| |
| unsigned char
**
../../libsrc/util/utf8funs.h:52:68: note: expected ‘const unsigned char **’ but
argument is of type ‘unsigned char **’
52 | extern size_t virt_mbsnrtowcs (wchar_t *dst, const unsigned char **src,
size_t nmc, size_t len, virt_mbstate_t *ps);
| ~~^~~
Dksesstr.c: In function ‘strses_get_wide_part’:
Dksesstr.c:1505:37: error: passing argument 2 of ‘virt_mbsnrtowcs’ from
incompatible pointer type [-Wincompatible-pointer-types]
1505 | if (virt_mbsnrtowcs (buf, &data_ptr,
| ^
| |
| unsigned char **
../../libsrc/util/utf8funs.h:52:68: note: expected ‘const unsigned char **’ but
argument is of type ‘unsigned char **’
52 | extern size_t virt_mbsnrtowcs (wchar_t *dst, const unsigned char **src,
size_t nmc, size_t len, virt_mbstate_t *ps);
| ~~^~~
Dksesstr.c:1549:18: warning: comparison of integer expressions of different
signedness: ‘int’ and ‘size_t’ {aka ‘long unsigned int’} [-Wsign-compare]
1549 | if (-1 == readed)
| ^~
Dksesstr.c:1578:50: error: passing argument 2 of ‘virt_mbsnrtowcs’ from
incompatible pointer type [-Wincompatible-pointer-types]
1578 | if ((converted = virt_mbsnrtowcs (buf, &data_ptr_start,
| ^~~
| |
| unsigned char **
../../libsrc/util/utf8funs.h:52:68: note: expected ‘const unsigned char **’ but
argument is of type ‘unsigned char **’
52 | extern size_t virt_mbsnrtowcs (wchar_t *dst, const unsigned char **src,
size_t nmc, size_t len, virt_mbstate_t *ps);
| ~~^~~
Dksesstr.c: In function ‘strses_readtable_initialize’:
Dksesstr.c:1793:37: warning: cast between incompatible function types from
‘void (*)(char *, dk_session_t *)’ {aka ‘void (*)(char *, struct dk_session_s
*)’} to ‘int (*)(const void *, dk_session_t *)’ {aka ‘int (*)(const void *,
struct dk_session_s *)’} [-Wcast-function
Bug#1075614: v-sim: ftbfs with GCC-14
Package: src:v-sim Version: 3.7.2-9 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/v-sim_3.7.2-9_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] 350 | item = gtk_tool_button_new_from_stock(GTK_STOCK_REFRESH); | ^~~~ pythongi.c:357:3: warning: ‘gtk_misc_set_alignment’ is deprecated [-Wdeprecated-declarations] 357 | gtk_misc_set_alignment(GTK_MISC(wd), 0., 0.5); | ^~ /usr/include/gtk-3.0/gtk/deprecated/gtkmisc.h:72:9: note: declared here 72 | voidgtk_misc_set_alignment (GtkMisc *misc, | ^~ pythongi.c:364:3: warning: ‘gtk_misc_set_padding’ is deprecated [-Wdeprecated-declarations] 364 | gtk_misc_set_padding(GTK_MISC(wd), 5, 0); | ^~~~ /usr/include/gtk-3.0/gtk/deprecated/gtkmisc.h:80:9: note: declared here 80 | voidgtk_misc_set_padding (GtkMisc *misc, | ^~~~ pythongi.c:370:3: warning: ‘gtk_button_new_from_stock’ is deprecated: Use 'gtk_button_new_with_label' instead [-Wdeprecated-declarations] 370 | pyExecute = gtk_button_new_from_stock(GTK_STOCK_EXECUTE); | ^ In file included from /usr/include/gtk-3.0/gtk/gtk.h:54: /usr/include/gtk-3.0/gtk/gtkbutton.h:103:16: note: declared here 103 | GtkWidget* gtk_button_new_from_stock(const gchar*stock_id); |^ pythongi.c:370:3: warning: ‘GtkStock’ is deprecated [-Wdeprecated-declarations] 370 | pyExecute = gtk_button_new_from_stock(GTK_STOCK_EXECUTE); | ^ pythongi.c:403:3: warning: ‘gtk_tool_button_new_from_stock’ is deprecated: Use 'gtk_tool_button_new' instead [-Wdeprecated-declarations] 403 | item = gtk_tool_button_new_from_stock(GTK_STOCK_CLEAR); | ^~~~ /usr/include/gtk-3.0/gtk/gtktoolbutton.h:84:14: note: declared here 84 | GtkToolItem *gtk_tool_button_new_from_stock (const gchar *stock_id); | ^~ pythongi.c:403:3: warning: ‘GtkStock’ is deprecated [-Wdeprecated-declarations] 403 | item = gtk_tool_button_new_from_stock(GTK_STOCK_CLEAR); | ^~~~ pythongi.c:408:3: warning: ‘gtk_tool_button_new_from_stock’ is deprecated: Use 'gtk_tool_button_new' instead [-Wdeprecated-declarations] 408 | item = gtk_tool_button_new_from_stock(GTK_STOCK_CANCEL); | ^~~~ /usr/include/gtk-3.0/gtk/gtktoolbutton.h:84:14: note: declared here 84 | GtkToolItem *gtk_tool_button_new_from_stock (const gchar *stock_id); | ^~ pythongi.c:408:3: warning: ‘GtkStock’ is deprecated [-Wdeprecated-declarations] 408 | item = gtk_tool_button_new_from_stock(GTK_STOCK_CANCEL); | ^~~~ pythongi.c:413:3: warning: ‘gtk_tool_button_new_from_stock’ is deprecated: Use 'gtk_tool_button_new' instead [-Wdeprecated-declarations] 413 | item = gtk_tool_button_new_from_stock(GTK_STOCK_FIND); | ^~~~ /usr/include/gtk-3.0/gtk/gtktoolbutton.h:84:14: note: declared here 84 | GtkToolItem *gtk_tool_button_new_from_stock (const gchar *stock_id); | ^~ pythongi.c:413:3: warning: ‘GtkStock’ is deprecated [-Wdeprecated-declarations] 413 | item = gtk_tool_button_new_from_stock(GTK_STOCK_FIND); | ^~~~ pythongi.c: In function ‘onInitScriptAdded’: pythongi.c:524:40: warning: ‘GtkStock’ is deprecated [-Wdeprecated-declarations] 524 |GTK_STOCK_CANCEL, GTK_RESPONSE_CANCEL, |^~~~ pythongi.c:525:40: warning: ‘GtkStock’ is deprecated [-Wdeprecated-declarations] 525 |GTK_STOCK_OPEN, GTK_RESPONSE_ACCEPT, |^~ make[5]: *** [Makefile:619: pythongi.lo] Error 1 make[5]: Leaving di
Bug#1075580: togl: ftbfs with GCC-14
Package: src:togl Version: 2.0-2 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/togl_2.0-2_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] checking for gcc option to enable C11 features... none needed checking how to run the C preprocessor... gcc -E checking whether make sets $(MAKE)... yes checking for ranlib... ranlib checking for stdio.h... yes checking for stdlib.h... yes checking for string.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for strings.h... yes checking for sys/stat.h... yes checking for sys/types.h... yes checking for unistd.h... yes checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking if the compiler understands -pipe... yes checking whether byte ordering is bigendian... no checking for sin... no checking for main in -lieee... no checking for main in -linet... no checking for net/errno.h... no checking for connect... yes checking for gethostbyname... yes checking dirent.h... yes checking for errno.h... yes checking for float.h... yes checking for values.h... yes checking for limits.h... yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking for sys/wait.h... yes checking for dlfcn.h... yes checking for sys/param.h... yes checking whether to link with stubs library... stubs checking for autostereo directory... checking for autostereod... no checking for Tcl private include files... Using srcdir found in tclConfig.sh: /usr/include/tcl8.6/tcl-private checking for Tk private include files... Using srcdir found in tkConfig.sh: /usr/include/tcl8.6/tk-private checking for X... libraries , headers checking for X11 header files... checking for pthread_mutex_init in -lpthread... yes checking for building with threads... yes (default) checking how to build libraries... shared checking if 64bit support is requested... no checking if 64bit Sparc VIS support is requested... no checking if compiler supports visibility "hidden"... yes checking if rpath support is requested... yes checking system version... Linux-6.1.0-21-cloud-amd64 checking for dlopen in -ldl... yes checking for ar... ar checking for required early compiler flags... _LARGEFILE64_SOURCE checking for 64-bit integer type... using long checking for build with symbols... no checking for tclsh... /usr/bin/tclsh8.6 checking for wish... /usr/bin/wish8.6 configure: creating ./config.status config.status: creating Makefile config.status: creating pkgIndex.tcl config.status: creating togl_ws.h configure: WARNING: unrecognized options: --disable-maintainer-mode, --disable-dependency-tracking, --disable-silent-rules touch debian/stamp-autotools /usr/bin/make -C . make[1]: Entering directory '/<>' gcc -DPACKAGE_NAME=\"Togl\" -DPACKAGE_TARNAME=\"togl\" -DPACKAGE_VERSION=\"2.0\" -DPACKAGE_STRING=\"Togl\ 2.0\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_PARAM_H=1 -DUSE_THREAD_ALLOC=1 -D_REENTRANT=1 -D_THREAD_SAFE=1 -DTCL_THREADS=1 -DMODULE_SCOPE=extern\ __attribute__\(\(__visibility__\(\"hidden\"\)\)\) -D_LARGEFILE64_SOURCE=1 -DTCL_WIDE_INT_IS_LONG=1 -DUSE_TCL_STUBS=1 -DUSE_TK_STUBS=1 -DAUTOSTEREOD=\"\" -I"/usr/include/tcl8.6/tcl-private/generic" -I"/usr/include/tcl8.6/tcl-private/unix" -I"/usr/include/tcl8.6/tk-private/generic" -I"/usr/include/tcl8.6/tk-private/unix" -I"/usr/include/tcl8.6/tk-private/generic/ttk" -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -pipe -O2 -fomit-frame-pointer -Wall -Wno-implicit-int -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -c `echo t
Bug#1075572: tilem: ftbfs with GCC-14
Package: src:tilem
Version: 2.0-5
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/tilem_2.0-5_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
from /usr/include/glib-2.0/glib-object.h:24,
from /usr/include/glib-2.0/gio/gioenums.h:30,
from /usr/include/glib-2.0/gio/giotypes.h:30,
from /usr/include/glib-2.0/gio/gio.h:28,
from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
from /usr/include/gtk-2.0/gdk/gdk.h:32,
from /usr/include/gtk-2.0/gtk/gtk.h:32:
/usr/include/glib-2.0/gobject/gtype.h:725:1: note: declared here
725 | {
| ^
./memview.c: In function ‘get_column_index’:
./memview.c:41:13: warning: variable ‘i’ set but not used
[-Wunused-but-set-variable]
41 | int i;
| ^
In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
from /usr/include/gtk-2.0/gtk/gtk.h:126:
/usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTimeVal’ is deprecated:
Use 'GDateTime' instead [-Wdeprecated-declarations]
73 | GTimeVal last_popdown;
| ^~~~
In file included from /usr/include/glib-2.0/glib/galloca.h:34,
from /usr/include/glib-2.0/glib.h:32,
from /usr/include/glib-2.0/gobject/gbinding.h:30:
/usr/include/glib-2.0/glib/gtypes.h:580:8: note: declared here
580 | struct _GTimeVal
|^
In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
from /usr/include/gtk-2.0/gtk/gtk.h:33,
from ./preferences.c:27:
/usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: ‘GTypeDebugFlags’ is
deprecated [-Wdeprecated-declarations]
236 | voidgtk_type_init (GTypeDebugFlagsdebug_flags);
| ^~~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:26,
from /usr/include/glib-2.0/gobject/gbinding.h:31,
from /usr/include/glib-2.0/glib-object.h:24,
from /usr/include/glib-2.0/gio/gioenums.h:30,
from /usr/include/glib-2.0/gio/giotypes.h:30,
from /usr/include/glib-2.0/gio/gio.h:28,
from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
from /usr/include/gtk-2.0/gdk/gdk.h:32,
from /usr/include/gtk-2.0/gtk/gtk.h:32:
/usr/include/glib-2.0/gobject/gtype.h:725:1: note: declared here
725 | {
| ^
In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
from /usr/include/gtk-2.0/gtk/gtk.h:126:
/usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTimeVal’ is deprecated:
Use 'GDateTime' instead [-Wdeprecated-declarations]
73 | GTimeVal last_popdown;
| ^~~~
In file included from /usr/include/glib-2.0/glib/galloca.h:34,
from /usr/include/glib-2.0/glib.h:32,
from /usr/include/glib-2.0/gobject/gbinding.h:30:
/usr/include/glib-2.0/glib/gtypes.h:580:8: note: declared here
580 | struct _GTimeVal
|^
make[2]: Leaving directory '/<>/gui'
make[1]: *** [Makefile:41: all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: error: make -j8 retu
Bug#1075565: texmaker: ftbfs with GCC-14
Package: src:texmaker Version: 5.1.3+dfsg-1 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/texmaker_5.1.3+dfsg-1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] gcc -c -pipe -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fno-exceptions -w -fvisibility=hidden -D_REENTRANT -fPIC -DTEXMAKERVERSION=5.1.3 -DOPJ_STATIC -DPNG_PREFIX -DPNG_USE_READ_MACROS -DV8_DEPRECATION_WARNINGS -DNOMINMAX -DFT2_BUILD_LIBRARY -DPREFIX=\"/usr\" -D_FX_CPU_=_FX_X64_ -DAUTHORIZE_LINUX_QSTYLES -DDEBIAN_SPELLDIR -DQT_NO_EXCEPTIONS -DQT_NO_DYNAMIC_CAST -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_QML_LIB -DQT_NETWORK_LIB -DQT_CONCURRENT_LIB -DQT_CORE_LIB -I. -Ipdfium -Ipdfium -Ipdfium/third_party -Ipdfium/third_party/freetype/include -Ipdfium/third_party/freetype/include/freetype -Ipdfium/fpdfsdk -Ipdfium/third_party/zlib_v128 -I/include/ -I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets -I/usr/include/x86_64-linux-gnu/qt5/QtGui -I/usr/include/x86_64-linux-gnu/qt5/QtXml -I/usr/include/x86_64-linux-gnu/qt5/QtQml -I/usr/include/x86_64-linux-gnu/qt5/QtNetwork -I/usr/include/x86_64-linux-gnu/qt5/QtConcurrent -I/usr/include/x86_64-linux-gnu/qt5/QtCore/5.15.13 -I/usr/include/x86_64-linux-gnu/qt5/QtCore/5.15.13/QtCore -I/usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc -I.ui -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o .obj/cmssamp.o pdfium/third_party/lcms/src/cmssamp.c gcc -c -pipe -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fno-exceptions -w -fvisibility=hidden -D_REENTRANT -fPIC -DTEXMAKERVERSION=5.1.3 -DOPJ_STATIC -DPNG_PREFIX -DPNG_USE_READ_MACROS -DV8_DEPRECATION_WARNINGS -DNOMINMAX -DFT2_BUILD_LIBRARY -DPREFIX=\"/usr\" -D_FX_CPU_=_FX_X64_ -DAUTHORIZE_LINUX_QSTYLES -DDEBIAN_SPELLDIR -DQT_NO_EXCEPTIONS -DQT_NO_DYNAMIC_CAST -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_QML_LIB -DQT_NETWORK_LIB -DQT_CONCURRENT_LIB -DQT_CORE_LIB -I. -Ipdfium -Ipdfium -Ipdfium/third_party -Ipdfium/third_party/freetype/include -Ipdfium/third_party/freetype/include/freetype -Ipdfium/fpdfsdk -Ipdfium/third_party/zlib_v128 -I/include/ -I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets -I/usr/include/x86_64-linux-gnu/qt5/QtGui -I/usr/include/x86_64-linux-gnu/qt5/QtXml -I/usr/include/x86_64-linux-gnu/qt5/QtQml -I/usr/include/x86_64-linux-gnu/qt5/QtNetwork -I/usr/include/x86_64-linux-gnu/qt5/QtConcurrent -I/usr/include/x86_64-linux-gnu/qt5/QtCore/5.15.13 -I/usr/include/x86_64-linux-gnu/qt5/QtCore/5.15.13/QtCore -I/usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc -I.ui -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o .obj/cmssm.o pdfium/third_party/lcms/src/cmssm.c gcc -c -pipe -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fno-exceptions -w -fvisibility=hidden -D_REENTRANT -fPIC -DTEXMAKERVERSION=5.1.3 -DOPJ_STATIC -DPNG_PREFIX -DPNG_USE_READ_MACROS -DV8_DEPRECATION_WARNINGS -DNOMINMAX -DFT2_BUILD_LIBRARY -DPREFIX=\"/usr\" -D_FX_CPU_=_FX_X64_ -DAUTHORIZE_LINUX_QSTYLES -DDEBIAN_SPELLDIR -DQT_NO_EXCEPTIONS -DQT_NO_DYNAMIC_CAST -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_QML_LIB -DQT_NETWORK_LIB -DQT_CONCURRENT_LIB -DQT_CORE_LIB -I. -Ipdfium -Ipdfium -Ipdfium/th
Bug#1075547: sundials: ftbfs with GCC-14
Package: src:sundials
Version: 6.4.1+dfsg1-3
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/sundials_6.4.1+dfsg1-3_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
make -f examples/sunmatrix/band/CMakeFiles/test_sunmatrix_band.dir/build.make
examples/sunmatrix/band/CMakeFiles/test_sunmatrix_band.dir/build
make[3]: Entering directory '/<>/debian/build'
[ 13%] Building Fortran object
src/sundials/fmod/CMakeFiles/sundials_fgeneric_mod_obj_shared.dir/fsundials_nonlinearsolver_mod.f90.o
cd /<>/debian/build/src/sundials/fmod && /usr/bin/gfortran
-Dsundials_generic_EXPORTS
-I/usr/lib/petscdir/petsc3.20/x86_64-linux-gnu-real/include
-I/<>/include -I/<>/debian/build/include
-I/<>/src/sundials -I/<>/debian/build/fortran_SHARED
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -fcf-protection -J../../../fortran_SHARED -fPIC -cpp
-c /<>/src/sundials/fmod/fsundials_nonlinearsolver_mod.f90 -o
CMakeFiles/sundials_fgeneric_mod_obj_shared.dir/fsundials_nonlinearsolver_mod.f90.o
[ 13%] Building C object
examples/sunmatrix/band/CMakeFiles/test_sunmatrix_band.dir/test_sunmatrix_band.c.o
make[3]: Leaving directory '/<>/debian/build'
cd /<>/debian/build/examples/sunmatrix/band && /usr/bin/cc
-I/usr/lib/petscdir/petsc3.20/x86_64-linux-gnu-real/include
-I/<>/examples/sunmatrix/band/.
-I/<>/examples/sunmatrix/band/.. -I/<>/include
-I/<>/debian/build/include -I/<>/src/sundials
-fcommon -std=gnu99 -MD -MT
examples/sunmatrix/band/CMakeFiles/test_sunmatrix_band.dir/test_sunmatrix_band.c.o
-MF CMakeFiles/test_sunmatrix_band.dir/test_sunmatrix_band.c.o.d -o
CMakeFiles/test_sunmatrix_band.dir/test_sunmatrix_band.c.o -c
/<>/examples/sunmatrix/band/test_sunmatrix_band.c
/<>/src/sunnonlinsol/petscsnes/sunnonlinsol_petscsnes.c: In
function ‘SUNNonlinSolGetNumIters_PetscSNES’:
/<>/src/sunnonlinsol/petscsnes/sunnonlinsol_petscsnes.c:326:54:
error: passing argument 2 of ‘SNESGetIterationNumber’ from incompatible pointer
type [-Wincompatible-pointer-types]
326 | ierr = SNESGetIterationNumber(SUNNLS_SNESOBJ(NLS), &niters);
| ^~~
| |
| sunindextype *
{aka long int *}
In file included from
/<>/src/sunnonlinsol/petscsnes/sunnonlinsol_petscsnes.c:22:
/usr/lib/petscdir/petsc3.20/x86_64-linux-gnu-real/include/petscsnes.h:152:58:
note: expected ‘PetscInt *’ {aka ‘int *’} but argument is of type ‘sunindextype
*’ {aka ‘long int *’}
152 | PETSC_EXTERN PetscErrorCode SNESGetIterationNumber(SNES, PetscInt *);
| ^~
/<>/src/sunnonlinsol/petscsnes/sunnonlinsol_petscsnes.c: In
function ‘SUNNonlinSolGetNumIters_PetscSNES’:
/<>/src/sunnonlinsol/petscsnes/sunnonlinsol_petscsnes.c:326:54:
error: passing argument 2 of ‘SNESGetIterationNumber’ from incompatible pointer
type [-Wincompatible-pointer-types]
326 | ierr = SNESGetIterationNumber(SUNNLS_SNESOBJ(NLS), &niters);
| ^~~
| |
| sunindextype *
{aka long int *}
In file included from
/<>/src/sunnonlinsol/petscsnes/sunnonlinsol_petscsnes.c:22:
/usr/lib/petscdir/petsc3.20/x86_64-linux-gnu-real/include/petscsnes.h:152:58:
note: expected ‘PetscInt *’ {aka ‘int *’} but argument is of type ‘sunindextype
*’ {aka ‘long int *’}
152 | PETSC_EXTERN PetscErrorCode SNESGetIterationNumber(SNES, PetscInt *);
| ^~
make[3]: ***
[src/sunnonlinsol/petscsnes/CMakeFiles/sundials_sunnonlinsolpetscsnes_obj_static.dir/build.make:79:
src/sunnonlinsol/petscsnes
Bug#1075534: spooles: ftbfs with GCC-14
Package: src:spooles Version: 2.2-14.1 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/spooles_2.2-14.1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] |^~~~ 48 |(count)*sizeof(type), __LINE__, __FILE__) ; \ | || |long unsigned int basics.c:27:1: note: in expansion of macro ‘ALLOCATE’ 27 | ALLOCATE(etree, struct _ETree, 1) ; | ^~~~ ../../Utilities/MM.h:47:40: note: format string is defined here 47 |"\n ALLOCATE error : bytes %d, line %d, file %s", \ | ~^ || |int | %ld c99 -c -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>/ETree/src=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection compress.c -o ETree_compress.o -I/usr/include/x86_64-linux-gnu/mpi c99 -c -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>/ETree/src=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection init.c -o ETree_init.o -I/usr/include/x86_64-linux-gnu/mpi c99 -c -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>/ETree/src=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection initFromSubtree.c -o ETree_initFromSubtree.o -I/usr/include/x86_64-linux-gnu/mpi c99 -c -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>/ETree/src=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection instance.c -o ETree_instance.o -I/usr/include/x86_64-linux-gnu/mpi c99 -c -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>/ETree/src=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection justify.c -o ETree_justify.o -I/usr/include/x86_64-linux-gnu/mpi c99 -c -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>/ETree/src=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection maps.c -o ETree_maps.o -I/usr/include/x86_64-linux-gnu/mpi c99 -c -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>/ETree/src=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection metrics.c -o ETree_metrics.o -I/usr/include/x86_64-linux-gnu/mpi c99 -c -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>/ETree/src=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection ms.c -o ETree_ms.o -I/usr/include/x86_64-linux-gnu/mpi c99 -c -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>/ETree/src=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection permute.c -o ETree_permute.o -I/usr/include/x86_64-linux-gnu/mpi c99 -c -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>/ETree/src=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection semi.c -o ETree_semi.o -I/usr/include/x86_64-linux-gnu/mpi c99 -c -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>/ETree/src=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection storage.c -o ETree_storage.o -I/usr/include/x86_64-linux-gnu/mpi c99 -c -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>/ETree/src=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection transform.c -o ETree_transform.o -I/usr/include/x86_64-linux-gnu/mpi transf
Bug#1075495: scotch: ftbfs with GCC-14
Package: src:scotch Version: 7.0.4-2 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/scotch_7.0.4-2_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] make[4]: 'libscotchmetisv5.a' is up to date. make[4]: Leaving directory '/<>/src/libscotchmetis' cp -a metis.h metisf.h ../../include cp -a libscotchmetisv3.a libscotchmetisv5.a libscotchmetisv3*.so libscotchmetisv5*.so ../../lib make[3]: Leaving directory '/<>/src/libscotchmetis' (cd libscotch ; make VERSION=7 RELEASE=0 PATCHLEVEL=4 ptscotch && make ptinstall) make[3]: Entering directory '/<>/src/libscotch' make\ CC="mpicc" \ CCD="mpicc" \ scotch.h \ scotchf.h \ libscotch.a \ libscotcherr.a \ libscotcherrexit.a make[4]: Entering directory '/<>/src/libscotch' make[4]: 'scotch.h' is up to date. make[4]: 'scotchf.h' is up to date. make[4]: 'libscotch.a' is up to date. make[4]: 'libscotcherr.a' is up to date. make[4]: 'libscotcherrexit.a' is up to date. make[4]: Leaving directory '/<>/src/libscotch' make\ CC="mpicc" \ CFLAGS="-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>/src/libscotch=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O3 -fPIC -I. -Drestrict=__restrict -DCOMMON_FILE_COMPRESS_GZ -DCOMMON_FILE_COMPRESS_BZ2 -DCOMMON_FILE_COMPRESS_LZMA -DSCOTCH_PTHREAD -DCOMMON_PTHREAD -DSCOTCH_PTHREAD_NUMBER=2 -DCOMMON_PTHREAD_FILE -DSCOTCH_PTHREAD_MPI -DCOMMON_RANDOM_FIXED_SEED -DSCOTCH_RENAME -DSCOTCH_RENAME_PARSER -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -DCOMMON_PTHREAD_AFFINITY_LINUX -DLONG -DSCOTCH_PTSCOTCH" \ CCDFLAGS="-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>/src/libscotch=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O3 -fPIC -I. -Drestrict=__restrict -DCOMMON_FILE_COMPRESS_GZ -DCOMMON_FILE_COMPRESS_BZ2 -DCOMMON_FILE_COMPRESS_LZMA -DSCOTCH_PTHREAD -DCOMMON_PTHREAD -DSCOTCH_PTHREAD_NUMBER=2 -DCOMMON_PTHREAD_FILE -DSCOTCH_PTHREAD_MPI -DCOMMON_RANDOM_FIXED_SEED -DSCOTCH_RENAME -DSCOTCH_RENAME_PARSER -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -DCOMMON_PTHREAD_AFFINITY_LINUX -DLONG -DSCOTCH_PTSCOTCH" \ ptscotch.h \ ptscotchf.h \ libptscotch.a \ libptscotcherr.a \ libptscotcherrexit.a make[4]: Entering directory '/<>/src/libscotch' mpicc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>/src/libscotch=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O3 -fPIC -I. -Drestrict=__restrict -DCOMMON_FILE_COMPRESS_GZ -DCOMMON_FILE_COMPRESS_BZ2 -DCOMMON_FILE_COMPRESS_LZMA -DSCOTCH_PTHREAD -DCOMMON_PTHREAD -DSCOTCH_PTHREAD_NUMBER=2 -D
Bug#1075494: scilab: ftbfs with GCC-14
Package: src:scilab Version: 2024.1.0+dfsg-1 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/scilab_2024.1.0+dfsg-1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] make[4]: Entering directory '/<>/scilab/modules/localization' make all-am make[5]: Entering directory '/<>/scilab/modules/localization' /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../modules/core/includes -I/usr/lib/jvm/java-17-openjdk-amd64/include -I/usr/lib/jvm/java-17-openjdk-amd64/include/linux -I./includes/ -I./src/c/ -I../../modules/ast/includes/ast/ -I../../modules/ast/includes/exps/ -I../../modules/ast/includes/operations/ -I../../modules/ast/includes/parse/ -I../../modules/ast/includes/symbol/ -I../../modules/ast/includes/system_env/ -I../../modules/ast/includes/types/ -I../../modules/functions_manager/includes/ -I../../modules/core/includes/ -I../../modules/string/includes/ -I../../modules/fileio/includes/ -I../../modules/api_scilab/includes/ -I../../modules/output_stream/includes/ -I../../modules/dynamic_link/includes/ -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -g -O2 -m64 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -MT src/c/libscilocalization_algo_la-InitializeLocalization.lo -MD -MP -MF src/c/.deps/libscilocalization_algo_la-InitializeLocalization.Tpo -c -o src/c/libscilocalization_algo_la-InitializeLocalization.lo `test -f 'src/c/InitializeLocalization.c' || echo './'`src/c/InitializeLocalization.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../modules/core/includes -I/usr/lib/jvm/java-17-openjdk-amd64/include -I/usr/lib/jvm/java-17-openjdk-amd64/include/linux -I./includes/ -I./src/c/ -I../../modules/ast/includes/ast/ -I../../modules/ast/includes/exps/ -I../../modules/ast/includes/operations/ -I../../modules/ast/includes/parse/ -I../../modules/ast/includes/symbol/ -I../../modules/ast/includes/system_env/ -I../../modules/ast/includes/types/ -I../../modules/functions_manager/includes/ -I../../modules/core/includes/ -I../../modules/string/includes/ -I../../modules/fileio/includes/ -I../../modules/api_scilab/includes/ -I../../modules/output_stream/includes/ -I../../modules/dynamic_link/includes/ -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -g -O2 -m64 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -MT src/c/libscilocalization_algo_la-InitializeLocalization.lo -MD -MP -MF src/c/.deps/libscilocalization_algo_la-InitializeLocalization.Tpo -c src/c/InitializeLocalization.c -fPIC -DPIC -o src/c/.libs/libscilocalization_algo_la-InitializeLocalization.o mv -f src/c/.deps/libscilocalization_algo_la-InitializeLocalization.Tpo src/c/.deps/libscilocalization_algo_la-InitializeLocalization.Plo /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../modules/core/includes -I/usr/lib/jvm/java-17-openjdk-amd64/include -I/usr/lib/jvm/java-17-openjdk-amd64/include/linux -I./includes/ -I./src/c/ -I../../modules/ast/includes/ast/ -I../../modules/ast/includes/exps/ -I../../modules/ast/includes/operations/ -I../../modules/ast/includes/parse/ -I../../modules/ast/includes/symbol/ -I../../modules/ast/includes/system_env/ -I../../modules/ast/includes/types/ -I../../modules/functions_manager/includes/ -I../../modules/core/includes/ -I../../modules/string/includes/ -I../../modules/fileio/includes/ -I../../modules/api_scilab/includes/ -I../../modules/output_stream/includes/ -I../../modules/dynamic_link/includes/ -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -g -O2 -m64 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=form
Bug#1075488: scalapack: ftbfs with GCC-14
Package: src:scalapack Version: 2.2.1-3.1 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/scalapack_2.2.1-3.1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] /<>/BLACS/SRC/Bdef.h:297:9: error: implicit declaration of function ‘BI_dvmcopy’; did you mean ‘BI_cvmcopy’? [-Wimplicit-function-declaration] 297 | BI_dvmcopy(2*(m), (n), (double *) (A), 2*(lda), (double *) (buff)) | ^~ /<>/BLACS/SRC/zgsum2d_.c:171:13: note: in expansion of macro ‘BI_zvmcopy’ 171 | BI_zvmcopy(Mpval(m), Mpval(n), A, tlda, bp2->Buff); | ^~ /<>/BLACS/SRC/zgsum2d_.c:83:39: warning: variable ‘ierr’ set but not used [-Wunused-but-set-variable] 83 |Int N, length, dest, tlda, trdest, ierr; | ^~~~ make[4]: *** [CMakeFiles/scalapack.dir/build.make:695: CMakeFiles/scalapack.dir/BLACS/SRC/zgsum2d_.c.o] Error 1 In file included from /<>/BLACS/SRC/cgsum2d_.c:1: /<>/BLACS/SRC/cgsum2d_.c: In function ‘cgsum2d_’: /<>/BLACS/SRC/Bdef.h:291:9: error: implicit declaration of function ‘BI_smvcopy’; did you mean ‘BI_cmvcopy’? [-Wimplicit-function-declaration] 291 | BI_smvcopy(2*(m), (n), (float *) (A), 2*(lda), (float *) (buff)) | ^~ /<>/BLACS/SRC/cgsum2d_.c:154:7: note: in expansion of macro ‘BI_cmvcopy’ 154 | BI_cmvcopy(Mpval(m), Mpval(n), A, tlda, bp->Buff); | ^~ /<>/BLACS/SRC/Bdef.h:293:9: error: implicit declaration of function ‘BI_svmcopy’; did you mean ‘BI_cvmcopy’? [-Wimplicit-function-declaration] 293 | BI_svmcopy(2*(m), (n), (float *) (A), 2*(lda), (float *) (buff)) | ^~ /<>/BLACS/SRC/cgsum2d_.c:169:13: note: in expansion of macro ‘BI_cvmcopy’ 169 | BI_cvmcopy(Mpval(m), Mpval(n), A, tlda, bp2->Buff); | ^~ /<>/BLACS/SRC/cgsum2d_.c:83:39: warning: variable ‘ierr’ set but not used [-Wunused-but-set-variable] 83 |Int N, length, dest, tlda, trdest, ierr; | ^~~~ make[4]: *** [CMakeFiles/scalapack.dir/build.make:681: CMakeFiles/scalapack.dir/BLACS/SRC/cgsum2d_.c.o] Error 1 /<>/BLACS/SRC/igamx2d_.c: In function ‘igamx2d_’: /<>/BLACS/SRC/igamx2d_.c:201:7: error: implicit declaration of function ‘BI_imvcopy’; did you mean ‘BI_cmvcopy’? [-Wimplicit-function-declaration] 201 | BI_imvcopy(Mpval(m), Mpval(n), A, tlda, bp->Buff); | ^~ | BI_cmvcopy /<>/BLACS/SRC/igamx2d_.c:280:13: error: implicit declaration of function ‘BI_ivmcopy’; did you mean ‘BI_cvmcopy’? [-Wimplicit-function-declaration] 280 | BI_ivmcopy(Mpval(m), Mpval(n), A, tlda, bp2->Buff); | ^~ | BI_cvmcopy /<>/BLACS/SRC/igamx2d_.c:282:16: error: implicit declaration of function ‘BI_TransDist’ [-Wimplicit-function-declaration] 282 |BI_TransDist(ctxt, tscope, Mpval(m), Mpval(n), rA, cA, tldia, |^~~~ /<>/BLACS/SRC/igamx2d_.c:108:59: warning: variable ‘ierr’ set but not used [-Wunused-but-set-variable] 108 |Int i, j, N, dest, idist, length, tlda, tldia, trdest, ierr; | ^~~~ /<>/BLACS/SRC/sgamx2d_.c: In function ‘sgamx2d_’: /<>/BLACS/SRC/sgamx2d_.c:204:7: error: implicit declaration of function ‘BI_smvcopy’; did you mean ‘BI_cmvcopy’? [-Wimplicit-function-declaration] 204 | BI_smvcopy(Mpval(m), Mpval(n), A, tlda, bp->Buff); | ^~ | BI_cmvcopy /<>/BLACS/SRC/sgamx2d_.c:283:13: error: implicit declaration of function ‘BI_svmcopy’; did you mean ‘BI_cvmcopy’? [-Wimplicit-function-declaration] 283 | BI_svmcopy(Mpval(m), Mpval(n), A, tlda, bp2->Buff); | ^~ | BI_cvmcopy make
Bug#1075449: robot-testing-framework: ftbfs with GCC-14
Package: src:robot-testing-framework Version: 2.0.1+ds1-3 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/robot-testing-framework_2.0.1+ds1-3_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/robottestingframework/dll/DllPluginLoader.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/robottestingframework/dll/Plugin.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/robottestingframework/dll/SharedLibrary.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/robottestingframework/dll/SharedLibraryClass.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/robottestingframework/dll/SharedLibraryClassApi.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/robottestingframework/dll/SharedLibraryClassFactory.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/robottestingframework/dll/SharedLibraryFactory.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/robottestingframework/dll/Vocab.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/robottestingframework/dll/robottestingframework_dll_config.h -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/librobottestingframework-lua.so.2 -- Set non-toolchain portion of runtime path of "/<>/debian/tmp/usr/lib/x86_64-linux-gnu/librobottestingframework-lua.so.2" to "" -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/librobottestingframework-lua.so -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/robottestingframework/lua/LuaPluginLoader.h -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/librobottestingframework-ruby.so.2 -- Set non-toolchain portion of runtime path of "/<>/debian/tmp/usr/lib/x86_64-linux-gnu/librobottestingframework-ruby.so.2" to "" -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/librobottestingframework-ruby.so -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/robottestingframework/ruby/RubyPluginLoader.h -- Installing: /<>/debian/tmp/usr/bin/robottestingframework-testrunner -- Set non-toolchain portion of runtime path of "/<>/debian/tmp/usr/bin/robottestingframework-testrunner" to "" make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu' dh_install debian/rules override_dh_installdocs-indep make[1]: Entering directory '/<>' dh_installdocs -plibrobottestingframework-doc --doc-main-package=robot-testing-framework -Xjquery.js dh_installdocs --remaining-packages dh_installdocs: warning: No packages to build. Possible architecture mismatch: amd64, want: all any dh_doxygen -plibrobottestingframework-doc make[1]: Leaving directory '/<>' dh_installdocs -Nlibrobottestingframework-doc dh_installchangelogs debian/rules override_dh_installexamples-indep make[1]: Entering directory '/<>' dh_installexamples -plibrobottestingframework-doc --doc-main-package=robot-testing-framework dh_installexamples --remaining-packages dh_installexamples: warning: No packages to build. Possible architecture mismatch: amd64, want: all any make[1]: Leaving directory '/<>' dh_installexamples -Nlibrobottestingframework-doc dh_perl dh_link dh_strip_nondeterminism dh_compress dh_fixperms dh_missing dh_dwz -a dh_strip -a dh_makeshlibs -a dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/librobottestingframework2/DEBIAN/symbols doesn't match completely debian/librobottestingframework2.symbols --- debian/librobottestingframework2.symbols (librobottestingframework2_2.0.1+ds1-3_amd64) +++ dpkg-gensymbolsUYmJ3x 2024-07-02 01:14:52.827298430 + @@ -236,10 +236,11 @@ _ZNSt6thread11_State_implINS_8_InvokerISt5tupleIJPFvPvEPN21robottestingframework23WebProgressL
Bug#1075445: reprozip: ftbfs with GCC-14
Package: src:reprozip Version: 1.3-2 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/reprozip_1.3-2_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] copying reprozip/__init__.py -> /<>/.pybuild/cpython3_3.11_reprozip/build/reprozip creating /<>/.pybuild/cpython3_3.11_reprozip/build/reprozip/tracer copying reprozip/tracer/trace.py -> /<>/.pybuild/cpython3_3.11_reprozip/build/reprozip/tracer copying reprozip/tracer/linux_pkgs.py -> /<>/.pybuild/cpython3_3.11_reprozip/build/reprozip/tracer copying reprozip/tracer/__init__.py -> /<>/.pybuild/cpython3_3.11_reprozip/build/reprozip/tracer running build_ext building 'reprozip._pytracer' extension creating build creating build/temp.linux-x86_64-cpython-311 creating build/temp.linux-x86_64-cpython-311/native x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -Werror=implicit-function-declaration -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.11 -c native/database.c -o build/temp.linux-x86_64-cpython-311/native/database.o x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -Werror=implicit-function-declaration -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.11 -c native/ptrace_utils.c -o build/temp.linux-x86_64-cpython-311/native/ptrace_utils.o x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -Werror=implicit-function-declaration -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.11 -c native/pylog.c -o build/temp.linux-x86_64-cpython-311/native/pylog.o x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -Werror=implicit-function-declaration -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.11 -c native/pytracer.c -o build/temp.linux-x86_64-cpython-311/native/pytracer.o x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -Werror=implicit-function-declaration -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.11 -c native/syscalls.c -o build/temp.linux-x86_64-cpython-311/native/syscalls.o native/syscalls.c: In function ‘handle_socket’: native/syscalls.c:864:22: error: passing argument 2 of ‘strncpy’ from incompatible pointer type [-Wincompatible-pointer-types] 864 | strncpy(buf, &address_->sun_path, 108); | ^~~ | | | char (*)[108] In file included from /usr/include/features.h:502, from /usr/include/errno.h:25, from native/syscalls.
Bug#1075380: petsc: ftbfs with GCC-14
Package: src:petsc
Version: 3.20.6+dfsg1-1
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/petsc_3.20.6+dfsg1-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
144 | int SCOTCH_dgraphBuild (SCOTCH_Dgraph * const,
const SCOTCH_Num, const SCOTCH_Num, const SCOTCH_Num, SCOTCH_Num * const,
SCOTCH_Num * const, SCOTCH_Num * const, SCOTCH_Num * const, const SCOTCH_Num,
const SCOTCH_Num, SCOTCH_Num * const, SCOTCH_Num * const, SCOTCH_Num * const);
|
^~
/<>/src/mat/partition/impls/scotch/scotch.c:388:72: error: passing
argument 4 of ‘SCOTCH_graphBuild’ from incompatible pointer type
[-Wincompatible-pointer-types]
388 | PetscCallExternal(SCOTCH_graphBuild, &grafdat, 0, vertlocnbr,
adj->i, adj->i + 1, veloloctab, NULL, edgelocnbr, adj->j, edloloctab);
|
~~~^~~
||
|
PetscInt * {aka long int *}
/<>/include/petscerror.h:1770:44: note: in definition of macro
‘PetscCallExternal’
1770 | int ierr_petsc_call_external_ = func(__VA_ARGS__); \
|^~~
In file included from /usr/include/scotch/ptscotch.h:73:
/usr/include/scotch/scotch.h:258:108: note: expected ‘const SCOTCH_Num * const’
{aka ‘const int * const’} but argument is of type ‘PetscInt *’ {aka ‘long int
*’}
258 | int SCOTCH_graphBuild (SCOTCH_Graph * const,
const SCOTCH_Num, const SCOTCH_Num, const SCOTCH_Num * const, const SCOTCH_Num
* const, const SCOTCH_Num * const, const SCOTCH_Num * const, const SCOTCH_Num,
const SCOTCH_Num * const, const SCOTCH_Num * const);
|
^~~~
/<>/src/mat/partition/impls/scotch/scotch.c:388:84: error: passing
argument 5 of ‘SCOTCH_graphBuild’ from incompatible pointer type
[-Wincompatible-pointer-types]
388 | PetscCallExternal(SCOTCH_graphBuild, &grafdat, 0, vertlocnbr,
adj->i, adj->i + 1, veloloctab, NULL, edgelocnbr, adj->j, edloloctab);
|
~~~^~~
|
|
|
PetscInt * {aka long int *}
/<>/include/petscerror.h:1770:44: note: in definition of macro
‘PetscCallExternal’
1770 | int ierr_petsc_call_external_ = func(__VA_ARGS__); \
|^~~
/usr/include/scotch/scotch.h:258:134: note: expected ‘const SCOTCH_Num * const’
{aka ‘const int * const’} but argument is of type ‘PetscInt *’ {aka ‘long int
*’}
258 | int SCOTCH_graphBuild (SCOTCH_Graph * const,
const SCOTCH_Num, const SCOTCH_Num, const SCOTCH_Num * const, const SCOTCH_Num
* const, const SCOTCH_Num * const, const SCOTCH_Num * const, const SCOTCH_Num,
const SCOTCH_Num * const, const SCOTCH_Num * const);
|
^~~~
/<>/src/mat/partition/impls/scotch/scotch.c:388:122: error:
passing argument 9 of ‘SCOTCH_graphBuild’ from incompatible pointer type
[-Wincompatible-pointer-types]
388 | PetscCallExternal(SCOTCH_gr
Bug#1075350: opm-simulators: ftbfs with GCC-14
Package: src:opm-simulators Version: 2024.04+ds-2 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/opm-simulators_2024.04+ds-2_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f CMakeFiles/flow_libsolvent_foam.dir/build.make CMakeFiles/flow_libsolvent_foam.dir/build make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' [ 30%] Building CXX object CMakeFiles/flow_libsolvent_foam.dir/flow/flow_solvent_foam.cpp.o /usr/bin/c++ -DFMT_SHARED -DHAVE_CONFIG_H=1 -I/<>/obj-x86_64-linux-gnu -I/<> -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -I/usr/include/parmetis -I/usr/include/superlu -I/usr/include/suitesparse -I/usr/include/cjson -I/usr/include/trilinos -I/usr/include/scotch -I/usr/include/hdf5/openmpi -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -fopenmp -pthread -std=c++17 -MD -MT CMakeFiles/flow_libsolvent_foam.dir/flow/flow_solvent_foam.cpp.o -MF CMakeFiles/flow_libsolvent_foam.dir/flow/flow_solvent_foam.cpp.o.d -o CMakeFiles/flow_libsolvent_foam.dir/flow/flow_solvent_foam.cpp.o -c /<>/flow/flow_solvent_foam.cpp [ 31%] Building CXX object CMakeFiles/opmsimulators.dir/opm/simulators/linalg/PropertyTree.cpp.o /usr/bin/c++ -DBOOST_DATE_TIME_DYN_LINK -DBOOST_DATE_TIME_NO_LIB -DBOOST_SYSTEM_DYN_LINK -DBOOST_SYSTEM_NO_LIB -DENABLE_MPI=1 -DFMT_SHARED -DHAVE_CONFIG_H=1 -DModelP -Dopmsimulators_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<> -I/usr/include/parmetis -I/usr/include/superlu -I/usr/include/suitesparse -I/usr/include/cjson -I/usr/include/trilinos -I/usr/include/scotch -I/usr/include/hdf5/openmpi -isystem /usr/lib/x86_64-linux-gnu/openmpi/include -isystem /usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -fopenmp -pthread -std=c++17 -fPIC -fopenmp -MD -MT CMakeFiles/opmsimulators.dir/opm/simulators/linalg/PropertyTree.cpp.o -MF CMakeFiles/opmsimulators.dir/opm/simulators/linalg/PropertyTree.cpp.o.d -o CMakeFiles/opmsimulators.dir/opm/simulators/linalg/PropertyTree.cpp.o -c /<>/opm/simulators/linalg/PropertyTree.cpp [ 31%] Building CXX object CMakeFiles/opmsimulators.dir/opm/simulators/linalg/setupPropertyTree.cpp.o /usr/bin/c++ -DBOOST_DATE_TIME_DYN_LINK -DBOOST_DATE_TIME_NO_LIB -DBOOST_SYSTEM_DYN_LINK -DBOOST_SYSTEM_NO_LIB -DENABLE_MPI=1 -DFMT_SHARED -DHAVE_CONFIG_H=1 -DModelP -Dopmsimulators_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<> -I/usr/include/parmetis -I/usr/include/superlu -I/usr/include/suitesparse -I/usr/include/cjson -I/usr/include/trilinos -I/usr/include/scotch -I/usr/include/hdf5/openmpi -isystem /usr/lib/x86_64-linux-gnu/openmpi/include -isystem /usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -fopenmp -pthread -std=c++17 -fPIC -fopenmp -MD -MT CMakeFiles/opmsimulators.dir/opm/simulators/linalg/setupPropertyTree.cpp.o -MF CMakeFiles/opmsimulators.dir/opm/simulators/linalg/setupPropertyTree.cpp.o.d -o CMakeFiles/opmsimulators.dir/opm/simulators/linalg/setupPropertyTree.cpp.o -c /<>/opm/simulators/linalg/setupPropertyTree.cpp [ 31%] Building CXX object CMakeFiles/opmsimulators.dir/opm/simulators/timestepping/AdaptiveSimulatorTimer.cpp.o /usr/bin/c++ -DBOOST_DATE_TIME_DYN_LINK -DBOOST_DATE_TIME_NO_LIB -DBOOST_SYSTEM_DYN_LINK -DBOOST_SYSTEM_NO_LIB -DENABLE_MPI=1 -DFMT_SHARED -DHAVE_CONFIG_H=1 -DModelP -Dopmsimulators_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<> -I/usr/include/parmetis -I/usr/i
Bug#1075348: opm-common: ftbfs with GCC-14
Package: src:opm-common Version: 2024.04+ds-1 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/opm-common_2024.04+ds-1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] /usr/bin/c++ -DBOOST_SYSTEM_DYN_LINK -DBOOST_SYSTEM_NO_LIB -DEMBEDDED_PYTHON -DFMT_SHARED -DHAVE_CONFIG_H=1 -Dopmcommon_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<>/obj-x86_64-linux-gnu/include -I/<> -I/usr/include/cjson -isystem /usr/include/python3.12 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -fopenmp -pthread -std=c++17 -fPIC -fopenmp -MD -MT CMakeFiles/opmcommon.dir/opm/common/utility/String.cpp.o -MF CMakeFiles/opmcommon.dir/opm/common/utility/String.cpp.o.d -o CMakeFiles/opmcommon.dir/opm/common/utility/String.cpp.o -c /<>/opm/common/utility/String.cpp [ 23%] Building CXX object CMakeFiles/opmcommon.dir/opm/common/utility/TimeService.cpp.o /usr/bin/c++ -DBOOST_SYSTEM_DYN_LINK -DBOOST_SYSTEM_NO_LIB -DEMBEDDED_PYTHON -DFMT_SHARED -DHAVE_CONFIG_H=1 -Dopmcommon_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<>/obj-x86_64-linux-gnu/include -I/<> -I/usr/include/cjson -isystem /usr/include/python3.12 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -fopenmp -pthread -std=c++17 -fPIC -fopenmp -MD -MT CMakeFiles/opmcommon.dir/opm/common/utility/TimeService.cpp.o -MF CMakeFiles/opmcommon.dir/opm/common/utility/TimeService.cpp.o.d -o CMakeFiles/opmcommon.dir/opm/common/utility/TimeService.cpp.o -c /<>/opm/common/utility/TimeService.cpp [ 23%] Building CXX object CMakeFiles/opmcommon.dir/opm/common/utility/parameters/Parameter.cpp.o /usr/bin/c++ -DBOOST_SYSTEM_DYN_LINK -DBOOST_SYSTEM_NO_LIB -DEMBEDDED_PYTHON -DFMT_SHARED -DHAVE_CONFIG_H=1 -Dopmcommon_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<>/obj-x86_64-linux-gnu/include -I/<> -I/usr/include/cjson -isystem /usr/include/python3.12 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -fopenmp -pthread -std=c++17 -fPIC -fopenmp -MD -MT CMakeFiles/opmcommon.dir/opm/common/utility/parameters/Parameter.cpp.o -MF CMakeFiles/opmcommon.dir/opm/common/utility/parameters/Parameter.cpp.o.d -o CMakeFiles/opmcommon.dir/opm/common/utility/parameters/Parameter.cpp.o -c /<>/opm/common/utility/parameters/Parameter.cpp [ 24%] Building CXX object CMakeFiles/opmcommon.dir/opm/common/utility/parameters/ParameterGroup.cpp.o /usr/bin/c++ -DBOOST_SYSTEM_DYN_LINK -DBOOST_SYSTEM_NO_LIB -DEMBEDDED_PYTHON -DFMT_SHARED -DHAVE_CONFIG_H=1 -Dopmcommon_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<>/obj-x86_64-linux-gnu/include -I/<> -I/usr/include/cjson -isystem /usr/include/python3.12 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -fopenmp -pthread -std=c++17 -fPIC -fopenmp -MD -MT CMakeFiles/opmcommon.dir/opm/common/utility/parameters/ParameterGroup.cpp.o -MF CMakeFiles/opmcommon.dir/opm/common/utility/parameters/ParameterGroup.cpp.o.d -o CMakeFiles/opmcommon.dir/opm/common/utility/parameters/ParameterGroup.cpp.o -c /<>/opm/common/utility/parameters/ParameterGroup.cpp [ 24%] Building CXX object CMakeFiles/opmcommon.dir/opm/common/utility/parameters/ParameterRequirement.cpp.o /usr/bin/c++ -DBOOST_SYSTEM_DYN_LINK -DBOOST_SYSTEM_NO_LIB -DEMBEDDED_PYTHON -DFMT_SHARED -DHAVE_CONFIG_H=1 -Dopmcommon_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<>/obj-x86_64-linux-gnu/include -I/<> -I/usr/include/cjson -isystem /usr/include/python3.12 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=f
Bug#1075347: opm-grid: ftbfs with GCC-14
Package: src:opm-grid Version: 2024.04+ds-2 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/opm-grid_2024.04+ds-2_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] [ 7%] Generating tests/FIVE_PINCH.DATA /usr/bin/c++ -DBOOST_SYSTEM_DYN_LINK -DBOOST_SYSTEM_NO_LIB -DENABLE_MPI=1 -DFMT_SHARED -DHAVE_CONFIG_H=1 -DModelP -Dopmgrid_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<> -I/usr/include/parmetis -I/usr/include/superlu -I/usr/include/suitesparse -I/usr/include/cjson -I/usr/include/trilinos -I/usr/include/scotch -isystem /usr/lib/x86_64-linux-gnu/openmpi/include -isystem /usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -fopenmp -pthread -std=c++17 -fPIC -fopenmp -MD -MT CMakeFiles/opmgrid.dir/opm/grid/cpgrid/Intersection.cpp.o -MF CMakeFiles/opmgrid.dir/opm/grid/cpgrid/Intersection.cpp.o.d -o CMakeFiles/opmgrid.dir/opm/grid/cpgrid/Intersection.cpp.o -c /<>/opm/grid/cpgrid/Intersection.cpp /usr/bin/cmake -E copy /<>/tests/FIVE_PINCH.DATA /<>/obj-x86_64-linux-gnu/tests/FIVE_PINCH.DATA /usr/bin/cmake -E copy /<>/tests/CORNERPOINT_ACTNUM.DATA /<>/obj-x86_64-linux-gnu/tests/CORNERPOINT_ACTNUM.DATA [ 7%] Generating tests/FIVE_PINCH_NOGAP2.DATA [ 8%] Building CXX object CMakeFiles/opmgrid.dir/opm/grid/cpgrid/CpGridData.cpp.o /usr/bin/cmake -E copy /<>/tests/FIVE_PINCH_NOGAP2.DATA /<>/obj-x86_64-linux-gnu/tests/FIVE_PINCH_NOGAP2.DATA /usr/bin/c++ -DBOOST_SYSTEM_DYN_LINK -DBOOST_SYSTEM_NO_LIB -DENABLE_MPI=1 -DFMT_SHARED -DHAVE_CONFIG_H=1 -DModelP -Dopmgrid_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<> -I/usr/include/parmetis -I/usr/include/superlu -I/usr/include/suitesparse -I/usr/include/cjson -I/usr/include/trilinos -I/usr/include/scotch -isystem /usr/lib/x86_64-linux-gnu/openmpi/include -isystem /usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -fopenmp -pthread -std=c++17 -fPIC -fopenmp -MD -MT CMakeFiles/opmgrid.dir/opm/grid/cpgrid/CpGridData.cpp.o -MF CMakeFiles/opmgrid.dir/opm/grid/cpgrid/CpGridData.cpp.o.d -o CMakeFiles/opmgrid.dir/opm/grid/cpgrid/CpGridData.cpp.o -c /<>/opm/grid/cpgrid/CpGridData.cpp [ 8%] Building CXX object CMakeFiles/opmgrid.dir/opm/grid/cpgrid/CpGrid.cpp.o /usr/bin/c++ -DBOOST_SYSTEM_DYN_LINK -DBOOST_SYSTEM_NO_LIB -DENABLE_MPI=1 -DFMT_SHARED -DHAVE_CONFIG_H=1 -DModelP -Dopmgrid_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<> -I/usr/include/parmetis -I/usr/include/superlu -I/usr/include/suitesparse -I/usr/include/cjson -I/usr/include/trilinos -I/usr/include/scotch -isystem /usr/lib/x86_64-linux-gnu/openmpi/include -isystem /usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -fopenmp -pthread -std=c++17 -fPIC -fopenmp -MD -MT CMakeFiles/opmgrid.dir/opm/grid/cpgrid/CpGrid.cpp.o -MF CMakeFiles/opmgrid.dir/opm/grid/cpgrid/CpGrid.cpp.o.d -o CMakeFiles/opmgrid.dir/opm/grid/cpgrid/CpGrid.cpp.o -c /<>/opm/grid/cpgrid/CpGrid.cpp [ 9%] Building CXX object CMakeFiles/opmgrid.dir/opm/grid/cpgrid/GridHelpers.cpp.o [ 10%] Building CXX object CMakeFiles/opmgrid.dir/opm/grid/cpgrid/DataHandleWrappers.cpp.o /usr/bin/c++ -DBOOST_SYSTEM_DYN_LINK -DBOOST_SYSTEM_NO_LIB -DENABLE_MPI=1 -DFMT_SHARED -DHAVE_CONFIG_H=1 -DModelP -Dopmgrid_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<> -I/usr/include/parmetis -I/usr/include/superlu -I/usr/include/suitesparse -I/usr/include/cjson -I/usr/include/trilinos -I/usr/include/scotch -isystem /usr/lib/x86_64-linux-gnu/openmpi/include -isystem /usr
Bug#1075340: openfst: ftbfs with GCC-14
Package: src:openfst Version: 1.7.9-5 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/openfst_1.7.9-5_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] from fst.cc:13: ./../include/fst/replace.h: In member function ‘bool fst::internal::ReplaceFstImpl::ComputeArc(const StateTuple&, const Arc&, Arc*, uint8)’: ./../include/fst/replace.h:804:32: warning: expected ‘template’ keyword before dependent template name [-Wmissing-template-keyword] 804 | if (arc.olabel == 0 || arc.olabel < *nonterminal_set_.begin() || |^~ |template make[5]: *** [Makefile:479: fst.lo] Error 1 In file included from ./../include/fst/symbol-table-ops.h:12, from symbol-table-ops.cc:5: ./../include/fst/fst.h: In member function ‘fst::internal::FstImpl& fst::internal::FstImpl::operator=(const fst::internal::FstImpl&)’: ./../include/fst/fst.h:679:59: error: no match for ‘operator=’ (operand types are ‘std::unique_ptr’ and ‘fst::SymbolTable*’) 679 | isymbols_ = impl.isymbols_ ? impl.isymbols_->Copy() : nullptr; | ^~~ In file included from /usr/include/c++/14/memory:78, from ./../include/fst/fst.h:16: /usr/include/c++/14/bits/unique_ptr.h:424:9: note: candidate: ‘template typename std::enable_if::pointer, typename std::__uniq_ptr_impl<_Tp, _Dp>::pointer>, std::__not_ > >, std::is_assignable<_T2&, _U2&&> >::value, std::unique_ptr<_Tp, _Dp>&>::type std::unique_ptr<_Tp, _Dp>::operator=(std::unique_ptr<_Up, _Ep>&&) [with _Ep = _Up; _Tp = fst::SymbolTable; _Dp = std::default_delete]’ 424 | operator=(unique_ptr<_Up, _Ep>&& __u) noexcept | ^~~~ /usr/include/c++/14/bits/unique_ptr.h:424:9: note: template argument deduction/substitution failed: ./../include/fst/fst.h:679:59: note: mismatched types ‘std::unique_ptr<_Tp, _Dp>’ and ‘fst::SymbolTable*’ 679 | isymbols_ = impl.isymbols_ ? impl.isymbols_->Copy() : nullptr; | ^~~ /usr/include/c++/14/bits/unique_ptr.h:408:19: note: candidate: ‘std::unique_ptr<_Tp, _Dp>& std::unique_ptr<_Tp, _Dp>::operator=(std::unique_ptr<_Tp, _Dp>&&) [with _Tp = fst::SymbolTable; _Dp = std::default_delete]’ 408 | unique_ptr& operator=(unique_ptr&&) = default; | ^~~~ /usr/include/c++/14/bits/unique_ptr.h:408:29: note: no known conversion for argument 1 from ‘fst::SymbolTable*’ to ‘std::unique_ptr&&’ 408 | unique_ptr& operator=(unique_ptr&&) = default; | ^~~~ /usr/include/c++/14/bits/unique_ptr.h:434:7: note: candidate: ‘std::unique_ptr<_Tp, _Dp>& std::unique_ptr<_Tp, _Dp>::operator=(std::nullptr_t) [with _Tp = fst::SymbolTable; _Dp = std::default_delete; std::nullptr_t = std::nullptr_t]’ 434 | operator=(nullptr_t) noexcept | ^~~~ /usr/include/c++/14/bits/unique_ptr.h:434:17: note: no known conversion for argument 1 from ‘fst::SymbolTable*’ to ‘std::nullptr_t’ 434 | operator=(nullptr_t) noexcept | ^ ./../include/fst/fst.h:680:59: error: no match for ‘operator=’ (operand types are ‘std::unique_ptr’ and ‘fst::SymbolTable*’) 680 | osymbols_ = impl.osymbols_ ? impl.osymbols_->Copy() : nullptr; | ^~~ /usr/include/c++/14/bits/unique_ptr.h:424:9: note: candidate: ‘template typename std::enable_if::pointer, typename std::__uniq_ptr_impl<_Tp, _Dp>::pointer>, std::__not_ > >, std::is_assignable<_T2&, _U2&&> >::value, std::unique_ptr<_Tp, _Dp>&>::type std::unique_ptr<_Tp, _Dp>::operator=(std::unique_ptr<_Up, _Ep>&&) [with _Ep = _Up; _Tp = fst::SymbolTable; _Dp = std::default_de
Bug#1075336: opencascade: ftbfs with GCC-14
Package: src:opencascade Version: 7.8.1+dfsg1-2 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/opencascade_7.8.1+dfsg1-2_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] [ 96%] Building CXX object src/TKDESTEP/CMakeFiles/TKDESTEP.dir/__/StepData/StepData_SelectMember.cxx.o cd /<>/obj-x86_64-linux-gnu/src/TKDESTEP && /usr/bin/c++ -DHAVE_FREEIMAGE -DHAVE_FREETYPE -DHAVE_OPENGL_EXT -DHAVE_RAPIDJSON -DHAVE_TBB -DHAVE_TK -DHAVE_XLIB -DOCC_CONVERT_SIGNALS -DTKDESTEP_EXPORTS -I/usr/include/tcl -I/usr/include/freetype2 -I/<>/obj-x86_64-linux-gnu/include/opencascade -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fexceptions -fPIC -Wall -Wextra -O2 -g -DNDEBUG -std=gnu++11 -fPIC -MD -MT src/TKDESTEP/CMakeFiles/TKDESTEP.dir/__/StepData/StepData_SelectMember.cxx.o -MF CMakeFiles/TKDESTEP.dir/__/StepData/StepData_SelectMember.cxx.o.d -o CMakeFiles/TKDESTEP.dir/__/StepData/StepData_SelectMember.cxx.o -c /<>/src/StepData/StepData_SelectMember.cxx [ 96%] Building CXX object src/TKDESTEP/CMakeFiles/TKDESTEP.dir/__/StepData/StepData_SelectNamed.cxx.o cd /<>/obj-x86_64-linux-gnu/src/TKDESTEP && /usr/bin/c++ -DHAVE_FREEIMAGE -DHAVE_FREETYPE -DHAVE_OPENGL_EXT -DHAVE_RAPIDJSON -DHAVE_TBB -DHAVE_TK -DHAVE_XLIB -DOCC_CONVERT_SIGNALS -DTKDESTEP_EXPORTS -I/usr/include/tcl -I/usr/include/freetype2 -I/<>/obj-x86_64-linux-gnu/include/opencascade -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fexceptions -fPIC -Wall -Wextra -O2 -g -DNDEBUG -std=gnu++11 -fPIC -MD -MT src/TKDESTEP/CMakeFiles/TKDESTEP.dir/__/StepData/StepData_SelectNamed.cxx.o -MF CMakeFiles/TKDESTEP.dir/__/StepData/StepData_SelectNamed.cxx.o.d -o CMakeFiles/TKDESTEP.dir/__/StepData/StepData_SelectNamed.cxx.o -c /<>/src/StepData/StepData_SelectNamed.cxx [ 96%] Building CXX object src/TKDESTEP/CMakeFiles/TKDESTEP.dir/__/StepData/StepData_SelectReal.cxx.o cd /<>/obj-x86_64-linux-gnu/src/TKDESTEP && /usr/bin/c++ -DHAVE_FREEIMAGE -DHAVE_FREETYPE -DHAVE_OPENGL_EXT -DHAVE_RAPIDJSON -DHAVE_TBB -DHAVE_TK -DHAVE_XLIB -DOCC_CONVERT_SIGNALS -DTKDESTEP_EXPORTS -I/usr/include/tcl -I/usr/include/freetype2 -I/<>/obj-x86_64-linux-gnu/include/opencascade -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fexceptions -fPIC -Wall -Wextra -O2 -g -DNDEBUG -std=gnu++11 -fPIC -MD -MT src/TKDESTEP/CMakeFiles/TKDESTEP.dir/__/StepData/StepData_SelectReal.cxx.o -MF CMakeFiles/TKDESTEP.dir/__/StepData/StepData_SelectReal.cxx.o.d -o CMakeFiles/TKDESTEP.dir/__/StepData/StepData_SelectReal.cxx.o -c /<>/src/StepData/StepData_SelectReal.cxx [ 96%] Building CXX object src/TKDESTEP/CMakeFiles/TKDESTEP.dir/__/StepData/StepData_SelectType.cxx.o cd /<>/obj-x86_64-linux-gnu/src/TKDESTEP && /usr/bin/c++ -DHAVE_FREEIMAGE -DHAVE_FREETYPE -DHAVE_OPENGL_EXT -DHAVE_RAPIDJSON -DHAVE_TBB -DHAVE_TK -DHAVE_XLIB -DOCC_CONVERT_SIGNALS -DTKDESTEP_EXPORTS -I/usr/include/tcl -I/usr/include/freetype2 -I/<>/obj-x86_64-linux-gnu/include/opencascade -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fexceptions -fPIC -Wall -Wextra -O2 -g -DNDEBUG -std=gnu++11 -fPIC -MD -MT src/TKDESTEP/CMakeFiles/TKDESTEP.dir/__/StepData/StepData_SelectType.cxx.o -MF CMakeFiles/TKDESTEP.dir/__/StepData/StepData_SelectType.cxx.o.d -o CMakeFiles/TKDESTEP.dir/__/StepData/StepData_SelectType.cxx.o -c /<>/src/StepData/S
Bug#1075332: octomap: ftbfs with GCC-14
Package: src:octomap Version: 1.9.7+dfsg-3.1 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/octomap_1.9.7+dfsg-3.1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] [ 9%] Building CXX object octomap/src/CMakeFiles/octomap.dir/OcTreeNode.cpp.o [ 10%] Building CXX object octomap/src/CMakeFiles/octomap.dir/OcTree.cpp.o [ 11%] Building CXX object octomap/src/CMakeFiles/octomap.dir/AbstractOccupancyOcTree.cpp.o [ 11%] Building CXX object octomap/src/CMakeFiles/octomap.dir/AbstractOcTree.cpp.o cd /<>/obj-x86_64-linux-gnu/octomap/src && /usr/bin/c++ -Doctomap_EXPORTS -I/<>/octomap/include -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -Wextra -Wpedantic -std=gnu++11 -fPIC -fPIC -MD -MT octomap/src/CMakeFiles/octomap.dir/OcTreeNode.cpp.o -MF CMakeFiles/octomap.dir/OcTreeNode.cpp.o.d -o CMakeFiles/octomap.dir/OcTreeNode.cpp.o -c /<>/octomap/src/OcTreeNode.cpp cd /<>/obj-x86_64-linux-gnu/octomap/src && /usr/bin/c++ -Doctomap_EXPORTS -I/<>/octomap/include -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -Wextra -Wpedantic -std=gnu++11 -fPIC -fPIC -MD -MT octomap/src/CMakeFiles/octomap.dir/OcTree.cpp.o -MF CMakeFiles/octomap.dir/OcTree.cpp.o.d -o CMakeFiles/octomap.dir/OcTree.cpp.o -c /<>/octomap/src/OcTree.cpp cd /<>/obj-x86_64-linux-gnu/octomap/src && /usr/bin/c++ -Doctomap_EXPORTS -I/<>/octomap/include -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -Wextra -Wpedantic -std=gnu++11 -fPIC -fPIC -MD -MT octomap/src/CMakeFiles/octomap.dir/AbstractOcTree.cpp.o -MF CMakeFiles/octomap.dir/AbstractOcTree.cpp.o.d -o CMakeFiles/octomap.dir/AbstractOcTree.cpp.o -c /<>/octomap/src/AbstractOcTree.cpp cd /<>/obj-x86_64-linux-gnu/octomap/src && /usr/bin/c++ -Doctomap_EXPORTS -I/<>/octomap/include -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -Wextra -Wpedantic -std=gnu++11 -fPIC -fPIC -MD -MT octomap/src/CMakeFiles/octomap.dir/AbstractOccupancyOcTree.cpp.o -MF CMakeFiles/octomap.dir/AbstractOccupancyOcTree.cpp.o.d -o CMakeFiles/octomap.dir/AbstractOccupancyOcTree.cpp.o -c /<>/octomap/src/AbstractOccupancyOcTree.cpp [ 12%] Linking CXX static library /<>/lib/liboctomath.a cd /<>/obj-x86_64-linux-gnu/octomap/src/math && /usr/bin/cmake -P CMakeFiles/octomath-static.dir/cmake_clean_target.cmake cd /<>/obj-x86_64-linux-gnu/octomap/src/math && /usr/bin/cmake -E cmake_link_script CMakeFiles/octomath-static.dir/link.txt --verbose=1 /usr/bin/ar qc /<>/lib/liboctomath.a "CMakeFiles/octomath-static.dir/Vector3.cpp.o" "CMakeFiles/octomath-static.dir/Quaternion.cpp.o" "CMakeFiles/octomath-static.dir/Pose6D.cpp.o" /usr/bin/ranlib /<>/lib/liboctomath.a make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' [ 12%] Built target octomath-static make -f octomap/src/CMakeFiles/octomap-static.dir/build.make octomap/src/CMakeFiles/octomap-static.dir/depend make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/octomap/src /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/octomap/src /<>/obj-x86_64-linux-gnu/octomap/src/CMakeFiles/octomap-static.dir/DependInfo.cmake "--color=" make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f octomap/src/CMakeFiles/octomap-static.dir/build.make octomap/src/CMakeFiles/octomap-static.dir/build make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' [ 13%] Buil
Bug#1075308: ncl: ftbfs with GCC-14
Package: src:ncl
Version: 6.6.2.dfsg.1-7
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/ncl_6.6.2.dfsg.1-7_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
created NclTypedouble.h
created NclTypefloat.h
created NclTypeint.h
created NclTypelong.h
created NclTypeshort.h
created NclTypestring.h
created NclTypeushort.h
created NclTypeuint.h
created NclTypeulong.h
created NclTypeint64.h
created NclTypeuint64.h
created NclTypeubyte.h
created NclTypebyte.h
created NclTypechar.h
created TypeSupport.h
created NclTypedouble.c
created NclTypefloat.c
created NclTypeint.c
created NclTypelogical.c
created NclTypelong.c
created NclTypeobj.c
created NclTypeshort.c
created NclTypestring.c
created NclTypeushort.c
created NclTypeuint.c
created NclTypeulong.c
created NclTypeint64.c
created NclTypeuint64.c
created NclTypebyte.c
created NclTypeubyte.c
created NclTypechar.c
created TypeSupport.c
created NclMultiDValData.c
cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
-I/usr/include/hdf5/serial -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-I../../../.././include -I/usr/include/freetype2 -I/usr/include/gdal
-I/usr/include/hdf-eos5 -I/usr/include/hdf -I/usr/include/x86_64-linux-gnu/hdf
-I/usr/include/mpi -DLinux -DMAJOR=6 -DUSE_NETCDF4 -DBuildHDFEOS -DBuildHDF4
-DBuildHDFEOS5 -DBuildHDF5 -DBuildGRIB2 -D__64BIT__ -DBuildGDAL -DNIO_LIB_ONLY
-DENV_DEFS='{"tmp","TMPDIR",NULL,"/tmp",NULL,
"fontcap","FONTCAP",NULL,"/usr/share/ncarg/fontcaps",NULL,
"graphcap","GRAPHCAP",NULL,"/usr/share/ncarg/graphcaps",NULL,
"root",NULL,NULL,"/usr",NULL,
"usrresfile",NULL,NULL,"~/.hluresfile",NULL,
"gks_output",NULL,NULL,"gmeta",NULL,
"bin",NULL,"root","/usr/bin",NULL,
"lib",NULL,NULL,"/usr/lib/x86_64-linux-gnu/ncarg",NULL,
"include",NULL,"root","/usr/include/ncarg",NULL,
"man",NULL,"root","/usr/share/man",NULL,
"ncarg",NULL,NULL,"/usr/share/ncarg",NULL,
"config",NULL,"ncarg",NULL,NULL,
"data",NULL,"ncarg","/usr/share/ncarg/data",NULL,
"database",NULL,"ncarg","/usr/share/ncarg/database",NULL,
"doc",NULL,"ncarg","/usr/share/doc/libncarg-data",NULL,
"fontcaps",NULL,"ncarg","/usr/share/ncarg/fontcaps",NULL,
"graphcaps",NULL,"ncarg","/usr/share/ncarg/graphcaps",NULL,
"colormaps",NULL,"ncarg","/usr/share/ncarg/colormaps",NULL,
"rangs","NCARG_RANGS","database","/usr/share/rangs",NULL,
"udunits","NCARG_UDUNITS",NULL,"/usr/share/xml/udunits",NULL,
"psadilookup","PSADILOOKUP_PATH",NULL,NULL,NULL,
"examples",NULL,"ncarg","/usr/share/doc/libncarg-dev/examples",NULL,
"hluex",NULL,"ncarg","/usr/share/ncarg/hluex",NULL,
"nclex",NULL,"ncarg","/usr/share/ncarg/nclex",NULL,
"pynglex",NULL,"ncarg",NULL,NULL,
"resfiles",NULL,"ncarg","/usr/share/ncarg/resfiles",NULL,
"tests",NULL,"ncarg","/usr/share/ncarg/tests",NULL,
"tutorial",NULL,"ncarg","/usr/share/doc/libncarg-dev/tutorial",NULL,
"xapp",NULL,"ncarg",NULL,NULL,
"ngwww",NULL,"ncarg","/usr/share/ncarg/ngwww",NULL,
"ngurl",NULL,"ngww
Bug#1075295: mrcal: ftbfs with GCC-14
Package: src:mrcal Version: 2.4.1-1 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/mrcal_2.4.1-1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] < state_index_calobject_warp.docstring sed 's/\\//g; s/"/\\"/g; s/^/"/; s/$/\\n"/;' > state_index_calobject_warp.docstring.h < state_index_extrinsics.docstring sed 's/\\//g; s/"/\\"/g; s/^/"/; s/$/\\n"/;' > state_index_extrinsics.docstring.h < state_index_frames.docstring sed 's/\\//g; s/"/\\"/g; s/^/"/; s/$/\\n"/;' > state_index_frames.docstring.h < state_index_intrinsics.docstring sed 's/\\//g; s/"/\\"/g; s/^/"/; s/$/\\n"/;' > state_index_intrinsics.docstring.h < state_index_points.docstring sed 's/\\//g; s/"/\\"/g; s/^/"/; s/$/\\n"/;' > state_index_points.docstring.h < supported_lensmodels.docstring sed 's/\\//g; s/"/\\"/g; s/^/"/; s/$/\\n"/;' > supported_lensmodels.docstring.h < unpack_state.docstring sed 's/\\//g; s/"/\\"/g; s/^/"/; s/$/\\n"/;' > unpack_state.docstring.h ./minimath/minimath_generate.pl > minimath/minimath_generated.h.tmp && mv minimath/minimath_generated.h.tmp minimath/minimath_generated.h cc -Wall -Wextra -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection --std=gnu99 -I/usr/include/suitesparse -Wno-missing-field-initializers -Wno-unused-variable -Wno-unused-parameter -Wno-missing-braces -MMD -MP -g -fno-omit-frame-pointer -DMRBUILD_VERSION='"2.4.1-1"' -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -c -o mrcal-opencv.o mrcal-opencv.c cc -Wall -Wextra -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection --std=gnu99 -I/usr/include/suitesparse -Wno-missing-field-initializers -Wno-unused-variable -Wno-unused-parameter -Wno-missing-braces -MMD -MP -g -fno-omit-frame-pointer -DMRBUILD_VERSION='"2.4.1-1"' -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -c -o mrcal-image.o mrcal-image.c cc -Wall -Wextra -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection --std=gnu99 -I/usr/include/suitesparse -Wno-missing-field-initializers -Wno-unused-variable -Wno-unused-parameter -Wno-missing-braces -MMD -MP -g -fno-omit-frame-pointer -DMRBUILD_VERSION='"2.4.1-1"' -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -c -o poseutils.o poseutils.c cc -Wall -Wextra -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection --std=gnu99 -I/usr/include/suitesparse -Wno-missing-field-initializers -Wno-unused-variable -Wno-unused-parameter -Wno-missing-braces -MMD -MP -g -fno-omit-frame-pointer -DMRBUILD_VERSION='"2.4.1-1"' -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -c -o poseutils-opencv.o poseutils-opencv.c g++ -Wall -Wextra -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wno-missing-field-initializers -Wno-unused-variable -Wno-unused-parameter -Wno-missing-braces -MMD -MP -g -fno-omit-frame-pointer -DMRBUILD_VERSION='"2.4.1-1"' -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x -c -o poseutils-uses-autodiff.o poseutils-uses-autodiff.cc g++ -Wall -Wextra -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wno-missing-field-initializers -Wno-unused-variable -Wno-unused-parameter -Wno-missing-braces -MMD -MP -g -fno-omit-frame-pointer -DMRBUILD_VERSION='"2.4.1-1"' -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x -c -o triangulation.o triangulation.cc g++ -Wall -Wextra -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fs
Bug#1075292: mpich: ftbfs with GCC-14
Package: src:mpich Version: 4.2.0-6 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/mpich_4.2.0-6_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] - mpix_stream_isend__@Base 4.1 +#MISSING: 4.2.0-6# mpix_stream_isend__@Base 4.1 mpix_stream_isend_c_f08ts_@Base 4.2 mpix_stream_isend_f08ts_@Base 4.1 #MISSING: 4.2# mpix_stream_isend_f08ts_large_@Base 4.1 - mpix_stream_progress@Base 4.1 +#MISSING: 4.2.0-6# mpix_stream_progress@Base 4.1 mpix_stream_progress_@Base 4.1 - mpix_stream_progress__@Base 4.1 +#MISSING: 4.2.0-6# mpix_stream_progress__@Base 4.1 mpix_stream_progress_f08_@Base 4.1 - mpix_stream_recv@Base 4.1 +#MISSING: 4.2.0-6# mpix_stream_recv@Base 4.1 mpix_stream_recv_@Base 4.1 - mpix_stream_recv__@Base 4.1 +#MISSING: 4.2.0-6# mpix_stream_recv__@Base 4.1 mpix_stream_recv_c_f08ts_@Base 4.2 mpix_stream_recv_f08ts_@Base 4.1 #MISSING: 4.2# mpix_stream_recv_f08ts_large_@Base 4.1 - mpix_stream_send@Base 4.1 +#MISSING: 4.2.0-6# mpix_stream_send@Base 4.1 mpix_stream_send_@Base 4.1 - mpix_stream_send__@Base 4.1 +#MISSING: 4.2.0-6# mpix_stream_send__@Base 4.1 mpix_stream_send_c_f08ts_@Base 4.2 mpix_stream_send_f08ts_@Base 4.1 #MISSING: 4.2# mpix_stream_send_f08ts_large_@Base 4.1 - mpix_threadcomm_finish@Base 4.2 +#MISSING: 4.2.0-6# mpix_threadcomm_finish@Base 4.2 mpix_threadcomm_finish_@Base 4.2 - mpix_threadcomm_finish__@Base 4.2 +#MISSING: 4.2.0-6# mpix_threadcomm_finish__@Base 4.2 mpix_threadcomm_finish_f08_@Base 4.2 - mpix_threadcomm_free@Base 4.2 +#MISSING: 4.2.0-6# mpix_threadcomm_free@Base 4.2 mpix_threadcomm_free_@Base 4.2 - mpix_threadcomm_free__@Base 4.2 +#MISSING: 4.2.0-6# mpix_threadcomm_free__@Base 4.2 mpix_threadcomm_free_f08_@Base 4.2 - mpix_threadcomm_init@Base 4.2 +#MISSING: 4.2.0-6# mpix_threadcomm_init@Base 4.2 mpix_threadcomm_init_@Base 4.2 - mpix_threadcomm_init__@Base 4.2 +#MISSING: 4.2.0-6# mpix_threadcomm_init__@Base 4.2 mpix_threadcomm_init_f08_@Base 4.2 - mpix_threadcomm_start@Base 4.2 +#MISSING: 4.2.0-6# mpix_threadcomm_start@Base 4.2 mpix_threadcomm_start_@Base 4.2 - mpix_threadcomm_start__@Base 4.2 +#MISSING: 4.2.0-6# mpix_threadcomm_start__@Base 4.2 mpix_threadcomm_start_f08_@Base 4.2 - mpix_wait_enqueue@Base 4.1 +#MISSING: 4.2.0-6# mpix_wait_enqueue@Base 4.1 mpix_wait_enqueue_@Base 4.1 - mpix_wait_enqueue__@Base 4.1 +#MISSING: 4.2.0-6# mpix_wait_enqueue__@Base 4.1 mpix_wait_enqueue_f08_@Base 4.1 - mpix_waitall_enqueue@Base 4.1 +#MISSING: 4.2.0-6# mpix_waitall_enqueue@Base 4.1 mpix_waitall_enqueue_@Base 4.1 - mpix_waitall_enqueue__@Base 4.1 +#MISSING: 4.2.0-6# mpix_waitall_enqueue__@Base 4.1 mpix_waitall_enqueue_f08_@Base 4.1 pmpi_abort@Base 0 pmpi_abort_@Base 0 mv debian/.debhelper/generated/libmpich12/triggers.new debian/.debhelper/generated/libmpich12/triggers rm -f debian/mpich/DEBIAN/shlibs dh_makeshlibs: error: failing due to earlier errors make: *** [debian/rules:101: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1075279: mlpy: ftbfs with GCC-14
Package: src:mlpy
Version: 3.5.0+ds-3
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/mlpy_3.5.0+ds-3_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
/usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning:
Cython directive 'language_level' not set, using 2 for now (Py2). This will
change in a later release! File: /<>/mlpy/dtw/dtw.pyx
tree = Parsing.p_module(s, pxd, full_module_name)
/usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning:
Cython directive 'language_level' not set, using 2 for now (Py2). This will
change in a later release! File: /<>/mlpy/lcs/lcs.pyx
tree = Parsing.p_module(s, pxd, full_module_name)
In file included from
/usr/lib/python3/dist-packages/numpy/core/include/numpy/ndarraytypes.h:1929,
from
/usr/lib/python3/dist-packages/numpy/core/include/numpy/ndarrayobject.h:12,
from
/usr/lib/python3/dist-packages/numpy/core/include/numpy/arrayobject.h:5,
from mlpy/gsl/gsl.c:754:
/usr/lib/python3/dist-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:17:2:
warning: #warning "Using deprecated NumPy API, disable it with " "#define
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
17 | #warning "Using deprecated NumPy API, disable it with " \
| ^~~
In file included from
/usr/lib/python3/dist-packages/numpy/core/include/numpy/ndarraytypes.h:1929,
from
/usr/lib/python3/dist-packages/numpy/core/include/numpy/ndarrayobject.h:12,
from
/usr/lib/python3/dist-packages/numpy/core/include/numpy/arrayobject.h:5,
from mlpy/liblinear/liblinear.c:752:
/usr/lib/python3/dist-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:17:2:
warning: #warning "Using deprecated NumPy API, disable it with " "#define
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
17 | #warning "Using deprecated NumPy API, disable it with " \
| ^~~
mlpy/liblinear/liblinear.c: In function
‘__pyx_pf_4mlpy_9liblinear_9LibLinear___cinit__’:
mlpy/liblinear/liblinear.c:2870:30: error: passing argument 1 of
‘set_print_string_function’ from incompatible pointer type
[-Wincompatible-pointer-types]
2870 | set_print_string_function((&__pyx_f_4mlpy_9liblinear_print_null));
| ~^
| |
| void (*)(char *)
In file included from mlpy/liblinear/liblinear.c:761:
mlpy/liblinear/liblinear/linear.h:66:39: note: expected ‘void (*)(const char
*)’ but argument is of type ‘void (*)(char *)’
66 | void set_print_string_function(void (*print_func) (const char*));
|~~~^
mlpy/liblinear/liblinear.c: In function
‘__pyx_pf_4mlpy_9liblinear_9LibLinear_6learn’:
mlpy/liblinear/liblinear.c:3902:15: warning: assignment discards ‘const’
qualifier from pointer target type [-Wdiscarded-qualifiers]
3902 | __pyx_v_ret = check_parameter((&__pyx_v_self->problem),
(&__pyx_v_self->parameter));
| ^
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:389: build: plugin distutils failed with: exit code=1:
/usr/bin/python3.11 setup.py build
I: pybuild base:311: /usr/bin/python3 setup.py build
/<>/setup.py:27: SyntaxWarning: invalid escape sequence '\s'
data_files += [("Lib\site-packages\mlpy", dlls)]
In file included from
/usr/lib/python3/dist-packages/numpy/core/include/numpy/ndarraytypes.h:1929,
from
/usr/lib/python3/dist-packages/numpy/core/include/numpy/ndarrayobject.h:12,
from
/usr/lib/python3/dist-packages/numpy/core/include/numpy/arrayobject.h:5,
from mlpy/gsl/gsl.c:754:
/usr/lib/python3/dist-packages/numpy/core/include/numpy/npy_1_7_deprecated_ap
Bug#1075278: mlpack: ftbfs with GCC-14
Package: src:mlpack
Version: 4.4.0-1
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/mlpack_4.4.0-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
/usr/include/stb/stb_image_write.h:514:32: warning: missing initializer for
member ‘stbi__write_context::context’ [-Wmissing-field-initializers]
514 |stbi__write_context s = { 0 };
|^
/usr/include/stb/stb_image_write.h:514:32: warning: missing initializer for
member ‘stbi__write_context::buffer’ [-Wmissing-field-initializers]
/usr/include/stb/stb_image_write.h:514:32: warning: missing initializer for
member ‘stbi__write_context::buf_used’ [-Wmissing-field-initializers]
/usr/include/stb/stb_image_write.h: In function ‘int stbi_write_bmp(const
char*, int, int, int, const void*)’:
/usr/include/stb/stb_image_write.h:522:32: warning: missing initializer for
member ‘stbi__write_context::context’ [-Wmissing-field-initializers]
522 |stbi__write_context s = { 0 };
|^
/usr/include/stb/stb_image_write.h:522:32: warning: missing initializer for
member ‘stbi__write_context::buffer’ [-Wmissing-field-initializers]
/usr/include/stb/stb_image_write.h:522:32: warning: missing initializer for
member ‘stbi__write_context::buf_used’ [-Wmissing-field-initializers]
/usr/include/stb/stb_image_write.h: In function ‘int
stbi_write_tga_to_func(void (*)(void*, void*, int), void*, int, int, int, const
void*)’:
/usr/include/stb/stb_image_write.h:613:32: warning: missing initializer for
member ‘stbi__write_context::context’ [-Wmissing-field-initializers]
613 |stbi__write_context s = { 0 };
|^
/usr/include/stb/stb_image_write.h:613:32: warning: missing initializer for
member ‘stbi__write_context::buffer’ [-Wmissing-field-initializers]
/usr/include/stb/stb_image_write.h:613:32: warning: missing initializer for
member ‘stbi__write_context::buf_used’ [-Wmissing-field-initializers]
/usr/include/stb/stb_image_write.h: In function ‘int stbi_write_tga(const
char*, int, int, int, const void*)’:
/usr/include/stb/stb_image_write.h:621:32: warning: missing initializer for
member ‘stbi__write_context::context’ [-Wmissing-field-initializers]
621 |stbi__write_context s = { 0 };
|^
/usr/include/stb/stb_image_write.h:621:32: warning: missing initializer for
member ‘stbi__write_context::buffer’ [-Wmissing-field-initializers]
/usr/include/stb/stb_image_write.h:621:32: warning: missing initializer for
member ‘stbi__write_context::buf_used’ [-Wmissing-field-initializers]
/usr/include/stb/stb_image_write.h: In function ‘int
stbi_write_hdr_to_func(void (*)(void*, void*, int), void*, int, int, int, const
float*)’:
/usr/include/stb/stb_image_write.h:789:32: warning: missing initializer for
member ‘stbi__write_context::context’ [-Wmissing-field-initializers]
789 |stbi__write_context s = { 0 };
|^
/usr/include/stb/stb_image_write.h:789:32: warning: missing initializer for
member ‘stbi__write_context::buffer’ [-Wmissing-field-initializers]
/usr/include/stb/stb_image_write.h:789:32: warning: missing initializer for
member ‘stbi__write_context::buf_used’ [-Wmissing-field-initializers]
/usr/include/stb/stb_image_write.h: In function ‘int stbi_write_hdr(const
char*, int, int, int, const float*)’:
/usr/include/stb/stb_image_write.h:796:32: warning: missing initializer for
member ‘stbi__write_context::context’ [-Wmissing-field-initializers]
796 |stbi__write_context s = { 0 };
|^
/usr/include/stb/stb_image_write.h:796:32: warning: missing initializer for
member ‘stbi__write_context::buffer’ [-Wmissing-field-initializers]
/usr/include/stb/stb_image_write.h:796:32: warning: missing initializer for
member ‘stbi__write_context::buf_used’ [
Bug#1075249: magic: ftbfs with GCC-14
Package: src:magic Version: 8.3.105+ds.1-1.1 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/magic_8.3.105+ds.1-1.1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] make[3]: Leaving directory '/<>/gcr' make[3]: Entering directory '/<>/tcltk' ../rules.mak:24: warning: ignoring prerequisites on suffix rule definition gcc -g -m64 -fPIC -Wimplicit-int -fPIC -I/usr/include/tcl8.6/tk-private/generic -I/usr/include/tcl8.6 -I. -I.. -DCAD_DIR=\"/usr/lib/x86_64-linux-gnu\" -DBIN_DIR=\"/usr/bin\" -DTCL_DIR=\"/usr/lib/x86_64-linux-gnu/magic/tcl\" -DUSE_TCL_STUBS -DUSE_TK_STUBS -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DSIZEOF_VOID_P=8 -DSIZEOF_UNSIGNED_INT=4 -DSIZEOF_UNSIGNED_LONG=8 -DSIZEOF_UNSIGNED_LONG_LONG=8 -DHAVE_SETENV=1 -DHAVE_PUTENV=1 -DHAVE_SYS_MMAN_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_PATHS_H=1 -DHAVE_VA_COPY=1 -DHAVE___VA_COPY=1 -DFILE_LOCKS=1 -DCALMA_MODULE=1 -DCIF_MODULE=1 -DPLOT_MODULE=1 -DLEF_MODULE=1 -DROUTE_MODULE=1 -DUSE_NEW_MACROS=1 -DHAVE_LIBGL=1 -DHAVE_LIBGLU=1 -DVECTOR_FONTS=1 -DHAVE_LIBCAIRO=1 -DMAGIC_WRAPPER=1 -DTHREE_D=1 -Dlinux=1 -DSYSV=1 -DISC=1 -DMAGIC_VERSION=\"`cat ../VERSION | cut -d. -f1-2`\" -DMAGIC_REVISION=\"`cat ../VERSION | cut -d. -f3`\" -DGCORE=\"no\" -DSHDLIB_EXT=\".so\" -DNDEBUG -DMAGIC_DATE="\"`dpkg-parsechangelog -l../debian/changelog --show-field Date`\"" -MM tclmagic.c | \ sed -e "/#/D" -e "/ \//s/ \/.*\.h//" -e "/ \\\/D" \ > Depend ../rules.mak:24: warning: ignoring prerequisites on suffix rule definition make[3]: Nothing to be done for 'depend'. make[3]: Leaving directory '/<>/tcltk' make[3]: Entering directory '/<>/readline' make[3]: Nothing to be done for 'depend'. make[3]: Leaving directory '/<>/readline' make[3]: Entering directory '/<>/lisp' ../rules.mak:24: warning: ignoring prerequisites on suffix rule definition gcc -g -m64 -fPIC -Wimplicit-int -fPIC -I/usr/include/tcl8.6/tk-private/generic -I/usr/include/tcl8.6 -I. -I.. -DCAD_DIR=\"/usr/lib/x86_64-linux-gnu\" -DBIN_DIR=\"/usr/bin\" -DTCL_DIR=\"/usr/lib/x86_64-linux-gnu/magic/tcl\" -DUSE_TCL_STUBS -DUSE_TK_STUBS -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DSIZEOF_VOID_P=8 -DSIZEOF_UNSIGNED_INT=4 -DSIZEOF_UNSIGNED_LONG=8 -DSIZEOF_UNSIGNED_LONG_LONG=8 -DHAVE_SETENV=1 -DHAVE_PUTENV=1 -DHAVE_SYS_MMAN_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_PATHS_H=1 -DHAVE_VA_COPY=1 -DHAVE___VA_COPY=1 -DFILE_LOCKS=1 -DCALMA_MODULE=1 -DCIF_MODULE=1 -DPLOT_MODULE=1 -DLEF_MODULE=1 -DROUTE_MODULE=1 -DUSE_NEW_MACROS=1 -DHAVE_LIBGL=1 -DHAVE_LIBGLU=1 -DVECTOR_FONTS=1 -DHAVE_LIBCAIRO=1 -DMAGIC_WRAPPER=1 -DTHREE_D=1 -Dlinux=1 -DSYSV=1 -DISC=1 -DMAGIC_VERSION=\"`cat ../VERSION | cut -d. -f1-2`\" -DMAGIC_REVISION=\"`cat ../VERSION | cut -d. -f3`\" -DGCORE=\"no\" -DSHDLIB_EXT=\".so\" -DNDEBUG -MM lispMain.c lispEval.c lispPrint.c lispParse.c lispA-Z.c lispGC.c lispFrame.c lispTrace.c lispMagic.c lispArith.c lispString.c lispIO.c | \ sed -e "/#/D" -e "/ \//s/ \/.*\.h//" -e "/ \\\/D" \ > Depend ../rules.mak:24: warning: ignoring prerequisites on suffix rule definition make[3]: Nothing to be done for 'depend'. make[3]: Leaving directory '/<>/lisp' make[3]: Entering directory '/<>/magic' ../rules.mak:24: warning: ignoring prerequisites on suffix rule definition gcc -g -m64 -fPIC -Wimplicit-int -fPIC -I/usr/include/tcl8.6/tk-private/generi
Bug#1075159: libcgns: ftbfs with GCC-14
Package: src:libcgns Version: 3.4.0-4 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/libcgns_3.4.0-4_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] cd /<>/obj-x86_64-linux-gnu/src/cgnstools/cgnsview && /usr/bin/cc -DBUILD_HDF5 -DH5_BUILT_AS_STATIC_LIB -I/<>/obj-x86_64-linux-gnu/src -I/<>/src -I/usr/include/hdf5/serial -I/usr/include/tcl -I/<>/src/cgnstools/cgnsview/../common -I/<>/src/cgnstools/cgnsview/../.. -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/tcl/tk-private/generic -I/usr/include/tcl/tk-private/unix -MD -MT src/cgnstools/cgnsview/CMakeFiles/cgiowish.dir/cgiowish.c.o -MF CMakeFiles/cgiowish.dir/cgiowish.c.o.d -o CMakeFiles/cgiowish.dir/cgiowish.c.o -c /<>/src/cgnstools/cgnsview/cgiowish.c [ 63%] Building C object src/cgnstools/cgnsview/CMakeFiles/cgiowish.dir/cgiotcl.c.o cd /<>/obj-x86_64-linux-gnu/src/cgnstools/cgnsview && /usr/bin/cc -DBUILD_HDF5 -DH5_BUILT_AS_STATIC_LIB -I/<>/obj-x86_64-linux-gnu/src -I/<>/src -I/usr/include/hdf5/serial -I/usr/include/tcl -I/<>/src/cgnstools/cgnsview/../common -I/<>/src/cgnstools/cgnsview/../.. -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/tcl/tk-private/generic -I/usr/include/tcl/tk-private/unix -MD -MT src/cgnstools/cgnsview/CMakeFiles/cgiowish.dir/cgiotcl.c.o -MF CMakeFiles/cgiowish.dir/cgiotcl.c.o.d -o CMakeFiles/cgiowish.dir/cgiotcl.c.o -c /<>/src/cgnstools/cgnsview/cgiotcl.c [ 63%] Linking C executable cgiowish cd /<>/obj-x86_64-linux-gnu/src/cgnstools/cgnsview && /usr/bin/cmake -E cmake_link_script CMakeFiles/cgiowish.dir/link.txt --verbose=1 /usr/bin/cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/tcl/tk-private/generic -I/usr/include/tcl/tk-private/unix -Wl,-z,relro -rdynamic CMakeFiles/cgiowish.dir/cgiowish.c.o CMakeFiles/cgiowish.dir/cgiotcl.c.o -o cgiowish -L. -Wl,-rpath,.:/<>/obj-x86_64-linux-gnu/src:/usr/lib/x86_64-linux-gnu/hdf5/serial: ../../libcgns.so.3.4 -ltcl -ltk /usr/lib/x86_64-linux-gnu/hdf5/serial/libhdf5.so -lcrypto -lcurl -Wl,-Bstatic -lpthread -Wl,-Bdynamic -lsz -lz -Wl,-Bstatic -ldl -Wl,-Bdynamic -lm -lX11 -lm -ldl make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' [ 63%] Built target cgiowish make -f src/cgnstools/calclib/CMakeFiles/calclib.dir/build.make src/cgnstools/calclib/CMakeFiles/calclib.dir/depend make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/src/cgnstools/calclib /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/src/cgnstools/calclib /<>/obj-x86_64-linux-gnu/src/cgnstools/calclib/CMakeFiles/calclib.dir/DependInfo.cmake "--color=" make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f src/cgnstools/calclib/CMakeFiles/calclib.dir/build.make src/cgnstools/calclib/CMakeFiles/calclib.dir/build make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' [ 63%] Building C object src/cgnstools/calclib/CMakeFiles/calclib.dir/calc.c.o cd /<>/obj-x86_64-linux-gnu/src/cgnstools/calclib && /usr/bin/cc -DBUILD_HDF5 -DH5_BUILT_AS_STATIC_LIB -I/<>/obj-x86_64-linux-gnu/src -I/<>/src -I/usr/include/hdf5/serial -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/tcl/tk-private/generic -I/usr/include/tcl/tk-private/unix
Bug#1075155: libccp4: ftbfs with GCC-14
Package: src:libccp4 Version: 8.0.0-3 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/libccp4_8.0.0-3_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] Warning: Array reference at (1) out of bounds (2 > 1) in loop beginning at (2) fortran/modlib.f:1442:25: 1440 | DO 120 I = 2,M |2 1441 | H = ALPHA(I) 1442 | ALPHA(I) = A(I,I) | 1 Warning: Array reference at (1) out of bounds (2 > 1) in loop beginning at (2) fortran/modlib.f:1443:14: 1440 | DO 120 I = 2,M |2 .. 1443 | A(I,I) = H | 1 Warning: Array reference at (1) out of bounds (2 > 1) in loop beginning at (2) ccp4/cmtzlib.c: In function ‘MtzPut’: ccp4/cmtzlib.c:2746:27: warning: ‘%74s’ directive writing between 74 and 80 bytes into a region of size 76 [-Wformat-overflow=] 2746 | sprintf(hdrrec,"SYMM %74s",symline); | ^~~~ ~~~ In file included from /usr/include/stdio.h:964, from ccp4/cmtzlib.c:23: In function ‘sprintf’, inlined from ‘MtzPut’ at ccp4/cmtzlib.c:2746:6: /usr/include/x86_64-linux-gnu/bits/stdio2.h:30:10: note: ‘__builtin___sprintf_chk’ output between 80 and 86 bytes into a destination of size 81 30 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1, | ^~ 31 | __glibc_objsize (__s), __fmt, | ~ 32 | __va_arg_pack ()); | ~ ccp4/cmtzlib.c: In function ‘MtzPut’: ccp4/cmtzlib.c:2840:52: warning: ‘%1X’ directive writing between 1 and 8 bytes into a region of size 7 [-Wformat-overflow=] 2840 |sprintf(hdrrec,"COLGRP %-30s %-30s %-4s %1X %4d","M/ISYM",mtz->xtal[i]->set[j]->col[k]->grpname,mtz->xtal[i]->set[j]->col[k]->grptype,mtz->xtal[i]->set[j]->col[k]->grpposn,mtz->xtal[i]->set[j]->setid); |^~~ ccp4/cmtzlib.c:2840:27: note: directive argument in the range [0, 2147483647] 2840 |sprintf(hdrrec,"COLGRP %-30s %-30s %-4s %1X %4d","M/ISYM",mtz->xtal[i]->set[j]->col[k]->grpname,mtz->xtal[i]->set[j]->col[k]->grptype,mtz->xtal[i]->set[j]->col[k]->grpposn,mtz->xtal[i]->set[j]->setid); | ^ In function ‘sprintf’, inlined from ‘MtzPut’ at ccp4/cmtzlib.c:2840:5: /usr/include/x86_64-linux-gnu/bits/stdio2.h:30:10: note: ‘__builtin___sprintf_chk’ output between 81 and 95 bytes into a destination of size 81 30 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1, | ^~ 31 | __glibc_objsize (__s), __fmt, | ~ 32 | __va_arg_pack ()); | ~ ccp4/cmtzlib.c: In function ‘MtzPut’: ccp4/cmtzlib.c:2842:52: warning: ‘%1X’ directive writing between 1 and 8 bytes into a region of size 7 [-Wformat-overflow=] 2842 |sprintf(hdrrec,"COLGRP %-30s %-30s %-4s %1X %4d",mtz->xtal[i]->set[j]->col[k]->label,mtz->xtal[i]->set[j]->col[k]->grpname,mtz->xtal[i]->set[j]->col[k]->grptype,mtz->xtal[i]->set[j]->col[k]->grpposn,mtz->xtal[i]->set[j]->setid); |^~~ ccp4/cmtzlib.c:2842:27: note: directive argument in the range [0, 2147483647] 2842 |sprintf(hdrrec,"COLGRP %-30s %-30s %-4s %1X %4
Bug#1075136: lfortran: ftbfs with GCC-14
Package: src:lfortran
Version: 0.36.0-1
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/lfortran_0.36.0-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
/<>/src/libasr/diagnostics.h:15:8: warning: ‘*(__vector(4)
unsigned int*)((char*)& + offsetof(LCompilers::diag::Span,
LCompilers::diag::Span::first_line))’ may be used uninitialized
[-Wmaybe-uninitialized]
15 | struct Span {
|^~~~
/<>/src/libasr/diagnostics.h: In member function ‘void
LCompilers::diag::Diagnostics::message_label(const std::string&, const
std::vector&, const std::string&, const
LCompilers::diag::Level&, const LCompilers::diag::Stage&)’:
/<>/src/libasr/diagnostics.h:54:37: note: ‘’ declared
here
54 | spans.push_back(Span(loc));
| ^
In file included from /<>/src/libasr/exception.h:29,
from /<>/src/libasr/assert.h:7,
from /<>/src/libasr/alloc.h:10,
from /<>/src/lfortran/ast.h:6,
from
/<>/src/lfortran/semantics/ast_body_visitor.cpp:10:
In constructor ‘LCompilers::diag::Span::Span(LCompilers::diag::Span&&)’,
inlined from ‘void std::__new_allocator<_Tp>::construct(_Up*, _Args&& ...)
[with _Up = LCompilers::diag::Span; _Args = {LCompilers::diag::Span}; _Tp =
LCompilers::diag::Span]’ at /usr/include/c++/14/bits/new_allocator.h:191:4,
inlined from ‘static void std::allocator_traits
>::construct(allocator_type&, _Up*, _Args&& ...) [with _Up =
LCompilers::diag::Span; _Args = {LCompilers::diag::Span}; _Tp =
LCompilers::diag::Span]’ at /usr/include/c++/14/bits/alloc_traits.h:534:17,
inlined from ‘std::vector<_Tp, _Alloc>::reference std::vector<_Tp,
_Alloc>::emplace_back(_Args&& ...) [with _Args = {LCompilers::diag::Span}; _Tp
= LCompilers::diag::Span; _Alloc = std::allocator]’ at
/usr/include/c++/14/bits/vector.tcc:117:30,
inlined from ‘void std::vector<_Tp, _Alloc>::push_back(value_type&&) [with
_Tp = LCompilers::diag::Span; _Alloc = std::allocator]’
at /usr/include/c++/14/bits/stl_vector.h:1301:21,
inlined from ‘LCompilers::diag::Label::Label(const std::string&, const
std::vector&, bool)’ at
/<>/src/libasr/diagnostics.h:54:28:
/<>/src/libasr/diagnostics.h:15:8: warning: ‘*(__vector(4)
unsigned int*)((char*)& + offsetof(LCompilers::diag::Span,
LCompilers::diag::Span::first_line))’ may be used uninitialized
[-Wmaybe-uninitialized]
15 | struct Span {
|^~~~
/<>/src/libasr/diagnostics.h: In constructor
‘LCompilers::diag::Label::Label(const std::string&, const
std::vector&, bool)’:
/<>/src/libasr/diagnostics.h:54:37: note: ‘’ declared
here
54 | spans.push_back(Span(loc));
| ^
In file included from /<>/src/libasr/exception.h:29,
from /<>/src/libasr/assert.h:7,
from /<>/src/libasr/alloc.h:10,
from /<>/src/lfortran/ast.h:6,
from /<>/src/lfortran/semantics/ast_to_asr.cpp:8:
In constructor ‘LCompilers::diag::Span::Span(LCompilers::diag::Span&&)’,
inlined from ‘void std::__new_allocator<_Tp>::construct(_Up*, _Args&& ...)
[with _Up = LCompilers::diag::Span; _Args = {LCompilers::diag::Span}; _Tp =
LCompilers::diag::Span]’ at /usr/include/c++/14/bits/new_allocator.h:191:4,
inlined from ‘static void std::allocator_traits
>::construct(allocator_type&, _Up*, _Args&& ...) [with _Up =
LCompilers::diag::Span; _Args = {LCompilers::diag::Span}; _Tp =
LCompilers::diag::Span]’ at /usr/include/c++/14/bits/alloc_traits.h:534:17,
inlined from ‘std::vector<_Tp, _Alloc>::reference std::vector<_Tp,
_Alloc>::emplace_back(_Args&& ...) [with _Args = {LCompilers::diag::Span}; _Tp
= LCompilers::diag::Span; _Alloc = std::allocator]’ at
/usr/include/c++/14/bits/vector.tcc:117:30,
inlined from ‘void std::vector<_Tp, _Alloc>::push_back
Bug#1075090: inventor: ftbfs with GCC-14
Package: src:inventor
Version: 2.1.5-10+dfsg-2.1
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/inventor_2.1.5-10+dfsg-2.1_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
rm -rf
rm -rf Makedepend
make[3]: Entering directory '/<>/tools/ppp'
rm -rf *.[oue] a.out core lex.yy.[co] y.tab.[cho] _force ar.tmp.*
rm -rf ppp
rm -rf Makedepend
make[3]: Leaving directory '/<>/tools/ppp'
make[2]: Leaving directory '/<>/tools'
make[2]: Entering directory '/<>/libFL'
rm -rf *.[oue] a.out core lex.yy.[co] y.tab.[cho] xxx_force ar.tmp.*
rm -rf
rm -rf Makedepend
make[3]: Entering directory '/<>/libFL'
make[3]: *** freetype: No such file or directory. Stop.
make[3]: Leaving directory '/<>/libFL'
make[2]: *** [GNUmakefile:17: clobber] Error 1
make[2]: Leaving directory '/<>/libFL'
make[1]: *** [GNUmakefile:12: clobber] Error 1
make[1]: Leaving directory '/<>'
make: [debian/rules:77: clean] Error 2 (ignored)
# Clear out symlinks created during build.
rm -f libFL/ang/flclient.h libFL/freetype lib/libInventor.so.1
libSoXt/libInventorXt.so.1
dh_clean
debian/rules binary
dh_testdir
# libFL binary archive changed name in CVS version
rm -f libFL/src/libFL*.a
install -d /<>/debian/tmp
LD_LIBRARY_PATH=/<>/debian/tmp/usr/lib dh_auto_build -- install
make -j8 "INSTALL=install --strip-program=true" install
make[1]: Entering directory '/<>'
make[2]: Entering directory '/<>'
make[2]: warning: jobserver unavailable: using -j1. Add '+' to parent make
rule.
/usr/bin/gcc-g -D_REENTRANT -O3 -I/usr/X11R6/include -I.
-I../lib/database/include -I../lib/interaction/include
-I../lib/nodekits/include -I../libSoXt/include -fPIC-O -DNDEBUG
-Wdate-time -D_FORTIFY_SOURCE=2 -c -o close.o close.c
close.c: In function ‘iclose’:
close.c:15:5: error: implicit declaration of function ‘iflush’; did you mean
‘fflush’? [-Wimplicit-function-declaration]
15 | iflush(image);
| ^~
| fflush
close.c:16:5: error: implicit declaration of function ‘img_optseek’
[-Wimplicit-function-declaration]
16 | img_optseek(image, 0);
| ^~~
close.c:19:13: error: implicit declaration of function ‘cvtimage’
[-Wimplicit-function-declaration]
19 | cvtimage(image);
| ^~~~
close.c:20:13: error: implicit declaration of function ‘img_write’
[-Wimplicit-function-declaration]
20 | if (img_write(image,(char *)image,sizeof(IMAGE)) !=
sizeof(IMAGE)) {
| ^
close.c:21:13: error: implicit declaration of function ‘i_errhdlr’
[-Wimplicit-function-declaration]
21 | i_errhdlr("iclose: error on write of image header\n");
| ^
close.c:30:17: error: implicit declaration of function ‘cvtlongs’
[-Wimplicit-function-declaration]
30 | cvtlongs(image->rowstart,tablesize);
| ^~~~
close.c:57:11: error: implicit declaration of function ‘close’; did you mean
‘iclose’? [-Wimplicit-function-declaration]
57 | ret = close(image->file);
| ^
| iclose
close.c: In function ‘iflush’:
close.c:70:17: error: implicit declaration of function ‘putrow’; did you mean
‘putw’? [-Wimplicit-function-declaration]
70 | if (putrow(image, base, image->y,image->z)!=image->xsize) {
| ^~
| putw
make[2]: *** [: close.o] Error 1
make[2]: Leaving directory '/<>/libimage'
make[1]: *** [GNUmakefile:12: install] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: error: make -j8 "INSTALL=install --strip-program=true" install
returned exit code 2
make: *** [debian/rules:65: build-stamp] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--
debian-science-maintainers mailing list
debian-science-maintainers@alio
Bug#1075077: hypre: ftbfs with GCC-14
Package: src:hypre Version: 2.29.0-2 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/hypre_2.29.0-2_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] 3150 | comm_handle = hypre_ParCSRCommHandleCreate (2, comm_pkg, x_ext_data, buf_data); | ^~~~ schwarz.c:3014:16: note: ‘buf_data’ was declared here 3014 |HYPRE_Real *buf_data; |^~~~ schwarz.c: In function ‘hypre_ParAMGCreateDomainDof’: schwarz.c:3686:49: warning: ‘a_ext_i’ may be used uninitialized [-Wmaybe-uninitialized] 3686 | for (j = a_ext_i[i_dof]; j < a_ext_i[i_dof + 1]; j++) | ^ schwarz.c:3216:15: note: ‘a_ext_i’ was declared here 3216 |HYPRE_Int *a_ext_i; | ^~~ schwarz.c:3688:19: warning: ‘a_ext_j’ may be used uninitialized [-Wmaybe-uninitialized] 3688 |jj = a_ext_j[j]; |~~~^~~~ schwarz.c:3217:18: note: ‘a_ext_j’ was declared here 3217 |HYPRE_BigInt *a_ext_j; | ^~~ schwarz.c:3703:72: warning: ‘a_ext_data’ may be used uninitialized [-Wmaybe-uninitialized] 3703 | AE[i_loc + j_loc * local_dof_counter] = a_ext_data[j]; | ~~^~~ schwarz.c:3218:16: note: ‘a_ext_data’ was declared here 3218 |HYPRE_Real *a_ext_data; |^~ schwarz.c: In function ‘hypre_ParGenerateScale’: schwarz.c:3797:22: warning: ‘scale_ext’ may be used uninitialized [-Wmaybe-uninitialized] 3797 | scale_ext[j_loc - num_variables] += 1.0; | ~^~~ schwarz.c:3762:16: note: ‘scale_ext’ was declared here 3762 |HYPRE_Real *scale_ext; |^ schwarz.c:3763:16: warning: ‘scale_int’ may be used uninitialized [-Wmaybe-uninitialized] 3763 |HYPRE_Real *scale_int; |^ schwarz.c: In function ‘hypre_ParGenerateHybridScale’: schwarz.c:3990:42: warning: ‘send_map_starts’ may be used uninitialized [-Wmaybe-uninitialized] 3990 | for (j = start; j < send_map_starts[i + 1]; j++) | ~~~^~~ schwarz.c:3859:15: note: ‘send_map_starts’ was declared here 3859 |HYPRE_Int *send_map_starts; | ^~~ schwarz.c:3992:30: warning: ‘send_map_elmts’ may be used uninitialized [-Wmaybe-uninitialized] 3992 | scale[send_map_elmts[j]] += scale_int[index++]; |~~^~~ schwarz.c:3860:15: note: ‘send_map_elmts’ was declared here 3860 |HYPRE_Int *send_map_elmts; | ^~ schwarz.c:3897:20: warning: ‘index_ext’ may be used uninitialized [-Wmaybe-uninitialized] 3897 | index_ext[i] = -1; | ~^~~~ schwarz.c:3861:15: note: ‘index_ext’ was declared here 3861 |HYPRE_Int *index_ext; | ^ schwarz.c:3910:25: warning: ‘scale_ext’ may be used uninitialized [-Wmaybe-uninitialized] 3910 |scale_ext[j_loc] += 1.0; |~^~~ schwarz.c:3854:16: note: ‘scale_ext’ was declared here 3854 |HYPRE_Real *scale_ext; |^ schwarz.c:3855:16: warning: ‘scale_int’ may be used uninitialized [-Wmaybe-uninitialized] 3855 |HYPRE_Real *scale_int; |^ make[3]: Leaving directory '/<>/src64/parcsr_ls' make[2]: *** [Makefile:90: all] Error 1 make[2]: Leaving directory '/<>/src64' dh_auto_build: error: cd src64 && make -j8 returned exit code 2 make[1]: *** [debian/rules:153: override_dh_auto_build] Error 25 make[1]: Leaving directory '/<>' make: *** [debian/rules:25: build] Error 2 dp
Bug#1075068: hmat-oss: ftbfs with GCC-14
Package: src:hmat-oss Version: 1.8.1-2 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/hmat-oss_1.8.1-2_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] [ 26%] Building CXX object CMakeFiles/hmat.dir/src/admissibility.cpp.o [ 30%] Building CXX object CMakeFiles/hmat.dir/src/clustering.cpp.o /usr/bin/c++ -DHMAT_DLL_EXPORTS -I/<>/src -I/<>/include -I/<>/obj-x86_64-linux-gnu -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fopenmp -Werror -Wall -Wno-sign-compare -Wno-undefined-var-template -Wno-unused-parameter -ffast-math -funsafe-math-optimizations -MD -MT CMakeFiles/hmat.dir/src/admissibility.cpp.o -MF CMakeFiles/hmat.dir/src/admissibility.cpp.o.d -o CMakeFiles/hmat.dir/src/admissibility.cpp.o -c /<>/src/admissibility.cpp /usr/bin/c++ -DHMAT_DLL_EXPORTS -I/<>/src -I/<>/include -I/<>/obj-x86_64-linux-gnu -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fopenmp -Werror -Wall -Wno-sign-compare -Wno-undefined-var-template -Wno-unused-parameter -ffast-math -funsafe-math-optimizations -MD -MT CMakeFiles/hmat.dir/src/clustering.cpp.o -MF CMakeFiles/hmat.dir/src/clustering.cpp.o.d -o CMakeFiles/hmat.dir/src/clustering.cpp.o -c /<>/src/clustering.cpp /usr/bin/c++ -DHMAT_DLL_EXPORTS -I/<>/src -I/<>/include -I/<>/obj-x86_64-linux-gnu -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fopenmp -Werror -Wall -Wno-sign-compare -Wno-undefined-var-template -Wno-unused-parameter -ffast-math -funsafe-math-optimizations -MD -MT CMakeFiles/hmat.dir/src/assembly.cpp.o -MF CMakeFiles/hmat.dir/src/assembly.cpp.o.d -o CMakeFiles/hmat.dir/src/assembly.cpp.o -c /<>/src/assembly.cpp /usr/bin/c++ -DHMAT_DLL_EXPORTS -I/<>/src -I/<>/include -I/<>/obj-x86_64-linux-gnu -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fopenmp -Werror -Wall -Wno-sign-compare -Wno-undefined-var-template -Wno-unused-parameter -ffast-math -funsafe-math-optimizations -MD -MT CMakeFiles/hmat.dir/src/cluster_tree.cpp.o -MF CMakeFiles/hmat.dir/src/cluster_tree.cpp.o.d -o CMakeFiles/hmat.dir/src/cluster_tree.cpp.o -c /<>/src/cluster_tree.cpp In file included from /<>/src/full_matrix.hpp:32, from /<>/src/rk_matrix.hpp:27, from /<>/src/h_matrix.hpp:33, from /<>/src/hmat_cpp_interface.hpp:47, from /<>/src/c_default_interface.cpp:26: /<>/src/scalar_array.hpp:572:14: error: template-id not allowed for constructor in C++20 [-Werror=template-id-cdtor] 572 | Vector(const Vector& o); | ^ /<>/src/scalar_array.hpp:572:14: note: remove the ‘< >’ In file included from /<>/src/full_matrix.hpp:32, from /<>/src/assembly.cpp:25: /<>/src/scalar_array.hpp:572:14: error: template-id not allowed for constructor in C++20 [-Werror=template-id-cdtor] 572 | Vector(const Vector& o); | ^ /<>/src/scalar_array.hpp:572:14: note: remove the ‘< >’ In file included from /<>/src/full_matrix.hpp:32, from /<>/src/rk_matrix.hpp:27, from /<>/src/h_matrix.hpp:33, from /<>/src/hmat_cpp_interface.hpp:47, from /<>/src/clustering.cpp:26: /<>/src/scalar_array.hpp:572:14: error: template-id not allowed for constructor in C++20 [-Werror=template-id-cdtor] 572 | Vec
Bug#1075066: hfst: ftbfs with GCC-14
Package: src:hfst
Version: 3.16.0-5
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/hfst_3.16.0-5_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
In file included from /usr/include/fst/disambiguate.h:22,
from /usr/include/fst/fstlib.h:47:
/usr/include/fst/project.h:19:30: note: declared here
19 | static constexpr ProjectType PROJECT_INPUT = ProjectType::INPUT;
| ^
TropicalWeightTransducer.cc: In static member function ‘static
fst::StdVectorFst*
hfst::implementations::TropicalWeightTransducer::extract_output_language(fst::StdVectorFst*)’:
TropicalWeightTransducer.cc:2054:50: warning: ‘fst::PROJECT_OUTPUT’ is
deprecated: Use `ProjectType::OUTPUT` instead. [-Wdeprecated-declarations]
2054 | (*t,PROJECT_OUTPUT));
| ^~
/usr/include/fst/project.h:21:30: note: declared here
21 | static constexpr ProjectType PROJECT_OUTPUT = ProjectType::OUTPUT;
| ^~
LogWeightTransducer.cc: In static member function ‘static
hfst::implementations::LogFst*
hfst::implementations::LogWeightTransducer::extract_input_language(hfst::implementations::LogFst*)’:
LogWeightTransducer.cc:1495:57: warning: ‘fst::PROJECT_INPUT’ is deprecated:
Use `ProjectType::INPUT` instead. [-Wdeprecated-declarations]
1495 | { LogFst * retval = new LogFst(ProjectFst(*t,PROJECT_INPUT));
| ^
In file included from /usr/include/fst/disambiguate.h:22,
from /usr/include/fst/fstlib.h:47:
/usr/include/fst/project.h:19:30: note: declared here
19 | static constexpr ProjectType PROJECT_INPUT = ProjectType::INPUT;
| ^
LogWeightTransducer.cc: In static member function ‘static
hfst::implementations::LogFst*
hfst::implementations::LogWeightTransducer::extract_output_language(hfst::implementations::LogFst*)’:
LogWeightTransducer.cc:1501:56: warning: ‘fst::PROJECT_OUTPUT’ is deprecated:
Use `ProjectType::OUTPUT` instead. [-Wdeprecated-declarations]
1501 | { LogFst * retval = new LogFst(ProjectFst(*t,PROJECT_OUTPUT));
|^~
/usr/include/fst/project.h:21:30: note: declared here
21 | static constexpr ProjectType PROJECT_OUTPUT = ProjectType::OUTPUT;
| ^~
TropicalWeightTransducer.cc: In static member function ‘static
hfst::FdTable*
hfst::implementations::TropicalWeightTransducer::get_flag_diacritics(fst::StdVectorFst*)’:
TropicalWeightTransducer.cc:3074:34: warning: ‘SymbolTableIterator’ is
deprecated: Use SymbolTable::iterator, a C++ compliant iterator, instead
[-Wdeprecated-declarations]
3074 | for(fst::SymbolTableIterator it=fst::SymbolTableIterator(*symbols);
| ^~
/usr/include/fst/symbol-table.h:545:5: note: declared here
545 | SymbolTableIterator {
| ^~~
TropicalWeightTransducer.cc:3074:70: warning: ‘SymbolTableIterator’ is
deprecated: Use SymbolTable::iterator, a C++ compliant iterator, instead
[-Wdeprecated-declarations]
3074 | for(fst::SymbolTableIterator it=fst::SymbolTableIterator(*symbols);
| ^
/usr/include/fst/symbol-table.h:545:5: note: declared here
545 | SymbolTableIterator {
| ^~~
LogWeightTransducer.cc: In static member function ‘static hfst::FdTable*
hfst::implementations::LogWeightTransducer::get_flag_diacritics(hfst::implementations::LogFst*)’:
LogWeightTransducer.cc:2256:34: warning: ‘SymbolTableIterator’ is deprecated:
Use SymbolTable::iterator, a C++ complian
Bug#1075065: heaptrack: ftbfs with GCC-14
Package: src:heaptrack Version: 1.5.0+dfsg1-2 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/heaptrack_1.5.0+dfsg1-2_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_NONE CMAKE_STATIC_LINKER_FLAGS_NONE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STRIP CMAKE_STRIP-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_TAPI CMAKE_TAPI-ADVANCED:INTERNAL=1 //uname command CMAKE_UNAME:INTERNAL=/usr/bin/uname //ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1 //Details about finding Boost FIND_PACKAGE_MESSAGE_DETAILS_Boost:INTERNAL=[/usr/lib/x86_64-linux-gnu/cmake/Boost-1.83.0/BoostConfig.cmake][cfound components: system filesystem iostreams container ][v1.83.0(1.60.0)] //Details about finding Threads FIND_PACKAGE_MESSAGE_DETAILS_Threads:INTERNAL=[TRUE][v()] //Details about finding ZLIB FIND_PACKAGE_MESSAGE_DETAILS_ZLIB:INTERNAL=[/usr/lib/x86_64-linux-gnu/libz.so][/usr/include][c ][v1.3.1()] //Details about finding ZSTD FIND_PACKAGE_MESSAGE_DETAILS_ZSTD:INTERNAL=[/usr/lib/x86_64-linux-gnu/libzstd.so][/usr/include][v()] //Have symbol cfree HAVE_CFREE:INTERNAL= //Have symbol valloc HAVE_VALLOC:INTERNAL=1 //Test LIBUNWIND_HAS_UNW_BACKTRACE LIBUNWIND_HAS_UNW_BACKTRACE:INTERNAL= //Test LIBUNWIND_HAS_UNW_BACKTRACE_SKIP LIBUNWIND_HAS_UNW_BACKTRACE_SKIP:INTERNAL= //Test LIBUNWIND_HAS_UNW_CACHE_PER_THREAD LIBUNWIND_HAS_UNW_CACHE_PER_THREAD:INTERNAL=1 //Test LIBUNWIND_HAS_UNW_GETCONTEXT LIBUNWIND_HAS_UNW_GETCONTEXT:INTERNAL=1 //Test LIBUNWIND_HAS_UNW_INIT_LOCAL LIBUNWIND_HAS_UNW_INIT_LOCAL:INTERNAL=1 //Test LIBUNWIND_HAS_UNW_SET_CACHE_SIZE LIBUNWIND_HAS_UNW_SET_CACHE_SIZE:INTERNAL=1 //ADVANCED property for variable: ZLIB_INCLUDE_DIR ZLIB_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ZLIB_LIBRARY_DEBUG ZLIB_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ZLIB_LIBRARY_RELEASE ZLIB_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ZSTD_INCLUDE_DIR ZSTD_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ZSTD_LIBRARY ZSTD_LIBRARY-ADVANCED:INTERNAL=1 //linker supports push/pop state _CMAKE_LINKER_PUSHPOP_STATE_SUPPORTED:INTERNAL=TRUE //ADVANCED property for variable: boost_atomic_DIR boost_atomic_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: boost_container_DIR boost_container_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: boost_filesystem_DIR boost_filesystem_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: boost_headers_DIR boost_headers_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: boost_iostreams_DIR boost_iostreams_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: boost_system_DIR boost_system_DIR-ADVANCED:INTERNAL=1 dh_auto_configure: error: cd debian/build && DEB_PYTHON_INSTALL_LAYOUT=deb cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DHEAPTRACK_BUILD_PRINT=ON -DHEAPTRACK_BUILD_GUI=ON ../.. returned exit code 1 make[1]: *** [debian/rules:11: override_dh_auto_configure] Error 2 make
Bug#1074991: gf2x: ftbfs with GCC-14
Package: src:gf2x Version: 1.3.0-2 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/gf2x_1.3.0-2_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] config.status: creating Makefile config.status: creating tests/Makefile config.status: creating lowlevel/Makefile config.status: creating src/Makefile config.status: creating fft/Makefile config.status: creating apps/Makefile config.status: creating fft/gf2x-fft.h config.status: creating gf2x.h.in config.status: creating gf2x.pc config.status: creating gf2x/gf2x-config.h config.status: creating gf2x/gf2x-config-export.h config.status: creating gf2x.h config.status: gf2x.h is unchanged config.status: linking already_tuned/generic64/gf2x-thresholds.h to gf2x/gf2x-thresholds.h config.status: linking already_tuned/generic64/gf2x_mul1.h to gf2x/gf2x_mul1.h config.status: linking already_tuned/generic/gf2x_mul2.h to gf2x/gf2x_mul2.h config.status: linking already_tuned/generic/gf2x_mul3.h to gf2x/gf2x_mul3.h config.status: linking already_tuned/generic/gf2x_mul4.h to gf2x/gf2x_mul4.h config.status: linking already_tuned/generic/gf2x_mul5.h to gf2x/gf2x_mul5.h config.status: linking already_tuned/generic/gf2x_mul6.h to gf2x/gf2x_mul6.h config.status: linking already_tuned/generic/gf2x_mul7.h to gf2x/gf2x_mul7.h config.status: linking already_tuned/generic/gf2x_mul8.h to gf2x/gf2x_mul8.h config.status: linking already_tuned/generic/gf2x_mul9.h to gf2x/gf2x_mul9.h config.status: executing depfiles commands config.status: executing libtool commands make[1]: Leaving directory '/<>' dh_auto_build make -j8 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in lowlevel make[3]: Entering directory '/<>/lowlevel' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/<>/lowlevel' Making all in src make[3]: Entering directory '/<>/src' sed -e s/@@SIZE@@/1/g < ./tuneup_pre.c > tuneup_1.c sed -e s/@@SIZE@@/1/g < ./tuning_undefs_pre.h > tuning_undefs_1.h sed -e s/@@SIZE@@/2/g < ./tuneup_pre.c > tuneup_2.c sed -e s/@@SIZE@@/2/g < ./tuning_undefs_pre.h > tuning_undefs_2.h sed -e s/@@SIZE@@/3/g < ./tuneup_pre.c > tuneup_3.c sed -e s/@@SIZE@@/3/g < ./tuning_undefs_pre.h > tuning_undefs_3.h sed -e s/@@SIZE@@/4/g < ./tuneup_pre.c > tuneup_4.c sed -e s/@@SIZE@@/4/g < ./tuning_undefs_pre.h > tuning_undefs_4.h sed -e s/@@SIZE@@/5/g < ./tuneup_pre.c > tuneup_5.c sed -e s/@@SIZE@@/5/g < ./tuning_undefs_pre.h > tuning_undefs_5.h sed -e s/@@SIZE@@/6/g < ./tuneup_pre.c > tuneup_6.c sed -e s/@@SIZE@@/6/g < ./tuning_undefs_pre.h > tuning_undefs_6.h sed -e s/@@SIZE@@/7/g < ./tuneup_pre.c > tuneup_7.c sed -e s/@@SIZE@@/7/g < ./tuning_undefs_pre.h > tuning_undefs_7.h sed -e s/@@SIZE@@/8/g < ./tuneup_pre.c > tuneup_8.c sed -e s/@@SIZE@@/8/g < ./tuning_undefs_pre.h > tuning_undefs_8.h sed -e s/@@SIZE@@/9/g < ./tuneup_pre.c > tuneup_9.c sed -e s/@@SIZE@@/9/g < ./tuning_undefs_pre.h > tuning_undefs_9.h c89 `test -f '../lowlevel/gen_bb_mul_code.c' || echo './'`../lowlevel/gen_bb_mul_code.c -o gen_bb_mul_code ../lowlevel/gen_bb_mul_code.c: In function ‘main’: ../lowlevel/gen_bb_mul_code.c:95:17: error: C++ style comments are not allowed in ISO C90 95 | // continue;/* mul_1_n is no longer used */ | ^ ../lowlevel/gen_bb_mul_code.c:95:17: note: (this will be reported only once per input file) make[3]: *** [Makefile:4249: gen_bb_mul_code] Error 1 make[3]: Leaving directory '/<>/src' make[2]: *** [Makefile:908: all-recursive] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [Makefile:537: all] Error 2 make[1]: Leaving directory '/<>' dh_auto_build: error: make -j8 returned exit code 2 make: *** [debian/rules:6: build] Error 25 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 -- debian-science-maintainers mailing list debian-science-maintainers@alioth-l
Bug#1074988: gerris: ftbfs with GCC-14
Package: src:gerris
Version: 20131206+dfsg-19.1
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/gerris_20131206+dfsg-19.1_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
dvidir='${docdir}'
exec_prefix='NONE'
have_m4=''
have_pkg_config=''
host='x86_64-pc-linux-gnu'
host_alias=''
host_cpu='x86_64'
host_os='linux-gnu'
host_vendor='pc'
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${prefix}/share/info'
install_sh='${SHELL} /<>/install-sh'
libdir='${prefix}/lib/x86_64-linux-gnu'
libexecdir='${exec_prefix}/libexec'
localedir='${datarootdir}/locale'
localstatedir='/var'
mandir='${prefix}/share/man'
mkdir_p='$(MKDIR_P)'
ode=''
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
runstatedir='/run'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''
use_mpicc='yes'
## --- ##
## confdefs.h. ##
## --- ##
/* confdefs.h */
#define PACKAGE_NAME ""
#define PACKAGE_TARNAME ""
#define PACKAGE_VERSION ""
#define PACKAGE_STRING ""
#define PACKAGE_BUGREPORT ""
#define PACKAGE_URL ""
#define GFS_MAJOR_VERSION 1
#define GFS_MINOR_VERSION 3
#define GFS_MICRO_VERSION 2
#define GFS_INTERFACE_AGE 0
#define GFS_BINARY_AGE 0
#define GFS_VERSION "1.3.2"
#define GFS_COMPILATION_FLAGS "-g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection"
#define HAVE_MPI 1
#define HAVE_STDIO_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_STDINT_H 1
#define HAVE_STRINGS_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_SYS_TYPES_H 1
#define HAVE_UNISTD_H 1
#define STDC_HEADERS 1
#define HAVE_DLFCN_H 1
#define LT_OBJDIR ".libs/"
configure: exit 1
dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --enable-mpi returned
exit code 1
make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1074963: foma: ftbfs with GCC-14
Package: src:foma
Version: 1:0.10.0+s311-1.2
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/foma_0.10.0+s311-1.2_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
| ^
[ 11%] Building C object CMakeFiles/foma-static.dir/define.c.o
/usr/bin/cc -D_GNU_SOURCE -I/<> -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -Wall
-Wextra -Wno-missing-field-initializers -Wno-deprecated -Wno-unused-parameter
-fvisibility=hidden -fPIC -std=c2x -fPIC -MD -MT
CMakeFiles/foma-static.dir/define.c.o -MF
CMakeFiles/foma-static.dir/define.c.o.d -o
CMakeFiles/foma-static.dir/define.c.o -c /<>/define.c
[ 12%] Building C object CMakeFiles/foma-static.dir/determinize.c.o
/usr/bin/cc -D_GNU_SOURCE -I/<> -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -Wall
-Wextra -Wno-missing-field-initializers -Wno-deprecated -Wno-unused-parameter
-fvisibility=hidden -fPIC -std=c2x -fPIC -MD -MT
CMakeFiles/foma-static.dir/determinize.c.o -MF
CMakeFiles/foma-static.dir/determinize.c.o.d -o
CMakeFiles/foma-static.dir/determinize.c.o -c /<>/determinize.c
/<>/determinize.c: In function ‘fsm_subset’:
/<>/determinize.c:209:29: warning: comparison of integer
expressions of different signedness: ‘int’ and ‘unsigned int’ [-Wsign-compare]
209 | while (tail < tptr->size && transitions->inout ==
minsym) {
| ^
/<>/determinize.c:231:26: warning: comparison of integer
expressions of different signedness: ‘int’ and ‘unsigned int’ [-Wsign-compare]
231 | if (tail == tptr->size)
| ^~
/<>/determinize.c: In function ‘nhash_find_insert’:
/<>/determinize.c:656:34: warning: comparison of integer
expressions of different signedness: ‘unsigned int’ and ‘int’ [-Wsign-compare]
656 | if ((tableptr)->size != setsize) {
| ^~
/<>/determinize.c: In function ‘move_set’:
/<>/determinize.c:705:36: warning: comparison of integer
expressions of different signedness: ‘unsigned int’ and ‘int’ [-Wsign-compare]
705 | if (set_table_offset + setsize >= set_table_size) {
|^~
/<>/determinize.c:706:43: warning: comparison of integer
expressions of different signedness: ‘unsigned int’ and ‘int’ [-Wsign-compare]
706 | while (set_table_offset + setsize >= set_table_size) {
| ^~
/<>/determinize.c: In function ‘nhash_rebuild_table’:
/<>/determinize.c:759:25: warning: comparison of integer
expressions of different signedness: ‘unsigned int’ and ‘int’ [-Wsign-compare]
759 | for (i=0; primes[i] < nhash_tablesize; i++) { }
| ^
/<>/determinize.c: In function ‘nhash_init’:
/<>/determinize.c:795:23: warning: comparison of integer
expressions of different signedness: ‘unsigned int’ and ‘int’ [-Wsign-compare]
795 | for (i=0; primes[i] < initial_size; i++) { }
| ^
[ 13%] Building C object CMakeFiles/foma-static.dir/dynarray.c.o
/usr/bin/cc -D_GNU_SOURCE -I/<> -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -Wall
-Wextra -Wno-missing-field-initializers -Wno-deprecated -Wno-unused-parameter
-fvisibility=hidden -fPIC -std=c2x -fPIC -MD -MT
CMakeFiles/foma-static.dir/dynarray.c.o -MF
CMakeFiles/foma-static.dir/dynarray.c.o.d -o
CMakeFiles/foma-static.dir/dynarray.c.o -c /<>/dynarray.c
Bug#1074955: fftw: ftbfs with GCC-14
Package: src:fftw
Version: 2.1.5-6
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/fftw_2.1.5-6_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
mv -f .deps/transpose_mpi.Tpo .deps/transpose_mpi.Plo
/bin/bash ../libtool --tag=CC --mode=compile mpicc -DHAVE_CONFIG_H -I.
-I../fftw -I./../tests -I./../fftw -I./../rfftw -I. -Wdate-time
-D_FORTIFY_SOURCE=2 -O3 -fomit-frame-pointer -fno-schedule-insns
-fschedule-insns2 -malign-double -fstrict-aliasing -MT fftwnd_mpi.lo -MD -MP
-MF .deps/fftwnd_mpi.Tpo -c -o fftwnd_mpi.lo fftwnd_mpi.c
libtool: compile: mpicc -DHAVE_CONFIG_H -I. -I../fftw -I./../tests -I./../fftw
-I./../rfftw -I. -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -fomit-frame-pointer
-fno-schedule-insns -fschedule-insns2 -malign-double -fstrict-aliasing -MT
fftwnd_mpi.lo -MD -MP -MF .deps/fftwnd_mpi.Tpo -c fftwnd_mpi.c -fPIC -DPIC -o
.libs/fftwnd_mpi.o
libtool: compile: mpicc -DHAVE_CONFIG_H -I. -I../fftw -I./../tests -I./../fftw
-I./../rfftw -I. -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -fomit-frame-pointer
-fno-schedule-insns -fschedule-insns2 -malign-double -fstrict-aliasing -MT
fftwnd_mpi.lo -MD -MP -MF .deps/fftwnd_mpi.Tpo -c fftwnd_mpi.c -o fftwnd_mpi.o
>/dev/null 2>&1
mv -f .deps/fftwnd_mpi.Tpo .deps/fftwnd_mpi.Plo
/bin/bash ../libtool --tag=CC --mode=compile mpicc -DHAVE_CONFIG_H -I.
-I../fftw -I./../tests -I./../fftw -I./../rfftw -I. -Wdate-time
-D_FORTIFY_SOURCE=2 -O3 -fomit-frame-pointer -fno-schedule-insns
-fschedule-insns2 -malign-double -fstrict-aliasing -MT fftw_mpi.lo -MD -MP -MF
.deps/fftw_mpi.Tpo -c -o fftw_mpi.lo fftw_mpi.c
libtool: compile: mpicc -DHAVE_CONFIG_H -I. -I../fftw -I./../tests -I./../fftw
-I./../rfftw -I. -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -fomit-frame-pointer
-fno-schedule-insns -fschedule-insns2 -malign-double -fstrict-aliasing -MT
fftw_mpi.lo -MD -MP -MF .deps/fftw_mpi.Tpo -c fftw_mpi.c -fPIC -DPIC -o
.libs/fftw_mpi.o
libtool: compile: mpicc -DHAVE_CONFIG_H -I. -I../fftw -I./../tests -I./../fftw
-I./../rfftw -I. -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -fomit-frame-pointer
-fno-schedule-insns -fschedule-insns2 -malign-double -fstrict-aliasing -MT
fftw_mpi.lo -MD -MP -MF .deps/fftw_mpi.Tpo -c fftw_mpi.c -o fftw_mpi.o
>/dev/null 2>&1
mv -f .deps/fftw_mpi.Tpo .deps/fftw_mpi.Plo
/bin/bash ../libtool --tag=CC --mode=compile mpicc -DHAVE_CONFIG_H -I.
-I../fftw -I./../tests -I./../fftw -I./../rfftw -I. -Wdate-time
-D_FORTIFY_SOURCE=2 -O3 -fomit-frame-pointer -fno-schedule-insns
-fschedule-insns2 -malign-double -fstrict-aliasing -MT fftw_f77_mpi.lo -MD -MP
-MF .deps/fftw_f77_mpi.Tpo -c -o fftw_f77_mpi.lo fftw_f77_mpi.c
libtool: compile: mpicc -DHAVE_CONFIG_H -I. -I../fftw -I./../tests -I./../fftw
-I./../rfftw -I. -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -fomit-frame-pointer
-fno-schedule-insns -fschedule-insns2 -malign-double -fstrict-aliasing -MT
fftw_f77_mpi.lo -MD -MP -MF .deps/fftw_f77_mpi.Tpo -c fftw_f77_mpi.c -fPIC
-DPIC -o .libs/fftw_f77_mpi.o
In file included from fftw_f77_mpi.c:20:
fftw_f77_mpi.c: In function ‘fftw_f77_mpi_create_plan_’:
fftw_f77_mpi.h:50:48: error: passing argument 1 of ‘MPI_Comm_f2c’ makes integer
from pointer without a cast [-Wint-conversion]
50 | # define FFTW_MPI_COMM_F2C(comm) MPI_Comm_f2c(*((MPI_Comm *) comm))
|^~~~
||
|MPI_Comm {aka struct
ompi_communicator_t *}
fftw_f77_mpi.c:35:32: note: in expansion of macro ‘FFTW_MPI_COMM_F2C’
35 | *p = fftw_mpi_create_plan(FFTW_MPI_COMM_F2C(comm), *n,dir,*flags);
|^
In file included from fftw_mpi.h:24,
from fftw_f77_mpi.h:23:
/usr/lib/x86_64-linux-gnu/openmpi/include/mpi.h:1413:47: note: expected ‘int’
but
Bug#1074951: fenics-dolfinx: ftbfs with GCC-14
Package: src:fenics-dolfinx Version: 1:0.8.0-10 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/fenics-dolfinx_0.8.0-10_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] FAILED test/unit/mesh/test_higher_order_mesh.py::test_tetrahedron_mesh[float32-1] FAILED test/unit/mesh/test_higher_order_mesh.py::test_tetrahedron_mesh[float32-2] FAILED test/unit/mesh/test_higher_order_mesh.py::test_tetrahedron_mesh[float32-3] FAILED test/unit/mesh/test_higher_order_mesh.py::test_tetrahedron_mesh[float32-4] FAILED test/unit/mesh/test_higher_order_mesh.py::test_tetrahedron_mesh[float64-1] FAILED test/unit/mesh/test_higher_order_mesh.py::test_tetrahedron_mesh[float64-2] FAILED test/unit/mesh/test_higher_order_mesh.py::test_tetrahedron_mesh[float64-3] FAILED test/unit/mesh/test_higher_order_mesh.py::test_tetrahedron_mesh[float64-4] FAILED test/unit/mesh/test_higher_order_mesh.py::test_quadrilateral_mesh[float32-1] FAILED test/unit/mesh/test_higher_order_mesh.py::test_quadrilateral_mesh[float32-2] FAILED test/unit/mesh/test_higher_order_mesh.py::test_quadrilateral_mesh[float32-3] FAILED test/unit/mesh/test_higher_order_mesh.py::test_quadrilateral_mesh[float32-4] FAILED test/unit/mesh/test_higher_order_mesh.py::test_quadrilateral_mesh[float64-1] FAILED test/unit/mesh/test_higher_order_mesh.py::test_quadrilateral_mesh[float64-2] FAILED test/unit/mesh/test_higher_order_mesh.py::test_quadrilateral_mesh[float64-3] FAILED test/unit/mesh/test_higher_order_mesh.py::test_quadrilateral_mesh[float64-4] FAILED test/unit/mesh/test_higher_order_mesh.py::test_hexahedron_mesh[float32-1] FAILED test/unit/mesh/test_higher_order_mesh.py::test_hexahedron_mesh[float32-2] FAILED test/unit/mesh/test_higher_order_mesh.py::test_hexahedron_mesh[float32-3] FAILED test/unit/mesh/test_higher_order_mesh.py::test_hexahedron_mesh[float32-4] FAILED test/unit/mesh/test_higher_order_mesh.py::test_hexahedron_mesh[float64-1] FAILED test/unit/mesh/test_higher_order_mesh.py::test_hexahedron_mesh[float64-2] FAILED test/unit/mesh/test_higher_order_mesh.py::test_hexahedron_mesh[float64-3] FAILED test/unit/mesh/test_higher_order_mesh.py::test_hexahedron_mesh[float64-4] FAILED test/unit/mesh/test_higher_order_mesh.py::test_triangle_mesh_vtk[float32-1] FAILED test/unit/mesh/test_higher_order_mesh.py::test_triangle_mesh_vtk[float32-2] FAILED test/unit/mesh/test_higher_order_mesh.py::test_triangle_mesh_vtk[float32-3] FAILED test/unit/mesh/test_higher_order_mesh.py::test_triangle_mesh_vtk[float32-4] FAILED test/unit/mesh/test_higher_order_mesh.py::test_triangle_mesh_vtk[float64-1] FAILED test/unit/mesh/test_higher_order_mesh.py::test_triangle_mesh_vtk[float64-2] FAILED test/unit/mesh/test_higher_order_mesh.py::test_triangle_mesh_vtk[float64-3] FAILED test/unit/mesh/test_higher_order_mesh.py::test_triangle_mesh_vtk[float64-4] FAILED test/unit/mesh/test_higher_order_mesh.py::test_tetrahedron_mesh_vtk[float32-1] FAILED test/unit/mesh/test_higher_order_mesh.py::test_tetrahedron_mesh_vtk[float32-2] FAILED test/unit/mesh/test_higher_order_mesh.py::test_tetrahedron_mesh_vtk[float32-3] FAILED test/unit/mesh/test_higher_order_mesh.py::test_tetrahedron_mesh_vtk[float64-1] FAILED test/unit/mesh/test_higher_order_mesh.py::test_tetrahedron_mesh_vtk[float64-2] FAILED test/unit/mesh/test_higher_order_mesh.py::test_tetrahedron_mesh_vtk[float64-3] FAILED test/unit/mesh/test_higher_order_mesh.py::test_quadrilateral_mesh_vtk[float32-1] FAILED test/unit/mesh/test_higher_order_mesh.py::test_quadrilateral_mesh_vtk[float32-2] FAILED test/unit/mesh/test_higher_order_mesh.py::test_quadrilateral_mesh_vtk[float32-3] FAILED test/unit/mesh/test_higher_order_mesh.py::test_quadrilateral_mesh_vtk[float32-4] FAILED test/unit/mesh/test_higher_order_mesh.py::test_quadrilateral_mesh_vtk[float64-1] FAILED test/unit/mesh/test_higher_order_mesh.py::test_quadrilateral_me
Bug#1074927: dx: ftbfs with GCC-14
Package: src:dx Version: 1:4.4.4-16 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/dx_4.4.4-16_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../include -I../../../include -I./../dpexec -I/<>/include -Dlinux -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fsigned-char -fno-strict-aliasing -std=c++11 -D_GNU_SOURCE -I/usr/include/x86_64-linux-gnu/ImageMagick-6 -I/usr/include/ImageMagick-6 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -c selector.c -o selector.o >/dev/null 2>&1 /bin/bash ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../include -I../../../include -I./../dpexec -I/<>/include -Dlinux -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fsigned-char -fno-strict-aliasing -std=c++11 -D_GNU_SOURCE -I/usr/include/x86_64-linux-gnu/ImageMagick-6 -I/usr/include/ImageMagick-6 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -c -o shade.lo shade.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../include -I../../../include -I./../dpexec -I/<>/include -Dlinux -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fsigned-char -fno-strict-aliasing -std=c++11 -D_GNU_SOURCE -I/usr/include/x86_64-linux-gnu/ImageMagick-6 -I/usr/include/ImageMagick-6 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -c shade.c -fPIC -DPIC -o .libs/shade.o cc1: warning: command-line option ‘-std=c++11’ is valid for C++/ObjC++ but not for C libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../include -I../../../include -I./../dpexec -I/<>/include -Dlinux -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fsigned-char -fno-strict-aliasing -std=c++11 -D_GNU_SOURCE -I/usr/include/x86_64-linux-gnu/ImageMagick-6 -I/usr/include/ImageMagick-6 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -c shade.c -o shade.o >/dev/null 2>&1 /bin/bash ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../include -I../../../include -I./../dpexec -I/<>/include -Dlinux -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fsigned-char -fno-strict-aliasing -std=c++11 -D_GNU_SOURCE -I/usr/include/x86_64-linux-gnu/ImageMagick-6 -I/usr/include/ImageMagick-6 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -c -o showboundary.lo showboundary.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../include -I../../../include -I./../dpexec -I/<>/include -Dlinux -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fsigned-char -fno-strict-aliasing -std=c++11 -D_GNU_SOURCE -I/usr/include/x86_64-linux-gnu/ImageMagick-6 -I/usr/include/ImageMagick-6 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -c showboundary.c -fPIC -DPIC -o .libs/showboundary.o cc1: warning: command-line option ‘-std=c++11’ is valid for C++/ObjC++ but not for C libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../include -I../../../include
Bug#1074920: dolfinx-mpc: ftbfs with GCC-14
Package: src:dolfinx-mpc Version: 0.8.0.post1-4 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/dolfinx-mpc_0.8.0.post1-4_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] FAILED test_matrix_assembly.py::test_mpc_assembly[CellType.quadrilateral-1-master_point1-C++] FAILED test_matrix_assembly.py::test_mpc_assembly[CellType.quadrilateral-2-master_point0-C++] FAILED test_matrix_assembly.py::test_mpc_assembly[CellType.quadrilateral-2-master_point1-C++] FAILED test_matrix_assembly.py::test_mpc_assembly[CellType.quadrilateral-3-master_point0-C++] FAILED test_matrix_assembly.py::test_mpc_assembly[CellType.quadrilateral-3-master_point1-C++] FAILED test_matrix_assembly.py::test_mpc_assembly[CellType.triangle-1-master_point0-C++] FAILED test_matrix_assembly.py::test_mpc_assembly[CellType.triangle-1-master_point1-C++] FAILED test_matrix_assembly.py::test_mpc_assembly[CellType.triangle-2-master_point0-C++] FAILED test_matrix_assembly.py::test_mpc_assembly[CellType.triangle-2-master_point1-C++] FAILED test_matrix_assembly.py::test_mpc_assembly[CellType.triangle-3-master_point0-C++] FAILED test_matrix_assembly.py::test_mpc_assembly[CellType.triangle-3-master_point1-C++] FAILED test_matrix_assembly.py::test_slave_on_same_cell[CellType.triangle-1-master_point0-C++] FAILED test_matrix_assembly.py::test_slave_on_same_cell[CellType.triangle-1-master_point1-C++] FAILED test_matrix_assembly.py::test_slave_on_same_cell[CellType.triangle-2-master_point0-C++] FAILED test_matrix_assembly.py::test_slave_on_same_cell[CellType.triangle-2-master_point1-C++] FAILED test_matrix_assembly.py::test_slave_on_same_cell[CellType.triangle-3-master_point0-C++] FAILED test_matrix_assembly.py::test_slave_on_same_cell[CellType.triangle-3-master_point1-C++] FAILED test_matrix_assembly.py::test_slave_on_same_cell[CellType.quadrilateral-1-master_point0-C++] FAILED test_matrix_assembly.py::test_slave_on_same_cell[CellType.quadrilateral-1-master_point1-C++] FAILED test_matrix_assembly.py::test_slave_on_same_cell[CellType.quadrilateral-2-master_point0-C++] FAILED test_matrix_assembly.py::test_slave_on_same_cell[CellType.quadrilateral-2-master_point1-C++] FAILED test_matrix_assembly.py::test_slave_on_same_cell[CellType.quadrilateral-3-master_point0-C++] FAILED test_matrix_assembly.py::test_slave_on_same_cell[CellType.quadrilateral-3-master_point1-C++] FAILED test_mpc_pipeline.py::test_pipeline[master_point0-C++] - TypeError: __... FAILED test_mpc_pipeline.py::test_pipeline[master_point1-C++] - TypeError: __... FAILED test_mpc_pipeline.py::test_linearproblem[master_point0] - TypeError: _... FAILED test_mpc_pipeline.py::test_linearproblem[master_point1] - TypeError: _... FAILED test_nonlinear_assembly.py::test_nonlinear_poisson[1] - TypeError: cre... FAILED test_nonlinear_assembly.py::test_nonlinear_poisson[2] - TypeError: cre... FAILED test_nonlinear_assembly.py::test_nonlinear_poisson[3] - TypeError: cre... FAILED test_nonlinear_assembly.py::test_homogenize[1-0] - TypeError: create_p... FAILED test_nonlinear_assembly.py::test_homogenize[1-1] - TypeError: create_p... FAILED test_nonlinear_assembly.py::test_homogenize[1-2] - TypeError: create_p... FAILED test_nonlinear_assembly.py::test_homogenize[2-0] - TypeError: create_p... FAILED test_nonlinear_assembly.py::test_homogenize[2-1] - TypeError: create_p... FAILED test_nonlinear_assembly.py::test_homogenize[2-2] - TypeError: create_p... FAILED test_nonlinear_assembly.py::test_homogenize[3-0] - TypeError: create_p... FAILED test_nonlinear_assembly.py::test_homogenize[3-1] - TypeError: create_p... FAILED test_nonlinear_assembly.py::test_homogenize[3-2] - TypeError: create_p... FAILED test_rectangular_assembly.py::test_mixed_element[GhostMode.none-CellType.triangle] FAILED test_rectangular_assembly.py::test_mixed_element[GhostMode.none-CellType.quadrilateral] FAILED test_rectang
Bug#1074886: coda: ftbfs with GCC-14
Package: src:coda
Version: 2.25.2-1.1
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/coda_2.25.2-1.1_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
../../java/coda_jni.c:730:20: warning: ‘SWIG_JavaArrayOutFloat’ defined but not
used [-Wunused-function]
730 | static jfloatArray SWIG_JavaArrayOutFloat (JNIEnv *jenv, float *result,
jsize sz) {
|^~
../../java/coda_jni.c:684:19: warning: ‘SWIG_JavaArrayOutLonglong’ defined but
not used [-Wunused-function]
684 | static jlongArray SWIG_JavaArrayOutLonglong (JNIEnv *jenv, long long
*result, jsize sz) {
| ^
../../java/coda_jni.c:638:19: warning: ‘SWIG_JavaArrayOutUlong’ defined but not
used [-Wunused-function]
638 | static jlongArray SWIG_JavaArrayOutUlong (JNIEnv *jenv, unsigned long
*result, jsize sz) {
| ^~
../../java/coda_jni.c:630:13: warning: ‘SWIG_JavaArrayArgoutUlong’ defined but
not used [-Wunused-function]
630 | static void SWIG_JavaArrayArgoutUlong (JNIEnv *jenv, jlong *jarr,
unsigned long *carr, jlongArray input) {
| ^
../../java/coda_jni.c:609:12: warning: ‘SWIG_JavaArrayInUlong’ defined but not
used [-Wunused-function]
609 | static int SWIG_JavaArrayInUlong (JNIEnv *jenv, jlong **jarr, unsigned
long **carr, jlongArray input) {
|^
../../java/coda_jni.c:592:18: warning: ‘SWIG_JavaArrayOutLong’ defined but not
used [-Wunused-function]
592 | static jintArray SWIG_JavaArrayOutLong (JNIEnv *jenv, long *result,
jsize sz) {
| ^
../../java/coda_jni.c:546:19: warning: ‘SWIG_JavaArrayOutUint’ defined but not
used [-Wunused-function]
546 | static jlongArray SWIG_JavaArrayOutUint (JNIEnv *jenv, unsigned int
*result, jsize sz) {
| ^
../../java/coda_jni.c:538:13: warning: ‘SWIG_JavaArrayArgoutUint’ defined but
not used [-Wunused-function]
538 | static void SWIG_JavaArrayArgoutUint (JNIEnv *jenv, jlong *jarr,
unsigned int *carr, jlongArray input) {
| ^~~~
../../java/coda_jni.c:517:12: warning: ‘SWIG_JavaArrayInUint’ defined but not
used [-Wunused-function]
517 | static int SWIG_JavaArrayInUint (JNIEnv *jenv, jlong **jarr, unsigned
int **carr, jlongArray input) {
|^~~~
../../java/coda_jni.c:500:18: warning: ‘SWIG_JavaArrayOutInt’ defined but not
used [-Wunused-function]
500 | static jintArray SWIG_JavaArrayOutInt (JNIEnv *jenv, int *result, jsize
sz) {
| ^~~~
../../java/coda_jni.c:454:18: warning: ‘SWIG_JavaArrayOutUshort’ defined but
not used [-Wunused-function]
454 | static jintArray SWIG_JavaArrayOutUshort (JNIEnv *jenv, unsigned short
*result, jsize sz) {
| ^~~
../../java/coda_jni.c:446:13: warning: ‘SWIG_JavaArrayArgoutUshort’ defined but
not used [-Wunused-function]
446 | static void SWIG_JavaArrayArgoutUshort (JNIEnv *jenv, jint *jarr,
unsigned short *carr, jintArray input) {
| ^~
../../java/coda_jni.c:425:12: warning: ‘SWIG_JavaArrayInUshort’ defined but not
used [-Wunused-function]
425 | static int SWIG_JavaArrayInUshort (JNIEnv *jenv, jint **jarr, unsigned
short **carr, jintArray input) {
|^~
../../java/coda_jni.c:408:20: warning: ‘SWIG_JavaArrayOutShort’ defined but not
used [-Wunused-function]
408 | static jshortArray SWIG_JavaArrayOutShort (JNIEnv *jenv, short *result,
jsize sz) {
|^~
../../java/coda_jni.c:362:20: warning: ‘SWIG_JavaArrayOutUchar’ defined but not
used [-Wunused-function]
362 | static jshortArray SW
Bug#1074861: calculix-cgx: ftbfs with GCC-14
Package: src:calculix-cgx
Version: 2.21+dfsg-1
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/calculix-cgx_2.21+dfsg-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
generateTet.cpp:416:31: warning: ISO C++ forbids converting a string constant
to ‘char*’ [-Wwrite-strings]
416 | mnodSet=pre_seta("+mnodSet","i",0);
| ^~~
generateTet.cpp:417:18: warning: ISO C++ forbids converting a string constant
to ‘char*’ [-Wwrite-strings]
417 | setNr=pre_seta("+velemSet","i",0);
| ^~~
generateTet.cpp:417:30: warning: ISO C++ forbids converting a string constant
to ‘char*’ [-Wwrite-strings]
417 | setNr=pre_seta("+velemSet","i",0);
| ^~~
generateTet.cpp:428:41: warning: ISO C++ forbids converting a string constant
to ‘char*’ [-Wwrite-strings]
428 | for(k=0; k<3; k++)
seta(mnodSet,"n",e_enqire[surf[s].elem[i]].nod[k+3]);
| ^~~
generateTet.cpp:435:39: warning: ISO C++ forbids converting a string constant
to ‘char*’ [-Wwrite-strings]
435 | for(k=0; k<3; k++)
seta(snodSet,"n",e_enqire[surf[s].elem[i]].nod[k]);
| ^~~
generateTet.cpp:451:14: warning: ISO C++ forbids converting a string constant
to ‘char*’ [-Wwrite-strings]
451 | { errMsg("ERROR: realloc failure in generateTet\n"); return(0); }
| ^
generateTet.cpp:521:21: warning: ISO C++ forbids converting a string constant
to ‘char*’ [-Wwrite-strings]
521 | if ( ( readNG( "test.vol", anz_ng, &setx, &node_ng, &elem_ng,
NULL)) == -1)
| ^~
generateTet.cpp:579:14: warning: ISO C++ forbids converting a string constant
to ‘char*’ [-Wwrite-strings]
579 | { errMsg("ERROR: realloc failure in generateTet\n"); return(0); }
| ^
generateTet.cpp:652:82: warning: ISO C++ forbids converting a string constant
to ‘char*’ [-Wwrite-strings]
652 | elem_define(anz,&e_enqire, anz->enext++, 3, cgxtet, 1, eattr );
seta( setNr, "e", anz->emax );
|
^~~
generateTet.cpp:663:39: warning: ISO C++ forbids converting a string constant
to ‘char*’ [-Wwrite-strings]
663 | fixMidsideNodes( set[setNr].name, "gen" );
| ^
generateTet.cpp:665:23: warning: ISO C++ forbids converting a string constant
to ‘char*’ [-Wwrite-strings]
665 | snodSet2=pre_seta("+snodSet2","i",0);
| ^~~
generateTet.cpp:665:35: warning: ISO C++ forbids converting a string constant
to ‘char*’ [-Wwrite-strings]
665 | snodSet2=pre_seta("+snodSet2","i",0);
| ^~~
generateTet.cpp:683:25: warning: ISO C++ forbids converting a string constant
to ‘char*’ [-Wwrite-strings]
683 |
seta(snodSet2,"n",e_enqire[set[setNr].elem[k]].nod[nodseq_te10[n*3+1]]);
| ^~~
generateTet.cpp:691:41: warning: ISO C++ forbids converting a string constant
to ‘char*’ [-Wwrite-strings]
691 | for (n=0; n<10; n++) seta( setNr, "n",
e_enqire[set[setNr].elem[k]].nod[n] );
| ^~~
generateTet.cpp:694:39: warning: ISO C++ forbids converting a string constant
to ‘char*’ [-Wwrite-strings]
694 | fixMidsideNodes( set[setNr].name, "" );
| ^~
generateTet.cpp:700:40: warning: ISO C++ forbids converting a string constant
to ‘char*’ [-Wwrite-strings]
700 | for (n=0; n<4; n++) seta( setNr, "n",
e_enqire[set[setNr].elem[k]].nod[n] );
|^~~
generateTet.cpp
Bug#1074826: atlas-ecmwf: ftbfs with GCC-14
Package: src:atlas-ecmwf Version: 0.38.0-1 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/atlas-ecmwf_0.38.0-1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] cd /<>/debian/build/src/atlas && /usr/bin/c++ -DCGAL_USE_GMPXX=1 -Datlas_ecmwf_EXPORTS -I/<>/debian/build/src -I/<>/atlas_io/eckit_codec_adaptor/src -I/usr/lib/x86_64-linux-gnu/fortran/gfortran-mod-15/fckit -I/usr/include/x86_64-linux-gnu/fckit -I/usr/include/x86_64-linux-gnu/ectrans -I/usr/include/x86_64-linux-gnu/eckit -I/usr/include/x86_64-linux-gnu/eckit/geometry -I/usr/include/x86_64-linux-gnu/eckit/linalg -I/usr/include/x86_64-linux-gnu/eckit/maths -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -I/usr/include/x86_64-linux-gnu/eckit/mpi -I/usr/include/x86_64-linux-gnu/eckit/option -I/usr/include/x86_64-linux-gnu/eckit/codec -isystem /usr/include/eigen3 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -I/<>/src -I/<>/debian/build/src -I/<>/atlas_io/src -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -O3 -DNDEBUG -std=gnu++17 -fPIC -fopenmp -MD -MT src/atlas/CMakeFiles/atlas_ecmwf.dir/grid/detail/pl/classic_gaussian/N2000.cc.o -MF CMakeFiles/atlas_ecmwf.dir/grid/detail/pl/classic_gaussian/N2000.cc.o.d -o CMakeFiles/atlas_ecmwf.dir/grid/detail/pl/classic_gaussian/N2000.cc.o -c /<>/src/atlas/grid/detail/pl/classic_gaussian/N2000.cc [ 16%] Building CXX object src/atlas/CMakeFiles/atlas_ecmwf.dir/grid/detail/pl/classic_gaussian/N4000.cc.o cd /<>/debian/build/src/atlas && /usr/bin/c++ -DCGAL_USE_GMPXX=1 -Datlas_ecmwf_EXPORTS -I/<>/debian/build/src -I/<>/atlas_io/eckit_codec_adaptor/src -I/usr/lib/x86_64-linux-gnu/fortran/gfortran-mod-15/fckit -I/usr/include/x86_64-linux-gnu/fckit -I/usr/include/x86_64-linux-gnu/ectrans -I/usr/include/x86_64-linux-gnu/eckit -I/usr/include/x86_64-linux-gnu/eckit/geometry -I/usr/include/x86_64-linux-gnu/eckit/linalg -I/usr/include/x86_64-linux-gnu/eckit/maths -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -I/usr/include/x86_64-linux-gnu/eckit/mpi -I/usr/include/x86_64-linux-gnu/eckit/option -I/usr/include/x86_64-linux-gnu/eckit/codec -isystem /usr/include/eigen3 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -I/<>/src -I/<>/debian/build/src -I/<>/atlas_io/src -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -O3 -DNDEBUG -std=gnu++17 -fPIC -fopenmp -MD -MT src/atlas/CMakeFiles/atlas_ecmwf.dir/grid/detail/pl/classic_gaussian/N4000.cc.o -MF CMakeFiles/atlas_ecmwf.dir/grid/detail/pl/classic_gaussian/N4000.cc.o.d -o CMakeFiles/atlas_ecmwf.dir/grid/detail/pl/classic_gaussian/N4000.cc.o -c /<>/src/atlas/grid/detail/pl/classic_gaussian/N4000.cc [ 16%] Building CXX object src/atlas/CMakeFiles/atlas_ecmwf.dir/grid/detail/pl/classic_gaussian/N8000.cc.o cd /<>/debian/build/src/atlas && /usr/bin/c++ -DCGAL_USE_GMPXX=1 -Datlas_ecmwf_EXPORTS -I/<>/debian/build/src -I/<>/atlas_io/eckit_codec_adaptor/src -I/usr/lib/x86_64-linux-gnu/fortran/gfortran-mod-15/fckit -I/usr/include/x86_64-linux-gnu/fckit -I/usr/include/x86_64-linux-gnu/ectrans -I/usr/include/x86_64-linux-gnu/eckit -I/usr/include/x86_64-linux-gnu/eckit/geometry -I/usr/include/x86_64-linux-gnu/eckit/linalg -I/usr/include/x86_64-linux-gnu/eckit/maths -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -I/usr/include/x86_64-linux-gnu/eckit/mpi -I/usr/include/x86_64-linux-gnu/eckit/option -I/usr/include/x86_64-linux-gnu/eckit/codec -isystem /usr/include/eigen3 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -I/<>/src -I/<>/debian/build/src -I/<>/atlas_i
Bug#1069220: mrcal ftbfs with Python 3.12
On 18.04.24 09:09, Dima Kogan wrote: Thanks for the report, but I cannot reproduce. I upgraded my python3 install to what's currently in experimental: "python3" starts up 3.12.3, and mrcal builds just fine. Can I get the version of these packages please: - mrbuild - python3-numpy Any other specific suggestions would be good too. Thanks. seen here https://launchpad.net/ubuntu/+source/mrcal/2.4.1-1build2 maybe you need to wait until 3.12 is the default in Debian. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1069223: yp-svipc ftbfs with Python 3.12
Package: src:yp-svipc
Version: 0.16-5
Severity: important
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
[...]
dpkg-buildpackage: info: host architecture amd64
fakeroot debian/rules clean
dh clean --without python2 \
--with python3 \
--buildsystem=pybuild
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
debian/rules override_dh_auto_clean
make[1]: Entering directory '/<>'
cp -n yorick/Makefile yorick/Makefile.orig
cp: warning: behavior of -n is non-portable and may change in future;
use --update=none instead
cd yorick; yorick -batch make.i
updated ./Makefile
dh_auto_clean
dh_auto_clean: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
I: pybuild base:311: python3.12 setup.py clean
Traceback (most recent call last):
File "/<>/setup.py", line 21, in
from numpy.distutils.core import setup, Extension
ModuleNotFoundError: No module named 'numpy.distutils'
E: pybuild pybuild:389: clean: plugin distutils failed with: exit
code=1: python3.12 setup.py clean
dh_auto_clean: error: pybuild --clean -i python{version} -p 3.12
returned exit code 13
make[1]: *** [debian/rules:42: override_dh_auto_clean] Error 255
make[1]: Leaving directory '/<>'
make: *** [debian/rules:12: clean] Error 2
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1069220: mrcal ftbfs with Python 3.12
Package: src:mrcal Version: 2.4.1-1 Severity: important Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 [...] cc -Wall -Wextra -g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/<>=/usr/src/mrcal-2.4.1-1build2 --std=gnu99 -I/usr/include/suitesparse -Wno-array-bounds -Wno-cast-function-type -fno-strict-overflow -Wsign-compare -DNDEBUG -g -Wall -fPIC -I/usr/include/python3.12 -Wno-missing-field-initializers -Wno-unused-variable -Wno-unused-parameter -Wno-missing-braces -MMD -MP -g -fno-omit-frame-pointer -DMRBUILD_VERSION='"2.4.1-1build2"' -Wdate-time -D_FORTIFY_SOURCE=3 -c -o poseutils-npsp-pywrap-GENERATED.o poseutils-npsp-pywrap-GENERATED.c mrcal-pywrap.c:14:10: fatal error: numpy/arrayobject.h: No such file or directory 14 | #include | ^ compilation terminated. make[2]: *** [/usr/include/mrbuild/Makefile.common.footer:148: mrcal-pywrap.o] Error 1 make[2]: *** Waiting for unfinished jobs poseutils-npsp-pywrap-GENERATED.c:46:10: fatal error: numpy/arrayobject.h: No such file or directory 46 | #include | ^ mrcal-npsp-pywrap-GENERATED.c:40:10: fatal error: numpy/arrayobject.h: No such file or directory 40 | #include | ^ compilation terminated. compilation terminated. make[2]: *** [/usr/include/mrbuild/Makefile.common.footer:148: mrcal-npsp-pywrap-GENERATED.o] Error 1 make[2]: *** [/usr/include/mrbuild/Makefile.common.footer:148: poseutils-npsp-pywrap-GENERATED.o] Error 1 make[2]: Leaving directory '/<>' -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1067000: ros-diagnostics ftbfs with Python 3.12
Package: src:ros-diagnostics Version: 1.11.0+ds-4 Severity: important Tags: sid trixie patch User: debian-pyt...@lists.debian.org Usertags: python3.12 tests fail with Python 3.12, patch at http://launchpadlibrarian.net/719734251/ros-diagnostics_1.11.0+ds-4build4_1.11.0+ds-4ubuntu1.diff.gz -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1066999: ros-vision-opencv ftbfs with Python 3.12
Package: src:ros-vision-opencv Version: 1.16.2+ds-1 Severity: important Tags: sid trixie patch User: debian-pyt...@lists.debian.org Usertags: python3.12 tests fail with Python 3.12, patch at http://launchpadlibrarian.net/719733685/ros-vision-opencv_1.16.2+ds-1build4_1.16.2+ds-1ubuntu1.diff.gz -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1066946: fix ftbfs with Python 3.12
Package: src:ros-ros-comm Version: 1.16.0+ds-3.1 Severity: important Tags: sid trixie patch User: debian-pyt...@lists.debian.org Usertags: python3.12 tests fail with Python 3.12, patch at http://launchpadlibrarian.net/719571248/ros-ros-comm_1.16.0+ds-3.1build2_1.16.0+ds-3.1ubuntu1.diff.gz -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1063796: use chrpath instead of patchelf (broken on mips64el)
Control: tags -1 + patch use chrpath instead of patchelf (broken on mips64el) diff -Nru plplot-5.15.0+dfsg2/debian/changelog plplot-5.15.0+dfsg2/debian/changelog --- plplot-5.15.0+dfsg2/debian/changelog 2024-01-19 12:24:17.0 +0100 +++ plplot-5.15.0+dfsg2/debian/changelog 2024-02-29 01:58:07.0 +0100 @@ -1,3 +1,10 @@ +plplot (5.15.0+dfsg2-7.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Use chrpath instead of patchelf. Closes: #1063796. + + -- Matthias Klose Thu, 29 Feb 2024 01:58:07 +0100 + plplot (5.15.0+dfsg2-7+deb13u1) unstable; urgency=medium * d/rules: Avoid FTBFS on armhf. diff -Nru plplot-5.15.0+dfsg2/debian/control plplot-5.15.0+dfsg2/debian/control --- plplot-5.15.0+dfsg2/debian/control 2024-01-19 12:24:17.0 +0100 +++ plplot-5.15.0+dfsg2/debian/control 2024-02-29 01:58:07.0 +0100 @@ -6,6 +6,7 @@ Rafael Laboissière Standards-Version: 4.6.2 Build-Depends: camlidl, + chrpath, cmake (>= 2.6.3), debhelper-compat (= 13), default-jdk, @@ -37,7 +38,6 @@ m4, ocaml-findlib, ocaml-nox, - patchelf, pkg-config, pyqt5-dev, python3-dev, diff -Nru plplot-5.15.0+dfsg2/debian/rules plplot-5.15.0+dfsg2/debian/rules --- plplot-5.15.0+dfsg2/debian/rules 2024-01-19 12:24:17.0 +0100 +++ plplot-5.15.0+dfsg2/debian/rules 2024-02-29 01:58:07.0 +0100 @@ -84,7 +84,7 @@ debian/tmp/usr/share/plplot*/examples/tk/tk* # Remove RUNPATH from OCaml binding library - patchelf --remove-rpath debian/tmp/usr/lib/ocaml/stublibs/dllplplot_stubs.so + chrpath --delete debian/tmp/usr/lib/ocaml/stublibs/dllplplot_stubs.so dh_numpy3 -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1064426: evolver fails the last two autopkg tests with glibc 2.39 on amd64
Package: src:evolver Version: 2.70+ds-8 Severity: important Tags: sid trixie evolver fails the last two autopkg tests with glibc 2.39 on amd64. Currently only seen in Ubuntu noble. The segfaults are also seen when building without link time optimization, and when building with -O0. https://bugs.launchpad.net/ubuntu/+source/evolver/+bug/2052929 However the build shows many format-overflow and stringop-overflow warnings already present in the Debian build. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1063410: ros-bloom's autopkg tests fail with Python 3.12
Package: src:ros-bloom
Version: 0.11.2-6
Severity: important
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
ros-bloom's autopkg tests fail with Python 3.12
[...]
578s = test session starts
==
578s platform linux -- Python 3.12.1, pytest-7.4.4, pluggy-1.3.0
578s rootdir: /tmp/tmp.BgIMXvxH90
578s collected 2 items / 5 errors
578s
578s ERRORS
578s ERROR collecting test/system_tests/test_bloom_setup.py
578s /usr/lib/python3/dist-packages/bloom/rosdistro_api.py:60: in
578s import rosdistro
578s /usr/lib/python3/dist-packages/rosdistro/__init__.py:51: in
578s from .distribution import Distribution # noqa
578s /usr/lib/python3/dist-packages/rosdistro/distribution.py:35: in
578s from .manifest_provider.git import git_manifest_provider,
git_source_manifest_provider
578s
/usr/lib/python3/dist-packages/rosdistro/manifest_provider/git.py:44: in
578s from rosdistro.vcs import Git, ref_is_hash
578s /usr/lib/python3/dist-packages/rosdistro/vcs.py:39: in
578s from distutils.version import LooseVersion
578s E ModuleNotFoundError: No module named 'distutils'
578s
578s During handling of the above exception, another exception occurred:
578s test/system_tests/test_bloom_setup.py:13: in
578s from bloom.config import BLOOM_CONFIG_BRANCH
578s /usr/lib/python3/dist-packages/bloom/config.py:60: in
578s from bloom.rosdistro_api import get_non_eol_distros_prompt
578s /usr/lib/python3/dist-packages/bloom/rosdistro_api.py:67: in
578s error("rosdistro was not detected, please install it.",
file=sys.stderr,
578s /usr/lib/python3/dist-packages/bloom/logging.py:280: in error
578s sys.exit(msg)
578s E SystemExit: [31m[1mrosdistro was not detected, please install
it.[0m
578s __ ERROR collecting
test/system_tests/test_catkin_release.py ___
578s test/system_tests/test_catkin_release.py:12: in
578s from vcstools.vcs_abstraction import get_vcs_client
578s /usr/lib/python3/dist-packages/vcstools/__init__.py:47: in
578s from vcstools.git import GitClient
578s /usr/lib/python3/dist-packages/vcstools/git.py:63: in
578s from distutils.version import LooseVersion
578s E ModuleNotFoundError: No module named 'distutils'
578s
578s During handling of the above exception, another exception occurred:
578s test/system_tests/test_catkin_release.py:15: in
578s sys.exit(1)
578s E SystemExit: 1
578s --- Captured stderr
578s vcstools was not detected, please install it.
578s ___ ERROR collecting test/unit_tests/test_config.py
578s /usr/lib/python3/dist-packages/bloom/rosdistro_api.py:60: in
578s import rosdistro
578s /usr/lib/python3/dist-packages/rosdistro/__init__.py:51: in
578s from .distribution import Distribution # noqa
578s /usr/lib/python3/dist-packages/rosdistro/distribution.py:35: in
578s from .manifest_provider.git import git_manifest_provider,
git_source_manifest_provider
578s
/usr/lib/python3/dist-packages/rosdistro/manifest_provider/git.py:44: in
578s from rosdistro.vcs import Git, ref_is_hash
578s /usr/lib/python3/dist-packages/rosdistro/vcs.py:39: in
578s from distutils.version import LooseVersion
578s E ModuleNotFoundError: No module named 'distutils'
578s
578s During handling of the above exception, another exception occurred:
578s test/unit_tests/test_config.py:6: in
578s from bloom.config import validate_track_versions
578s /usr/lib/python3/dist-packages/bloom/config.py:60: in
578s from bloom.rosdistro_api import get_non_eol_distros_prompt
578s /usr/lib/python3/dist-packages/bloom/rosdistro_api.py:67: in
578s error("rosdistro was not detected, please install it.",
file=sys.stderr,
578s /usr/lib/python3/dist-packages/bloom/logging.py:280: in error
578s sys.exit(msg)
578s E SystemExit: [31m[1mrosdistro was not detected, please install
it.[0m
578s __ ERROR collecting test/unit_tests/test_packages.py
___
578s /usr/lib/python3/dist-packages/bloom/rosdistro_api.py:60: in
578s import rosdistro
578s /usr/lib/python3/dist-packages/rosdistro/__init__.py:51: in
578s from .distribution import Distribution # noqa
578s /usr/lib/python3/dist-packages/rosdistro/distribution.py:35: in
578s from .manifest_provider.git import git_manifest_provider,
git_source_manifest_provider
578s
/usr/lib/python3/dist-packages/rosdistro/manifest_provider/git.py:44: in
578s from rosdistro.vcs import Git, ref_is_hash
578s /usr/lib/python3/dist-packages/rosdistro/vcs.py:39: in
578s from distutils.version import LooseVersion
578s E ModuleNotFoundError: No module named 'distutils'
578s
578s During handling of the above exception, another exception occurred:
578s test/unit_tests
Bug#1061813: add patch
Control: tags -1 + patch patch at http://launchpadlibrarian.net/713303806/mpi4py_3.1.5-4_3.1.5-4ubuntu1.diff.gz -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1063409: mpi4py accesses the net for the build
Package: src:mpi4py
Version: 3.1.5-4
Severity: serious
Tags: sid trixie
at least the first repository should be available in the python3-doc
package.
[...]
make -C docs/source/usrman/ html man info latexpdf SPHINXOPTS="-D
today=\"January 14, 2024\""
make[2]: Entering directory '/<>/docs/source/usrman'
Running Sphinx v7.2.6
making output directory... done
[autosummary] generating autosummary for: appendix.rst, citing.rst,
index.rst, install.rst, intro.rst, mpi4py.MPI.rst, mpi4py.futures.rst,
mpi4py.rst, mpi4py.run.rst, mpi4py.util.dtlib.rst, mpi4py.util.pkl5.rst,
mpi4py.util.rst, overview.rst, reference.rst, tutorial.rst
[autosummary] generating autosummary for:
/<>/docs/source/usrman/reference/mpi4py.MPI.rst
loading intersphinx inventory from https://docs.python.org/3/objects.inv...
loading intersphinx inventory from
https://numpy.org/doc/stable/objects.inv...
WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://numpy.org/doc/stable/objects.inv' not
fetchable due to :
HTTPSConnectionPool(host='numpy.org', port=443): Max retries exceeded
with url: /doc/stable/objects.inv (Caused by ProxyError('Cannot connect
to proxy.', NewConnectionError('object at 0x7fec6bad3e90>: Failed to establish a new connection: [Errno
111] Connection refused')))
WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://docs.python.org/3/objects.inv' not
fetchable due to :
HTTPSConnectionPool(host='docs.python.org', port=443): Max retries
exceeded with url: /3/objects.inv (Caused by ProxyError('Cannot connect
to proxy.', NewConnectionError('object at 0x7fec6baa4550>: Failed to establish a new connection: [Errno
111] Connection refused')))
building [mo]: targets for 0 po files that are out of date
writing output...
building [html]: targets for 15 source files that are out of date
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1063358: c-blosc2 tests fail with bus errors on armhf
Package: src:c-blosc2 Version: 2.13.1+ds-1 Severity: important Tags: sid trixie c-blosc2 tests fail with bus errors on armhf, only seen on the Ubuntu buildds, which have the alignment checks turned on in the kernel. The following tests FAILED: 1 - test_plugin_test_ndlz (Bus error) 2 - test_plugin_test_zfp_acc_float (Bus error) 3 - test_plugin_test_zfp_prec_float (Bus error) 4 - test_plugin_test_zfp_rate_float (Bus error) 5 - test_plugin_test_zfp_rate_getitem (Bus error) 6 - test_plugin_test_ndcell (Bus error) 7 - test_plugin_ndmean_repart (Bus error) 8 - test_plugin_ndmean_mean (Bus error) 9 - test_plugin_bytedelta (Bus error) 11 - test_b2nd_append (Bus error) 12 - test_b2nd_copy (Bus error) 14 - test_b2nd_delete (Bus error) 15 - test_b2nd_full (Bus error) 16 - test_b2nd_get_slice (Bus error) 17 - test_b2nd_get_slice_buffer (Bus error) 18 - test_b2nd_insert (Bus error) 22 - test_b2nd_resize (Bus error) 23 - test_b2nd_roundtrip (Bus error) 24 - test_b2nd_save (Bus error) 25 - test_b2nd_serialize (Bus error) 26 - test_b2nd_set_slice_buffer (Bus error) 27 - test_b2nd_squeeze (Bus error) 28 - test_b2nd_squeeze_index (Bus error) 30 - test_b2nd_zeros (Bus error) 310 - test_fill_special (Bus error) Errors while running CTest make[2]: *** [Makefile:94: test] Error 8 make[2]: Leaving directory '/<>/obj-arm-linux-gnueabihf' I also checked that building with or without link time optimization doesn't make any difference. -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1062809: dh-fortran-mod's autopkg tests fail
Package: dh-fortran-mod Version: 0.37 Severity: serious this blocks migration of gcc-defaults: [...] 40s autopkgtest [11:14:38]: test debhelper-interaction: [--- 40s /usr/share/debhelper/dh-fortran/fortran-support.mk:144: *** missing separator (did you mean TAB instead of 8 spaces?). Stop. 40s autopkgtest [11:14:38]: test debhelper-interaction: ---] 40s autopkgtest [11:14:38]: test debhelper-interaction: - - - - - - - - - - results - - - - - - - - - - 40s debhelper-interaction FAIL non-zero exit status 2 40s autopkgtest [11:14:38]: test debhelper-interaction: - - - - - - - - - - stderr - - - - - - - - - - 40s /usr/share/debhelper/dh-fortran/fortran-support.mk:144: *** missing separator (did you mean TAB instead of 8 spaces?). Stop. 40s autopkgtest [11:14:38]: summary 40s debhelper-interaction FAIL non-zero exit status 2 -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1061858: wannier90 fails its autopkg tests with Python 3.12
Package: src:wannier90
Version: 3.1.0+ds-7
Severity: important
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
With python3-defaults from experimental, the package fails its autopkg
tests:
[...]
808s autopkgtest [14:33:03]: test upstream: ---]
808s upstream FAIL stderr:
/tmp/autopkgtest.o659zE/autopkgtest_tmp/test-suite/testcode/bin/testcode.py:354:
SyntaxWarning: invalid escape sequence '\*'autopkgtest [14:33:03]: test
upstream: - - - - - - - - - - results - - - - - - - - - -
808s
808s autopkgtest [14:33:03]: test upstream: - - - - - - - - - - stderr
- - - - - - - - - -
808s
/tmp/autopkgtest.o659zE/autopkgtest_tmp/test-suite/testcode/bin/testcode.py:354:
SyntaxWarning: invalid escape sequence '\*'
808s wildcards = re.compile('.*(\*|\?|\[.*\]).*')
808s
/tmp/autopkgtest.o659zE/autopkgtest_tmp/test-suite/tools/parsers/parse_wout.py:17:
SyntaxWarning: invalid escape sequence '\s'
808s near_neigh_re = re.compile("^\s*\|\s+(\d+)\s+([\d\.]+)\s*(\d+)\s*")
808s
/tmp/autopkgtest.o659zE/autopkgtest_tmp/test-suite/tools/parsers/parse_wout.py:27:
SyntaxWarning: invalid escape sequence '\s'
808s completeness_re =
re.compile("^\s*\|\s+(\d+)\s+([\d\.-]+)\s+([\d\.-]+)\s+([\d\.-]+)\s*([\d\.]+)\s*")
808s
/tmp/autopkgtest.o659zE/autopkgtest_tmp/test-suite/tools/parsers/parse_wout.py:36:
SyntaxWarning: invalid escape sequence '\s'
808s spread_re = re.compile("^\s*WF centre and
spread\s+(\d+)\s+\(\s*([0-9\.-]+)\s*,\s*([0-9\.-]+)\s*,\s*([0-9\.-]+)\s*\)\s*([0-9\.-]+)\s*$")
808s
/tmp/autopkgtest.o659zE/autopkgtest_tmp/test-suite/tools/parsers/parse_wout.py:41:
SyntaxWarning: invalid escape sequence '\ '
808s omegaI_re = re.compile("Omega\ I\s+=\s*([0-9\.-]+)\s*$")
808s
/tmp/autopkgtest.o659zE/autopkgtest_tmp/test-suite/tools/parsers/parse_wout.py:42:
SyntaxWarning: invalid escape sequence '\ '
808s omegaD_re = re.compile("Omega\ D\s+=\s*([0-9\.-]+)\s*$")
808s
/tmp/autopkgtest.o659zE/autopkgtest_tmp/test-suite/tools/parsers/parse_wout.py:43:
SyntaxWarning: invalid escape sequence '\ '
808s omegaOD_re = re.compile("Omega\ OD\s+=\s*([0-9\.-]+)\s*$")
808s
/tmp/autopkgtest.o659zE/autopkgtest_tmp/test-suite/tools/parsers/parse_wout.py:44:
SyntaxWarning: invalid escape sequence '\ '
808s omegaTotal_re = re.compile("Omega\ Total\s+=\s*([0-9\.-]+)\s*$")
808s
/tmp/autopkgtest.o659zE/autopkgtest_tmp/test-suite/tools/parsers/parse_wout.py:45:
SyntaxWarning: invalid escape sequence '\ '
808s omegaIOD_C_re = re.compile("Omega\ IOD_C\s+=\s*([0-9\.-]+)\s*$")
808s
/tmp/autopkgtest.o659zE/autopkgtest_tmp/test-suite/tools/parsers/parse_wout.py:46:
SyntaxWarning: invalid escape sequence '\ '
808s omegaRest_re = re.compile("Omega\ Rest\s+=\s*([0-9\.-]+)\s*$")
808s
/tmp/autopkgtest.o659zE/autopkgtest_tmp/test-suite/tools/parsers/parse_wout.py:47:
SyntaxWarning: invalid escape sequence '\ '
808s penaltyfunc_re = re.compile("Penalty\ func\s+=\s*([0-9\.-]+)\s*$")
808s
/tmp/autopkgtest.o659zE/autopkgtest_tmp/test-suite/tools/parsers/parse_wout.py:48:
SyntaxWarning: invalid escape sequence '\ '
808s omegaTotal_C_re = re.compile("Omega\ Total_C\s+=\s*([0-9\.-]+)\s*$")
808s
/tmp/autopkgtest.o659zE/autopkgtest_tmp/test-suite/tools/parsers/parse_wpout.py:16:
SyntaxWarning: invalid escape sequence '\s'
808s near_neigh_re = re.compile("^\s*\|\s+(\d+)\s+([\d\.]+)\s*(\d+)\s*")
808s
/tmp/autopkgtest.o659zE/autopkgtest_tmp/test-suite/tools/parsers/parse_wpout.py:26:
SyntaxWarning: invalid escape sequence '\s'
808s completeness_re =
re.compile("^\s*\|\s+(\d+)\s+([\d\.-]+)\s+([\d\.-]+)\s+([\d\.-]+)\s*([\d\.]+)\s*")
808s
/tmp/autopkgtest.o659zE/autopkgtest_tmp/test-suite/tools/parsers/parse_wpout.py:35:
SyntaxWarning: invalid escape sequence '\s'
808s spread_re = re.compile("^\s*WF centre and
spread\s+(\d+)\s+\(\s*([0-9\.-]+)\s*,\s*([0-9\.-]+)\s*,\s*([0-9\.-]+)\s*\)\s*([0-9\.-]+)\s*$")
808s
/tmp/autopkgtest.o659zE/autopkgtest_tmp/test-suite/tools/parsers/parse_wpout.py:42:
SyntaxWarning: invalid escape sequence '\s'
808s ahc_re =
re.compile("^\s*==\s+([-+]?[0-9]*\.?[0-9]+)\s+([-+]?[0-9]*\.?[0-9]+)\s+([-+]?[0-9]*\.?[0-9]+)\s*")
808s
/tmp/autopkgtest.o659zE/autopkgtest_tmp/test-suite/tools/parsers/parse_wpout.py:50:
SyntaxWarning: invalid escape sequence '\s'
808s morb_re =
re.compile("^\s*==\s+([-+]?[0-9]*\.?[0-9]+)\s+([-+]?[0-9]*\.?[0-9]+)\s+([-+]?[0-9]*\.?[0-9]+)\s*")
808s
/tmp/autopkgtest.o659zE/autopkgtest_tmp/test-suite/tools/parsers/parse_wpout.py:54:
SyntaxWarning: invalid escape sequence '\ '
808s spinx_re = re.compile("x\ component:\s*([0-9\.-]+)\s*$")
808s
/tmp/autopkgtest.o659zE/autopkgtest_tmp/test-suite/tools/parsers/parse_wpout.py:55:
SyntaxWarning: invalid escape sequence '\ '
808s spiny_re = re.compile("y\ component:\s*([0-9\.-]+)\s*$")
808s
/tmp/autopkgtest.o659zE/autopkgtest_tmp/test-suite/tools/parsers/parse_wpout.py:56:
SyntaxWarning: invalid escape se
Bug#1061843: siconos fails its autopkg tests with Python 3.12
Package: src:siconos Version: 4.4.0+dfsg-3 Severity: important Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 With python3-defaults from experimental, the package fails its autopkg tests: [...] 2449s autopkgtest [14:52:26]: test mechanics-tools: [--- 2449s test_cube_scene_info_filter_compare 2449s Wrote cube_scene.hdf5 2450s No module named siconos.fclib. 2454s Traceback (most recent call last): 2454s File "/usr/bin/siconos_run", line 43, in 2454s from siconos.io.mechanics_run import MechanicsHdf5Runner 2454s File "/usr/lib/python3/dist-packages/siconos/io/mechanics_run.py", line 43, in 2454s from siconos.io.FrictionContactTrace import GlobalFrictionContactTrace as GFCTrace 2454s File "/usr/lib/python3/dist-packages/siconos/io/FrictionContactTrace.py", line 41, in 2454s import imp 2454s ModuleNotFoundError: No module named 'imp' 2454s [1;31mASSERT:[0munknown failure encountered running a test 2454s 2454s Ran [1;36m1[0m test. 2454s 2454s [1;31mFAILED[0m ([1;31mfailures=1[0m) 2454s autopkgtest [14:52:31]: test mechanics-tools: ---] 2455s autopkgtest [14:52:32]: test mechanics-tools: - - - - - - - - - - results - - - - - - - - - - 2455s mechanics-tools FAIL non-zero exit status 2 -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
