9001 / 9001/copyparty

Copyparty cannot delete volume folder that is no longer in the config.

Offen
#1,082 0 Kommentare 1 Reaktion 1 zugewiesene Person Beansprucht von @9001 Auf GitHub ansehen
bug
Vorherrschende Sprache
Python
Sterne
46.6k
Forks
1.9k
Ø Merge
10 T. 16 Std.
Gemergte PRs (30 T.)
5

Beschreibung

### Describe the bug
I removed a copyparty volume from the config to a different folder, and then when trying to delete the old volume folder from the copyparty ui, it still fails.

### To Reproduce
- Make volume

```yaml
[/whopper/test-volume]
/src/copyparty/test-volume
accs:
.rwmda: me
```
- Start copypary.
- You can try to delete now and it will fail (good, expected)
- Comment out volume
- Restart copyparty.
- Try delete - failed to delete, may be blocked by config.

### Server details (if you're NOT using docker/podman)
remove the ones that are not relevant:
* **server OS / version:** EndeavourOS linux (arch-based)
* **what copyparty did you grab:** sfx
* **how you're running it:** systemd-service
* run copyparty with `--version` and grab the last 3 lines (they start with `copyparty`, `CPython`, `sqlite`) and paste them below this line:
```
copyparty v1.19.21 "usernames" (2025-12-02)
CPython v3.13.5 on Linux64 6.12.48 [GCC 14.2.0]
sqlite 3.46.1*1 | jinja 2.11.3 | pyftpd 1.5.10 | tftp 0.4.0
```

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.