# How to find package preventing others from updating

**URL:** <https://discourse.julialang.org/t/how-to-find-package-preventing-others-from-updating/8235>\
**Category:** General Usage\
**Tags:** packages, package-manager\
**Created:** [January 8, 2018, 4:50pm UTC](https://discourse.julialang.org/t/how-to-find-package-preventing-others-from-updating/8235 "2018-01-08T16:50:31Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Ralph\_Smith](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ralph_smith/32/10344_2.png) [@Ralph\_Smith](https://discourse.julialang.org/u/Ralph_Smith)\
**Post date:** [January 9, 2018, 3:34am UTC](https://discourse.julialang.org/t/how-to-find-package-preventing-others-from-updating/8235/3 "2018-01-09T03:34:27Z")

</div>

I like this, but IIUC your approach is not quite right when an upper bound is introduced via METADATA. This occurred, for example, when the recent breaking revision of DataFrames forced them to bound all dependencies. You could handle these cases by getting the `line`s from `METADATA/$package/versions/$version/requires` file instead of the package’s REQUIRE file.

---

_[View the full topic](https://discourse.julialang.org/t/how-to-find-package-preventing-others-from-updating/8235)._