Autopkgtests fail with version 2.3.3+dfsg-0ubuntu1

Bug #2062378 reported by Pushkar Kulkarni
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ogre-next (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Both the tests listed in debian/tests/control fail on all archs. Here is an example [1]

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-Next.cmake" in CMAKE_MODULE_PATH this project
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.cmake
1334s ogre-next-config.cmake
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.cmake file through libogre-next-dev*.deb.

$ dpkg -c libogre-next-dev_2.2.5+dfsg3-0ubuntu4_amd64.deb | grep "OGRE-NextConfig.cmake"
-rw-r--r-- root/root 26057 2024-04-01 01:50 ./usr/lib/x86_64-linux-gnu/cmake/OGRE-Next/OGRE-NextConfig.cmake

$ dpkg -c libogre-next-dev_2.3.3+dfsg-0ubuntu1_amd64.deb | grep "OGRE-NextConfig.cmake"
$

[1] https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/amd64/o/ogre-next/20240418_090809_3828f@/log.gz

Related branches

Revision history for this message
Pushkar Kulkarni (pushkarnk) wrote :

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?

Revision history for this message
Pushkar Kulkarni (pushkarnk) wrote :
tags: added: update-excuse
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ogre-next (Ubuntu):
status: New → Confirmed
Revision history for this message
Dave Jones (waveform) wrote :

I'm sponsoring this under the assumption that the FFe from LP: #2054477 still applies (it covered the original upload that failed to pass autopkgtests; this upload is intended to correct that failure).

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ogre-next - 2.3.3+dfsg-0ubuntu2

---------------
ogre-next (2.3.3+dfsg-0ubuntu2) noble; urgency=medium

  * Include the OGRE-Next Module in the installation.
    (LP: #2062378)
  * Cleanup debug message from Ogre-Next module

 -- Jose Luis Rivero <email address hidden> Fri, 19 Apr 2024 14:18:04 +0200

Changed in ogre-next (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.