Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Andrei Dinu <andrei.adrianx.dinu@intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel@lists.openembedded.org,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] gypsy: removed gypsy from meta/recipes-connectivity
Date: Wed, 24 Oct 2012 11:20:52 +0300	[thread overview]
Message-ID: <5087A4E4.1010801@intel.com> (raw)
In-Reply-To: <20121024080007.GZ3269@jama.jama.net>

The newer code points to :

commit be8c9c382d2d1d37b51d29b0843045121ec90213
Author: iain <iain@sleepfive.com>
Date:   Tue Aug 28 12:31:42 2012 +0100

     Configure automake to generate .gz and .bz2 archives

This is the latest commit in the gypsy git master branch.

Also, the lastest release is pointed here :
http://gypsy.freedesktop.org/releases/

and it is on the same date as the last commit in git.

I don't really know how git recipes work, do you suggest updating the PV ?

Andrei Dinu


On 10/24/2012 11:00 AM, Martin Jansa wrote:
> On Wed, Oct 24, 2012 at 10:46:08AM +0300, Andrei Dinu wrote:
>> Hi Martin,
>>
>> This change was caused by the bug :
>>
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=2797
>>
>> I removed the tarball and kept only the git package because that is what
>> says in the bug.
>>
>> Secondly, i modified the SRCREV because i took the latest version in the
>> git repo.
> Hi,
>
> So this SRCREV points to newer code then 0.9 now? Then you forgot to
> update PV to say so.
>
> That's why there is error about downgrading it.
>
> Cheers,
>   
>> If there is anything more to add please send me an email.
>>
>> Thanks,
>>
>> Andrei Dinu
>>
>> On 10/23/2012 09:54 PM, Martin Jansa wrote:
>>> On Thu, Oct 18, 2012 at 10:59:48PM +0200, Martin Jansa wrote:
>>>> On Thu, Oct 18, 2012 at 08:59:19PM +0200, Martin Jansa wrote:
>>>>> I know you've sent
>>>>> http://patchwork.openembedded.org/patch/37763/
>>>>> to add it to meta-oe, but this patch removed also newer gypsy_0.9.bb
>>>>> and only older gypsy_git.bb was added back.
>>>>>
>>>>> Please fix that.
>>>> There is also this diff which isn't mentioned in your commit.
>>>>
>>>> -SRCREV = "3652e1f37e82b8e63983e30fda3482cd099a8cf5"
>>>> +SRCREV = "be8c9c382d2d1d37b51d29b0843045121ec90213"
>>>>    PV = "0.8+git${SRCPV}"
>>>>    PR = "r2"
>>>>
>>>> @@ -15,4 +15,5 @@
>>>>                        file://gypsy/gypsy-time.h;beginline=1;endline=24;md5=06432ea19a7b6607428d04d9dadc37fd"
>>>>
>>>>    SRC_URI = "git://anongit.freedesktop.org/gypsy;protocol=git \
>>>> -           file://fixups.patch"
>>>> +           file://fixups.patch \
>>>> +           file://0001-gypsy-m4-directory-missing-from-structure.patch"
>>> ping
>>>
>>> meta-oe is still broken because of this
>>>
>>> Cheers,




  reply	other threads:[~2012-10-24  8:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-04 10:14 [PATCH] gypsy: removed gypsy from meta/recipes-connectivity Andrei Dinu
2012-10-18 18:59 ` Martin Jansa
2012-10-18 20:59   ` Martin Jansa
2012-10-23 18:54     ` Martin Jansa
2012-10-24  7:46       ` Andrei Dinu
2012-10-24  8:00         ` Martin Jansa
2012-10-24  8:20           ` Andrei Dinu [this message]
2012-10-24  8:35             ` Martin Jansa
2012-10-18 19:41 ` Saul Wold

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=5087A4E4.1010801@intel.com \
    --to=andrei.adrianx.dinu@intel.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@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