# Missconfiguration leading to missing package?

**URL:** <https://discourse.openrobotics.org/t/missconfiguration-leading-to-missing-package/1898>\
**Category:** Buildfarm\
**Created:** [June 7, 2017, 3:28pm UTC](https://discourse.openrobotics.org/t/missconfiguration-leading-to-missing-package/1898 "2017-06-07T15:28:32Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [June 7, 2017, 6:40pm UTC](https://discourse.openrobotics.org/t/missconfiguration-leading-to-missing-package/1898/4 "2017-06-07T18:40:19Z")

</div>

> [@alex-gee](#):
>
> Did I get this right so far? The only possible thing is to wait for a fix?
> 
> Could I get my package to green using travis as described in: [ros\_buildfarm/doc/jobs/devel\_jobs.rst at master · ros-infrastructure/ros\_buildfarm · GitHub](https://github.com/ros-infrastructure/ros_buildfarm/blob/master/doc/jobs/devel_jobs.rst) ?

It doesn’t matter where you run it. If a package that your package depends on is not successfully building, your devel job cannot install all the dependencies, and thus your package cannot be successfully built.

You have a few other options:

- You can wait for a fix.
- You can try to help fix the issue in the dependency. On your custom buildfarm you can choose to override versions of packages, such as rollback or patching repos too.
- You can find a way to eliminate that dependency and then you won’t be blocked by it.

Note that we’ve [rolled back the latest opencv3](https://github.com/ros/rosdistro/pull/15183) release in the main rosdistro and a rebuild is in progress so if that’s the only issue blocking your tests, the wait for a fix approach is likely to work in the short term.

---

_[View the full topic](https://discourse.openrobotics.org/t/missconfiguration-leading-to-missing-package/1898)._