On 15 Dec 2002 16:43:32 -0800 "Nathan G. Grennan" <[EMAIL PROTECTED]> wrote:
> Hello, > > I have since 8.0 betas had problems with rpm. I originally > submitted > a bug report(#68056) about rpm hanging during beta. At the time the > bug was reported fixed. Later RedHat 8.0 was released and the flood > gates opened with a number of bug reports(#73097, #73415, #74726, > #75553,#75647, #77480, #77562, #77988, #77997, #78366, #78679, #79272) > with the same symptom came in. Most have been closed with the the > result of WORKSFORME, which seems to me to be a poor choice. It may > work for the maintainer, Jeff Johnson([EMAIL PROTECTED]), but as the bug > reports mentioned above show it sure isn't working for everyone else. > There as been a test release made, which is mentioned in some of the > bug reports above. It is 4.1-9 and is at > ftp://people.redhat.com/jbj/test-4.1/ It doesn't fix the problem, it > just makes it more rare. The especially odd thing in my opinion is why > 4.1-9 or something like it hasn't been released as errata. Jeff seems > to suggest it's use to many that complain of the bug and has never > mentioned to my knowledge a reason not to use it. It has been months > since my original bug report and months since RedHat 8.0's release, > yet there hasn't been a fix made, or even a errata to help the > problem. Mostly what Jeff seems to have done is try to ignore the > problem while he Slowly tries to fix the problem. The best hint at any > hope seems to be this comment from him in #77988. Coincidentally, right as I was reading this, I was experiencing the precise same problem. I'm now going through the process of rebuilding things to get it all fixed. Again. For the second time today. For a problem that "WORKSFORME" even if it fails for many of the rest of us. It's happened to me so often I ended up writing a script to fix the problem when it comes up. It may be days before I see it again. But my personal record for the number of times in one day is 6. Is that a good sign? Is that acceptable? I didn't experience this until the last beta. There it's acceptable because it's a beta. When it showed up in 8.0, I thought it would be fixed pretty quickly. I figured the last beta was close enough to the release that maybe there weren't enough reports, or maybe the problem hadn't been determined by that time. Surely a week, two max, and this should all be sorted out. I'm personally pretty invested in 8.0 at this point. I'll continue living with it for now, I suppose. But if it's still present in the next release, I won't have any choice but to move along. Redhat needs to get their act together. People like me leaving won't break them. But people like me make recommendations to people who matter. If it's bad, I can't recommend it. If it's bad enough that I won't even use it myself, I certainly can't be in any position to recommend it anyone else. Continuing on that road means I'm less likely to even test it to be able to make any recommendation at all on down the road. To be fair, I almost never recommend an X.0 release anyway. But, this type of thing is making recommending Redhat at all more uncertain. Also to be fair, the above could just as easily apply to all bugfixes and such. Mostly Redhat has a good track record for repairing these things, so I still like them a lot in spite of this particular bug. -- I might be crazier than you think. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
