From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on sa.int.altlinux.org X-Spam-Level: X-Spam-Status: No, score=-3.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.2.5 Message-ID: <1356872735.30141.3.camel@kyoto.localdomain> From: Matt Burgess To: Linux console tools development discussion Date: Sun, 30 Dec 2012 13:05:35 +0000 In-Reply-To: <50C70BE2.7050508@gmail.com> References: <1355174446.1626.9.camel@kyoto.localdomain> <50C70BE2.7050508@gmail.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.4.4 (3.4.4-2.fc17) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [kbd] Kbd-1.15.5 fails to loadkeys X-BeenThere: kbd@lists.altlinux.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Linux console tools development discussion List-Id: Linux console tools development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Dec 2012 13:05:52 -0000 Archived-At: List-Archive: On Tue, 2012-12-11 at 14:33 +0400, Alexey Gladkov wrote: > 11.12.2012 01:20, Matt Burgess wrote: > > Hi, > > > > The Linux From Scratch bootscripts have a snippet that, on my box, does > > the following in order to convert a legacy (non-UTF-8) keymap to UTF-8: > > > > dumpkeys -c "iso-8859-1" | loadkeys -u > > > > This fails with the following output: > > > > unknown keysym 'compose' > > :693: syntax error > > syntax error in map file > > key bindings not changed > > Loading > > > > This appears to be a regression from 1.15.3. > > Can you test the fix ? > > http://git.altlinux.org/people/legion/packages/kbd.git?p=kbd.git;a=commit;h=7e06e56157e8431d02e1377cdc44230944203d88 Hi Alexey, Just to put this one to bed, hopefully! loadkeys works correctly when the 2nd hunk of the above fix is applied through the equivalent 'sed': sed -i -e '326 s/if/while/' src/loadkeys.analyze.l I can only assume that I somehow am screwing up the application of the patch, though I've no idea how. I'll try to watch out for the next release candidate and test to make sure the next release works as expected. Thanks for your support on this issue. Regards, Matt.