All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Koen Kooi <openembedded-devel@lists.openembedded.org>
Subject: Re: [RFC] Solving ipkg-utils issues
Date: Fri, 30 Mar 2007 12:12:21 +0300	[thread overview]
Message-ID: <7207965.20070330121221@gmail.com> (raw)
In-Reply-To: <460CD224.7050005@dominion.kabel.utwente.nl>

Hello Koen,

Friday, March 30, 2007, 12:02:28 PM, you wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1

> Paul Sokolovsky schreef:
>> Hello openembedded-devel,
>> 
>>   For quite some time bugs in ipkg-utils package (mostly in
>> ipkg-make-index tool) plagued image creation process in OE. Many of
>> them are known to old-time developers, and being (manually) worked
>> around. I was working on resolving them for some time, and guess now
>> finally have both clear picture of the issues and their interaction
>> with each other, and fixes for them. So, I would like to push these
>> fixes to mainline, and am opening this thread for review of
>> them, as well as to collect any other concerns about ipkg-utils.
>> 
>>   In my list, there're 3 major issues:
>> 
>> 1. Broken version comparison logic in ipkg-utils (note that this is
>> exactly ipkg-utils issues, nether bitbake nor ipkg is affected).
>> 
>> 2. Inability of ipkg-make-index to detect packages which were updated,
>> while version stays the same.

> It's hard to distinguish between 'update' and 'data corruption' without knowing if someone
> rebuilt the package.

  Yeah, so I followed suggestion to track ipk timestamps. But we
indeed have overloaded Packages files, and this timestamp is clearly
ipkg-make-index internal thing, so I did it a-la Packages.files,
introduced Packages.timestamps for that.

  But this will be second patch, and I'd like to have it step by step,
with interim testing, because interaction of issues can be indeed pretty bad.

> regards,

> Koen

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




  reply	other threads:[~2007-03-30  9:12 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 [this message]
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

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=7207965.20070330121221@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 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.