From: Chuck Hallenbeck <chuckh@ftml.net>
To: tyler@tysdomain.com,
"Speakup is a screen review system for Linux."
<speakup@braille.uwo.ca>
Subject: Re: aptitude upgrade error message
Date: Mon, 22 Nov 2010 13:16:04 -0500 [thread overview]
Message-ID: <20101122181604.GA30478@rx.localhost> (raw)
In-Reply-To: <4CEAB1BA.9070401@tysdomain.com>
On Mon, Nov 22, 2010 at 11:08:58AM -0700, Littlefield, Tyler wrote:
> I'm not totally sure if this helps, but try an aptitude update, then
> the upgrade.
Actually the script that does the aptitude full-upgrade includes an
aptitude update immediately before it, but in the meantime I have made
the error go away by doing this, strangely enough:
apt-get update
apt-get dist-upgrade
The above was done manually, not in a script. I had a bunch of packages
upgraded, one removed, and then out of curiosity I ran the script that
uses aptitude instead of apt-get, and the error message no longer
occured.
Very peculiar.
Chuck
--
The Moon is Waning Gibbous (99% of Full)
Website: hallenbeck.ftml.net, Jabber ID: chuckh1@jabber.org
--------
You're not an alcoholic unless you go to the meetings.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Chuck Hallenbeck
` Littlefield, Tyler
` Chuck Hallenbeck [this message]
Jude DaShiell
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=20101122181604.GA30478@rx.localhost \
--to=chuckh@ftml.net \
--cc=speakup@braille.uwo.ca \
--cc=tyler@tysdomain.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).