Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Richard Hirst <rhirst@linuxcare.com>
To: "Carlos O'Donell Jr." <carlos@megatonmonkey.net>,
	parisc-linux@lists.parisc-linux.org, baldric-exec@baldric.uwo.ca
Subject: Re: [parisc-linux] Users staying up to date.
Date: Tue, 28 Aug 2001 00:07:48 +0100	[thread overview]
Message-ID: <20010828000748.G7064@linuxcare.com> (raw)
In-Reply-To: <20010817155340.C8649@megatonmonkey.net>; from carlos@megatonmonkey.net on Fri, Aug 17, 2001 at 03:53:40PM -0400

On Fri, Aug 17, 2001 at 03:53:40PM -0400, Carlos O'Donell Jr. wrote:
> > 
> > /usr/share/locale
> > /usr/share/locale/cs
> > /usr/share/locale/cs/LC_MESSAGES
> > /usr/share/locale/cs/LC_MESSAGES/dpkg.mo
> > 
> > I seem to remember someone saying this was a bug in an old version
> > of dpkg.  So one way around this may be to dpkg --remove texinfo, then
> > install dpkg, then install texinfo again.
> >
> 
> I tried removing texinfo. Sadly, what proceeds to occur is a 
> relative chain of packages that continually depend on 
> /usr/share/locale/cs, all the way down to 'tar.' At which point
> I had lost most of my system functionality and was scp'ing 
> binaries into /bin to keep it alive.
> 
> A fruitless effort, but interesting none the less. ;)
> 
> When I get home tonight I'll roll a new kernel and do more testing.
> 
> How does the installer get around this problem?
> Since it too must start with a base system?
> (Maybe it's just my misunderstanding of the complete inner workings
> of hte installer).

The installer starts with a bunch of .debs which are sufficiently new
that they don't have the apt-segv problem.  That is the case for the
0.9.2 ISO, anyway.

You might me able to do a fresh install from the 0.9.2 ISO to get a
more stable system.  If you don't want to do that, you could try using
dpkg -i to install .debs from that ISO.  Possibly a dpkg -i *.deb in
the binary-hppa/base dir might just work.  You should probably be running
a new(ish) kernel before you do that.

Richard

  reply	other threads:[~2001-08-27 23:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-14 19:40 [parisc-linux] Users staying up to date Carlos O'Donell Jr.
2001-08-14 19:46 ` Bdale Garbee
2001-08-14 23:27 ` Matt Taggart
2001-08-15  0:00 ` Matthew Wilcox
2001-08-15  1:50   ` Carlos O'Donell Jr.
2001-08-15  3:16     ` Matthew Wilcox
2001-08-15  3:37       ` [parisc-linux] Users staying up to late. ;) Carlos O'Donell Jr.
2001-08-17 19:53       ` [parisc-linux] Users staying up to date Carlos O'Donell Jr.
2001-08-27 23:07         ` Richard Hirst [this message]
2001-08-28  4:22           ` Carlos O'Donell Jr.
2001-08-28 14:34             ` Richard Hirst
2001-08-28 15:14             ` Matt Taggart
2001-08-28 15:40               ` Carlos O'Donell Jr.

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=20010828000748.G7064@linuxcare.com \
    --to=rhirst@linuxcare.com \
    --cc=baldric-exec@baldric.uwo.ca \
    --cc=carlos@megatonmonkey.net \
    --cc=parisc-linux@lists.parisc-linux.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