Re: default speakup for Debian Sarge

Re: default speakup for Debian Sarge

[Gene Collins]

Hi Shane.  The latest cvs has been modified to work with 2.6.12, and
will no longer work with 2.6.11 and earlier.  I suggest you grab the
Speakup 2.0 tar ball and shoehorn that into the 2.6.8 kernel.

Gene

>On Sun, Jul 31, 2005 at 07:15:50PM -0400, Charles Hallenbeck wrote:
>> The issue of the speakup modified 2.6.8  kernel is a sticky one, since 
>> that kernel requires a speakup patch version that may only be available 
>> by rolling back the retrieval date in the CVS sources. The speakup 2.0 
>> tarball requires 2.6.10 or 2.6.11, so it cannot be used to patch 2.6.8  
>> for the Sarge release. I seem to recall that the mark/cut/paste problem 
>> was propagated in the CVS system for a short time before it was fixed, 
>> and it looks the luck of the draw that you used it while it was broken 
>> to patch the 2.6.8 kernel. 
>
>I just grabbed the latest CVS at the time and merged it
>into the Debian kernel.  I think it was 2.0.  It didn't go
>in cleanly and needed some manual work but nothing too
>extensive.
>
>I'll use latest CVS in the next CD though so hopefully that
>fixes things.
>
>-- 
>Shane Wegner
>http://www.cm.nu/~shane/
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup

CVS Updates - was default speakup for Debian Sarge

[Steve Holmes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Speaking of updates to cVS, I'm no longer getting any update
announcements when changes are posted to CVS.  Is that list broken
again? This Speakup/kernel version compatibility stuff is going to have
to be documented carefully and clearly.  the tar ball came out not more
than 3 months or so ago and now it is no longer compatible with the
latest kernel if I understand things correctly.  How easy would it be to
recreate the tar ball with the latest version to try and keep
reasonablly current with a current production kernel?  I have on some
occasions, patched a "working version of Speakup inside a given kernel
source and tar that back up for personal recovery purposes but I'm
trying to think of someone new to Speakup who wants to get started and
would hope he wouldn't have to do CVS and hopt to God it matches the
kernel he is using.

I would really like to know the procedure of how to take a CVS snap shot
of Speakup and convert it into a tarball that will still compile and
work.

On Thu, Aug 04, 2005 at 11:00:36AM -0500, Gene Collins wrote:
> Hi Shane.  The latest cvs has been modified to work with 2.6.12, and
> will no longer work with 2.6.11 and earlier.  I suggest you grab the
> Speakup 2.0 tar ball and shoehorn that into the 2.6.8 kernel.
> 
> Gene

- -- 
HolmesGrown Solutions
The best solutions for the best price!
http://ld.net/?holmesgrown
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)

iD8DBQFC8k8RWSjv55S0LfERA4rlAJ4/E2+eS6jV1ujx6OaWNXyQodz3AQCg9bgU
L0QeXRsWnGd82R5ttC8BAII=
=LPtH
-----END PGP SIGNATURE-----

Re: CVS Updates - was default speakup for Debian Sarge

[Steve Holmes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Also, What versions of 2.4 kernels will this latest CVS Speakup work on?
I have an old laptop here that I am sticking to 2.4 for the forseable
future.  Thanks for any help.  I could use Speakup 2.0 tar ball if needs
be.  thanks.

On Thu, Aug 04, 2005 at 10:23:31AM -0700, Steve Holmes wrote:
> Speaking of updates to cVS, I'm no longer getting any update
> announcements when changes are posted to CVS.  Is that list broken
> again? This Speakup/kernel version compatibility stuff is going to have
> to be documented carefully and clearly.  the tar ball came out not more
> than 3 months or so ago and now it is no longer compatible with the
> latest kernel if I understand things correctly.  How easy would it be to
> recreate the tar ball with the latest version to try and keep
> reasonablly current with a current production kernel?  I have on some
> occasions, patched a "working version of Speakup inside a given kernel
> source and tar that back up for personal recovery purposes but I'm
> trying to think of someone new to Speakup who wants to get started and
> would hope he wouldn't have to do CVS and hopt to God it matches the
> kernel he is using.
> 
> I would really like to know the procedure of how to take a CVS snap shot
> of Speakup and convert it into a tarball that will still compile and
> work.
> 
> On Thu, Aug 04, 2005 at 11:00:36AM -0500, Gene Collins wrote:
> > Hi Shane.  The latest cvs has been modified to work with 2.6.12, and
> > will no longer work with 2.6.11 and earlier.  I suggest you grab the
> > Speakup 2.0 tar ball and shoehorn that into the 2.6.8 kernel.
> > 
> > Gene
> 
> -- 
> HolmesGrown Solutions
> The best solutions for the best price!
> http://ld.net/?holmesgrown
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 

- -- 
HolmesGrown Solutions
The best solutions for the best price!
http://ld.net/?holmesgrown
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)

iD8DBQFC8lMzWSjv55S0LfERA1G+AJ0VGXuKKFo/sAsgiGim6nnFXLcqcQCeKfd9
S6AfgAqPwyg0uj+2QGxX/+U=
=Uy6w
-----END PGP SIGNATURE-----

Re: CVS Updates - was default speakup for Debian Sarge

[Kirk Reiser]

Hi Steve:  We cannot maintain compatability between speakup with the
new 2.6.12 kernels and the old kernels because of major console
changes in the kernel.  For that reason the speakup-2.0 tar ball is
the definitive answer for 2.4.xx kernels and kernels before the 2.6.12
release.  I will no longer be supporting any kernels prior to 2.6.12
and have already started ripping out 2.4.xx support.

I just made the first check in to cvs in the past three months so you
should have received a cvs update earlier this afternoon.  The link
between cvs and the mailing list is very unstable and I'd like to find
a better way to do automatic mail outs of cvs changes but am not sure
how to do that just yet.  Ideas are welcome.

CVS will probably be quite a hit and miss over the short term.  I am
adding code in submitted by the folks at APH and am starting to to
some long overdue clean-ups and extensions.  I will try to not check
in broken code but sometimes that's hard to avoid if I just plain miss
something.

  Kirk

-- 

Kirk Reiser				The Computer Braille Facility
e-mail: kirk@braille.uwo.ca		University of Western Ontario
phone: (519) 661-3061

Re: CVS Updates - was default speakup for Debian Sarge

[Gregory Nowak]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kirk, can you please describe how the link between cvs and the mail
system works, and what causes it to break down? I think that if we
knew how the system works, we would be better equipped to provide
ideas/suggestions for how it could be improved.

Greg


On Thu, Aug 04, 2005 at 02:27:53PM -0400, Kirk Reiser wrote:
> Hi Steve:  We cannot maintain compatability between speakup with the
> new 2.6.12 kernels and the old kernels because of major console
> changes in the kernel.  For that reason the speakup-2.0 tar ball is
> the definitive answer for 2.4.xx kernels and kernels before the 2.6.12
> release.  I will no longer be supporting any kernels prior to 2.6.12
> and have already started ripping out 2.4.xx support.
> 
> I just made the first check in to cvs in the past three months so you
> should have received a cvs update earlier this afternoon.  The link
> between cvs and the mailing list is very unstable and I'd like to find
> a better way to do automatic mail outs of cvs changes but am not sure
> how to do that just yet.  Ideas are welcome.
> 
> CVS will probably be quite a hit and miss over the short term.  I am
> adding code in submitted by the folks at APH and am starting to to
> some long overdue clean-ups and extensions.  I will try to not check
> in broken code but sometimes that's hard to avoid if I just plain miss
> something.
> 
>   Kirk
> 
> -- 
> 
> Kirk Reiser				The Computer Braille Facility
> e-mail: kirk@braille.uwo.ca		University of Western Ontario
> phone: (519) 661-3061
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 
> !DSPAM:42f25e9e155481223110344!
> 
> 

- -- 
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.2.3 (GNU/Linux)

iD8DBQFC8mNa7s9z/XlyUyARAp81AKDOOZnnnb8Cic9KEZF73zIIHuMJGgCfeP97
7Vm46P3hQhxSFaTnevgCFiU=
=UVKk
-----END PGP SIGNATURE-----

Re: CVS Updates - was default speakup for Debian Sarge

[Kirk Reiser]

Sure Greg I'll try.  The cvs repository/server is on bumpy or now
nondescript.ca.  I currently have it set to send mail upon check in to
cvs@braille.uwo.ca.  The problem is it sends the mail from the user
doing the check in such as kirk@nondescript.ca.  The problem is that
nondescript.ca does not handle mail itself.  It is all forwarded to
another machine which folks that have check in privileges do not have
accounts on.  Furthermore they would also need to have their
xxx@nondescript.ca addresses added to the cvs mailing list and because
bumpy doesn't handle mail itself they could never receive the
confirmation requests and so forth.  I do not want to have general
mail running on that machine because as you probably know it is
extremely over worked as it is.  If we could get cvs to send all
checkins from one address that would work but I haven't had the time
to look into how that might be done.

  Kirk

-- 

Kirk Reiser				The Computer Braille Facility
e-mail: kirk@braille.uwo.ca		University of Western Ontario
phone: (519) 661-3061

Re: CVS Updates - was default speakup for Debian Sarge

[Ameer Armaly]

Hmm... What of the possibility of hard-coding a configurable  "logging 
address" in to cvs, that way, you can tell it that basically I want all this 
mail sent from one  address, but at the same time show who actually did the 
checkin somewhere in the message.
 ----- Original Message ----- 
From: "Kirk Reiser" <kirk@braille.uwo.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Thursday, August 04, 2005 3:21 PM
Subject: Re: CVS Updates - was default speakup for Debian Sarge


> Sure Greg I'll try.  The cvs repository/server is on bumpy or now
> nondescript.ca.  I currently have it set to send mail upon check in to
> cvs@braille.uwo.ca.  The problem is it sends the mail from the user
> doing the check in such as kirk@nondescript.ca.  The problem is that
> nondescript.ca does not handle mail itself.  It is all forwarded to
> another machine which folks that have check in privileges do not have
> accounts on.  Furthermore they would also need to have their
> xxx@nondescript.ca addresses added to the cvs mailing list and because
> bumpy doesn't handle mail itself they could never receive the
> confirmation requests and so forth.  I do not want to have general
> mail running on that machine because as you probably know it is
> extremely over worked as it is.  If we could get cvs to send all
> checkins from one address that would work but I haven't had the time
> to look into how that might be done.
>
>  Kirk
>
> -- 
>
> Kirk Reiser The Computer Braille Facility
> e-mail: kirk@braille.uwo.ca University of Western Ontario
> phone: (519) 661-3061
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

Re: CVS Updates - was default speakup for Debian Sarge

[Steve Holmes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Yes, I did receive the notification today.  About your CVS mail delema,
I wonder if you could just have CVS send the mails like it now does to a
"dummy user" on that machine or inside your network.  Then have that
dummy user run an automated script of some kind to pass these messages
to CVS mailing list with whatever From: id you wish.  Does this make
sense? Perhaps the mail forwarding script written in perl, python, etc.
could run from a crontab a couple times a day or something.  I'm just
thinking on the fly right now but maybe this this could get around
subscriptions problem.  Hope I understood your question correctly:).

On Thu, Aug 04, 2005 at 02:27:53PM -0400, Kirk Reiser wrote:
> Hi Steve:  We cannot maintain compatability between speakup with the
> new 2.6.12 kernels and the old kernels because of major console
> changes in the kernel.  For that reason the speakup-2.0 tar ball is
> the definitive answer for 2.4.xx kernels and kernels before the 2.6.12
> release.  I will no longer be supporting any kernels prior to 2.6.12
> and have already started ripping out 2.4.xx support.
> 
> I just made the first check in to cvs in the past three months so you
> should have received a cvs update earlier this afternoon.  The link
> between cvs and the mailing list is very unstable and I'd like to find
> a better way to do automatic mail outs of cvs changes but am not sure
> how to do that just yet.  Ideas are welcome.
> 
> CVS will probably be quite a hit and miss over the short term.  I am
> adding code in submitted by the folks at APH and am starting to to
> some long overdue clean-ups and extensions.  I will try to not check
> in broken code but sometimes that's hard to avoid if I just plain miss
> something.
> 
>   Kirk
> 
> -- 
> 
> Kirk Reiser				The Computer Braille Facility
> e-mail: kirk@braille.uwo.ca		University of Western Ontario
> phone: (519) 661-3061
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 

- -- 
HolmesGrown Solutions
The best solutions for the best price!
http://ld.net/?holmesgrown
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)

iD8DBQFC8nfeWSjv55S0LfERA1MNAJ98ilJKX5OP+XutRhzph2gJx6MYOQCg5sEd
KWGhTgg0L7GRs1+FUjhf5ME=
=thE8
-----END PGP SIGNATURE-----

Re: CVS Updates - was default speakup for Debian Sarge

[Garrett Klein]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Hi Kirk, Steve, and all,

On Thu, Aug 04, 2005 at 01:17:36PM -0700, Steve Holmes wrote:
> Yes, I did receive the notification today.  About your CVS mail delema,
> I wonder if you could just have CVS send the mails like it now does to a
> "dummy user" on that machine or inside your network.  Then have that
> dummy user run an automated script of some kind to pass these messages
> to CVS mailing list with whatever From: id you wish.  Does this make
> sense? Perhaps the mail forwarding script written in perl, python, etc.
> could run from a crontab a couple times a day or something.  I'm just
> thinking on the fly right now but maybe this this could get around
> subscriptions problem.  Hope I understood your question correctly:).

How about using mail aliases? Just a thought. Depending on the mta you could use something like a .forward file or an alias in the alias file to accomplish that. Just have all mail sent from the cvs system *or the user checkign in code) forwarded to some other mail address. Oh wait, bumpy doesn't have an MTA, so never mind... unless you want it relaying things. Sigh. There goes my idea.

Garrett
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFC8r5mpyN96jH+4g0RA9KoAKC0NC6yHg/LVmi5kiQyR49b7dzq9gCgvWM1
Z3M0Umq4QJFHs1qYl8e2vO0=
=5rHM
-----END PGP SIGNATURE-----