From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by befuddled.reisers.ca (Postfix, from userid 65534) id 110F51EF829; Thu, 31 Dec 2015 08:45:23 -0500 (EST) Received: from sonata.ens-lyon.org (domu-toccata.ens-lyon.fr [140.77.166.138]) by befuddled.reisers.ca (Postfix) with ESMTPS id EAA371EF860 for ; Thu, 31 Dec 2015 08:43:51 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by sonata.ens-lyon.org (Postfix) with ESMTP id 88518200BF for ; Thu, 31 Dec 2015 14:43:50 +0100 (CET) Received: from sonata.ens-lyon.org ([127.0.0.1]) by localhost (sonata.ens-lyon.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eLOm5Te2hTuG for ; Thu, 31 Dec 2015 14:43:50 +0100 (CET) Received: from var.youpi.perso.aquilenet.fr (ABordeaux-655-1-80-117.w90-60.abo.wanadoo.fr [90.60.111.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by sonata.ens-lyon.org (Postfix) with ESMTPSA id 68643200BD for ; Thu, 31 Dec 2015 14:43:50 +0100 (CET) Received: from samy by var.youpi.perso.aquilenet.fr with local (Exim 4.86) (envelope-from ) id 1aEdW9-0001vg-UE for speakup@linux-speakup.org; Thu, 31 Dec 2015 14:43:49 +0100 Date: Thu, 31 Dec 2015 14:43:49 +0100 From: Samuel Thibault To: "Speakup is a screen review system for Linux." Subject: Re: Getting speakup to run on debian Message-ID: <20151231134349.GE4579@var.home> References: <558A5D8D.20209@gmail.com> <3616.1451565179@ccs.covici.com> <20151231131235.GA4579@var.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30) X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 X-BeenThere: speakup@linux-speakup.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Dec 2015 13:45:23 -0000 Steve Matzura, on Thu 31 Dec 2015 08:39:41 -0500, wrote: > OK then, what's the right way to do that, Googling "bug debian" brings https://www.debian.org/Bugs/ which explains everything. > and while I await the bug to be properly documented and fixed, how do > I work around it? Depends on the bug. Thus discussion is needed. Probably the better place in this case is the debian-accessibility@lists.debian.org mailing list. Samuel