From: Matt Taggart <taggart@carmen.fc.hp.com>
To: thunder7@xs4all.nl
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] WARNING: DO NOT APT-GET UPGRADE HPPA
Date: Wed, 31 Oct 2001 13:07:37 -0700 [thread overview]
Message-ID: <20011031200737.B7A7937CB2@carmen.fc.hp.com> (raw)
In-Reply-To: Your message of "Wed, 31 Oct 2001 20:21:07 +0100." <20011031202107.A2654@alpha.of.nowhere>
Jurriaan on Alpha writes...
> So what is the current status? Is there anything fundamental relying on
> python, or is it safe to upt-get update again?
We still don't know the extent of the problem and until known working
binutils/gcc/glibc are uploaded I think you should hold off. I'm hoping the
patch that Alan Modra posted earlier is the answer. I'm rebuilding the
toolchain now.
Stay tuned...
--
Matt Taggart Linux Development Lab
taggart@fc.hp.com HP Linux Systems Operation
prev parent reply other threads:[~2001-10-31 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-26 18:27 [parisc-linux] WARNING: DO NOT APT-GET UPGRADE HPPA Matt Taggart
2001-10-27 10:01 ` [parisc-linux] " Peter Mottram
2001-10-27 23:32 ` [parisc-linux] " andi
2001-10-28 1:38 ` andi
[not found] ` <20011031202107.A2654@alpha.of.nowhere>
2001-10-31 20:07 ` Matt Taggart [this message]
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=20011031200737.B7A7937CB2@carmen.fc.hp.com \
--to=taggart@carmen.fc.hp.com \
--cc=parisc-linux@parisc-linux.org \
--cc=thunder7@xs4all.nl \
/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