From: Mark Hatle <mark.hatle@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: Re: bb.utils.vercmp() not consistent with debian rules
Date: Fri, 6 Apr 2012 11:56:36 -0500 [thread overview]
Message-ID: <4F7F2044.9050604@windriver.com> (raw)
In-Reply-To: <857BE142E5399E46B20FD45B9DB8A7BC0FD2D07B@SHSMSX102.ccr.corp.intel.com>
On 4/5/12 1:42 AM, Lu, Lianhao wrote:
>
> Martin Jansa wrote on 2012-04-05:
>> On Thu, Apr 05, 2012 at 06:22:00AM +0000, Lu, Lianhao wrote:
>>> Hi guys,
>>>
>>> When I'm looking at the Yocto bug#2233, I find that the function
>>> bb.utils.vercmp() is not consistent with the debian packaging
>>> rules(http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-
>>> Version).
>>>
>>> According to debian rules, "r0" is earlier than "r0-dream", but the bb.utils.vercmp() thinks "r0" is later than "r0-dream".
>>
>> And what about something like this:
>>
>> Version: 3.2-r10
>> is older then
>> Version: 3.2-r2-oe0
As an FYI, RPM does:
3.2-r10 > 3.2-r2-oe0
3.2-r2 < 3.2-r2-oe0
--Mark
> I think this is exactly what the debian rules wants, "3.2-r10">"3.2-r2-oe0". And opkg follows that rule.
>
> The problem is that bb.utils.vercmp thinks "3.2-r2">"3.2-r2-oe0" while opkg thinks "3.2-r2"<"3.2-r2-oe0".
>
> -Lianhao
>
>> At least that was what target opkg was doing for me and I had to bump PE
>> http://git.shr-project.org/git/?p=meta-smartphone.git;a=commit;h=cb119753
>> a77208617936085100595e6343ade650
>>
>> Cheers,
>>
>>>
>>> A pervious patch
>>> http://cgit.openembedded.org/bitbake/commit/?id=727ce6ffe33a119cb17f7d91
>>> b173f11a055eea3c seems causing the bb.utils.vercmp to specially handle
>>> the separators of "." and "-".
>>>
>>> Is it desired to behave differently from debian rules?
>>>
>>> Best Regards,
>>> -Lianhao
>>>
>>> _______________________________________________
>>> bitbake-devel mailing list
>>> bitbake-devel@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel
>>
>
>
> _______________________________________________
> bitbake-devel mailing list
> bitbake-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel
prev parent reply other threads:[~2012-04-06 19:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 6:22 bb.utils.vercmp() not consistent with debian rules Lu, Lianhao
2012-04-05 6:28 ` Martin Jansa
2012-04-05 6:42 ` Lu, Lianhao
2012-04-05 12:18 ` Richard Purdie
2012-04-05 12:59 ` Richard Purdie
2012-04-05 14:44 ` Lu, Lianhao
2012-04-06 3:00 ` Lu, Lianhao
2012-04-06 16:56 ` Mark Hatle [this message]
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=4F7F2044.9050604@windriver.com \
--to=mark.hatle@windriver.com \
--cc=bitbake-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.