[needs sponsor] Sync to Jammy Gazebo11 simulator + dependencies (DART, ignitions) from Debian Unstable

[Jose Luis Rivero]

Hello:

I'm the maintainer of Gazebo and all the related dependencies listed her in Debian. There were some transitions affecting Gazebo in the last months, one affecting DART library (a dependency of Gazebo) and another important transition to duplicate the ignition libraries that needs Gazebo to run (to unblock new ignition of those libraries which are incompatible with Gazebo).

Checking Ubuntu auto migration excuses I found that, ignition-common seems to be blocked and msgs5 too:

* https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ignition-common
* https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ignition-msgs5

They had problems in Debian some weeks ago but are now fully clean (all them are also in testing except DART that has no blocker right now).

List of source packages and versions to sync from Debian unstable

# src:package | debian version | Ubuntu comment on Jammy versions

- dart 6.12.1+dfsg4-10 (Jammy has 6.9.5-4u1)
- gazebo 11.9.1+dfsg-8 (Jammy has 11.9.1+dfsg-2 needs 8 revision to use new dependencies)
- ignition-common3 3.14.0+dfsg-5 (Jammy has no ignition-common3 but ignition-common)
- ignition-common 4.4.0+ds-5 (Jammy has 3.14.0+dfsg-1)
- ignition-fuel-tools4 4.4.0+ds-3 (Jammy has no ignition-fuel-tools4 but ignition-fuel-tools)
- ignition-fuel-tools 7.0.0+ds-2 (Jammy has 4.1.0+dfsg-6)
- ignition-msgs5 5.8.1+ds-2 (Jammy has no ignition-msgs5 but ignition-msgs)
- ignition-msgs 8.2.0+ds-1 (Jammy 5.1.0+dfsg-7)
- ignition-transport 11.0.0+ds-3 (Jammy has 8.0.0+dfsg-3)
- ignition-transport8 8.2.1+ds-2 (Jammy has no ignition-transport8 but ignition-transport)

[Sebastien Bacher (seb128)]

Thanks for the report, the version you listed were already in Ubuntu but blocked in proposed pending britney migration, unsure how you check what is available in Ubuntu but you might want to check for proposed pocket versions. The ignition packages just needed to be called with the right trigger to ensure the tests were used an update set (which the depends don't seem to ensure?)

The new trigger worked and the ignition stack migrated now

The dart update is currently blocked by a riscv64 build failure which might have been a builder issue, a new build has been restarted, let's see if it works

[Jose Luis Rivero (j-rivero)]

Thanks Sebastien for the comment. I was checking my Debian QA page https://qa.debian.org/developer.php?<email address hidden> and did not check the -proposed pocket, I see now that the packages are there using rmadison (not sure if there is a better dashboard for the check).

I'm available to help with the riscv64 failure in DART if finally there is a valid bug there.

[Sebastien Bacher (seb128)]

I don't know of a better dashboard sorry, either rmadison or checking the launchpad pages for the package. The dart build retry worked but thanks for offering to help you, it has migrated now so I think that bug can be considered resolved now and I'm closing it

[Jose Luis Rivero (j-rivero)]

Thanks so much Sebastien!