[Fwd: Virtaal on ARM]

[Kevin Gordon]

On Mon, Nov 14, 2011 at 2:57 PM, Chris Leonard <cjlhomeaddress at gmail.com>wrote:

> All,
>
> Ignoring for the moment whether parachutes or Mars-style airbags are a
> better delivery option from helicopters, if one is going to "airdrop" an XO
> tablet into a remote area, one of the things that might be very useful
> would be the ability to bootstrap localization right on the machine.
>
> I'm a big fan of Virtaal (from the makers of Poolte) as an off-line PO
> file editor and general L10n tool for a variety of reasons I won't go into.
>
> http://translate.sourceforge.net/wiki/virtaal/index
>
> In previous interations of XO-1 builds, getting Virtaal on the Gnome boot
> was a simple "sudo yum install virtaal".  Unfortunately, when I tried this
> on an XO-1.75 with 883, I got errors (detailed far below).  I sent the
> errors to the Virtaal devs and got back the reply in-lined below.
>
> Can anyone shed some light on how it might be possible to get Virtaal
> working on the Gnome boot on an XO-1.75?
>
> Warmest Regards,
>
> cjl
> Sugar Labs Translation Team Coordinator
>
> ---------- Forwarded message ----------
> From: Dwayne Bailey <dwayne at translate.org.za>
> Date: Thu, Nov 3, 2011 at 6:03 AM
> Subject: Re: [Fwd: Virtaal on ARM]
> To: Chris Leonard <cjlhomeaddress at gmail.com>
> Cc: F Wolff <Friedel at translate.org.za>
>
>
>  On 2011-11-02 16:41, Chris Leonard wrote:
>
> On Wed, Nov 2, 2011 at 5:17 AM, Dwayne Bailey <dwayne at translate.org.za>wrote:
>
>>  Thanks for forwarding Friedel.
>>
>> Chris, it seems the issue is fc14 not having aedion which prevent
>> translate-toolkit from installing.  Where are those RPMs from? Are you
>> getting them from my repo or did you build them yourself.  I've thought in
>> the past of making subtitle support a different package.
>>
>> The mesa stuff is not related to Virtaal, I think its an existing error
>> in your RPM DB.
>>
>>
>> The package list used for the OLPC 883 ARM-supporting build (XO-1.75) is
>> here:
>>
>> http://download.laptop.org/xo-1.75/os/official/883/os883.packages.txt
>>
>> OLPC tends to pull from Fedora RPMs as our OS is in essence a specialized
>> Fedora spin
>>
>  OK so let me ramble a bit....
>
> In the install: virtaal pulls in translate-toolkit which pulls in aeidon
> aeidon is part of gaupol (gaupol is a subtitle editor aeidon implements
> the subtitle formats)
>
> The gaupol aeidon split happened during Fedora 14.  So in our
> translate-toolkit RPM we only import aeidon when Fedora >= 14.
>
> See ' %if 0%{?fedora} >= 14' at the top of:
> http://pkgs.fedoraproject.org/gitweb/?p=translate-toolkit.git;a=blob;f=translate-toolkit.spec;h=6172c89bdaeceaf684c61a3750dca120ab72aa9e;hb=1e65541302d3c3bd217e4bd7b126d32be5b9c189
>
> So from the looks of it OLPC pulls in packages from olpc-14 but also from
> fedora (but I assume that is base not updates).
>
> So my guess is this.  Our fc14 translate-toolkit relies of the fact that
> aeidon is available in updates for F14.  But OLPC doesn't have those
> updates either because it branched earlier or because it only uses the base
> repo (not updates repo)
>
> I'm also not sure why OLPC has not included the updates, maybe stability.
>
> I'm wondering if there is a way to handle this in Fedora packages. I
> already make package decisions depending on the Fedora version. I can make
> the OLPC package even leaner if I know how to identify an OLPC branch.  If
> you can help with that then I can probably build a new OLPC specific
> package.
>
>
> As for the issue with mesa I have a pretty good idea that it is not so
> much an "error" with the pre-existing RPM as the fact that I think OLPC has
> hacked a local copy down to size to save some space on the XO.  Choices
> like that get made because of the extremely limited storage of the XO
> laptop.  Let's call it a "misfeature" of a compromise that was made for the
> right reasons. with unintended consequences.
>
> So lets ignore it for this discussion.
>
> --
> regards
> Dwayne
>
>
>
>
>
>
> Output during Virtaa linstall:
>
>
> [olpc at xo-c5-b9-b6 ~]$ sudo yum install virtaal
> fedora/metalink
>                            | 2.9 kB     00:00
> fedora                                                   | 4.3 kB
> 00:00
> fedora/primary_db                                        | 9.3 MB
> 01:04
> olpc-f14                                                 |  951 B
> 00:00
> olpc-f14/primary                                         |  22 kB
> 00:00
> olpc-f14
> 151/151
> olpc-f14-xo1.75                                          |  951 B
> 00:00
> olpc-f14-xo1.75/primary                                  |  17 kB
> 00:00
> olpc-f14-xo1.75
> 165/165
> updates/metalink                                         | 2.7 kB
> 00:00
> updates                                                  | 4.3 kB
> 00:00
> updates/primary_db                                       | 1.3 MB
> 00:08
> Setting up Install Process
> Resolving Dependencies
> --> Running transaction check
> ---> Package virtaal.noarch 0:0.6.1-8.fc14 set to be installed
> --> Processing Dependency: translate-toolkit >= 1.5.1 for package:
> virtaal-0.6.1-8.fc14.noarch
> --> Processing Dependency: python-Levenshtein for package:
> virtaal-0.6.1-8.fc14.noarch
> --> Processing Dependency: libtranslate for package:
> virtaal-0.6.1-8.fc14.noarch
> --> Processing Dependency: gnome-python2-gtkspell for package:
> virtaal-0.6.1-8.fc14.noarch
> --> Processing Dependency: python-psycopg2 for package:
> virtaal-0.6.1-8.fc14.noarch
> --> Running transaction check
> ---> Package gnome-python2-gtkspell.armv5tel 0:2.25.3-34.fc14.1 set to be
> installed
> --> Processing Dependency: gnome-python2-extras = 2.25.3-34.fc14.1 for
> package: gnome-python2-gtkspell-2.25.3-34.fc14.1.armv5tel
> ---> Package libtranslate.armv5tel 0:0.99-23.fc13 set to be installed
> ---> Package python-Levenshtein.armv5tel 0:0.10.1-12.fc14 set to be
> installed
> ---> Package python-psycopg2.armv5tel 0:2.2.2-2.fc14 set to be installed
> --> Processing Dependency: libpq.so.5 for package:
> python-psycopg2-2.2.2-2.fc14.armv5tel
> ---> Package translate-toolkit.noarch 0:1.9.0-1.fc14 set to be installed
> --> Processing Dependency: aeidon for package:
> translate-toolkit-1.9.0-1.fc14.noarch
> --> Processing Dependency: python-enchant for package:
> translate-toolkit-1.9.0-1.fc14.noarch
> --> Processing Dependency: python-vobject for package:
> translate-toolkit-1.9.0-1.fc14.noarch
> --> Running transaction check
> ---> Package gnome-python2-extras.armv5tel 0:2.25.3-34.fc14.1 set to be
> installed
> ---> Package postgresql-libs.armv5tel 0:8.4.5-1.fc14 set to be installed
> ---> Package python-enchant.armv5tel 0:1.3.1-7.fc14 set to be installed
> ---> Package python-vobject.noarch 0:0.8.1c-3.fc14 set to be installed
> ---> Package translate-toolkit.noarch 0:1.9.0-1.fc14 set to be installed
> --> Processing Dependency: aeidon for package:
> translate-toolkit-1.9.0-1.fc14.noarch
> --> Finished Dependency Resolution
> Error: Package: translate-toolkit-1.9.0-1.fc14.noarch (updates)
>            Requires: aeidon
>  You could try using --skip-broken to work around the problem
> ** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
> mesa-libGL-7.9-6.fc14.armv5tel has missing requires of
> mesa-dri-drivers(armv5tel-32) = ('0', '7.9', '6.fc14')
>
>
Chris:


I believe that you can safely ignore the 'mesa' yum check error. AFAIK
these drivers are omitted by design.  yum check will give the same errors
on all the new XO builds, as the DRI modules are not used on the XO and are
no longer shipped to save a large amount of space - especially on the XO-1.
The other messages re dependencies, perhaps Mr Robinson can more
effieciently say if there are the necessary arm builds in the repos, or
whether he can generate them easily..

KG
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/devel/attachments/20111114/61c67c8b/attachment.html>