Why are packages in 15.4 OSS repository NOT receiving SUPPORT?
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??? -- David C. Rankin, J.D.,P.E.
On 10.07.2022 06:04, 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???
It starts just fine here on 15.4.
Am Sonntag, 10. Juli 2022, 05:04:48 CEST schrieb David C. Rankin:
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???
where did you get that freecad from, the main OSS repo? Cheers MH -- Mathias Homann Mathias.Homann@openSUSE.org Jabber (XMPP): lemmy@tuxonline.tech Matrix: @mathias:eregion.de IRC: [Lemmy] on freenode and ircnet (bouncer active) keybase: https://keybase.io/lemmy gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
On 10/07/2022 08.18, Mathias Homann wrote:
Am Sonntag, 10. Juli 2022, 05:04:48 CEST schrieb David C. Rankin:
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???
where did you get that freecad from, the main OSS repo?
He says from OSS, the official repo. In the Bugzilla he says he tried that one and the science repo, both crash. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.3 (Legolas))
Le 10/07/2022 à 17:38, Carlos E. R. a écrit :
He says from OSS, the official repo. In the Bugzilla he says he tried that one and the science repo, both crash.
So here's what FreeCAD's "maintenance" looks like: https://bugzilla.opensuse.org/show_bug.cgi?id=1200583#c9 I suggest to replace this jerk by an actual package maintainer, e. g. someone who reads bug reports and takes necessary action. Or you can move to LibreCAD as a software alternative. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info@microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12
Am Montag, 11. Juli 2022, 07:52:24 CEST schrieb Nicolas Kovacs:
So here's what FreeCAD's "maintenance" looks like:
https://bugzilla.opensuse.org/show_bug.cgi?id=1200583#c9
I suggest to replace this jerk by an actual package maintainer, e. g. someone who reads bug reports and takes necessary action.
that. 100% ack. -- Mathias Homann Mathias.Homann@openSUSE.org OBS: lemmy04 Jabber (XMPP): lemmy@tuxonline.tech Matrix: @mathias:eregion.de IRC: [Lemmy] on liberachat and ircnet (bouncer active) keybase: https://keybase.io/lemmy gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
Le 10/07/2022 à 05:04, David C. Rankin a écrit :
15.4 is a new release and it has a broken package in OSS -- Why isn't that going to be fixed???
Fixed that for you: https://bugzilla.opensuse.org/show_bug.cgi?id=1200583#c8 :o) -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info@microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12
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. -- 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
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. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.3 (Legolas))
* 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/... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
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
On 11/07/2022 14.20, 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.
In that case, he has to erase himself from being the receiver for Bugzilla entries for bugs in the package for Leap. It is not the user fault. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.3 (Legolas))
* Carlos E. R. <robin.listas@telefonica.net> [07-11-22 11:08]:
On 11/07/2022 14.20, 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.
In that case, he has to erase himself from being the receiver for Bugzilla entries for bugs in the package for Leap. It is not the user fault.
and *if* the packager did not submit the package for leap 15.4, IT IS NOT HIS FAULT. everything is not about BLAME! /end -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On 11/07/2022 17.18, Patrick Shanahan wrote:
* Carlos E. R. <> [07-11-22 11:08]:
On 11/07/2022 14.20, Patrick Shanahan wrote:
* Carlos E. R. <> [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.
In that case, he has to erase himself from being the receiver for Bugzilla entries for bugs in the package for Leap. It is not the user fault.
and *if* the packager did not submit the package for leap 15.4, IT IS NOT HIS FAULT. everything is not about BLAME!
If he did not submit it, why is he getting the Bugzillas, why are they assigned to him? (I'm not assigning blame, anyway, and I'm not shouting) -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.3 (Legolas))
Le 11/07/2022 à 17:18, Patrick Shanahan a écrit :
and *if* the packager did not submit the package for leap 15.4, IT IS NOT HIS FAULT. everything is not about BLAME!
Maintainers ARE HERE TO HELP (I can do all-caps too). The only thing pissing users off here is the "not my business" apartheid policy put into practice by the FreeCAD maintainer. Basic politeness is being considerate of other people's feelings, e. g. treat someone who submits a bug report with a minimum of empathy and respect. He's here because he has a problem, so the only thing to do is to help him out. Not suggest he switches to a different system. The maintainer's reaction is merely a subtle form of brutality, so we simply called him out for being a jerk. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info@microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12
Op maandag 11 juli 2022 19:01:40 CEST schreef Nicolas Kovacs:
The only thing pissing users off here is the "not my business" apartheid policy put into practice by the FreeCAD maintainer.
May I kindly point you to the Code of Conduct ?
snip
The maintainer's reaction is merely a subtle form of brutality, so we simply called him out for being a jerk. And again May I kindly point you to the Code of Conduct ? Calliing someone a jerk doesn't fit in there. Nor does "apartheid policy".
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board openSUSE Forums Team
On 11/07/2022 19.08, Knurpht-openSUSE wrote:
Op maandag 11 juli 2022 19:01:40 CEST schreef Nicolas Kovacs:
The only thing pissing users off here is the "not my business" apartheid policy put into practice by the FreeCAD maintainer.
May I kindly point you to the Code of Conduct ?
Please apply that first to the maintainer in question. He was certainly somewhat brutal in his bugzilla response, I am afraid.
snip
The maintainer's reaction is merely a subtle form of brutality, so we simply called him out for being a jerk. And again May I kindly point you to the Code of Conduct ? Calliing someone a jerk doesn't fit in there. Nor does "apartheid policy".
Pleaae have a look at what the maintainer said. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.3 (Legolas))
Op maandag 11 juli 2022 19:31:00 CEST schreef Carlos E. R.:
Please apply that first to the maintainer in question. He was certainly somewhat brutal in his bugzilla response, I am afraid. They said that they were not going to maintain it for 15.4 . And there is no rule or responsibility on their side. That said, there is no excuse for others to phrase like what I quoted, and it will not make things better.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board openSUSE Forums Team
Le 11/07/2022 à 19:39, Knurpht-openSUSE a écrit :
They said that they were not going to maintain it for 15.4 . And there is no rule or responsibility on their side. That said, there is no excuse for others to phrase like what I quoted, and it will not make things better.
"Wer bei manchen Dingen nicht den Verstand verliert, der hat wahrscheinlich gar keinen." -- Gotthold Ephraim Lessing -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info@microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12
Am 11.07.22 um 19:42 schrieb Nicolas Kovacs:
Le 11/07/2022 à 19:39, Knurpht-openSUSE a écrit :
They said that they were not going to maintain it for 15.4 . And there is no rule or responsibility on their side. That said, there is no excuse for others to phrase like what I quoted, and it will not make things better.
"Wer bei manchen Dingen nicht den Verstand verliert, der hat wahrscheinlich gar keinen."
-- Gotthold Ephraim Lessing
Please: first its a english list, even if the sentence is nice. second: maybe some here have not read carefully: andrei borzenkov wrote: ==================== Am 10.07.22 um 07:58 schrieb Andrei Borzenkov:
It starts just fine here on 15.4.
==================== so maybe its not a problem of the package, maybe its a problem of something installed from a third party repo. (or of the processor (amd/intel or the graphic nvidia/amd) to go further, it may good if the people who have an interest on running the software on 15.4 check what libary's (or hardware) is using and where is the different from the installation of boris. simoN -- www.becherer.de
I am sorry: here corrected: Am 11.07.22 um 19:42 schrieb Nicolas Kovacs:
Le 11/07/2022 à 19:39, Knurpht-openSUSE a écrit :
They said that they were not going to maintain it for 15.4 . And there is no rule or responsibility on their side. That said, there is no excuse for others to phrase like what I quoted, and it will not make things better.
"Wer bei manchen Dingen nicht den Verstand verliert, der hat wahrscheinlich gar keinen."
-- Gotthold Ephraim Lessing
Please: first its a english list, even if the sentence is nice. second: maybe some here have not read carefully: andrei borzenkov wrote: ==================== Am 10.07.22 um 07:58 schrieb Andrei Borzenkov:
It starts just fine here on 15.4.
==================== so maybe its not a problem of the package, maybe its a problem of something installed from a third party repo. (or of the processor (amd/intel or the graphic nvidia/amd) to go further, it may good if the people who have an interest on running the software on 15.4 check what libary's (or hardware) is using and where is the different from the installation of ANDREI regards, simoN -- www.becherer.de
On 7/12/22 00:35, Carlos E. R. wrote:
On 11/07/2022 14.20, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [07-11-22 07:26]:
On 11/07/2022 12.20, Simon Lees wrote:
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.
In that case, he has to erase himself from being the receiver for Bugzilla entries for bugs in the package for Leap. It is not the user fault.
Unfortunately I don't know if our current tooling is that smart generally it defaults to the list in the devel project and should go to anyone marked as a bugowner in this case as there is presumably only one it was assigned to them. In a more normal case i'd expect both the tumbleweed and leap maintainers to end up probably on all bug reports and they generally work well enough together to sort these things out. -- 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
Le 11/07/2022 à 13:24, Carlos E. R. a écrit :
If the maintainer is not willing to maintain for Leap, the package should not be provided in Leap in the first place.
may be it just works in most places? could be moved to obs jdd -- http://dodin.org http://valeriedodin.com
On Sat, 9 Jul 2022 22:04:48 -0500 "David C. Rankin" <drankinatty@suddenlinkmail.com> 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???
Given all the statements in the thread subsequently, it seems you need to do some diagnosis, which you offer in the bug report. Where does it segfault? i.e. most likely, which library and doing/calling what?
participants (11)
-
Andrei Borzenkov -
Carlos E. R. -
Dave Howorth -
David C. Rankin -
jdd＠dodin.org -
Knurpht-openSUSE -
Mathias Homann -
Nicolas Kovacs -
Patrick Shanahan -
Simon Becherer -
Simon Lees