I think I painted myself into a corner somehow with package requirements. The error message for trying to test TransformVariables#master is pkg> test TransformVariables Testing TransformVariables Resolving package versions... ERROR: Unsatisfiable requirements detected for package LogDensityProb…

To workaround this while it is being worked on, register TransformVariables version 0.3 and then after register LogDensityProblems and it should work.

LogDensityTransforms are according to the registry compatible only with 0.2 of TransformVariables ( https://github.com/JuliaRegistries/General/blob/master/L/LogDensityProblems/Compat.toml#L22 ). What you have in your Project file doesn’t matter unless the package is either devved or tracking a branch.…

Thanks, but the latest version was registered with that project file, so shouldn’t that compat spec be taken into account and reflected by the registry?

Alright, the reason is that the maximum version of TransformVariables in the Registry is 0.2 and the current script does some upper bounding based on the highest registered version. We are discussing how to resolve this right now.

I’m having similar issues here Package manager: what are "explicit requirements"? - #4 by baggepinnen and I can’t for my life figure out how to get around it :confused:

I am hoping that as soon as the new version is registered, my issue will be resolved in this specific case as the bounds in registry will be updated.

Unfortunately I don’t think this will be the case, because in https://github.com/JuliaRegistries/General/pull/228 we don’t update the bounds for LogDensityProblems. The fact that LogDensityProblems work with TransformVariables@0.3 was also “forgotten” in the compression algorithm in this PR: https:/…

[image] Switching package registration systems soon Announcements If anyone package maintainer feels that dependencies of their package or on their package have been inappropriately capped and it’s causing version resolution problems, please let me know and I can make PRs …

Understanding an "Unsatisfiable requirements" problems

General Usage

StefanKarpinski April 24, 2019, 1:47pm 10

Topic		Replies	Views
Package Manager resolve complaining of "Unsatisfiable requirements" due to "no known versions" General Usage package-manager	6	4172	December 18, 2021
Package manager: what are "explicit requirements"? General Usage pkg	24	3672	April 25, 2019
A guide: How to handle "ERROR: Unsatisfiable requirements detected ..." New to Julia	7	13205	June 17, 2022
What exactly does "restricted to versions 1.0.0 by an explicit requirement" mean? New to Julia	2	2308	May 3, 2019
Fixing an "explicit requirement" problem General Usage pkg	1	485	July 14, 2020

Understanding an "Unsatisfiable requirements" problems

Related topics