Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Solving ipkg-utils issues
Date: Wed, 4 Apr 2007 15:38:15 +0300	[thread overview]
Message-ID: <612419699.20070404153815@gmail.com> (raw)
In-Reply-To: <474904993.20070330162851@gmail.com>

Hello,

Friday, March 30, 2007, 4:28:51 PM, you wrote:

> Hello Richard,

> Friday, March 30, 2007, 12:50:00 PM, you wrote:

>> Hi Paul,

>> Thanks for looking at this, its something that does need fixing.

> []
>>>
>>> 1. Broken version comparison logic in ipkg-utils (note that this is
>>> exactly ipkg-utils issues, nether bitbake nor ipkg is affected).
>>> 
> []
>>>
>>>   Patch for p.1 is here: http://bugs.openembedded.org/show_bug.cgi?id=2061

>> I agree with fixing all the above. I've only had a quick glance at the
>> actual patch but I'm fine with committing it and getting testing that
>> way. There is python version comparison code in bitbake which may or may
>> not be of use.

>   Ok, thanks. I'll commit (cleaned up version of) it on weekend then,
> after more people get chance to read this thread and be in loop.

  Ok, committed finally.

  Please reopen http://bugs.openembedded.org/show_bug.cgi?id=2061 if
you face any issues.

>   
> []

>> Cheers,

>> Richard






-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com




      reply	other threads:[~2007-04-04 12:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-30  8:52 [RFC] Solving ipkg-utils issues Paul Sokolovsky
2007-03-30  9:02 ` Koen Kooi
2007-03-30  9:12   ` Paul Sokolovsky
2007-03-30  9:50 ` Richard Purdie
2007-03-30 10:06   ` Koen Kooi
2007-03-30 13:28   ` Paul Sokolovsky
2007-04-04 12:38     ` Paul Sokolovsky [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=612419699.20070404153815@gmail.com \
    --to=pmiscml@gmail.com \
    --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