From: Andrei Dinu <andrei.adrianx.dinu@intel.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] mtools : upgrade to 4.0.18
Date: Wed, 30 Jan 2013 11:05:27 +0200 [thread overview]
Message-ID: <5108E257.7000500@intel.com> (raw)
In-Reply-To: <5107FCE4.6000602@linux.intel.com>
Hi Darren,
I created an atom-pc hddimg and loaded it into qemu. The image booted
with no errors. So everything seems to work fine. Thanks for the help!
Andrei
On 01/29/2013 06:46 PM, Darren Hart wrote:
> On 01/29/2013 01:49 AM, Andrei Dinu wrote:
>> Hello,
> Hi Andrei,
>
>> No, i performed only minimal testing, to see if the package is included
>> and also that it works when summoned in the console. If you can tell me
>> how i can test it further, i would be grateful.
> The mtools are used to populate the live images. Pick a BSP that
> supports this format (atom-pc for example) and build the minimal image.
> Then boot the resulting core-image-minimal.hddimg. You can do this with
> qemu if you don't have an atom machine handy.
>
> That would add enough confidence to bump the version for me.
>
> --
> Darren
>
>> Thanks,
>>
>> Andrei Dinu
>>
>> On 01/28/2013 08:45 PM, Darren Hart wrote:
>>> Have you performed testing with the generation of live images using this
>>> version?
>>>
>>> Thanks,
>>>
>>> Darren
>>>
>>> On 01/28/2013 04:27 AM, Andrei Dinu wrote:
>>>> Signed-off-by: Andrei Dinu <andrei.adrianx.dinu@intel.com>
>>>> ---
>>>> .../mtools/{mtools_4.0.17.bb => mtools_4.0.18.bb} | 6 +++---
>>>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>>> rename meta/recipes-devtools/mtools/{mtools_4.0.17.bb => mtools_4.0.18.bb} (86%)
>>>>
>>>> diff --git a/meta/recipes-devtools/mtools/mtools_4.0.17.bb b/meta/recipes-devtools/mtools/mtools_4.0.18.bb
>>>> similarity index 86%
>>>> rename from meta/recipes-devtools/mtools/mtools_4.0.17.bb
>>>> rename to meta/recipes-devtools/mtools/mtools_4.0.18.bb
>>>> index 5ce6c09..0f99685 100644
>>>> --- a/meta/recipes-devtools/mtools/mtools_4.0.17.bb
>>>> +++ b/meta/recipes-devtools/mtools/mtools_4.0.18.bb
>>>> @@ -5,7 +5,7 @@ SECTION = "optional"
>>>> LICENSE = "GPLv3"
>>>> LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504"
>>>>
>>>> -PR = "r1"
>>>> +PR = "r0"
>>>>
>>>> RDEPENDS_${PN} = "glibc-gconv-ibm850"
>>>> RRECOMMENDS_${PN} = "\
>>>> @@ -24,13 +24,13 @@ RRECOMMENDS_${PN} = "\
>>>> glibc-gconv-ibm866 \
>>>> glibc-gconv-ibm869 \
>>>> "
>>>> +SRC_URI[md5sum] = "a23646617546bf6ad56f061d8b283c85"
>>>> +SRC_URI[sha256sum] = "59e9cf80885399c4f229e5d87e49c0c2bfeec044e1386d59fcd0b0aead6b2f85"
>>>>
>>>> SRC_URI = "${GNU_MIRROR}/mtools/mtools-${PV}.tar.bz2 \
>>>> file://mtools-makeinfo.patch \
>>>> file://no-x11.gplv3.patch"
>>>>
>>>> -SRC_URI[md5sum] = "15571c615d8f75f5f6d294272f80c7fa"
>>>> -SRC_URI[sha256sum] = "0ecc358e30a72d215b1d4c625b27e67121cd6f6075370dfb791ef2a8b980ecb6"
>>>>
>>>> inherit autotools
>>>>
>>>>
next prev parent reply other threads:[~2013-01-30 9:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 12:27 [PATCH] mtools : upgrade to 4.0.18 Andrei Dinu
2013-01-28 18:45 ` Darren Hart
2013-01-29 9:49 ` Andrei Dinu
2013-01-29 16:46 ` Darren Hart
2013-01-30 9:05 ` Andrei Dinu [this message]
2013-01-30 16:09 ` Darren Hart
2013-01-31 11:49 ` Andrei Dinu
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=5108E257.7000500@intel.com \
--to=andrei.adrianx.dinu@intel.com \
--cc=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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