Am 05.10.22 um 14:44 schrieb AW:

Sorry, even with this command the output is in German.

If you're using sudo instead of running from a root terminal, you need to add --preserve-env: LANG=... LC_ALL=... sudo --preserve-env=LANG,LC_ALL zypper ... Though in this case I think LANG should be enough, and you can also just set LANG=C: LANG=C sudo --preserve-env=LANG zypper ... Aaron

Hi, Am 05.10.22 um 15:15 schrieb Cor Blom:

One package that calibre depends on had a build failure. One of the next snapshots will have a fix. See

https://bugzilla.opensuse.org/show_bug.cgi?id=1203967

A little bit more background info: - Qt 6.4.0 was released on September 29. - The qt-* packages for Tumbleweed were submitted by Christophe on Sept 30 and accepted into Factory on Oct 1. - PyQt6 (packaged as python-PyQt6*) did not support building with Qt 6.4.0 until version PyQt6 v6.4.0 which was officially released on Oct 3. - The python-PyQt6* packages for Tumbleweed were prepared from a pre-release submitted on the same day shortly after the official release. - They were accepted into Factory yesterday evening (Oct 4). In this case, Tumbleweed is absolutely bleeding edge. The Qt6 library or any of its dependents are not in Ring1 yet, so the acceptance into Factory does not check for any failing builds except for the packages themselves. We were lucky that upstream PyQt6 came up with support for the Qt6 update in a very timely manner. If you don't want to have an updated library break your application, see that it gets tested during a build in staging or in openQA before the release of a new snapshot. - Ben

On 2022-10-07 01:04, Jim Henderson wrote:

On Wed, 05 Oct 2022 14:18:46 +0200, AW wrote:

...

seems to be an update for Calibre, but it did not make it into factory, there still is an older version.

Calibre's current version is 6.6.1, as installed from the official website. They do specifically state that they recommend installing from their site rather than using a distribution's package manager:

"Please do not use your distribution provided calibre package, as those are often buggy/outdated. Instead use the Binary install described below."

For what it's worth, I've always installed from their site and it has never failed me - no problems with incompatible libraries or anything like that. Maybe instead of repackaging it, there's a way to just install a helper that installs the package from their site directly?

You can install the rpm once, lock it, and then update from upstream thereafter. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)

On 2022-10-07 06:01, Jim Henderson wrote:

On Fri, 7 Oct 2022 02:05:54 +0200, Carlos E. R. wrote:

...

You can install the rpm once, lock it, and then update from upstream thereafter.

Sure, but then again, the upgrade procedure is to run the upstream installer, so it makes sense to me to just start with that. :)

Yes, but installing the rpm first tells the rpm database that calibre is installed, deps are satisfied, and file browsers offer to open books with calibre ;-) -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)

Am 07.10.22 um 01:04 schrieb Jim Henderson:

For what it's worth, I've always installed from their site and it has never failed me - no problems with incompatible libraries or anything like that. Maybe instead of repackaging it, there's a way to just install a helper that installs the package from their site directly? It would still be an outdated package only updated when someone at openSUSE's side remembers to update it. Either you take upstream's package or you don't. But if upstream provides a rpm-md repo it can be part of your zypper call to update it.

Greetings, Stephan

Am Freitag, 7. Oktober 2022, 07:35:20 CEST schrieb Stephan Kulow:

Am 07.10.22 um 01:04 schrieb Jim Henderson:

...

For what it's worth, I've always installed from their site and it has never failed me - no problems with incompatible libraries or anything like that. Maybe instead of repackaging it, there's a way to just install a helper that installs the package from their site directly?

It would still be an outdated package only updated when someone at openSUSE's side remembers to update it. Either you take upstream's package or you don't. But if upstream provides a rpm-md repo it can be part of your zypper call to update it.

Also, in my opinion, the developer of calibre is a, shall we say, somewhat special person. And even with him the packages do not always work without errors. It is not uncommon for him to release an update a day or even a few hours after the release of a version. Oh, and about the package in SUSE. I used the package now for about 6 years. And I can't remember any real problem concerning the packaging during this time. In the current case a few things came together. Translated with www.DeepL.com/Translator (free version)

On Fri, 7 Oct 2022 07:16:36 -0700, Carl Symons wrote:

I've used it for more than 10 years. As suggested by Kovid Goyal, the developer, updating from the Calibre website with the command on the Linux download page. Update glitches are rare to nonexistent. The recommended update process is reliable.

If appropriate, an update notification is displayed when Calibre starts. It's easy to update from the Calibre site.

Same here - I've found it to be a very reliable process. I get what folks are saying about the benefits of using the repo; but I also understand what the original developer is saying about update reliability from certain distros' repos (that's why I've historically built pan myself, for example - though I have to say that now that I'm using Tumbleweed as my main driver, I haven't had the need). -- Jim Henderson Please keep on-topic replies on the list so everyone benefits

Am 07.10.22 um 01:04 schrieb Jim Henderson:

Calibre's current version is 6.6.1, as installed from the official website. They do specifically state that they recommend installing from their site rather than using a distribution's package manager:

"Please do not use your distribution provided calibre package, as those are often buggy/outdated. Instead use the Binary install described below."

Quite a number of projects say something like this, yet many users appreciate the convenience of being able to install everything through one package manager and have it updated semi-automatically. On top of this repackaging can improve consistency with the remaining system and deduplicate common resources like libraries, possibly updating them independently. Of course everybody is free to install software through binary installers that they find on the internet, but our goal as a distribution is to nevertheless provide it as package that we reproducibly build from source, so that nobody has to go look for an installer and then update manually. That being said, I know that Calibre is a very special snowflake and I'm glad that I don't have to maintain it. ;) Aaron

Am 08.10.22 um 13:01 schrieb Carlos E. R.:

I have forgotten why I went years ago for independent upgrades in this case, but I can see that Leap 15.3 has version 3.48.0 , while I have version 5.25 (Aug 2021), and that is not the latest. There is a serious delay. I have no idea how things are in TW, though.

I guess that's just a reflection of what was the current version of Calibre at the time when Leap 15.3 was released. Feeding feature updates into Leap is not a thing, so the official repos never got an update from 3.48.0. The devel repo provided a build for 15.3 and 15.4 until Calibre started to require Python >= 3.7. You don't have that in vanilla Leap 15.X., lest PyQt6. Unfortunately, https://build.opensuse.org/package/binaries/Documentation:Tools/calibre/open... and  openSUSE_Leap_15.4 don't have those last supported Python 3.6 builds of calibre 5. They are empty for reasons I don't want to go into again (repository renames). - Ben

Am Samstag, 8. Oktober 2022, 13:01:47 CEST schrieb Carlos E. R.:

On 2022-10-08 00:55, Aaron Puchert wrote:

...

Am 07.10.22 um 01:04 schrieb Jim Henderson:

...

Calibre's current version is 6.6.1, as installed from the official website. They do specifically state that they recommend installing from their site rather than using a distribution's package manager:

"Please do not use your distribution provided calibre package, as those are often buggy/outdated. Instead use the Binary install described below."

Quite a number of projects say something like this, yet many users appreciate the convenience of being able to install everything through one package manager and have it updated semi-automatically. On top of this repackaging can improve consistency with the remaining system and deduplicate common resources like libraries, possibly updating them independently.

Of course everybody is free to install software through binary installers that they find on the internet, but our goal as a distribution is to nevertheless provide it as package that we reproducibly build from source, so that nobody has to go look for an installer and then update manually.

That being said, I know that Calibre is a very special snowflake and I'm glad that I don't have to maintain it. ;)

Yes, I agree that the proper method should be the distro rpms. It would be hell having to upgrade every app independently.

I have forgotten why I went years ago for independent upgrades in this case, but I can see that Leap 15.3 has version 3.48.0 , while I have version 5.25 (Aug 2021), and that is not the latest. There is a serious delay. I have no idea how things are in TW, though.

This has nothing to do with delay. But with the fact that the developer always thinks he has to use the latest libraries. For example QT and python. Here even partly newer than in Tumbleweed. Thus calibre can simply no longer be built. Thus in Leap 15.3: max 3.48.0 in official repos Leap 15.4: max 4.23.0 only in my repo, officially there is no calibre at all Leap 15.5: not built at the moment because of too old python packages. I hope there is said goodbye to the dead python 3.6. Only in tumbleweed the newest version is possible: 6.6.1

I suspect that if the author does not like distributions packaging it, he doesn't make things easy for packagers.

And yes he does not make it easy for packagers. Once for the reasons mentioned above, that he is quite unwilling to look for a bug if you do not take directly his package, but also because of the fact that he is quite special. Regards Eric

Am Samstag, 8. Oktober 2022, 00:55:35 CEST schrieb Aaron Puchert:

Am 07.10.22 um 01:04 schrieb Jim Henderson:

...

Calibre's current version is 6.6.1, as installed from the official website. They do specifically state that they recommend installing from their site rather than using a distribution's package manager:

"Please do not use your distribution provided calibre package, as those are often buggy/outdated. Instead use the Binary install described below."

Quite a number of projects say something like this, yet many users appreciate the convenience of being able to install everything through one package manager and have it updated semi-automatically. On top of this repackaging can improve consistency with the remaining system and deduplicate common resources like libraries, possibly updating them independently.

Of course everybody is free to install software through binary installers that they find on the internet, but our goal as a distribution is to nevertheless provide it as package that we reproducibly build from source, so that nobody has to go look for an installer and then update manually.

That being said, I know that Calibre is a very special snowflake and I'm glad that I don't have to maintain it. ;)

Aaron, I totally agree with you and that's also why I'm always in favor of distribution packages first. Unfortunately, SUSE itself wants to do away with that. Why is still not clear to me. And I also think nothing of it. The container, flatpack, etc. can only be a stopgap if the package is not available in the distribution or it is perhaps too old. If I take all programs from container, snap, flatpack sourcen from upstream, then I can take the original right away, which has decades of experience with it. You know who I mean...:-) And the packaging is limited, except for two things: - Upstream always uses the latest libraries. So you have to live with older versions. But I have never missed anything. And for special things I don't use calibre anyway. - Upstream sometimes pushes a new version after a few hours or a day. And no, to this extent I have never noticed it in any other project. Regards Eric

Am Montag, 10. Oktober 2022, 01:17:39 CEST schrieb Jim Henderson:

On Sat, 8 Oct 2022 00:55:35 +0200, Aaron Puchert wrote:

...

Quite a number of projects say something like this, yet many users appreciate the convenience of being able to install everything through one package manager and have it updated semi-automatically.

Yes, of course.

But few packages actually are as easy to install as Calibre as well, so a failed install is pretty easy to get around. :)

Simple maybe so. But simply executing a script over the Internet I see as very critical. And then also a 1000 line one! No. I'd rather not start that. I have no desire to check the script and then also with each update. No, no. Do that who wants. I do not. Regards Eric