Error with Save to Disk after update

[MerlinMama]

I hope I'm putting this in the right place.

After the update to Calibre 1.42.0 this morning, I get an error when I try to save to disk. This feature was working yesterday. I get the following details:

calibre, version 1.42.0
WARNING: Could not save some books: Could not save some books, Click the show details button to see which ones.

Traceback (most recent call last):
File "site-packages\calibre\library\save_to_disk.py", line 440, in save_serialized_to_disk
File "site-packages\calibre\library\save_to_disk.py", line 312, in do_save_book_to_disk
ValueError: Failed to calculate path for save to disk. Template: {series}{series_index:| | - }{title}
Error: 'Formatter' object has no attribute 'strip_results'

[chaley]

This has been fixed.

Kovid will upload a new version of 1.42 containing the fix in a few hours.

[MerlinMama]

Thanks! I looked but didn't see anything. Probably just missed it somehow.

[kovidgoyal]

https://bugs.launchpad.net/calibre/+bug/1335010

[sinelunte]

No, it has not been resolved. I tried to send an e-book to my Kobo and the same error.

I use the version 1:42

[chaley]

Originally Posted by sinelunte

No, it has not been resolved. I tried to send an e-book to my Kobo and the same error.

I use the version 1:42

Did you download V1.42 after 12:30 UK time? If you downloaded it before, or if you downloaded the same file again because of a cache somewhere, then the problem will not be fixed.

[BetterRed]

Originally Posted by chaley

Did you download V1.42 after 12:30 UK time? If you downloaded it before, or if you downloaded the same file again because of a cache somewhere, then the problem will not be fixed.

Q. to avoid confusion as to which version one has, would it be possible to use the low order segment of the version number to differentiate 'quick fix' releases - i.e. the one that's there now would be V1.42.1?

Can't recall the low order segment ever being any value other than 0.

BR

[theducks]

Originally Posted by BetterRed

@chaley - I think you mean V1.42.

Q. to avoid confusion as to which version one has, would it be possible to use the low order segment of the version number to differentiate 'quick fix' releases - i.e. the one that's there now would be V1.42.1?

Can't recall the low order segment ever being any value other than 0.

BR

You echo my thoughts.
Calibre used to use those digits. Normal releases would always be a dot 0

an emergency fix would bump that (and cause the version new detector to fire)

[MerlinMama]

Yeah, I was waiting for the notice there was a new version until I realized it wouldn't show up. All is good now, though.

[BetterRed]

Originally Posted by theducks

... and cause the version new detector to fire

Didn't think of that serendipitous side effect

I had a longish to & fro with someone here a while back, we were tossing checksums back & forth, I think the OP downloaded from a third party site - unique version numbers would have avoided some of the confusion

BR