Skip to content

GeoInterfaceRecipes precompilation error with GeoInterface v1.5 #200

Closed

Description

@bclyons12

GeoInterfaceRecipes can't precompile with the new GeoInterface v1.5. Downgrading to v1.4.1 solves this issue. Right now other upstream packages like LibGEOS require GeoInterfaceRecipes, so a whole software stack can't precompile.

julia> versioninfo()
Julia Version 1.11.6
Commit 9615af0f269 (2025-07-09 12:58 UTC)
Build Info:
  Official https://julialang.org/ release
Platform Info:
  OS: macOS (arm64-apple-darwin24.0.0)
  CPU: 12 × Apple M4 Pro
  WORD_SIZE: 64
  LLVM: libLLVM-16.0.6 (ORCJIT, apple-m1)
Threads: 8 default, 0 interactive, 4 GC (on 8 virtual cores)
Environment:
  JULIA_NUM_THREADS = auto

julia> import Pkg; Pkg.activate(temp=true)
  Activating new project at `/var/folders/nt/ct_lf2n94_1c21908mmbx55w0000gq/T/jl_FMl6kv`

(jl_FMl6kv) pkg> add GeoInterfaceRecipes
[ Info: Use `./GeoInterfaceRecipes` to add or develop the local directory at `~/.julia/compiled/v1.11/GeoInterfaceRecipes`.
   Resolving package versions...
    Updating `/private/var/folders/nt/ct_lf2n94_1c21908mmbx55w0000gq/T/jl_FMl6kv/Project.toml`
  [0329782f] + GeoInterfaceRecipes v1.0.2
    Updating `/private/var/folders/nt/ct_lf2n94_1c21908mmbx55w0000gq/T/jl_FMl6kv/Manifest.toml`
  [9a962f9c] + DataAPI v1.16.0
  [411431e0] + Extents v0.1.6
  [68eda718] + GeoFormatTypes v0.4.4
  [cf35fbd7] + GeoInterface v1.5.0
  [0329782f] + GeoInterfaceRecipes v1.0.2
⌅ [aea7be01] + PrecompileTools v1.2.1
  [21216c6a] + Preferences v1.4.3
  [3cdcf5f2] + RecipesBase v1.3.4
  [ade2ca70] + Dates v1.11.0
  [de0858da] + Printf v1.11.0
  [fa267f1f] + TOML v1.0.3
  [4ec0a83e] + Unicode v1.11.0
        Info Packages marked with ⌅ have new versions available but compatibility constraints restrict them from upgrading. To see why use `status --outdated -m`
Precompiling project...
  ? GeoInterfaceRecipes

julia> import GeoInterfaceRecipes
Precompiling GeoInterfaceRecipes...
Info Given GeoInterfaceRecipes was explicitly requested, output will be shown live 
WARNING: Method definition apply_recipe(Base.AbstractDict{Symbol, Any}, Union{GeoInterface.MultiPointTrait, GeoInterface.PointTrait}, Any) in module GeoInterfaceRecipesBaseExt at /Users/lyons/.julia/packages/RecipesBase/BRe07/src/RecipesBase.jl:296 overwritten in module GeoInterfaceRecipes on the same line (check for duplicate calls to `include`).
ERROR: Method overwriting is not permitted during Module precompilation. Use `__precompile__(false)` to opt-out of precompilation.
  ? GeoInterfaceRecipes
[ Info: Precompiling GeoInterfaceRecipes [0329782f-3d07-4b52-b9f6-d3137cf03c7a] 
WARNING: Method definition apply_recipe(Base.AbstractDict{Symbol, Any}, Union{GeoInterface.MultiPointTrait, GeoInterface.PointTrait}, Any) in module GeoInterfaceRecipesBaseExt at /Users/lyons/.julia/packages/RecipesBase/BRe07/src/RecipesBase.jl:296 overwritten in module GeoInterfaceRecipes on the same line (check for duplicate calls to `include`).
ERROR: Method overwriting is not permitted during Module precompilation. Use `__precompile__(false)` to opt-out of precompilation.
┌ Info: Skipping precompilation due to precompilable error. Importing GeoInterfaceRecipes [0329782f-3d07-4b52-b9f6-d3137cf03c7a].
└   exception = Error when precompiling module, potentially caused by a __precompile__(false) declaration in the module.

Activity

  1. asinghvi17 commented on Jul 11, 2025

    @asinghvi17
    Member

    ah damn, we have to retroactively cap everything in the registry...

  2. asinghvi17 commented on Jul 11, 2025

    @asinghvi17
    Member

    But we are also getting dependency releases out now, fwiw, so this should be resolved soon

  3. added a commit that references this issue on Sep 3, 2025
  4. tiemvanderdeure commented on Nov 10, 2025

    @tiemvanderdeure
    Contributor

    Just noticed this is still (again?) an issue. See rasters test runs https://github.com/rafaqz/Rasters.jl/actions/runs/19234918647/job/54982184288?pr=1039

  5. evetion commented on Nov 10, 2025

    @evetion
    Member

    If this keeps being an issue (indicating some compat bounds are wrong), the best is to release new versions for those packages that are otherwise empty?

  6. asinghvi17 commented on Nov 10, 2025

    @asinghvi17
    Member

    I was thinking the same.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions