Your message dated Thu, 22 Jan 2026 13:06:23 +0000
with message-id <[email protected]>
and subject line Bug#1125763: fixed in ros-laser-geometry 1.6.7-6
has caused the Debian Bug report #1125763,
regarding ros-laser-geometry FTBFS with CMake 4
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1125763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1125763
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ros-laser-geometry
Version: 1.6.7-5
Severity: serious
Tags: ftbfs patch forky sid
Forwarded: 
https://github.com/ros-perception/laser_geometry/commit/d39ce225c9e6706043638f8e768d6627fd879643
X-Debbugs-Cc: Timo Röhling <[email protected]>

https://buildd.debian.org/status/fetch.php?pkg=ros-laser-geometry&arch=amd64&ver=1.6.7-5%2Bb3&stamp=1768615051&raw=0

...
CMake Error at CMakeLists.txt:1 (cmake_minimum_required):
  Compatibility with CMake < 3.5 has been removed from CMake.

  Update the VERSION argument <min> value.  Or, use the <min>...<max> syntax
  to tell CMake that the project requires at least <min> but has been updated
  to work with policies introduced by <max> or earlier.

  Or, add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to try configuring anyway.


-- Configuring incomplete, errors occurred!
...


Increasing cmake_minimum_required in CMakeLists.txt to 3.5 fixes
the build.

--- End Message ---
--- Begin Message ---
Source: ros-laser-geometry
Source-Version: 1.6.7-6
Done: Timo Röhling <[email protected]>

We believe that the bug you reported is fixed in the latest version of
ros-laser-geometry, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Timo Röhling <[email protected]> (supplier of updated ros-laser-geometry 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 22 Jan 2026 13:37:45 +0100
Source: ros-laser-geometry
Architecture: source
Version: 1.6.7-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 
<[email protected]>
Changed-By: Timo Röhling <[email protected]>
Closes: 1125763
Changes:
 ros-laser-geometry (1.6.7-6) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse.
 .
   [ Timo Röhling ]
   * Migrate debian/watch to version 5 format
   * Wrap and sort Debian package files
   * Bump Standards-Version to 4.7.3
   * Migrate to dh-ros (Closes: #1125763)
   * Add myself to uploaders
Checksums-Sha1:
 c27b83e527896105b0d8c59380524534f2f379f9 2707 ros-laser-geometry_1.6.7-6.dsc
 b4f1f71b1198312ca1d9fc1b58f4d7e35d6d37eb 4248 
ros-laser-geometry_1.6.7-6.debian.tar.xz
Checksums-Sha256:
 5ac2b9006121408bbecbbc29422b2aa24c38a3a8dff23a3e13c174dce5942a43 2707 
ros-laser-geometry_1.6.7-6.dsc
 b1b49b1d3b0fb5daf982e09d2229536a51c85ccb0334148eaab3cfce3e400e39 4248 
ros-laser-geometry_1.6.7-6.debian.tar.xz
Files:
 a9df9abcbfa5f3e359c53707c7a47516 2707 libs optional 
ros-laser-geometry_1.6.7-6.dsc
 c51bf83f8ed4c4f6b3fa533a81931b0e 4248 libs optional 
ros-laser-geometry_1.6.7-6.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEmwPruYMA35fCsSO/zIxr3RQD9MoFAmlyHD8ACgkQzIxr3RQD
9MpzKQ/+L0/auMEokEdZwtjqBLw3Jlt3Q7ooS6KnDvMQK47atFlptI+9fvxejAsO
o9KcxB2Kr9KrV8seMx3E9yKjxfqDPoGvTXnPgNWXxyleWdyjAZlTijY4JECrt06C
QMhTDhA0oNTUBYA5oL4LBoPn50CWd44u3EX12M+gmWabwpuTr8tlMHGvSTpEBbZ+
G1MCETrNRjAUV0oRGbninlcSX8LlYMfe4+XG08KggdQQiPXy1lGWLs4JvratFKLf
ni03JhftohoPAi9uAiUshiP2RF25rxH/BjqLGG/FDFr1rhMqDtw4uQD1Sif1x9oQ
8cN2ymSNyybOAs9vsgNd5/KH6EA436tIQ3q7PPbtzUwxBUCUwj4S2zdAO0BWNKw0
Tf1fYfVfzXuKgNP20KevmJ6wk5816IAaiWk6MyuzGJq3lheKSBvKjw5if7p4YFhc
CZPkgUKCQLHOfp0zVcEZly5PE7G26iQl37QueFqReDfyi9jF1DKuEwixSCX55Hsx
eVxrjvdsRlx4B33YwhVoW9UMIjPyzvi3Q7i2sWCYS+30Iz7uoafGMCptYQhS6JTx
cenOOPtlovJ/VXGr0/VYjuaPMDkL9Mvl5gz9/M+j07nBe1l+61p0mI12y/YUT19W
k7+i7auR56laBRj/Q9Bw4MyQMQjfJIsa23YRUoWbH8RuCYUqCUs=
=PdnV
-----END PGP SIGNATURE-----

Attachment: pgpDynaHk1RjK.pgp
Description: PGP signature


--- End Message ---

Reply via email to