Can't Set timestamp field to first or last of month via CLI
Bug #1883433 reported by
Marc Grissom
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| calibre |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Windows Calibre portable version 4.18
I was testing out changing metadata via the CLI and noticed this weird behavior. The command below is supposed to set the timestamp (aka Date) field to February 1, 2020. However it ends up getting set to February 2nd. If I try the 29th, it will get set to the 28th. Dates in between seem to always get set correctly. It seems to do this with all the other months as well.
"D:\Software\
| description: | updated |
| description: | updated |
| description: | updated |
Revision history for this message
| Kovid Goyal (kovid) wrote Fixed in master | #1 |
| Changed in calibre: | |
| status: | New → Fix Released |
To post a comment you must log in.
Fixed in branch master. The fix will be in the next release. calibre is usually released every alternate Friday.
status fixreleased