I'm creating a release repo to release a third party package into ROS distributions. I'm following the process described in the wiki pages below.

• Releasing a Third Party Package
• Bloom - First Time Release of a Package

Before I submit a PR and submit to the build farm, I'd like to test the package build locally, to make sure that I've set up the build dependencies correctly. What is the best known method to do so?

So far, I've tried this: after the final git-bloom-patch && git-bloom-release foxy, I check out the debian/ros-foxy-package_version_focal tag in the working copy of the release repo. I see that the debian/* control files are correctly set up. However, I'm not getting far with (p)debuild - I keep getting the following error, due to the way bloom set up the debian/source/options I think?

dpkg-source: error: can't build with source format '3.0 (quilt)': no upstream tarball found at ../ros-foxy-openvino_2022.2.0.orig.tar.{bz2,gz,lzma,xz} dpkg-source: info: using options from ros_openvino-release/debian/source/options: --auto-commit