Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"<Package> not found in current path" on v0.6.2 #25670

Closed
lobingera opened this issue Jan 21, 2018 · 5 comments
Closed

"<Package> not found in current path" on v0.6.2 #25670

lobingera opened this issue Jan 21, 2018 · 5 comments

Comments

@lobingera
Copy link

Just as i saw #25664 ...

I updated via Pkg.update() recently and now:

lobi@orange4:~/juliarepo$ ../julia062/bin/julia
               _
   _       _ _(_)_     |  A fresh approach to technical computing
  (_)     | (_) (_)    |  Documentation: https://docs.julialang.org
   _ _   _| |_  __ _   |  Type "?help" for help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 0.6.2 (2017-12-13 18:08 UTC)
 _/ |\__'_|_|_|\__'_|  |  Official http://julialang.org/ release
|__/                   |  x86_64-pc-linux-gnu

julia> using MakiE
ERROR: ArgumentError: Module MakiE not found in current path.
Run `Pkg.add("MakiE")` to install the MakiE package.
Stacktrace:
 [1] _require(::Symbol) at ./loading.jl:435
 [2] require(::Symbol) at ./loading.jl:405

julia> Pkg.status()
20 required packages:
 - Cairo                         0.4.0              master
 - Clang                         0.3.0
 - Compose                       0.5.4+             master
 - Fontconfig                    0.1.1
 - FreeType                      1.3.0
 - FreeTypeAbstraction           0.1.0              wip-debug (dirty)
 - GLVisualize                   0.6.1+             sd/makie
 - GR                            0.25.0
 - Gadfly                        0.6.4
 - Gallium                       0.1.0
 - Gtk                           0.13.1
 - Images                        0.12.0
 - InspectDR                     0.2.4
 - NearestNeighbors              0.3.0
 - PkgDev                        0.1.6
 - Plots                         0.15.0
 - Requires                      0.4.3
 - Rsvg                          0.2.0              master
 - WinRPM                        0.3.1
 - Winston                       0.13.2
121 additional packages:
 - ASTInterpreter2               0.1.1
 - AbstractFFTs                  0.2.1
 - AbstractNumbers               0.1.1
 - AxisAlgorithms                0.2.0
 - AxisArrays                    0.2.0
 - BinDeps                       0.8.5+             master
 - BufferedStreams               0.3.3
 - CCallBuild                    0.0.0-             master (unregistered, dirty)
 - CairoScript                   0.0.0-             master (unregistered)
 - CairoText                     0.0.0-             master (unregistered, dirty)
 - Calculus                      0.2.2
...
 - Luxor                         0.9.0+             master
 - MacroTools                    0.4.0
 - MakiE                         0.0.0-             master (unregistered)

and my .julia/v0.6/ lists MakiE with a reasonable git status.

@KristofferC
Copy link
Sponsor Member

KristofferC commented Jan 21, 2018

I think the problem with MakiE was that it got renamed to Makie? or vice versa? This has something to do with the casing at least...

julia> Base.isfile_casesensitive("/Users/kristoffer/.julia/v0.6/MakiE/src/MakiE.jl")
false

julia> isfile("/Users/kristoffer/.julia/v0.6/MakiE/src/MakiE.jl")
true

julia> Base.isfile_casesensitive("/Users/kristoffer/.julia/v0.6/MakiE/src/Makie.jl")
true

julia> using MakiE
ERROR: ArgumentError: Module MakiE not found in current path.
Run `Pkg.add("MakiE")` to install the MakiE package.

julia> using Makie
Precompiling...

@lobingera
Copy link
Author

I see. Still

Run Pkg.add("MakiE") to install the MakiE package

is misleading (but i have no idea to make this more correctly).

@KristofferC
Copy link
Sponsor Member

KristofferC commented Jan 21, 2018

is misleading

I don't think so. By renaming the file MakiE.jl -> Makie.jl the package that you pulled from no longer fulfills the package naming convention and is thus no longer found. Makie.jl is a completely other package than MakiE.jl so I think this is expected to break.

@lobingera
Copy link
Author

I'll check later, while i agree that i installed initially from a git clone. But still Pkg.update did something to this.

@KristofferC
Copy link
Sponsor Member

KristofferC commented Jan 21, 2018

Yes, Pkg.upgrade changed the file MakiE.jl -> Makie.jl which is not allowed if your package is called MakiE.jl. This is the same as the package would stop working if the author did a commit that deleted all files in the package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants