# Registered package not made available

**URL:** <https://discourse.julialang.org/t/registered-package-not-made-available/124461>\
**Category:** General Usage\
**Created:** [January 6, 2025, 9:44am UTC](https://discourse.julialang.org/t/registered-package-not-made-available/124461 "2025-01-06T09:44:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eben60](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/eben60/32/13475_2.png) [@Eben60](https://discourse.julialang.org/u/Eben60)\
**Post date:** [January 6, 2025, 9:44am UTC](https://discourse.julialang.org/t/registered-package-not-made-available/124461/1 "2025-01-06T09:44:23Z")

</div>

My new package PackageMaker.jl was registered [yesterday](https://github.com/JuliaRegistries/General/pull/122318), it appeared on [juliahub.com](http://juliahub.com) in short time, but it is not yet available for installation from the general registry.

```julia
(@PackageMaker) pkg> add PackageMaker
ERROR: The following package names could not be resolved:
 * PackageMaker (not found in project, manifest or registry)
   Suggestions: PackageStates PackageAnalyzer PackageCompiler

```

Usually it is possible to install a new package or updated version within less than one hour after the merge. What is wrong now?

---

<div class="post-metadata">

**Author:** ![ufechner7](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ufechner7/32/51363_2.png) [@ufechner7](https://discourse.julialang.org/u/ufechner7)\
**Post date:** [January 6, 2025, 9:52am UTC](https://discourse.julialang.org/t/registered-package-not-made-available/124461/2 "2025-01-06T09:52:05Z")

</div>

Did you try:

```julia
export JULIA_PKG_SERVER_REGISTRY_PREFERENCE="eager"

```

before starting Julia?

This makes new packages available faster.

---

<div class="post-metadata">

**Author:** ![kellertuer](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kellertuer/32/220707_2.png) [@kellertuer](https://discourse.julialang.org/u/kellertuer)\
**Post date:** [January 6, 2025, 10:05am UTC](https://discourse.julialang.org/t/registered-package-not-made-available/124461/3 "2025-01-06T10:05:37Z")

</div>

When I typed that just now it updated my general registry and then it installed your new package without problems.

I do not think there is anything wrong, maybe `] update` before yourself or follow the hint by Uwe, but I think it is just a caching issue and will be available for you soon as well.

---

<div class="post-metadata">

**Author:** ![Eben60](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/eben60/32/13475_2.png) [@Eben60](https://discourse.julialang.org/u/Eben60)\
**Post date:** [January 6, 2025, 10:54am UTC](https://discourse.julialang.org/t/registered-package-not-made-available/124461/4 "2025-01-06T10:54:08Z")

</div>

Thank you both 🙂

`"eager"` didn’t help, but `] update` worked.

---

<div class="post-metadata">

**Author:** ![Eben60](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/eben60/32/13475_2.png) [@Eben60](https://discourse.julialang.org/u/Eben60)\
**Post date:** [January 8, 2025, 8:55pm UTC](https://discourse.julialang.org/t/registered-package-not-made-available/124461/5 "2025-01-08T20:55:37Z")

</div>

Still a strange thing: I got the same problem - `PackageMaker (not found...` - on a computer which unused for 3 weeks, and that was 3 days after the package registration, too.