Prune -id -collect-only overwrites Fossil collection 1

Bug
,
#1

Please describe what you are doing to trigger the bug:

duplicacy prune -id a -keep 0:1800 -keep 7:30 -keep 1:7 -collect-only
duplicacy prune -id b -keep 0:1800 -keep 7:30 -keep 1:7 -collect-only
duplicacy prune -id c -keep 30:365 -keep 7:90 -keep 1:7

Please describe what you expect to happen (but doesn’t):
Expect prune to run without creating unreferenced fossils.

Please describe what actually happens (the wrong behaviour):
First prune command saves Fossil collection 1; second prune command overwrites Fossil collection 1, creating unreferenced fossils.

Trouble Pruning Multiple Snapshot IDs - "deletion criteria aren't met"
#2

I can confirm that this is a bug. I’ll fix it in the next CLI release.

Thank you for the find!

Prune - What happens when I stop backing up a particular ID
#3

I’m encountering an issue that sounds similar to the one in this thread. I’m using a series of duplicacy prune -id <id> ... -collect-only commands followed by duplicacy prune -delete-only, and I notice that they all only save to Fossil collection 1, and so are overwriting each other.

Was this bug ever fixed, or is it still outstanding?

#4

Was this bug ever fixed, @gchen (pinging just in case you missed this thread)? I can find no git commit about this bug.

1 Like
#5

Sorry I forgot about it. I will make sure to include it in the new release scheduled for later this week.

1 Like
#6

Hi, any news about CLI new release ?

#7

New version has been released: Release Duplicacy Command Line Version 3.2.4 · gilbertchen/duplicacy · GitHub

2 Likes
#8

Great many thanks for thé work.

#9

Thanks for the new release