On Fri, 1 Jul 2022 09:57:17 +0300 Stratos Zolotas wrote:

I have the same issue but when trying to update (dup) to latest snapshot. Calibre and nextcloud-client are broken after the latest snapshot release.

On Fri, Jul 1, 2022 at 9:48 AM Bob Williams <usenet@karmasailing.uk> wrote:

...

Trying to install nextcloud-desktop client fails because

nothing provides 'libQt5Gui.so.5(Qt_5.15.2_PRIVATE_API)(64bit)' needed by the to be installed nextcloud-desktop-3.5.1-1.1.x86_64

[...]

Hmm. I also use Calibre. I'll take a look and see if it's also broken. BTW, I'm subscribed to this list (obviously) so no need to CC me as well. I prefer to read replies in the same place I posted the question. Regards Bob -- Bob Williams

On Fri, Jul 1, 2022 at 11:12 AM Ben Greiner <code@bnavigator.de> wrote:

Calibre is already fixed and just needs to make its way through the machinery: https://build.opensuse.org/request/show/986099

Thank you for the information. So now, only nextcloud-client is a stopper for the snapshot (at least for anyone using it).

On Fri, 1 Jul 2022 10:06:18 +0300 Andrei Borzenkov wrote:

On Fri, Jul 1, 2022 at 9:48 AM Bob Williams <usenet@karmasailing.uk> wrote:

...

Trying to install nextcloud-desktop client fails because

nothing provides 'libQt5Gui.so.5(Qt_5.15.2_PRIVATE_API)(64bit)' needed by the to be installed nextcloud-desktop-3.5.1-1.1.x86_64

[ ] do not install nextcloud-desktop-3.5.1-1.1.x86_64

[ ] break nextcloud-desktop-3.5.1-1.1.x86_64 by ignoring some of its dependencies

This is a Tumbleweed system with the following repositories enabled

# | Alias | Name | Enabled | GPG Check | Refresh --+----------------------------------+----------------------------+---------+-----------+-------- 1 | Downloaded_RPMs | Downloaded RPMs | Yes | ( p) Yes | No 2 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes 3 | download.opensuse.org-oss | Main Repository (OSS) | Yes | (r ) Yes | Yes 4 | download.opensuse.org-tumbleweed | Main Update Repository | Yes | (r ) Yes | Yes 5 | ftp.gwdg.de-openSUSE_Tumbleweed | Packman Repository | Yes | (r ) Yes | Yes

Repository names are useless without knowing actual URLs.

http://download.opensuse.org/tumbleweed/repo/non-oss/ http://download.opensuse.org/tumbleweed/repo/oss/ http://download.opensuse.org/update/tumbleweed/

[...]

...

How can I restore Nextcloud synchronisation?

You can either fix this package so that it builds again (it fails to build in current TW) or revert to older TW snapshot where this package still worked.

The former is beyond my capabilities, so it looks like I'll have to revert to an older snapshot. -- Bob Williams

On Fri, 2022-07-01 at 14:37 +0200, Eric Schirra wrote:

Am Freitag, 1. Juli 2022, 09:20:11 CEST schrieb Mathias Homann:

...

Am Freitag, 1. Juli 2022, 08:47:59 CEST schrieb Bob Williams:

...

Trying to install nextcloud-desktop client fails because

nothing provides 'libQt5Gui.so.5(Qt_5.15.2_PRIVATE_API)(64bit)' needed by the to be installed nextcloud-desktop-3.5.1-1.1.x86_64

[ ] do not install nextcloud-desktop-3.5.1-1.1.x86_64

[ ] break nextcloud-desktop-3.5.1-1.1.x86_64 by ignoring some of its

dependencies

How can I restore Nextcloud synchronisation?

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

Both errors are fixed.

Thanks!

The reason are Tumbleweed own CFLAGS

FORTIFUY_SOURCE=3 you mean. They are not 'an error', they are a security feature.

There were and are no other errors. And above all, "not built for a long time" is not true. The packages have only

Last successful build was May 17 - first recorded failure on June 15. 'A long time' is relative.

not been built since the new CFLAGS from Suse. And that is now fixed in nextcloud package. But not in other packages!

The FORTIFY_SOURCE=3, as set by openSUSE, is not wrong and not surpringly does not warrant 'fixes' in most cases (most packages built without issues after all) The generic class of issues seen in packages failing with this setting are: * Upstreams declaring FORTIFY_SOURCE=2. This was done by almost all upstreams in an attempt to 'improve' their code, as FORTIFY_SOURCE=2 already helpd uncovering a bunch of bugs. But they forgot that the world keeps on spinning and now FORTIFY_SOURCE=3 is a thing. Specifying both on the command line is not permitted, which is why those packages now clash. I've seen some patches that remove the upstream definition back to 2, and others that eliminate the openSUSE setting to stick to upstreams provided =2 setting. before we switched to FORTIFY_SOURCE=3, we had FORTIFY_SOURCE=2 in optflags - this just happened to work for those packages as the value was the same. * A 2nd class of errors was/is packages actually failing with buffer overflows (we had seen that in qemu at the beginning for example) This are program bugs that need to be fixed. The fact that it worked with FORTIFY_SOURCE=2 is no prove that =3 is wrong. qemu for example fixed the code. Just recently we also got a fix in glibc (its bug resulted in rsyslog timeouts during shutdown) so, you see, generally, FORTIFY_SOURCE=3 is a perfectly valid flag - and if possible, upstreams should not overwrite and weaken security settings from distros (i.e. do not lower from 3 back to 2. Hope this clarifies it a bit. Cheers, Dominique

On Fri, 2022-07-01 at 15:05 +0100, Bob Williams wrote:

sudo zypper in nextcloud-desktop [sudo] password for root: Loading repository data... Reading installed packages... Resolving package dependencies...

Problem: nothing provides 'libQt5Gui.so.5(Qt_5.15.2_PRIVATE_API)(64bit)' needed by the to be installed nextcloud-desktop-3.5.1-1.1.x86_64 Solution 1: do not install nextcloud-desktop-3.5.1-1.1.x86_64 Solution 2: break nextcloud-desktop-3.5.1-1.1.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/c/d/?] (c):

Nothing fixed AFAICS! Or have I misunderstood?

The package has been fixed and submitted into Factory, where it's alrady accepted. It will be part of Snapshot 20220701. cheers, Dominique

Just saying, even though I'm late to the party: I had to uninstall and reinstall nextcloud client recently, too, because it stopped working. As it didn't yeild an error, I only discovered it because it denied to sync. Works again now. Am Freitag, 1. Juli 2022, 10:02:09 CEST schrieb Bob Williams:

On Fri, 01 Jul 2022 09:21:44 +0200

Fabian Vogt wrote:

...

Hi,

Am Freitag, 1. Juli 2022, 08:47:59 CEST schrieb Bob Williams:

...

Trying to install nextcloud-desktop client fails because

nothing provides 'libQt5Gui.so.5(Qt_5.15.2_PRIVATE_API)(64bit)' needed by the to be installed nextcloud-desktop-3.5.1-1.1.x86_64

[...]

...

...

How can I restore Nextcloud synchronisation?

The nextcloud-desktop package fails to build for a while already, probably needs to be updated. After the recent update to Qt 5.15.5, the old packages are no longer installable. There's no way around fixing nextcloud.

Cheers, Fabian

Thanks Fabian. That's a pity.

BTW, I'm subscribed to this list (obviously) so no need to CC me as well.

Regards Bob

-- Best Regards - Mit freundlichen Grüßen, Markus Feilner, Feilner IT - 20 years of open services - https://nitter.net/mfeilner ------------------------- Digital sovereignty in three words: "Exit Strategy First!" Digitale Souveränität in Drei Worten. ------------------------- Digitale Souveränität, Nachhaltigkeit, Dokumentation Linux, Security, Strategy, Politics, Journalism, Networking. https://www.feilner-it.net, 93059 Regensburg Wöhrdstr. 10, +49 170 302 7092 (+Signal) PGP: 40A3C306F96133067C11CFD9A958A906268C9F0A http://www.feilner-it.net/files/MFpub.asc Xing: http://www.xing.com/profile/Markus_Feilner LinkedIn: https://www.linkedin.com/in/markusfeilner @mfeilner: Matrix, Jabber, Skype, Twitter, Diaspora, ...