Autopkgtests fail with version 2.3.3+dfsg-0ubuntu1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ogre-next (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Both the tests listed in debian/
The tests fail with a CMake error. CMake isn't able to find package configuration file provided by OGRE-Next:
---
1334s By not providing "FindOGRE-
1334s has asked CMake to find a package configuration file provided by
1334s "OGRE-Next", but CMake did not find one.
1334s
1334s Could not find a package configuration file provided by "OGRE-Next" with
1334s any of the following names:
1334s
1334s OGRE-NextConfig
1334s ogre-next-
1334s
1334s Add the installation prefix of "OGRE-Next" to CMAKE_PREFIX_PATH or set
1334s "OGRE-Next_DIR" to a directory containing one of the above files. If
1334s "OGRE-Next" provides a separate development package or SDK, be sure it has
1334s been installed.
---
I can see that the latest release did a massive clean-up of debian/rules and we stopped shipping the OGRE-NextConfig
$ dpkg -c libogre-
-rw-r--r-- root/root 26057 2024-04-01 01:50 ./usr/lib/
$ dpkg -c libogre-
$
Related branches
- Dave Jones (community): Approve
-
Diff: 80 lines (+13/-11)3 files modifieddebian/changelog (+8/-0)
debian/extras/OGRE-NextConfig.cmake (+0/-10)
debian/rules (+5/-1)
I did some investigation. I realize there are changes upstream which allow the co-existence of OGRE and OGRE-Next projects. But, based in the limited time I spent, and if IIUC the CMake setup, FingOGRE.cmake does not provide the package configuration for OGRE-Next.
We probably need to reinstate the OGRE-NextConfig file?