Am 02.07.22 um 11:41 schrieb Eric Schirra:
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.
Absolutely not. Nobody tells you to do any work. But if you are not willing to properly maintain a package, then don't assume the role for the package. Even if you do, you should rather be thankful for any bug reports instead of harassing reporters.
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.
Which is completely on you, not on anything in "the internal process". Check your settings in https://build.opensuse.org/my/subscriptions Again, there is nothing wrong in don't willing to volunteer. But if you do, don't put the blame on others.
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.
Nonsense. Nothing is as fast as openSUSE Tumbleweed moving with upstream changes. You complain about Tumbleweed changing its packages too fast in one message and then on being too slow in the next.