On Sun, Jan 08, 2012 at 11:27:21AM +0800, Rolf Leggewie wrote: > On 06.01.2012 22:02, Joerg Dorchain wrote: > > just wondering if there are any news about this problem. I also > > changed the title in the hope to make it clearer. > > Well, in all honesty you've now added a third, separate issue to the two > you already had in your original report. "one issue, one ticket", > please. Anything else makes it very hard to deal with the problems and > track progress.
With all understanding of issue tracking and bug handling (I am earning part of my living with that), from my point of view I have one problem, that my relativly critical phone application ceases to work after an upgrade, that is one ticket. If this problem (previous version works, new one does not), which I would classify as a regression, needs several fixes, well, then I expect them be handled, one after another in the worst case if they come completely unexpected. I am sorry that most of this mess concerns the upstream part of the package, but heck, I am using the debian package and not upstream directly. As we are working in a volunteer organsation, which I would interpret in a way that there is no KPI or anything linked with it with bug handling that endorses many small bugs opened and closed even faster, I would could consider it good and friendly service when you split bug reports yourself as you see them fit. I mean bug cloning and merging is available, and who knows better than the maintainer how to organise "his" bug reports. Just closing them is what I consider extremly impolite. You might want to have a look at some ITIL documentation, some principles are not totally wrong and applicable also to debian bug handling processes. On the positive side, speaking of a volunteer and not a professional organisation, I think I should be happy that there was a fast reponse. > > Please open a new ticket about about the undefined symbol issue. After > a brief look at the proposed patch I'm not sure it's appropriate. There > are suggestions to stop shipping the .la files entirely. FWIW, I have > not looked into this newly uncovered problem at all, yet. I will open a new ticket for this in the hope it will be dealt with. I tried to be as constructive as I can by providing a patch which works for me. From what I see from searches on the web chan_capi is not the only application that breaks, it is just anything that actually tries to open an isdn channel. I will further go into details in the next bug report. Bye, Joerg
signature.asc
Description: Digital signature
