From: "Eric Bénard" <eric@eukrea.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] qt4: update to latest version 4.7.4
Date: Wed, 28 Sep 2011 12:23:23 +0200 [thread overview]
Message-ID: <4E82F59B.7080808@eukrea.com> (raw)
In-Reply-To: <201109281111.33193.paul.eggleton@linux.intel.com>
Hi Paul,
Le 28/09/2011 12:11, Paul Eggleton a écrit :
> On Wednesday 21 September 2011 14:16:25 Eric Bénard wrote:
>> Le 21/09/2011 15:05, Koen Kooi a écrit :
>>> WARNING: For recipe qt4-x11-free, the following files were installed but
>>> not shipped in any package:
>>> WARNING: /usr/share/qt4/phrasebooks/swedish.qph
>>> WARNING: /usr/share/qt4/phrasebooks/dutch.qph
>>> WARNING: /usr/share/qt4/phrasebooks/german.qph
>>> WARNING: /usr/share/qt4/phrasebooks/polish.qph
>>> WARNING: /usr/share/qt4/phrasebooks/danish.qph
>>> WARNING: /usr/share/qt4/phrasebooks/japanese.qph
>>> WARNING: /usr/share/qt4/phrasebooks/finnish.qph
>>> WARNING: /usr/share/qt4/phrasebooks/norwegian.qph
>>> WARNING: /usr/share/qt4/phrasebooks/french.qph
>>> WARNING: /usr/share/qt4/phrasebooks/russian.qph
>>> WARNING: /usr/share/qt4/phrasebooks/spanish.qph
>>> WARNING: /usr/share/qt4/phrasebooks/hungarian.qph
>>> WARNING: /usr/share/qt4/phrasebooks/italian.qph
>>
>> OK I forget to integrate Otavio's patch which fix the translations. I'll
>> update tonight.
>
> Did you have a chance to do this? I don't see an additional commit in the
> qt4_upgrade branch in your repo.
>
I have the patch locally and I will (really) work on this tonight.
Sorry for the delay I've been overbusy since last wednesday.
Eric
next prev parent reply other threads:[~2011-09-28 10:39 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-10 20:07 [PATCH 1/2] qt4: add blacklist-diginotar-certs patch Eric Bénard
2011-09-10 20:07 ` [PATCH 2/2] qt4: update to latest version 4.7.4 Eric Bénard
2011-09-11 17:22 ` Anders Darander
2011-09-11 17:33 ` [PATCH] " Eric Bénard
2011-09-12 10:34 ` Paul Eggleton
2011-09-14 11:11 ` Koen Kooi
2011-09-14 13:09 ` Eric Bénard
2011-09-14 15:34 ` Otavio Salvador
2011-09-15 7:57 ` Eric Bénard
2011-09-15 15:07 ` Otavio Salvador
2011-09-14 17:03 ` Koen Kooi
2011-09-15 17:32 ` Saul Wold
2011-09-15 18:41 ` Eric Bénard
2011-09-15 20:06 ` Otavio Salvador
2011-09-16 11:12 ` Paul Eggleton
2011-09-16 12:22 ` Eric Bénard
2011-09-16 12:54 ` Phil Blundell
2011-09-16 16:46 ` Richard Purdie
2011-09-16 13:11 ` Otavio Salvador
2011-09-19 9:45 ` Koen Kooi
2011-09-19 11:48 ` Otavio Salvador
2011-09-19 12:09 ` Koen Kooi
2011-09-19 12:25 ` Otavio Salvador
2011-09-19 13:03 ` Richard Purdie
2011-09-19 19:33 ` Eric Bénard
2011-09-20 21:18 ` Eric Bénard
2011-09-21 10:44 ` Koen Kooi
2011-09-21 12:52 ` Eric Bénard
2011-09-21 13:05 ` Koen Kooi
2011-09-21 13:16 ` Eric Bénard
2011-09-28 10:11 ` Paul Eggleton
2011-09-28 10:23 ` Eric Bénard [this message]
2011-09-28 13:11 ` Otavio Salvador
2011-09-28 13:33 ` Richard Purdie
2011-09-30 11:47 ` Eric Bénard
2011-09-30 16:23 ` Paul Eggleton
2011-09-12 10:34 ` [PATCH 1/2] qt4: add blacklist-diginotar-certs patch Paul Eggleton
2011-09-15 17:34 ` Saul Wold
-- strict thread matches above, loose matches on Subject: below --
2011-09-15 8:40 [PATCH] qt4: update to latest version 4.7.4 Eric Bénard
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=4E82F59B.7080808@eukrea.com \
--to=eric@eukrea.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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