Am Samstag, 2. Juli 2022, 11:27:03 CEST schrieb Ben Greiner:
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
If you are addressing me, since I am the maintainer, I find this statement an absolute impertinence. I do there in my spare time to help the general public and I have no time to fight with upstream in long discussions. For that there are paid employees of SUSE.
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.
Another insinuation. I have not received any notification. And I would say I always respond quickly. Even to normal requests by mail. And that the package could not be built I have never ignored or bechlossen nothing to do. An insolence is this assertion. Again, it is the internal processes at openSUSE but also at SUSE that do not work and are very slow. And these are still pushed by my opinion of many wrong decisions.
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.
This is how it looks. And further proof that internal processes don't work. Regards Eric