Am 2. Juli 2022 12:55:26 MESZ schrieb "Michael Ströder" <
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.
Calm down everybody. This personal fight does not help to solve any problem at all.
Although I don't always agree with Eric in all details I can confirm that he does an enormous amount of work also on packages I'm using.
I totally agree with you there. You don't always have to agree. But you should respect each other. I always miss that with him. And thank you for your words for my work.
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.
One of the things I'd like to be clarified at openSUSE project level is that following the old-fashioned mantra "Tumbleweed is experimental and Leap is for stable systems" sometimes leads to submit requests being declined by maintainers because the update is not compatible with Leap or is considered too new. IMHO this blocks progress in an inappropriate way.
Years ago, I had always refused the parcels here too. But I revised my opinion because of what you said. It prevents the "advance" in Tumbleweed. But you can also build the packages so that they can be built for Leap and Tumbleweed. At least in the Devel tepos. It doesn't always work, but most of the time. It's just a little more effort. I now always handle it like this: if it is possible to build for Leap and Tumbleweed, then you should do it and it will be accepted. If it is not possible to build for Leap, it is also accepted. Example calibre. Builder in the Devel repos only for Tumbleweed in version 5.44.0. The last possible build for calibre in Leap is 4.23.0. this is then only in my home repo. Regards Eric