Error when using -r about calcardbackup HOT 9 CLOSED

Seems to work like a charm, thanks!

+  Backup successfully compressed!
+  Find your backup here: /mnt/backup/calcardbackup-2019-05-27.tar.gz
+  deleting backups older than 30 days:
+     --> no backups older than 30 days found to delete.
+  Mon May 27 22:13:47 CEST 2019 --> END calcardbackup

from calcardbackup.

I can't reproduce the issue, which makes bughunting a bit complicated - but I kind of have an idea what the problem might be.
I'll have a closer look the next couple of days.

For my information:
Which operating system are you using on the machine where calcardbackup is running?
Which find version is installed (check with find --version)?

EDIT: just noticed, that the title is a bit misleading. This is about option -r and not about option -o
I changed the title of this issue

from calcardbackup.

0350d72 should fix this
The fix is currently only in the testing branch until the next release.

I am also going to rewrite the function which gets executed when run with option -ltm where the same problem exists

from calcardbackup.

@theincredibleschnigges could you please check whether the version from 8d973cae solves your issue?

from calcardbackup.

With the new version on the testing branch, I get the following error:

• deleting backups older than 30 days:
  date: illegal time format
  usage: date [-jnRu] [-d dst] [-r seconds] [-t west] [-v[+|-]val[ymwdHMS]] ...
  [-f fmt date | [[[[[cc]yy]mm]dd]HH]MM[.ss]] [+format]

I am working in a FreeBSD 11.2 jail (find --version is not supported).

from calcardbackup.

I need some more time, because I need to dig a bit deeper in options to FreeBSD commands.

from calcardbackup.

276ee15 should fix the issue for you (at least it does in my FreeBSD-VM)
Could you please test and verify?
EDIT: I did another minor modification, which should not make any difference. Could you please confirm, that your issue is solved with: a3f0188 - thanks.

from calcardbackup.

@theincredibleschnigges have you checked yet whether your issue still exists in the testing branch?

from calcardbackup.

This issue is solved with release v0.9.0 (2c7e9ba)

from calcardbackup.