Re: glib 1.1.12, gtk1.1.12 for debian/ppc
On Fri, 15 Jan 1999, luther sven wrote:
> i think in this case the correct thing to do is to fill a bug against this package, did you do it ?
> you state there that the package don't compile, because of so and so,
> that they should apply the appended patch. and also for such important
> package, you are not developper and thus cannot upload the package, you
> send a copy the problem to the debian-ppc mailing list.
what do you mean fill a bug? against egcs or gtk? In the case of egcs, it
is not a debian package's fault and the debian site is IMHO the wrong
place to report this bug, instead it should be at cygnus. But then as I
said it is a well known bug, so the report would be useless, and I don't
think that we should duplicate all egcs bugs (the intrinsic ones) to the
debian egcs package buglist -that would be useless.
In the case of gtk/glib it is not even a bug of these packages. And I have
never said that I had a patch for them. There was never one and no need
for one. I said I compiled the files with no optimizations -should I state
that I did this manually?- and then proceeded. Indeed, I suppose that
a patch could be written so that these files get compiled with no
optimizations, and the package be built with no problem. I really
question that approach though, and am totally against it. A package
should not be dealt in some special way because of a compiler
weakness, even more so when the failing files are not really failing
to the purposes of their existence. What is the need for a bug report?
> if you don't tell us the problems, there is no possibility that it will be fixed ...
I just did. twice. Although, I admit that I am a bit lazy when it comes to
bug reports. Still, when I do find a bug that has to do with the package
itself and not something else, I try to find a solution first and then
fill a bug report. In this case I found the cause, and a solution so that
the package could be built and working with no consequenses whatsoever of
the bug that prevented it from working in the first place. I think that
this is the important thing: to have working packages. Especially when
there is nothing you and I can do, unless we try and help the folks at
cygnus overcome the egcs bug.
> sure, but as all debian developper we have a real life beside it, and i have been busy. ...
> with the info you give to me now, i wil be able to fix it, but best would be to fill a complete
> bug report to the package maintainer, as said above...
One last note, I never meant to offend anyone, and this thing is starting
to look like a flame war. I only tried to help, and I believe I did and
certainly do not deserve to be treated like some newbie who's got to go
and read the FAQ's (no offence to the newbies).
Konstantinos Margaritis
kmargar@cc.uoa.gr
Reply to: