From: "Littlefield, Tyler" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Upgrading Debian to Testing with speakup
Date: Wed, 6 Jun 2007 14:28:22 -0600 [thread overview]
Message-ID: <001001c7a879$3aa6d630$6401a8c0@GRANDMA> (raw)
In-Reply-To: <BAY141-DAV35DF1AC4D786EA12DF47A8F270@phx.gbl>
I just edit the sources.list, and replace stable with testing, run apt-get
update, and then apt-get dist-upgrade, and it should work, just watch for
what it removes.
Thanks,
~~TheCreator~~
[My programs don't have bugs; just randomly added features]
msn:
compgeek13@gmail.com
aim: st8amnd2005
skype: st8amnd127
vertigo head coder
web: tysdomain.com
----- Original Message -----
From: "Zachary Kline" <Z_kline@hotmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Wednesday, June 06, 2007 12:35 PM
Subject: Upgrading Debian to Testing with speakup
> Hiya,
> I was wondering how to upgrade Debian Etch 4.0R0 to Testing with
Speakup? I've got the NetInst stuff from people.debian.org/~shane, but
don't know if kernel 2.6.18 is the latest version in Testing. I'm not sure
if I want to run a mixed distribution: is this common with Debian?
> I know that none of the official Deb kernels contain Speakup. Would I
need to roll my own if I wanted to upgrade to Testing?
> Thanks,
> Zack.
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
Zachary Kline
` Gregory Nowak
` Zachary Kline
` Gregory Nowak
` Zachary Kline
` Littlefield, Tyler
` Gregory Nowak
` Gregory Nowak
` Littlefield, Tyler [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='001001c7a879$3aa6d630$6401a8c0@GRANDMA' \
--to=compgeek13@gmail.com \
--cc=speakup@braille.uwo.ca \
/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).