Arch Linux User Repository

@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!

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...

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

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

Below issue is probably related to these messages I see when I build:

-- Found Git: /usr/bin/git (found version "2.48.1")
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
CMake Warning at CMakeLists.txt:309 (message):
  git is available (at /usr/bin/git) but has failed to execute 'log -1
  --format=%h'.  Consider providing explicit GIT_COMMIT_HASH or
  OVERRIDE_GIT_DESCRIBE


fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
CMake Warning at CMakeLists.txt:320 (message):
  git is available (at /usr/bin/git) but has failed to execute 'describe
  --tags --long', likely due to shallow clone.  Consider providing explicit
  OVERRIDE_GIT_DESCRIBE or clone with tags.  Continuing with dummy version
  v0.0.1


-- git hash 0123456789, version v0.0.1, extension folder v0.0.1
-- Extensions will be deployed to: /var/abs/local/duckdb/src/build/repository
-- Load extension 'core_functions' from '/var/abs/local/duckdb/src/duckdb-1.2.1/extensions' @ v0.0.1
-- Load extension 'parquet' from '/var/abs/local/duckdb/src/duckdb-1.2.1/extensions' @ v0.0.1

FYI, I ran into some issues with this package. Although I was able to finally get it to build (by overriding the env variable mentioned below) it somehow built with a version number of "v0.0.1 0123456789". This prevented the app from being able to download extensions, as it was getting a 403 when it attempted to download from the extensions web site. I didn't know how to correct this, and wound up having to install the duckdb-bin package instead. I'd rather install this one though, as I need to install python-duckdb as well, and this package takes care of 2 birds with one stone. If you know how to fix this versioning issue, please advise.

I'm running into a build error:

...
[100%] Linking CXX static library libimdb.a
[100%] Built target imdb
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
/usr/lib/python3.13/site-packages/setuptools/_distutils/dist.py:261: UserWarning: Unknown distribution option: 'tests_require'
  warnings.warn(msg)
Traceback (most recent call last):
  File "/var/abs/local/duckdb/src/duckdb-1.2.0/tools/pythonpkg/setup.py", line 379, in <module>
    setup(
    ~~~~~^
        name=lib_name,
        ^^^^^^^^^^^^^^
    ...<25 lines>...
        },
        ^^
    )
    ^
  File "/usr/lib/python3.13/site-packages/setuptools/__init__.py", line 117, in setup
    return distutils.core.setup(**attrs)
           ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^
  File "/usr/lib/python3.13/site-packages/setuptools/_distutils/core.py", line 145, in setup
    _setup_distribution = dist = klass(attrs)
                                 ~~~~~^^^^^^^
  File "/usr/lib/python3.13/site-packages/setuptools/dist.py", line 322, in __init__
    _Distribution.__init__(self, dist_attrs)
    ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.13/site-packages/setuptools/_distutils/dist.py", line 279, in __init__
    self.finalize_options()
    ~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/lib/python3.13/site-packages/setuptools/dist.py", line 674, in finalize_options
    ep(self)
    ~~^^^^^^
  File "/usr/lib/python3.13/site-packages/setuptools_scm/_integration/setuptools.py", line 123, in infer_version
    _assign_version(dist, config)
    ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
  File "/usr/lib/python3.13/site-packages/setuptools_scm/_integration/setuptools.py", line 58, in _assign_version
    _version_missing(config)
    ~~~~~~~~~~~~~~~~^^^^^^^^
  File "/usr/lib/python3.13/site-packages/setuptools_scm/_get_version_impl.py", line 117, in _version_missing
    raise LookupError(
    ...<8 lines>...
    )
LookupError: setuptools-scm was unable to detect version for /var/abs/local/duckdb/src/duckdb-1.2.0.

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
==> ERROR: A failure occurred in build().
    Aborting...

Any idea what the issue might be?

@seschwar, add

SETUPTOOLS_SCM_PRETEND_VERSION=1.1.0

below pkgver or pkgrel

The package doesn't build:

(...)
[100%] Built target unittest
fatal: No names found, cannot describe anything.
fatal: No names found, cannot describe anything.
Traceback (most recent call last):
  File "/home/seschwar/.cache/pacman/build/duckdb/src/duckdb-1.0.0/tools/pythonpkg/setup.py", line 386, in <module>
    setup(
  File "/usr/lib/python3.12/site-packages/setuptools/__init__.py", line 103, in setup
    return distutils.core.setup(**attrs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/setuptools/_distutils/core.py", line 147, in setup
    _setup_distribution = dist = klass(attrs)
                                 ^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/setuptools/dist.py", line 303, in __init__
    _Distribution.__init__(self, dist_attrs)
  File "/usr/lib/python3.12/site-packages/setuptools/_distutils/dist.py", line 283, in __init__
    self.finalize_options()
  File "/usr/lib/python3.12/site-packages/setuptools/dist.py", line 654, in finalize_options
    ep(self)
  File "/usr/lib/python3.12/site-packages/setuptools_scm/_integration/setuptools.py", line 123, in infer_version
    _assign_version(dist, config)
  File "/usr/lib/python3.12/site-packages/setuptools_scm/_integration/setuptools.py", line 58, in _assign_version
    _version_missing(config)
  File "/usr/lib/python3.12/site-packages/setuptools_scm/_get_version_impl.py", line 117, in _version_missing
    raise LookupError(
LookupError: setuptools-scm was unable to detect version for /home/seschwar/.cache/pacman/build/duckdb/src/duckdb-1.0.0.

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.
(...)

Why does this PKGBUILD try to use GitHub tarballs when the software clearly tells you to not do so?

Same issue with 0.10.0, even after downgrading python-setuptools-scm

I made it compile using SETUPTOOLS_SCM_PRETEND_VERSION

build() {
  cmake --build build

  SETUPTOOLS_SCM_PRETEND_VERSION="$pkgver" python "$pkgbase-$pkgver/tools/pythonpkg/setup.py" build
}

full diff

diff --git a/PKGBUILD b/PKGBUILD
index ba1a892..081b477 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -42,12 +42,12 @@ prepare() {
 build() {
   cmake --build build

-  python "$pkgbase-$pkgver/tools/pythonpkg/setup.py" build
+  SETUPTOOLS_SCM_PRETEND_VERSION="$pkgver" python "$pkgbase-$pkgver/tools/pythonpkg/setup.py" build
 }

 package_duckdb() {
   conflicts=("duckdb-git")
-  DESTDIR="$pkgdir" cmake --install build
+  SETUPTOOLS_SCM_PRETEND_VERSION="$pkgver" DESTDIR="$pkgdir" cmake --install build

   # sqlite wrapper
   install -vDm755 -t "$pkgdir/usr/lib" build/tools/sqlite3_api_wrapper/libsqlite3_api_wrapper.so
@@ -69,7 +69,7 @@ package_python-duckdb() {
   conflicts=("python-duckdb-git")

   # library
-  python "$pkgbase-$pkgver/tools/pythonpkg/setup.py" install --root="$pkgdir" --optimize=1 --skip-build
+  SETUPTOOLS_SCM_PRETEND_VERSION="$pkgver" python "$pkgbase-$pkgver/tools/pythonpkg/setup.py" install --root="$pkgdir" --optimize=1 --skip-build

   # license
   install -vDm644 -t "$pkgdir/usr/share/licenses/$pkgname" "$pkgbase-$pkgver/LICENSE"