Package Details: python-duckdb 1.4.0-1

Git Clone URL: https://aur.archlinux.org/duckdb.git (read-only, click to copy)
Package Base: duckdb
Description: An in-process SQL OLAP database management system (Python API)
Upstream URL: https://duckdb.org
Keywords: database management sql
Licenses: MIT
Conflicts: python-duckdb-git
Submitter: grawlinson
Maintainer: AlphaJack (Dominiquini)
Last Packager: Dominiquini
Votes: 17
Popularity: 1.71
First Submitted: 2021-10-30 06:37 (UTC)
Last Updated: 2025-09-19 22:31 (UTC)

Latest Comments

1 2 3 Next › Last »

Dominiquini commented on 2025-09-16 23:19 (UTC)

@AlphaJack: I update the package to the version 1.4.0, but I'm using a pre-compiled version for the python library. Can you try to fix that? Thanks

Dominiquini commented on 2025-09-16 21:17 (UTC)

@AlphaJack: I was unable to update this package (python-duckdb)! Even when I tried to separate the python package, I can't figure out how to make a script to build this. Can you take care of it? Thanks.

xsy420 commented on 2025-09-16 12:41 (UTC)

duckdb is 1.4.0 now and python-duckdb is moved to https://github.com/duckdb/duckdb-python. please update

micwoj92 commented on 2025-09-10 05:14 (UTC)

pip is not needed in makedeps, please remove.

JohnTh commented on 2025-07-20 08:34 (UTC) (edited on 2025-07-20 08:34 (UTC) by JohnTh) 

commit 083b513f1e79ec1a948841a8fe2e9f18943acaa7
Author: John Th
Date:   Sun Jul 20 13:04:08 2025 +1000

    Embed version information

    https://duckdb.org/docs/stable/dev/building/build_configuration.html#overriding-git-hash-and-version

    https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-db/duckdb/duckdb-1.3.2.ebuild

diff --git a/PKGBUILD b/PKGBUILD
index b813458e9ddd..d00f901b3602 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -36,7 +36,8 @@ prepare() {
     -S "$pkgbase-$pkgver" \
     -B build \
     -D CMAKE_BUILD_TYPE=Release \
-    -D CMAKE_INSTALL_PREFIX=/usr
+    -D CMAKE_INSTALL_PREFIX=/usr \
+    -D OVERRIDE_GIT_DESCRIBE="v${pkgver}"
 }

 build() {

dlb commented on 2025-06-03 22:32 (UTC)

I think the version number is not built correctly into the binary:

# duckdb -version
v0.0.1 0123456789

Looking at DuckDBConfigVersion.cmake, it might be necessary to set ${PACKAGE_VERSION}?

Dominiquini commented on 2025-04-29 17:31 (UTC) (edited on 2025-04-29 17:35 (UTC) by Dominiquini)

@gds506: Sorry. I meant to try this:

source=("${pkgbase}-${pkgver}::git+https://github.com/duckdb/duckdb.git#tag=v${pkgver}")
b2sums=('0ece9b96823e0d2eedab3dc6c8206a34395b4edb469e096256e7ca18a6141e8850fab5c55df0e785c5a790126773acf4656f5f8d79b77f4ac70c47c15a5034d0')

I think this program needs to be compiled inside a working git directory!

gds506 commented on 2025-04-29 15:21 (UTC)

Thanks @Dominiquini I changed the source and b2sums to:

source=(https://github.com/duckdb/duckdb/releases/download/v${pkgver}/duckdb_python_src.tar.gz)
b2sums=('80694db104684ba55c39fc9d92faacb2205badc72a4285b157e3afcf9c22785210102c0233df2d540ad2e468c14842b20e29f295dbb0bacaa640ca1020c05023')

But still get the setuptools_scm related error when compiling:

LookupError: setuptools-scm was unable to detect version for /var/tmp/pamac-build-gds506/duckdb/src/duckdb-1.2.2.

Make sure you're either building from a fully intact git repository or PyPI tarballs. Most other sources (such as GitHub's tarballs, a git checkout without the .git folder) don't contain the necessary metadata and will not work.

For example, if you're using pip, instead of https://github.com/user/proj/archive/master.zip use git+https://github.com/user/proj.git#egg=proj

Alternatively, set the version with the environment variable SETUPTOOLS_SCM_PRETEND_VERSION_FOR_${NORMALIZED_DIST_NAME} as described in https://setuptools-scm.readthedocs.io/en/latest/config.
==> ERROR: A failure occurred in build().
    Aborting...

Dominiquini commented on 2025-04-25 21:00 (UTC)

@gds506 I was able to install downloading the PKGBUILD and change the source to point to the git repo with the correct tag!

gds506 commented on 2025-04-25 19:00 (UTC)

Has anyone been able to install the current version? If that's the case please share with us how you did it.

1 2 3 Next › Last »