Am 02.07.22 um 10:55 schrieb Stefan Seyfried:
On 01.07.22 20:05, Eric Schirra wrote:
Calibre build error has nothing to do with FORTIFY_SOURCE=3. There was an typo error.
And nextcloud-desktop was build till cflags (opflags) was changed.
...which apparently uncovered a calibre bug which is now papered over by reverting to FORTIFY_SOURCE=2 in the calibre spec file.
s/calibre/nextcloud-desktop/ and if you have ever dealt with any nextcloud related package, you won't have any hope that upstream will fix it soon, even if you report it. (Something I would expect from a responsible openSUSE package maintainer). BTW: https://github.com/nextcloud/desktop/issues/4690 To reiterate, the nextcloud-desktop package was failing to build in Factory for 2 weeks and in the devel project since May 20. There must have been plenty of automatic OBS Notifications about it as mentioned by Larry. If a maintainer chooses to ignore those there is no justification for them to whine about it on the Factory mailing list. Lest harassing other users in the OBS package comments. IMHO, even the failure to fix the build is not a big a problem as some seem to make it look here. It's not that users started to see crashes. It's just that zypper/rpm did the right thing and told the user that they can not update to the current snapshot, because Tumbleweed kept rolling with a new Qt version and left behind packages which could not keep up. - Ben