Re: Ginkgo-CADx segfaults
On 11/10/2011 10:23 AM, Sebastian Hilbert wrote:
> On Thursday, November 10, 2011 10:03:09 AM Steffen Möller wrote:
> Hi all,
>> On 11/10/2011 09:21 AM, Andreas Tille wrote:
>>> On Thu, Nov 10, 2011 at 08:49:11AM +0100, Sebastian Hilbert wrote:
>>>> I am currently working with upstream to get some problems corrected.
>>>> Turns out that part of the problem is that e.g. ITK would need patches.
>>>> How would you consider the chances that those patches find their way
>>>> into Debian packages ?
>>> I'd file a (minor ??? - depending how general this problem is) bug
>>> report with patch against ITK package and add an "affects #648167" tag
>>> to stress the importance for GinkgoCADx.
>> Sorry for saying the obvious here, but if the bug is not
>> Debian-specific, then it should go to ITK upstream. Such issues are
>> (part of) why I am so much after getting upstream involved in the
>> distribution woes, be they maintainers or just visiting our sprints.
>> Just, we cannot be involved with everyone directly.
> Thanks for the pointers.
> The question was more along the lines if Debian packages accept patches which
> upstream refuses (have not checked with upstream ITK but have had issues with
Anything that is Debian-specific is something that upstream would refuse
to accept. Upstream wants their software to be used and so they are
typically on our side and happily help. As you may have guessed, there
is no general rule here.
I have just met some wxWidgets folks at the GSoC mentors summit.
Whenever you run into something and find your way around it to be
blocked for some non-traceable reason, my strategy around that is
to find someone to second me. That person may then also help with
the communication or find some second way around the problem that
the other side may find more acceptable.