Arch Linux User Repository

@Aromatic, are there plans to update dsh to 0.1.7-rc.2? Many plugins have updated to 0.1.7, and due to breaking changes, plugins for 0.1.7-rc.2 are incompatible with 0.1.5. If all the plugins have updated, it would probably be better not to stay on 0.1.5.

@C.Schmidpeter, Thanks for preparing and testing the update.

For deepseek-harness-bin, I currently only track upstream releases from the latest channel. I don't follow the next channel / RC releases, so I won't bump the package to 0.1.7-rc.1.

Once 0.1.7 (or another release) reaches latest, I'll update the package accordingly.

Also, thanks for keeping the .gitignore and aarch64 changes separate from the version bump.

I saw your co-maintainer request as well. I'll consider that separately from this release update.

@Aromatic, could you please add me as co-maintainer of deepseek-harness-bin as well?

I'm already co-maintaining deepseek-harness-git and mainly use the -bin package now, so I'd be happy to help with release bumps and packaging fixes.

I prepared and tested the 0.1.7-rc.1 update below.

From 12cfde33d5e4f32030958aff0e59f17ab8301ce1 Mon Sep 17 00:00:00 2001
From: Christoph Schmidpeter <christoph.schmidpeter@gmail.com>
Date: Thu, 24 Sep 2026 08:34:03 +0200
Subject: [PATCH] pkg: update DeepSeek Harness to 0.1.7-rc.1

---
 .SRCINFO | 6 +++---
 PKGBUILD | 6 +++---
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/.SRCINFO b/.SRCINFO
index c59c6a9..cd3fb99 100644
--- a/.SRCINFO
+++ b/.SRCINFO
@@ -1,6 +1,6 @@
 pkgbase = deepseek-harness-bin
        pkgdesc = DeepSeek Harness CLI and agent harness
-       pkgver = 0.1.5rc.3
+       pkgver = 0.1.7rc.1
        pkgrel = 1
        url = https://github.com/deepseek-ai/deepseek-harness
        arch = x86_64
@@ -12,7 +12,7 @@ pkgbase = deepseek-harness-bin
        conflicts = deepseek-harness
        conflicts = deepseek-harness-git
        options = !strip
-       source = dsh-0.1.5-rc.3.tgz::https://registry.npmjs.org/@deepseek-ai/dsh/-/dsh-0.1.5-rc.3.tgz
-       sha256sums = 4977d29233a5928a4ef1c16e44bdc19d77bbf38f16823d54ec87c5b0198830bf
+       source = dsh-0.1.7-rc.1.tgz::https://registry.npmjs.org/@deepseek-ai/dsh/-/dsh-0.1.7-rc.1.tgz
+       sha256sums = efc7f91923ae5e7bc35a654fd80a8eee9d36ed05a141ce61083973182d78cd42

 pkgname = deepseek-harness-bin
diff --git a/PKGBUILD b/PKGBUILD
index aacbba7..29ff59b 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,6 +1,6 @@
 pkgname=deepseek-harness-bin
-_npmver=0.1.5-rc.3
-pkgver=0.1.5rc.3
+_npmver=0.1.7-rc.1
+pkgver=0.1.7rc.1
 pkgrel=1
 pkgdesc='DeepSeek Harness CLI and agent harness'
 arch=('x86_64')
@@ -12,7 +12,7 @@ options=('!strip')
 provides=('deepseek-harness')
 conflicts=('deepseek-harness' 'deepseek-harness-git')
 source=("dsh-${_npmver}.tgz::https://registry.npmjs.org/@deepseek-ai/dsh/-/dsh-${_npmver}.tgz")
-sha256sums=('4977d29233a5928a4ef1c16e44bdc19d77bbf38f16823d54ec87c5b0198830bf')
+sha256sums=('efc7f91923ae5e7bc35a654fd80a8eee9d36ed05a141ce61083973182d78cd42')

 prepare() {
   rm -rf npm-root npm-cache
--
2.55.0

@Aromatic could you make me co-maintainer to this -bin package too pleae? then I could maintain/bump at times cause I am using the -bin one now

@wkaix: Thanks for the report. This dependency comes from the system nodejs binary rather than deepseek-harness-bin. This should be handled by the nodejs package maintainer. There is nothing to rebuild or change in this AUR package.

Hello maintainer, after gcc-ada upgrade libada.so soname changed from 3 to 4 (now only libada.so.4 is present). The binary still expects .3 and fails. Thanks for maintaining.

@papa33: Thanks for the report! This is a known false positive from namcap. The upstream npm package ships two prebuilt variants of koffi: linux_x64/koffi.node (glibc) and musl_x64/koffi.node (musl).

File "/usr/lib/node_modules/@deepseek-ai/dsh/node_modules/@koromix/koffi-linux-x64/musl_x64/koffi.node" from package "deepseek-harness-bin" is missing dependency "libc.musl-x86_64.so.1"

@szdytom: Thanks for looking into this, but I believe the premise doesn't hold for node-pty@1.1.0. Its scripts/prebuild.js exits 1 on linux-x64 (no prebuilds/linux-x64 directory is shipped — only darwin/win32 prebuilds exist in the tarball), so the || node-gyp rebuild fallback does run. The current PKGBUILD (--allow-scripts=...,node-pty) already produces a working node-pty/build/Release/pty.node — I verified it in my current pkgrel=2 build output, and reproduced it with a fresh npm install --global --allow-scripts of the same tarball. The extra node-gyp rebuild and the node-gyp/python/gcc/make makedepends are therefore unnecessary. If you're hitting a real failure in a clean chroot, share the makepkg log and I'll look at it.