# Cannot Pkg.resolve the new REQUIRE of a package in development

**URL:** https://discourse.julialang.org/t/cannot-pkg-resolve-the-new-require-of-a-package-in-development/12623
**Category:** General Usage
**Tags:** package
**Created:** [July 24, 2018, 3:02am UTC](https://discourse.julialang.org/t/cannot-pkg-resolve-the-new-require-of-a-package-in-development/12623 "2018-07-24T03:02:06Z")
**Posts on this page:** 1
**Showing post:** 6

<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: [July 25, 2018, 11:02am UTC](https://discourse.julialang.org/t/cannot-pkg-resolve-the-new-require-of-a-package-in-development/12623/6 "2018-07-25T11:02:59Z")

</div>

The manifest is automatically generated during the usage of the package manager. It contains the exact versions/git-tree-shas/paths that julia uses to find what packages to load.

For most libraries it does not need to be checked into version control. See also [Does Manifest.toml belong in the repository?](https://discourse.julialang.org/t/does-manifest-toml-belong-in-the-repository/12029)

---

_[View the full topic](https://discourse.julialang.org/t/cannot-pkg-resolve-the-new-require-of-a-package-in-development/12623)._