On 7/11/22 21:50, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [07-11-22 07:26]:
On 11/07/2022 12.20, Simon Lees wrote:
On 7/10/22 12:34, David C. Rankin wrote:
What is going on?
FreeCAD in the main OSS 15.4 repository is BROKEN. (It segfaults) I file a bug to have this package in OSS fixed and I get a response:
<quote> Comment # 3 on bug 1200583 from Stefan Brüns
FreeCAD works fine on TW, and thats the only thing I will support. For 15.4, you are on your own.
You are receiving this mail because:
You reported the bug. </quote>
15.4 is a new release and it has a broken package in OSS -- Why isn't that going to be fixed???
Unfortunetly there has been some cases where packages were submitted from Tumbleweed to Leap without a maintainers approval. Maintainers in openSUSE have every right to dictate which distro's they do and don't have time or are willing to support, they are volunteers after all.
Unless a maintainer can be found for Leap if this issue is affecting most users then the correct way to "Fix" the issue would be to simply drop the package. On the other hand if someone can figure out what is actually triggering the issue and provide a suggested fix then the tumbleweed maintainer seems that he would be happy to help in this instance and forward such a fix to Leap even though they are under no obligation to do so.
If the maintainer is not willing to maintain for Leap, the package should not be provided in Leap in the first place. A user assumes that if a package is provided in OSS, it is then officially maintained, and if the maintainer refuses it causes very bad impression, no matter if everybody is a volunteer.
you are assuming the maintainer for the package on TW is also the submitter for Leap and he has said that it is not so. so blame who-ever provided the package for Leap, not the non-provider. if you are going to blame, at least place the blame on the correct individual(s)/committee/...
Yeah this is more the point, our systems have changed a number of times with regards to this between various versions, It could also be that someone submitted it for 15.0 or 15.1 and stepped back from maintaining it and then its been auto upgraded since and because the build has never failed its never been dropped. Unless a package has a good test suite in openqa or a maintainer that is doing manual testing the best we have to go on as to whether a package works is whether it still builds or not. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B