[GUI Plugin] calibre Updater

[JSWolf]

Originally Posted by dunhill

That's why it was designed this way from the moment you suggested beta notifications: the plugin does its job of notifying users and providing the link, but automatic installation is reserved exclusively for stable versions. This is to avoid version conflicts.

However, users who want to install beta versions are notified and can proceed with the installation, depending on their intended use of the beta.

But asking if I want to install an older version when clearly that won't work is a bug. If I'm running the latest beta version, it should tell me I'm on the latest beta.

You could make it an option to allow beta versions to be downloaded and installed and treated like stable versions and if I'm running a beta, only show me a release version if it's newer because then it can be installed.

[jpiebrig]

First of all, I’d like to thank you for your plugin and all the work that goes into it. I find it very useful.
I’m just an ordinary user, and looking at this thread, I’m always surprised to see how complicated it is to do simple things.
Thank you also for wanting to keep this plugin simple to use, without adding extra features that have been rushed through just to satisfy a single user’s request.

“This plugin suits me. Perfect! It doesn’t suit me, so I’ll submit a feature request. It isn’t accepted, and as it stands it doesn’t suit me, so I won’t use it. End of story!”

If a significant number (a lot...) of users express a need for an additional feature, then yes, it’s worth looking into.

I’ve seen far too many developers who’ve created a good programme or plugin give in to simple requests—ones with no basis in general usage—only to very quickly end up with a convoluted mess on their hands, completely off-putting for a novice.

Keep it simple!

After that little digression, I’ll get to my own little request :


I’d like to translate Calibre Updater into French, if it is not already done. Even though there isn’t much to translate, it’s so much nicer and easier to read in your mother tongue.

Could you please tell me where I can find the localisation template or provide the relevant source file (.po or equivalent)?

Once translated, where should I send the French translation?


Thank you.

[dunhill]

Originally Posted by jpiebrig

First of all, I’d like to thank you for your plugin and all the work that goes into it. I find it very useful.
I’m just an ordinary user, and looking at this thread, I’m always surprised to see how complicated it is to do simple things.
Thank you also for wanting to keep this plugin simple to use, without adding extra features that have been rushed through just to satisfy a single user’s request.

“This plugin suits me. Perfect! It doesn’t suit me, so I’ll submit a feature request. It isn’t accepted, and as it stands it doesn’t suit me, so I won’t use it. End of story!”

If a significant number (a lot...) of users express a need for an additional feature, then yes, it’s worth looking into.

I’ve seen far too many developers who’ve created a good programme or plugin give in to simple requests—ones with no basis in general usage—only to very quickly end up with a convoluted mess on their hands, completely off-putting for a novice.

Keep it simple!

After that little digression, I’ll get to my own little request :


I’d like to translate Calibre Updater into French, if it is not already done. Even though there isn’t much to translate, it’s so much nicer and easier to read in your mother tongue.

Could you please tell me where I can find the localisation template or provide the relevant source file (.po or equivalent)?

Once translated, where should I send the French translation?


Thank you.

Thanks for your feedback. You can send me the file PO right here. I also invite requests for other languages; just place your order and I'll upload the translation updates soon.

[JSWolf]

Is the bug where it's offering me an earlier version because I'm running a beta going to be fixed? Is the bug where it won't download and install a beta going to be fixed?

[dunhill]

Originally Posted by JSWolf

Is the bug where it's offering me an earlier version because I'm running a beta going to be fixed? Is the bug where it won't download and install a beta going to be fixed?

Hi JSWolf. There are no plans to modify that part, as the plugin is deliberately designed for the stable branch and the standard installation flow used by the vast majority of users.

Beta versions (Previews) are downloaded from a different directory structure, have a very volatile lifecycle, and handle filenames that vary depending on the architecture or whether they are special packages. Attempting to automate all of that would open the door to many unforeseen version control errors and broken paths.

For those who prefer to test betas, the best approach is to keep the current informational notice as a reference and perform the download and update manually, thus ensuring that the environment and database remain under your control.

[dunhill]

Originally Posted by jpiebrig

First of all, I’d like to thank you for your plugin and all the work that goes into it. I find it very useful.
I’m just an ordinary user, and looking at this thread, I’m always surprised to see how complicated it is to do simple things.
Thank you also for wanting to keep this plugin simple to use, without adding extra features that have been rushed through just to satisfy a single user’s request.

“This plugin suits me. Perfect! It doesn’t suit me, so I’ll submit a feature request. It isn’t accepted, and as it stands it doesn’t suit me, so I won’t use it. End of story!”

If a significant number (a lot...) of users express a need for an additional feature, then yes, it’s worth looking into.

I’ve seen far too many developers who’ve created a good programme or plugin give in to simple requests—ones with no basis in general usage—only to very quickly end up with a convoluted mess on their hands, completely off-putting for a novice.

Keep it simple!

After that little digression, I’ll get to my own little request :


I’d like to translate Calibre Updater into French, if it is not already done. Even though there isn’t much to translate, it’s so much nicer and easier to read in your mother tongue.

Could you please tell me where I can find the localisation template or provide the relevant source file (.po or equivalent)?

Once translated, where should I send the French translation?


Thank you.

jpiebrig
Version 1.19 French translation
The only thing not translated is the text describing the features of the latest version.

[JSWolf]

Originally Posted by dunhill

Hi JSWolf. There are no plans to modify that part, as the plugin is deliberately designed for the stable branch and the standard installation flow used by the vast majority of users.

Beta versions (Previews) are downloaded from a different directory structure, have a very volatile lifecycle, and handle filenames that vary depending on the architecture or whether they are special packages. Attempting to automate all of that would open the door to many unforeseen version control errors and broken paths.

For those who prefer to test betas, the best approach is to keep the current informational notice as a reference and perform the download and update manually, thus ensuring that the environment and database remain under your control.

Even so, it's a bug offering me an older version to install when it won't install.

[dunhill]

If no errors are reported, I will release it as the official version.

Calibre Updater 1.21.0

Almost automatic installation on all three systems

Windows: There's no need to go through the installation wizard (Next, Next...). Simply confirm the plugin's prompt and accept Windows' permission, which displays the official installer signed by Kovid Goyal. From there, the installation continues automatically, with a progress bar, and Calibre reopens automatically upon completion.

macOS: There's no need to drag Calibre to Applications or choose between keeping or replacing the previous version. The plugin safely replaces the application (if something goes wrong, the previous version remains intact) and reopens Calibre. It works on Macs with Apple Silicon and Intel processors.
Linux: It uses the official Calibre installer, displays progress in a log window, and notifies you if authentication fails.

Gracious Calibre shutdown

The plugin waits for Calibre to completely close before installing, without a fixed time limit. Thus, tasks that other plugins perform upon closing, such as backing up settings, finish before the installation begins, regardless of how long they take.

Previously, the Viewer and Book Editor ran in the background without notification. Now, the plugin notifies you if either is open and lets you choose: close them yourself (to save changes), have the plugin close them, or cancel.

It also notifies you if there are ongoing tasks, such as conversions, metadata downloads, or uploads to a device, and waits for them to finish or be canceled.

Change List

Automatic translation to the Calibre interface language, with a button to view the original English text. This can be disabled in the settings.

Beta Versions (Preview)

Beta versions are trial versions of Calibre that are installed manually. The plugin can notify you when a new version is available (option in the settings), but it never downloads or installs them. If you have a Beta version installed, the plugin doesn't modify it: it only notifies you when a newer stable version is released, and the update is up to you.

If you're using the regular version of Calibre, none of this affects you: the plugin only installs official stable versions.

Security and Diagnostics

Downloads with certificate verification and file integrity checks.

If something goes wrong, Calibre is never left partially installed: the installer or the downloads page opens to complete the installation manually.
A log file (calibre-updater.log) is saved in the downloads folder, which is useful for reporting problems.

The plugin also differentiates our calibre installation. Image 5

Translations:
Calibre Updater is available in English (the original language) and 18 other languages: Spanish, French, German, Italian, Czech, Slovak, Swedish, Serbian (Latin American), Russian, Ukrainian, Japanese, Chinese (China), Korean, Arabic, Dutch, Portuguese (Brazil), Galician, and Tamil. Spanish, French, German, and Italian were the first languages ​​translated for the plugin. The other fourteen were chosen based on the progress of Calibre's translation. All languages ​​with a fully translated Calibre interface and those with over 80% translation were included. This ensures that users of Calibre in these languages ​​also see the plugin in their own language, instead of encountering only the English menu within a translated program.

[JSWolf]

Has it been fixed so it's not offering to install the latest stable when you are running a later beta version?

[dunhill]

Originally Posted by JSWolf

Has it been fixed so it's not offering to install the latest stable when you are running a later beta version?

Yes, this has been fixed.

[fogice]

Originally Posted by dunhill

If no errors are reported, I will release it as the official version.

Looks good on macOS 27.

[JSWolf]

Originally Posted by dunhill

Yes, this has been fixed.

Thank you.

[JSWolf]

I've found another bug. I'm running 9.16.100. I am unable to update to the 9.17.0 release version.

[dunhill]

Hi, thanks for the report! This is actually expected behaviour, not a bug. You’re running a Beta build of calibre (9.16.100), and as the message says, the plugin deliberately doesn’t install anything over a Beta. It only lets you know when a new stable version is out, which it did correctly with 9.17.0.
Also, Betas can be set up in many different ways depending on each user: installed over the stable version, in a separate folder, renamed, alongside a Portable copy, and so on. There’s no reliable way for the plugin to know which setup a user chose, or which copy they want updated, so overwriting anything there could easily break someone’s installation. That’s why the plugin only handles the standard stable installation automatically and just notifies on Betas and Portable versions. Users who run Betas are usually experienced enough to update them by hand, while the plugin is meant to make life easier for the typical calibre user with a single stable installation.
If you are using a portable version, the notification will look like this.
Betas are meant for testing and may contain bugs, so keeping them separate from the plugin’s automatic updates avoids confusion and protects your stable installation.

[dunhill]

Calibre Updater 1.22.0: what’s new

1. Update checks while calibre stays open
Before, the plugin only checked for new versions when calibre started. If you left calibre open for days, it could say “you already have the latest version” when a newer one was out. Now it checks again every 24 hours, and again whenever you click Update now. If a new version is available, the update window keeps showing up every 24 hours until you update.

2. A clearer settings window
The settings window now has three parts:

Notifications: the same options as before (translated changelog, maintenance versions only, Beta notices).
This calibre installation: shows which calibre you’re running (version, type and folder). It’s just information, and it’s handy to include in a screenshot when asking for help.
Advanced Configuration: only appears if you’re running a Beta or a Portable copy. Users with a normal installation never see it.

3. Optional automatic updates for Beta and Portable copies
Until now the plugin only notified Beta and Portable users and left the update to them. It still does that by default, but now you can choose to let it update that specific copy:

The option is off by default.
When you turn it on, the plugin asks you to confirm and shows the exact folder it will update.
Before updating, it shows the folder again.
Only that folder is updated. Any other copies of calibre on your computer are left alone.

How each case works

Normal installation (Windows, macOS, Linux in /opt/calibre): nothing changes. Updates work as before.
Beta: if you allow it, the plugin brings your Beta to the next stable version, in the same place. It never installs Betas; those are always your own choice, installed by hand. Once your Beta becomes stable, the permission is removed automatically, so a future Beta won’t be updated unless you allow it again.
Portable (Windows): if you allow it, the plugin downloads the official Portable installer and updates your Portable folder in place. Your library and settings stay untouched, and calibre reopens when it’s done. The folder name doesn’t matter; only the full path must be shorter than 59 characters (an official installer limit). If it’s longer, the plugin tells you.
Flatpak, AppImage, Snap, distribution packages, Wine, or a Linux Beta outside /opt/calibre: notifications only, as before. These have their own ways of updating, and the plugin won’t interfere.

Tested on Windows 11 with a Portable copy (9.16.0 → 9.17.0) and with a Beta (9.16.100 → 9.17.0)