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

Can't install extensions on Ubuntu because of version mismatch #623

Open
fmichonneau opened this issue Dec 3, 2024 · 7 comments
Open

Can't install extensions on Ubuntu because of version mismatch #623

fmichonneau opened this issue Dec 3, 2024 · 7 comments
Milestone

Comments

@fmichonneau
Copy link

With the duckdb package version 1.1.3, on Ubuntu 24.10 I see:

library(duckdb)
#> Loading required package: DBI
con <- dbConnect(duckdb())
dbExecute(con, "INSTALL spatial;")
#> Error in `duckdb_result()`:
#> ! rapi_execute: Failed to run query
#> Error: IO Error: Failed to install 'spatial'
#> The file was built for DuckDB version 'v1.1.3', but we can only load extensions built for DuckDB version '19864453f7'.
dbGetQuery(con, "PRAGMA version;")
#>   library_version  source_id
#> 1   v1.1.3-dev165 19864453f7

Created on 2024-12-03 with reprex v2.1.1

This doesn't happen with the duckdb cli:

 duckdb
v1.1.3 19864453f7
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
D pragma version;
┌─────────────────┬────────────┐
│ library_version │ source_id  │
│     varchar     │  varchar   │
├─────────────────┼────────────┤
│ v1.1.3          │ 19864453f7 │
└─────────────────┴────────────┘

With the R package, it seems like the extension installer is picking up the source_id instead of the version number. I am just guessing, but I'm wondering if it's because the duckdb version bundled with the R package has the dev165 suffix?

@fmichonneau
Copy link
Author

Update: I cloned the repository locally and removed the dev165 suffix from

#define DUCKDB_PATCH_VERSION "3-dev165"
(lines 2 and 11).

After reinstalling the package from these local files, the extension can be installed.

@kent37
Copy link

kent37 commented Dec 3, 2024

I have the same error on MacOS.

@kent37
Copy link

kent37 commented Dec 3, 2024

And the same fix works for me.

This was referenced Dec 3, 2024
@krlmlr
Copy link
Collaborator

krlmlr commented Dec 4, 2024

Thanks, good catch. I can push duckdb 1.1.3-1 soon.

@krlmlr krlmlr added this to the 1.1.3-1 milestone Dec 4, 2024
@krlmlr
Copy link
Collaborator

krlmlr commented Dec 4, 2024

Done in 5502a90.

@krlmlr krlmlr closed this as completed Dec 4, 2024
@eitsupi
Copy link
Contributor

eitsupi commented Dec 4, 2024

Shouldn't the release version be tested on CI for extension installation to prevent regression?

@krlmlr
Copy link
Collaborator

krlmlr commented Dec 4, 2024

Good catch, adding infrastructure for this.

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

4 participants