View Single Post
Old 06-06-2011, 08:04 AM   #2
kiwidude
Calibre Plugins Developer
kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.
 
Posts: 4,731
Karma: 2197770
Join Date: Oct 2010
Location: Australia
Device: Kindle Oasis
This error is discussed in the Modify ePub thread in the dev forums. It has already been fixed for the next Calibre release. It is caused by a change in Calibre 0.8.4 to use the timestamps from the zip file for files when exploding, rather than the system date/time. What this means is that in rare but nonethless existing circumstances, files that have no timestamp in the zip file will blow up when trying to zip them back up again.

The example ePub I found had this situation on the MimeType file. When you look at it in the file explorer, it shows no date present on the file when you look at it on the exploded ePub.

The workaround assuming you do not want to wait or run from source is to "touch" the files that have no timestamp when they are exploded. So look for any file(s) that have no timestamp in the exploded directly, and do an edit on them to cause them to now have a modified date. Obviously if it is a file like mimetype be sure to keep the content the same, either use an os touch command or just save from an editor on it.
kiwidude is offline   Reply With Quote