From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: What to do if SSpeakup fails to patch?
Date: Sun, 25 Feb 2007 13:35:52 -0700 [thread overview]
Message-ID: <20070225203552.GA13411@localhost.localdomain> (raw)
In-Reply-To: <003701c7591a$ba8f8c60$6401a8c0@YOUR3ADE1B78A3>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Most people don't bother to think about how they'll cross that bridge,
until they come to it. If the patch process fails, you'll see fail
messages during the patching process, and it will tell you that it's
saving the rejected hunks into files with a .rej extension.
If you do get those errors, post them here, along with the kernel
version you're patching against. After you do that, remove the source
tree you were trying to patch against, and untar a fresh one. Then,
wait for someone to tell you how to check out a different version of
cvs speakup appropriate for your kernel, or wait for someone to post
other directions for you to follow.
Alternatively, if you want to solve this yourself, don't post anything
to the list. Instead, learn how to checkout from cvs as of a certain
date, find out on what date the kernel that came after the one you're
patching against came out by looking at the changelog, (I.E. if
patching against 2.6.18.5, find out when 2.6.19 was released), and
check out cvs speakup from before that release date. If the issue is
not one of mismatched speakup and kernel version, then search the list
archives for the solution.
Greg
On Sun, Feb 25, 2007 at 01:22:53PM -0700, Keith Hinton wrote:
> Hi,
> I've grabbed the Speakup CVS checkout script, and will be running it at some point when I find time.
> Question is, what will happen if it doesn't patch? Do I remove the kernel tarball and run it all over again?
> Or what. Let me know,
> regards,
> --Keith.
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFF4fMo7s9z/XlyUyARAuldAKCop4rNook0V/3T2xV3tLHWR1C/+QCeJLJy
JHV05T6uo/nW99W/HTBRKtM=
=x8GL
-----END PGP SIGNATURE-----
prev parent reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Keith Hinton
` Gregory Nowak [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=20070225203552.GA13411@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--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).