# Unregistered nested dependencies

**URL:** <https://discourse.julialang.org/t/unregistered-nested-dependencies/123923>\
**Category:** General Usage\
**Tags:** pkg\
**Created:** [December 17, 2024, 12:12pm UTC](https://discourse.julialang.org/t/unregistered-nested-dependencies/123923 "2024-12-17T12:12:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![polhager](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/polhager/32/37340_2.png) [@polhager](https://discourse.julialang.org/u/polhager)\
**Post date:** [December 17, 2024, 12:12pm UTC](https://discourse.julialang.org/t/unregistered-nested-dependencies/123923/1 "2024-12-17T12:12:36Z")

</div>

Hi all. I have a local package (`PackageOne`) which uses an unregistered package (`PythonStructs`) as a dependency. I would then like to use said local package as a dependency for a second local package (`PackageTwo`).

The `Project.toml` for `PackageOne` is, using the source path functionality in 1.11,

```julia
name = "PackageOne"
uuid = "dbf1826d-e942-4fc0-a003-44f9f33e530f"
authors = ["polhager"]
version = "0.1.0"

[deps]
PythonStructs = "ac2a11db-85c8-4716-89e7-c323b56359f0"

[sources]
PythonStructs = {url = "https://github.com/mkitti/PythonStructs.jl.git"}

```

This works fine for `PackageOne`, I can do instantiate and everything. When trying to add `PackageOne` to `PackageTwo`, I get the following:

```julia
(@v1.11) pkg> activate PackageTwo
  Activating project at `~/.julia/dev/PackageTwo`

(PackageTwo) pkg> dev ./PackageOne
   Resolving package versions...
ERROR: Unsatisfiable requirements detected for package PythonStructs [ac2a11db]:
 PythonStructs [ac2a11db] log:
 ├─PythonStructs [ac2a11db] has no known versions!
 └─restricted to versions * by PackageOne [dbf1826d] — no versions left
   └─PackageOne [dbf1826d] log:
     ├─possible versions are: 0.1.0 or uninstalled
     └─PackageOne [dbf1826d] is fixed to version 0.1.0

```

Short of adding `PythonStructs` to our own internal registry, which I would prefer to avoid since it is not a package developed by us, or adding `PythonStructs` explicitly to `PackageTwo`, which I would prever to avoid since it is in fact not a direct dependency, what can I do to solve this?