public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: J Sloan <joe@tmsusa.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.5.66-bk12 causes "rpm" errors
Date: Sun, 06 Apr 2003 19:59:02 -0700	[thread overview]
Message-ID: <3E90E976.6020006@tmsusa.com> (raw)
In-Reply-To: 1049680140.753.175.camel@localhost

Yes, I loaded 2.5.66-mm3 on my new shrike box
and was disappointed to see that rpm was broken,
and I had to boot back to 2.4.20-8 (RH) to upgrade
anything -

I'll try the

    LD_ASSUME_KERNEL=2.2.5 rpm <...>

routine and see if that does the trick -

Joe

Robert Love wrote:

>On Sun, 2003-04-06 at 21:41, Robert Love wrote:
>
>  
>
>>This has been happening since 2.5.60-ish.
>>    
>>
>
>2.5.60-mm-ish I should say... which is a big difference if this bug just
>cropped up in Linus's 2.5 tree.
>
>	Robert Love
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>
>  
>



  reply	other threads:[~2003-04-07  2:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-07  1:18 2.5.66-bk12 causes "rpm" errors Robert P. J. Day
2003-04-07  1:32 ` Andrew Morton
2003-04-07  1:41   ` Robert Love
2003-04-07  1:47     ` Robert Love
2003-04-07 11:45       ` Alan Cox
2003-04-07 14:53         ` Robert Love
2003-04-07 14:17           ` Alan Cox
2003-04-07  1:49     ` Robert Love
2003-04-07  2:59       ` J Sloan [this message]
2003-04-07 12:07     ` Robert P. J. Day
2003-04-07  2:04   ` Robert P. J. Day
2003-04-07  1:28     ` Andrew Morton
2003-04-07  3:15       ` Robert Love
2003-04-07  3:19         ` Robert Love
2003-04-07  3:29         ` Andrew Morton
2003-04-07  3:35           ` Robert Love
2003-04-07  9:05 ` Felipe Alfaro Solana
  -- strict thread matches above, loose matches on Subject: below --
2004-04-20  8:10 Fred Shaul

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E90E976.6020006@tmsusa.com \
    --to=joe@tmsusa.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox