The README does not say what quak backup does with a photo that was deleted in Ente. That is the first thing a backup user asks.
Steps
quak backup ./my-backup
Delete one photo in Ente; it moves to the trash and leaves every album.
quak backup ./my-backup
What happened
The deleted photo's original and its JSON stay at their save path. Its symlinks in the album folders are removed. The summary does not mention it.
The README's "The backup directory" says what happens to deleted and renamed collections and to a photo whose date changes. It says nothing about a deleted photo, so a reader cannot tell whether deleting a photo in Ente also deletes it from the backup.
What should happen
"The backup directory" in README.md states the current behaviour in one or two sentences: a file deleted in Ente keeps its original and its JSON at its save path, and loses its links in the album folders.
Model: opus-5-5
The README does not say what `quak backup` does with a photo that was deleted in Ente. That is the first thing a backup user asks.
## Steps
1. `quak backup ./my-backup`
2. Delete one photo in Ente; it moves to the trash and leaves every album.
3. `quak backup ./my-backup`
## What happened
The deleted photo's original and its JSON stay at their save path. Its symlinks in the album folders are removed. The summary does not mention it.
The README's "The backup directory" says what happens to deleted and renamed collections and to a photo whose date changes. It says nothing about a deleted photo, so a reader cannot tell whether deleting a photo in Ente also deletes it from the backup.
## What should happen
"The backup directory" in `README.md` states the current behaviour in one or two sentences: a file deleted in Ente keeps its original and its JSON at its save path, and loses its links in the album folders.
Model: opus-5-5
clawbot
self-assigned this 2026-11-11 21:22:24 +01:00
PR: #246, branch issue-242-readme-deleted-photo. "Save paths" in README.md now says a file deleted in Ente keeps its original and its JSON at its save path, and the next run removes its symlinks from the collection directories.
Model: opus-5-5
PR: https://git.eeqj.de/sneak/quak/pulls/246, branch `issue-242-readme-deleted-photo`. "Save paths" in `README.md` now says a file deleted in Ente keeps its original and its JSON at its save path, and the next run removes its symlinks from the collection directories.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The README does not say what
quak backupdoes with a photo that was deleted in Ente. That is the first thing a backup user asks.Steps
quak backup ./my-backupquak backup ./my-backupWhat happened
The deleted photo's original and its JSON stay at their save path. Its symlinks in the album folders are removed. The summary does not mention it.
The README's "The backup directory" says what happens to deleted and renamed collections and to a photo whose date changes. It says nothing about a deleted photo, so a reader cannot tell whether deleting a photo in Ente also deletes it from the backup.
What should happen
"The backup directory" in
README.mdstates the current behaviour in one or two sentences: a file deleted in Ente keeps its original and its JSON at its save path, and loses its links in the album folders.Model: opus-5-5
PR: #246, branch
issue-242-readme-deleted-photo. "Save paths" inREADME.mdnow says a file deleted in Ente keeps its original and its JSON at its save path, and the next run removes its symlinks from the collection directories.Model: opus-5-5