# Ouster Packages Missing

**URL:** <https://discourse.openrobotics.org/t/ouster-packages-missing/33146>\
**Category:** Iron\
**Created:** [August 29, 2023, 7:14pm UTC](https://discourse.openrobotics.org/t/ouster-packages-missing/33146 "2023-08-29T19:14:23Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Samahu](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/samahu/32/18509_2.png) [@Samahu](https://discourse.openrobotics.org/u/Samahu)\
**Post date:** [August 29, 2023, 7:14pm UTC](https://discourse.openrobotics.org/t/ouster-packages-missing/33146/1 "2023-08-29T19:14:23Z")

</div>

Hi Yadunund, Do you have an idea on why “ros-iron-ouster-msgs: 0.10.3-1” was published but not " \* ros-iron-ouster-ros: 0.10.3-1". These two are part of the same repo and release so I would expect both to be published at the same time. Can you provide some leads on how to solve this?

---

<div class="post-metadata">

**Author:** ![Samahu](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/samahu/32/18509_2.png) [@Samahu](https://discourse.openrobotics.org/u/Samahu)\
**Post date:** [August 29, 2023, 7:52pm UTC](https://discourse.openrobotics.org/t/ouster-packages-missing/33146/2 "2023-08-29T19:52:01Z")

</div>

You can that both packages are listed in the linked merge request, check lines: [rosdistro/iron/distribution.yaml at 48793b2f6f8e06ce5b661b9790ef0d925bd8d9d5 · ros/rosdistro · GitHub](https://github.com/ros/rosdistro/blob/48793b2f6f8e06ce5b661b9790ef0d925bd8d9d5/iron/distribution.yaml#L3507-L3508)

---

<div class="post-metadata">

**Author:** ![tfoote](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/tfoote/32/3813_2.png) [@tfoote](https://discourse.openrobotics.org/u/tfoote)\
**Post date:** [August 29, 2023, 7:57pm UTC](https://discourse.openrobotics.org/t/ouster-packages-missing/33146/3 "2023-08-29T19:57:42Z")

</div>

The build of the package is failing on the buildfarm here’s the latest

> **[Ibin\_uJ64\_\_ouster\_ros\_\_ubuntu\_jammy\_amd64\_\_binary #8 Console \[Jenkins\]](https://build.ros2.org/job/Ibin_uJ64 __ouster_ros__ ubuntu_jammy_amd64__binary/8/console)**

It’s sending an email to the registered package maintainer. I’d double check that email is being routed to you as it looks like a mailing list on your end.

Looking at the build output you appear to have an invalid install rule for the LICENSE file

```auto
23:19:14 CMake Error at cmake_install.cmake:292 (file):
23:19:14 file INSTALL cannot find
23:19:14 "/tmp/binarydeb/ros-iron-ouster-ros-0.10.3/../LICENSE": No such file or
23:19:14 directory.
23:19:14 
23:19:14 
23:19:14 make[2]: *** [Makefile:133: install] Error 1
23:19:14 make[2]: Leaving directory '/tmp/binarydeb/ros-iron-ouster-ros-0.10.3/.obj-x86_64-linux-gnu'
23:19:14 dh_auto_install: error: cd .obj-x86_64-linux-gnu && make -j1 install DESTDIR=/tmp/binarydeb/ros-iron-ouster-ros-0.10.3/debian/ros-iron-ouster-ros AM_UPDATE_INFO_DIR=no returned exit code 2
23:19:14 make[1]: *** [debian/rules:66: override_dh_auto_install] Error 25
23:19:14 make[1]: Leaving directory '/tmp/binarydeb/ros-iron-ouster-ros-0.10.3'
23:19:14 make: *** [debian/rules:27: binary] Error 2
23:19:14 dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2
23:19:14 Traceback (most recent call last):
23:19:14 File "/tmp/ros_buildfarm/ros_buildfarm/binarydeb_job.py", line 149, in build_binarydeb
23:19:14 subprocess.check_call(cmd, cwd=source_dir, env=env)
23:19:14 File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
23:19:14 raise CalledProcessError(retcode, cmd)
23:19:14 subprocess.CalledProcessError: Command '['dpkg-buildpackage', '-b', '-us', '-uc', '-Pnocheck']' returned non-zero exit status 2.
23:19:14 # END SUBSECTION
23:19:14 
23:19:14 --------------------------------------------------------------------------------------------------
23:19:14 `dpkg-buildpackage -b -us -uc -Pnocheck` failed.
23:19:14 This is usually because of an error building the package.
23:19:14 The traceback from this failure (just above) is printed for completeness, but you can ignore it.
23:19:14 You should look above `E: Building failed` in the build log for the actual cause of the failure.
23:19:14 --------------------------------------------------------------------------------------------------
23:19:14

```

---

<div class="post-metadata">

**Author:** ![Samahu](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/samahu/32/18509_2.png) [@Samahu](https://discourse.openrobotics.org/u/Samahu)\
**Post date:** [August 31, 2023, 5:31am UTC](https://discourse.openrobotics.org/t/ouster-packages-missing/33146/4 "2023-08-31T05:31:12Z")

</div>

Thanks @tfoote, I am taking a look at the issue.

---

<div class="post-metadata">

**Author:** ![Samahu](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/samahu/32/18509_2.png) [@Samahu](https://discourse.openrobotics.org/u/Samahu)\
**Post date:** [August 31, 2023, 5:41pm UTC](https://discourse.openrobotics.org/t/ouster-packages-missing/33146/5 "2023-08-31T17:41:09Z")

</div>

I pushed a new pull request [ouster-ros: 0.10.4-1 in 'iron/distribution.yaml' [bloom] by Samahu · Pull Request #38390 · ros/rosdistro · GitHub](https://github.com/ros/rosdistro/pull/38390) which should resolve the LICENSE file issue.

---

<div class="post-metadata">

**Author:** ![Samahu](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/samahu/32/18509_2.png) [@Samahu](https://discourse.openrobotics.org/u/Samahu)\
**Post date:** [August 31, 2023, 7:41pm UTC](https://discourse.openrobotics.org/t/ouster-packages-missing/33146/6 "2023-08-31T19:41:34Z")

</div>

Thanks for merging, build is green now: [https://build.ros2.org/job/Ibin\_uJ64\_\_ouster\_ros\_\_ubuntu\_jammy\_amd64\_\_binary/12](https://build.ros2.org/job/Ibin_uJ64 __ouster_ros__ ubuntu_jammy_amd64__binary/12)