How can I find out why I have a curtain package installed (indirect dependency)?
I get these warnings:
WARNING: using deprecated binding Rotations.UnitQuaternion in KiteModels.
, use QuatRotation instead.
WARNING: KiteModels.UnitQuaternion is deprecated, use Rotations.QuatRotation{T} where T instead.
likely near none:8
WARNING: using deprecated binding ColorTypes.RGB1 in Colors.
, use XRGB instead.
WARNING: using deprecated binding Colors.RGB1 in ImageCore.
, use ColorTypes.XRGB{T} where T<:Union{AbstractFloat, FixedPointNumbers.FixedPoint{T, f} where f where T<:Integer} instead.
WARNING: using deprecated binding ImageCore.RGB1 in ImageAxes.
, use ColorTypes.XRGB{T} where T<:Union{AbstractFloat, FixedPointNumbers.FixedPoint{T, f} where f where T<:Integer} instead.
WARNING: ImageAxes.RGB1 is deprecated, use ColorTypes.XRGB{T} where T<:Union{AbstractFloat, FixedPointNumbers.FixedPoint{T, f} where f where T<:Integer} instead.
likely near none:8
Why are Colors and ImageCore in my dependencies?
(KiteControllers) pkg> why Colors
ERROR: The following package names could not be resolved:
* Colors (not found in project or manifest)
(KiteControllers) pkg> why ImageCore
ERROR: The following package names could not be resolved:
* ImageCore (not found in project or manifest)
julia> using TestEnv; TestEnv.activate()
"/tmp/jl_oL5KXg/Project.toml"
(jl_oL5KXg) pkg> why Colors
ControlPlots ā PyPlot ā Colors
KiteModels ā VortexStepMethod ā Colors
KiteViewers ā GLMakie ā Colors
KiteViewers ā GLMakie ā FreeTypeAbstraction ā Colors
KiteViewers ā GLMakie ā Makie ā Animations ā Colors
KiteViewers ā GLMakie ā Makie ā ColorBrewer ā Colors
KiteViewers ā GLMakie ā Makie ā ColorSchemes ā Colors
KiteViewers ā GLMakie ā Makie ā Colors
KiteViewers ā GLMakie ā Makie ā FreeTypeAbstraction ā Colors
KiteViewers ā GLMakie ā Makie ā ImageBase ā ImageCore ā Colors
KiteViewers ā GLMakie ā Makie ā ImageIO ā JpegTurbo ā ImageCore ā Colors
KiteViewers ā GLMakie ā Makie ā ImageIO ā Netpbm ā ImageCore ā Colors
KiteViewers ā GLMakie ā Makie ā ImageIO ā Netpbm ā ImageMetadata ā ImageAxes ā ImageBase ā ImageCore ā Colors
KiteViewers ā GLMakie ā Makie ā ImageIO ā Netpbm ā ImageMetadata ā ImageAxes ā ImageCore ā Colors
KiteViewers ā GLMakie ā Makie ā ImageIO ā Netpbm ā ImageMetadata ā ImageBase ā ImageCore ā Colors
KiteViewers ā GLMakie ā Makie ā ImageIO ā Netpbm ā ImageMetadata ā ImageCore ā Colors
KiteViewers ā GLMakie ā Makie ā ImageIO ā OpenEXR ā Colors
KiteViewers ā GLMakie ā Makie ā ImageIO ā PNGFiles ā ImageCore ā Colors
KiteViewers ā GLMakie ā Makie ā ImageIO ā Sixel ā ImageCore ā Colors
KiteViewers ā GLMakie ā Makie ā ImageIO ā WebP ā ImageCore ā Colors
KiteViewers ā GLMakie ā Makie ā MathTeXEngine ā FreeTypeAbstraction ā Colors
KiteViewers ā GLMakie ā Makie ā PlotUtils ā ColorSchemes ā Colors
KiteViewers ā GLMakie ā Makie ā PlotUtils ā Colors
The next question is, who can I find out which version of Colors is actually used in my test environment? Ok, I just found it in the Manifest.toml of the test environment.
version = "0.13.1"
st -m Colors
in the test environment
2 Likes
OK, the problem was not Colors, but ColorTypes.
julia> using TestEnv; TestEnv.activate()
Precompiling project...
1 dependency successfully precompiled in 3 seconds. 164 already precompiled.
"/tmp/jl_0fIxkW/Project.toml"
(jl_0fIxkW) pkg> st -o -m ColorTypes
Status `/tmp/jl_0fIxkW/Manifest.toml`
ā
[3da002f7] ColorTypes v0.11.5 (<v0.12.1): ColorVectorSpace, ShaderAbstractions
(jl_0fIxkW) pkg> st -o -m ColorVectorSpace
Status `/tmp/jl_0fIxkW/Manifest.toml`
ā [c3611d14] ColorVectorSpace v0.10.0 (<v0.11.0)
(jl_0fIxkW) pkg> st -m ColorVectorSpace
Status `/tmp/jl_0fIxkW/Manifest.toml`
ā [c3611d14] ColorVectorSpace v0.10.0
Info Packages marked with ā have new versions available and may be upgradable.
(jl_0fIxkW) pkg> st -o -m ShaderAbstractions
Status `/tmp/jl_0fIxkW/Manifest.toml`
ā
[65257c39] ShaderAbstractions v0.4.1 (<v0.5.0): GLMakie, Makie
(jl_0fIxkW) pkg> st -o -m GLMakie
Status `/tmp/jl_0fIxkW/Manifest.toml`
ā
[e9467ef8] GLMakie v0.10.18 (<v0.11.8): KiteViewers
So I need to upgrade GLMakie in KiteViewers to fix this warning, I guess.
1 Like