# Partial compatibility bounds
**URL:** https://discourse.julialang.org/t/partial-compatibility-bounds/47574
**Category:** Package Management
**Tags:** pkg
**Created:** [October 1, 2020, 7:45am UTC](https://discourse.julialang.org/t/partial-compatibility-bounds/47574 "2020-10-01T07:45:18Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@cstjean](https://discourse.julialang.org/u/cstjean)
#### Post date: [October 1, 2020, 7:45am UTC](https://discourse.julialang.org/t/partial-compatibility-bounds/47574/1 "2020-10-01T07:45:18Z")
We’ve been making slow progress towards a full private registry setup…
1. We registered our packages
2. We tagged all of them
3. We put some compatibility bounds on some packages
Am I right that step 3 is a terrible mistake? If I understand correctly, as soon as we add a bound on some dependency D which didn’t have a bound before, the package resolver is in an undesirable state (A@new\_version is restricted appropriately, but A@old\_version is compatible with all versions of D past and future)
If I’m reading things right, the recommended cure is:
1. [https://github.com/bcbi/RetroCap.jl](https://github.com/bcbi/RetroCap.jl)
2. [https://github.com/JuliaRegistries/CompatHelper.jl#4-self-hosting-and-other-environments](https://github.com/JuliaRegistries/CompatHelper.jl#4-self-hosting-and-other-environments)
Did I miss anything?
Cédric
---
### Author:  [@dilumaluthge](https://discourse.julialang.org/u/dilumaluthge)
#### Post date: [October 1, 2020, 7:48am UTC](https://discourse.julialang.org/t/partial-compatibility-bounds/47574/2 "2020-10-01T07:48:03Z")
Yeah RetroCap is designed to fix this exact issue.