# Package manager: what are "explicit requirements"?

**URL:** https://discourse.julialang.org/t/package-manager-what-are-explicit-requirements/18616
**Category:** General Usage
**Tags:** pkg
**Created:** [December 13, 2018, 12:16am UTC](https://discourse.julialang.org/t/package-manager-what-are-explicit-requirements/18616 "2018-12-13T00:16:40Z")
**Posts on this page:** 1
**Showing post:** 15

<div class="post-metadata">

### Author: ![kristoffer.carlsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kristoffer.carlsson/32/22_2.png) [@kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson)
#### Post date: [April 24, 2019, 6:38am UTC](https://discourse.julialang.org/t/package-manager-what-are-explicit-requirements/18616/15 "2019-04-24T06:38:55Z")

</div>

This is an interaction between the upper bounds placed by the METADATA converter and [https://github.com/JuliaLang/Pkg.jl/issues/110](https://github.com/JuliaLang/Pkg.jl/issues/110).

As it is right now, if a test dependency is not compatible with the versions of packages that gets resolved without the test dependency, the package will fail with a resolution error when tested.

The workaround is to check in a Manifest with versions that are compatible with the test dependencies. We should maybe think more about [https://github.com/JuliaLang/Pkg.jl/issues/110](https://github.com/JuliaLang/Pkg.jl/issues/110) and loosen how hard the version of project dependencies are being kept.

---

_[View the full topic](https://discourse.julialang.org/t/package-manager-what-are-explicit-requirements/18616)._