From: "H . J . Lu" <hjl@lucon.org>
To: Hartvig Ekner <hartvige@mips.com>
Cc: user alias <linux-mips@oss.sgi.com>
Subject: Re: Problems with H.J's latest RPM 4.0.4 binary packages
Date: Mon, 22 Apr 2002 09:40:37 -0700 [thread overview]
Message-ID: <20020422094037.A12357@lucon.org> (raw)
In-Reply-To: <200204221446.QAA23835@copsun17.mips.com>; from hartvige@mips.com on Mon, Apr 22, 2002 at 04:46:45PM +0200
On Mon, Apr 22, 2002 at 04:46:45PM +0200, Hartvig Ekner wrote:
> I have started to update our 7.1 RH/MIPS installation images with all the
> latest packages from H.J's collection.
>
> The latest RPM package gives an up-front error no matter what one does, but
> the command seems to work:
>
> [hartvige@copmalt13 /bin]$ rpm --version
> error: Macro %__id_u has empty body
> RPM version 4.0.4
> [hartvige@copmalt13 /bin]$
>
I have no problems with the mipsel rpm binary. Did you compile rpm 4.0.4
yourselves? Please send me
# cd /usr/lib/rpm
# grep __id_u * */*
H.J.
next prev parent reply other threads:[~2002-04-22 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 14:46 Problems with H.J's latest RPM 4.0.4 binary packages Hartvig Ekner
2002-04-22 14:46 ` Hartvig Ekner
2002-04-22 16:40 ` H . J . Lu [this message]
2002-04-22 17:42 ` Ralf Baechle
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=20020422094037.A12357@lucon.org \
--to=hjl@lucon.org \
--cc=hartvige@mips.com \
--cc=linux-mips@oss.sgi.com \
/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