I find it troubling to hear that this is still present, if it's what I think it is. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=73097 This started in RH 8, and apparently still exists in RawHide. If this isn't fixed before the next release, that will be 3 major versions shipped with a broken RPM. That is unacceptable. Sean Middleditch wrote: -- ; Justin Georgeson ; http://www.lopht.net ; mailto:jgeorgeson@lopht.net ; "Free the mallocs, delete the news"

On Mon, 2003-09-22 at 05:24, Paul Gear wrote: Would I be correct in assuming that this won't help in the least for graphical updaters or other apps, as they most likely use librpm? (and wouldn't use that alias anyhow even if they didn't) I almost never use the plain rpm command. :( -- Sean Middleditch <elanthis(a)awesomeplay.com&gt; AwesomePlay Productions, Inc.

On Mon, 2003-09-22 at 21:43, Barry K. Nathan wrote: Because in the instances I *do* use plain RPM, is *also* locks up. It never locks up when using apt or yum, now that I think on it - just plain rpm and the redhat-install-packages utility. I never use up2date, since it refuses to work w/ Rawhide, only the Severn beta, which isn't what I want. I've not found a pattern of crashes and lockups. More often, I'll install a couple packages just fine (usually using redhat-install-packages) and then go to install a another, and get the lockup. elanthis@stargrazer:~$ getconf GNU_LIBPTHREAD_VERSION NPTL 0.57 Running the latest Rawhide. Problem has existed ever since I installed Redhat, version 8.0, after switching from Debian. -- Sean Middleditch <elanthis(a)awesomeplay.com&gt; AwesomePlay Productions, Inc.

On Tue, 2003-09-23 at 04:48, M A Young wrote: The Severn channel seems to be a lot mroe out of date than the packages I can grab w/ yum. In any case, it's not really that much of a problem to me, I'm not even that fond the up2date UI. ~,^ And, again, in many instances that RPM fails, the previous command or app I ran *was* rpm (or redhat-install-packages). And, even *if* a "previous app" is causing it, it's still happening, which is bull. I don't care what the cause is (from a user standpoint), I only know that it stops working, and the only way to make it work is use "advanced hacker black magic". If there is a propensity for the rpm command or redhat-install-packages to fail (which should be *fixed*), then it should be very gracefully and cleanly handled. -- Sean Middleditch <elanthis(a)awesomeplay.com&gt; AwesomePlay Productions, Inc.

On Tue, 2003-09-23 at 09:56, Gerry Tool wrote: Well, um, no. ^^; I'll give that a try when I get home. Thanks! -- Sean Middleditch <elanthis(a)awesomeplay.com&gt; AwesomePlay Productions, Inc.

You may wish to consider posting this to rpm-list(a)redhat.com , so that Jeff Johnson, RPM maintainer @ red hat, can see / respond / etc to your issue... - Aaron rhllist(a)assursys.co.uk wrote: -- Aaron Bennett UNIX Administrator Franklin W. Olin College of Engineering

On Mon, 2003-09-22 at 10:08, rhllist(a)assursys.co.uk wrote: The backport you mention are the files in ftp://ftp.rpm.org/pub/rpm/test-4.1.1 ? -- Sean Middleditch <elanthis(a)awesomeplay.com&gt; AwesomePlay Productions, Inc.

On Mon, 2003-09-22 at 10:46, rhllist(a)assursys.co.uk wrote: Hmm, Rawhide has rpm 4.2.1-0.30, and the bug persists - I'm assuming I probably don't want to downgrade, since the 4.1.1 test is just backported stuff from 4.2, yes? -- Sean Middleditch <elanthis(a)awesomeplay.com&gt; AwesomePlay Productions, Inc.

On Mon, Sep 22, 2003 at 10:20:36PM -0400, Sean Middleditch wrote: Yes, it's backported from 4.2-1 (which is newer than the 4.2-0.69 that shipped with Red Hat 9, but older than the 4.2.1 stuff in rawhide). There's a newer 4.2.1 (I think 4.2.1-3 or so) in the current Red Hat Enterprise Linux update channel right now. Nonetheless, the one in rawhide has also been problem-free for me. However, I use neither apt nor redhat-install-packages. (I'll probably try redhat-install-packages again after the 2nd Fedora Core beta is released, but not until then.) I would second the suggestion to mention this on rpm-list. I can't think of anything better to try. (Unless you want to try completely avoiding redhat-install-packages and/or apt, and see if the hangs still happen. Even though you see lockups in rpm itself, one of those might be messing up rpm's locking, and you might not be seeing the effect until well after it happens.) -Barry K. Nathan <barryn(a)pobox.com&gt;

Michael Schwendt wrote: Why should that make any difference? If rpm can't handle being interrupted, that means that it is too fragile for the job. Handling user interrupts is one of the most important features rpm can have. Of course, i'm not saying that this makes the problem any easier to solve, but to require that people never interrupt rpm is to require that they never make mistakes, and we all do that... -- Paul http://paulgear.webhop.net A: Because we read from top to bottom, left to right. Q: Why should i start my reply below the quoted text?

On Tue, 2003-09-23 at 03:49, Michael Schwendt wrote: I run apt or yum once every couple days, but these *never* fail on me, that I can recall. I also download the occasional packages and its dependencies (for example, Abiword 2.0.0), which I generally install by having redhat-install-packages launched from the browser (Epiphany). I also sometimes run rpm to remove packages, or sometimes install things when redhat-install-packages fails (like it always does when there's dependency issues, since it doesn't seem to bother trying to resolve them from packages I've downloaded in the same folder as the package its trying to install). Of course not. I'm not a *complete* goober - were I doing something that stupid, I wouldn't be complaining about rpm sucking. ~,^ The only time I ever stop or kill rpm or redhat-install-packages is when they're locked up. Which makes this all rather confusing then. Perhaps there is something in my existing setup that is killing the stability. Guess I'll go the rpm list. -- Sean Middleditch <elanthis(a)awesomeplay.com&gt; AwesomePlay Productions, Inc.