Debian Science Project
Summary
Bugs of task robotics-dev
Total bugs: 40
Open bugs: 26
Fixed bugs: 14
Links to other tasks
Biology 14 (194)
Chemistry 80 (876)
Data acquisition 51 (205)
Data management 53 (480)
Devices 6 (105)
Economics 32 (117)
Engineering 90 (983)
Engineering-dev 43 (460)
Geography 73 (475)
Geometry 4 (21)
Linguistics 94 (376)
Logic 39 (261)
Machine learning 53 (450)
Mathematics 247 (2059)
Mathematics-dev 176 (1676)
Meteorology 76 (497)
Meteorology-dev 189 (734)
Nanoscale physics 323 (2381)
Physics 82 (921)
Physics-dev 34 (347)
Presentation 91 (750)
Psychophysics 19 (198)
Robotics 121 (569)
Robotics-dev 26 (300)
Simulations 39 (412)
Social 0 (0)
Statistics 60 (386)
Tools 19 (120)
Typesetting 292 (1941)
Viewing 299 (1734)
Viewing-dev 56 (540)
Workflow 28 (207)
Legend
SeverityDependentSuggested
critical 0 0
grave 0 0
serious 5 1
important 5 1
normal 4 0
minor 8 0
wishlist 2 0

Summary bugs page of task Robotics-dev

Immediately looking into bugs of the dependencies of this task is advised (300)*

Open bugs in dependent packages

5 serious, 5 important, 4 normal, 8 minor, 2 wishlist
1035120 apriltag: please add autopkgtests (to add coverage for python3-numpy)
998784 comedilib: bashism in configure script ftbfs
1015375 comedilib: ftbfs with LTO (link time optimization) enabled forky, sid, trixie
1037300 comedilib: reproducible-builds: Embedded buildpaths and usrmerge paths in various files patch
1072752 libcomedi0t64: contains soname-independent library support files
1105158 python3-comedilib: Python 3 comedi module cannot be imported with "import comedi"
973329 Use system libimgui-dev
705593 ode: embeds sourceless binary ./build/premake4.exe
1036483 ompl: please add autopkgtests (to add coverage for python3-matplotlib)
1045703 ompl: Fails to build source after successful build forky, ftbfs, sid, trixie
1131074 python-meshplex: autopkgtest regression with NumPy 2.4
1015652 robot-testing-framework: ftbfs with LTO (link time optimization) enabled forky, sid, trixie
1075449 robot-testing-framework: ftbfs with GCC-14 forky, ftbfs, sid, trixie
1123986 Should robot-testing-framework be removed from unstable?
916479 libtf2-dev has circular Depends on libtf2-geometry-msgs-dev fixed-upstream
1129838 ros-geometry2: FTBFS with boost 1.90 forky, ftbfs, sid
1129844 ros-kdl-parser: FTBFS with boost 1.90 forky, ftbfs, sid
1116113 ros-simulators: recommends gazebo9 which is not in unstable
1116114 ros-simulators-dev: recommends libgazebo9-dev which is not in unstable
1129846 ros-perception-pcl: FTBFS with boost 1.90 forky, ftbfs, sid
1129854 ros-urdf: FTBFS with boost 1.90 forky, ftbfs, sid
983954 simbody: ftbfs with -march=x86-64-v3
1024526 simbody: FTBFS on ppc64el, mips64el bookworm, ftbfs, sid
1129442 urdfdom-headers: debaudit/git2dsc regression in 2.1.0-1: 330 - failed to guess tag

Open bugs in suggested packages

1 serious, 1 important
1125545 libelas: FTBFS with CMake 4.2 forky, ftbfs, sid
1131061 mrgingham: autopkgtest regression with NumPy 2.4

Done bugs

1127034 ompl ftbfs with boost 1.90 forky, ftbfs, patch, sid
1127254 pcl: libboost-system-dev package is obsolete with boost 1.89 and newer forky, sid
1129482 pcl FTCBFS: unsatisfiable sphinx dependency patch
1129775 pcl: FTBFS: Could NOT find Boost: Found unsuitable version "1.90.0" forky, ftbfs, sid
1127273 ros-rosconsole: libboost-system-dev package is obsolete with boost 1.89 and newer forky, ftbfs, sid
1129832 ros-bond-core: FTBFS with boost 1.90 forky, ftbfs, sid
1129833 ros-actionlib: FTBFS with boost 1.90 forky, ftbfs, sid
1129839 ros-image-common: FTBFS with boost 1.90 forky, ftbfs, sid
1129841 ros-image-pipeline: FTBFS with boost 1.90 forky, ftbfs, sid
1129842 ros-interactive-markers: FTBFS with boost 1.90 forky, ftbfs, sid
1129845 ros-nodelet-core: FTBFS with boost 1.90 forky, ftbfs, sid
1129847 ros-opencv-apps: FTBFS with boost 1.90 forky, ftbfs, sid
1129852 ros-rosconsole-bridge: FTBFS with boost 1.90 forky, ftbfs, sid
1129853 ros-vision-opencv: FTBFS with boost 1.90 forky, ftbfs, sid
*To estimate the overall status of the packages in the dependencies of a metapackage a weighted severity is calculated. Done bugs are ignored and bugs in dependent and recommended packages are weighted by factor three compared to suggested packages. Release critical bugs have a much larger weight than important, while the contribution of normal bugs is even smaller and minor bugs have a very small weight. Wishlist bugs are ignored in this calculation. The resulting sum is compared to some boundaries to find a verbal form. The actual numbers need some adjustment to make real sense - this evaluation method is in testing phase.
The severities of bugs are weighted as follows:
critical10
grave10
serious10
important5
normal3
minor1
wishlist0
Last update: Sat, 21 Mar 2026 16:10:05 -0000