On Thu, May 13, 2010 at 09:43:49AM +0200, Jon Clausen wrote:
On Thu, 13 May, 2010 at 02:00:03 +0200, Carlos E. R. wrote:
On Wednesday, 2010-05-12 at 14:07 +0200, Jon Clausen wrote:
...
It makes me wonder how many other faulty packages I have on my systems, where commands have slight malfunctions, which I may overlook?
Probably a lot.
...please don't say that :P
Many get "repaired", but the repair is often only available on the next system release - which, of course, will contain its own bucketfulls of newer bugs.
Probably so. And to some extent 'fair enough', that fixes don't automatically get 'backported'. But I'm still somewhat disappointed that one has 'plead the case' in order for a fix, to a clearly documented bug, to be 'promoted' to an Update.
Is how software gets done. The important point is new features, not getting bugless software. Instead of stopping and clearing all bugs, we get lots of new features, with some old bugs solved, and new bugs added. >:-)
Yeah, I guess you're right. I wasn't entirely clear in what I wrote in the above quote. What I meant was not so much 'packages built from faulty source code', but rather 'packages that are known to be faultily built, from (maybe faulty) source code'.
What I think I'm trying to say is; If it's worth packaging, then it's worth packaging *correctly*. But also;
IMO packaging errors shouldn't be subject to a 'popularity contest'. Scrutiny and validation... of course, but the quality of the distribution is in large part 'quality of packaging'... isn't it?
Should I do something?
Well, if it is a problem for you (tree), perhaps you can add the patch and recompile yourself, or perhaps some kind soul does it somewhere in the buildservice :-)
Yeah well, I think I'll abstain from attempting to recomplie *myself* ;)
What I meant was more in the line of "should I do something, add comments or whatever, when the bug is reopened?"
It is not a problem for me because I do not use tree much. I think...
I use tree enough that it's certainly worth rebuilding the rpm for myself. With the research I put into tracking down the issue in the first place, it's not even going to be that big of a deal - especially now that I've found the src.rpm Marcus fixed - so I can see *how* he fixed it.
But I'd much rather just 'zypper up', and get the fixed package that way :P
The bug was approved to be fixed for 11.2, so I will prepare an update. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org