Package Details: slskdn-bin 2026051904.slskdn.263-4

Git Clone URL: https://aur.archlinux.org/slskdn-bin.git (read-only, click to copy)
Package Base: slskdn-bin
Description: slskdN, an unofficial batteries-included fork of slskd with SongID, Discovery Graph, multi-source downloads, DHT mesh networking, auto-replace, wishlist, and security hardening.
Upstream URL: https://github.com/snapetech/slskdn
Licenses: AGPL-3.0-or-later
Conflicts: slskd, slskd-bin, slskdN
Provides: slskdn
Submitter: keefshape
Maintainer: keefshape
Last Packager: keefshape
Votes: 1
Popularity: 0.43
First Submitted: 2025-12-06 07:25 (UTC)
Last Updated: 2026-05-19 05:03 (UTC)

Dependencies (5)

Required by (0)

Sources (5)

Latest Comments

keefshape commented on 2026-04-24 16:46 (UTC)

@dehumanizer Whoops, corrected that too in 178.

dehumanizer commented on 2026-04-24 09:04 (UTC) (edited on 2026-04-24 09:05 (UTC) by dehumanizer)

Hi!

THanks for the prompt reply. With the 177 build, the dependency issue is gone, I can confirm this. However, directories are created with incorrect permissions, preventing startup via systemd (or as any non-root user):

drwx------ 1 root root 28790 ápr   24 10.47 /usr/lib/slskd/releases/0.24.5.slskdn.177/

Setting correct permissions obviously fixes the issue.

keefshape commented on 2026-04-23 21:31 (UTC)

@dehumanizer Thanks for the report. This is not an upstream issue, this was ours. We've diverged from upstream a bit on libraries and dependencies, and that resulted in a packaging issue with the AUR build. New one coming, should resolve.

dehumanizer commented on 2026-04-23 20:16 (UTC)

Hi!

Latest version breaks on Manjaro: it misses "File name: 'Microsoft.AspNetCore.Diagnostics.Abstractions, Version=10.0.0.0". Downgraded (0.24.5.slskdn.175-1 => 0.24.5.slskdn.174-1) and works fine now. Could be some dependency thing but let me know whether I should report this upstream instead.

keefshape commented on 2026-03-15 19:02 (UTC)

@WinnerWind - thanks for the alert. hashes for aur releases should be fixed for all future releases, including one later today.

WinnerWind commented on 2026-03-14 14:01 (UTC)

These validity checks have been bothering me since forever, will they be fixed? 

==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found slskdn-main-linux-x64.zip
  -> Found slskd.service
  -> Found slskd.yml
  -> Found slskd.sysusers
==> Validating source files with sha256sums...
    slskdn-main-linux-x64.zip ... Skipped
    slskd.service ... FAILED
    slskd.yml ... Passed
    slskd.sysusers ... Passed
==> ERROR: One or more files did not pass the validity check!
 -> error making: slskdn-bin-exit status 1