public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Zachary Kline <zkline@speedpost.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Minor hiccups with espeak 1.44.05 and espeakup 0.71-3 on Arch
Date: Fri, 17 Sep 2010 20:45:30 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LNX.2.00.1009172044440.13393@localhost.localdomain> (raw)
In-Reply-To: <20100918024436.GA7504@lnx3.holmesgrown.com>

Hi,
Yes, Pacman will warn you if there is a new version available when you 
ignore espeak.  Telling when that version is new enough to be upgraded to 
safely is your problem.
Best,
Zack.


On Fri, 17 Sep 2010, Steve Holmes wrote:

> On Fri, Sep 17, 2010 at 03:13:43AM -0500, Christopher Brannon wrote:
>> One option is to downgrade, assuming that you still have access to
>> the old package.  As you know, those usually aren't kept on our mirrors.
>> I put a copy of the previous version on my website.  You should be able
>> to downgrade with the following command:
>> pacman -U http://the-brannons.com/misc/espeak-1.44.02-1-i686.pkg.tar.xz
>>
>> I hope this gets resolved soon!
>
> I hope so too.  I have a question relating to Arch in the meantime; if
> I specify espeak in an ignor option for pacman, will the upgrade
> process still tell me if new versions come available?  I ask this
> because if I don't formally ignore this package, pacman -Syu would
> merely try to upgrade all referenced packages including espeak.
> That's one thing where I wish pacman had an option where you could
> step through packages one by one; presently, it's an all or none
> situation.
>
> Most of the espeak problems I encountered seemed to happen with
> emacspeak; hadn't noticed any particular problem with espeakup and
> speakup yet.  But when I downgraded, emacspeak began to speak properly
> again.  With espeak 0.44.05 or whatever, emacspeak started wining all
> over the place with pitch changes.  To much for me.  Emacspeak and its
> varying voices is enough and well intentioned but this got to be out
> of hand so dropping back to previous version fixed that problem.
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

      reply	other threads:[~ UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Zachary Kline
 ` Luke Yelavich
 ` Christopher Brannon
   ` Willem van der Walt
   ` Zachary Kline
     ` Chuck Hallenbeck
   ` Steve Holmes
     ` Zachary Kline [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=alpine.LNX.2.00.1009172044440.13393@localhost.localdomain \
    --to=zkline@speedpost.net \
    --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).