Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] Koen Kooi : opkg-native: bump to r522 to get a fix to remove duplicate messages from do_rootfs logs
Date: Thu, 18 Feb 2010 10:09:40 +0100	[thread overview]
Message-ID: <hlj04i$926$1@ger.gmane.org> (raw)
In-Reply-To: <1266443018.5691.42.camel@trini-m4400>

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

On 17-02-10 22:43, Tom Rini wrote:
> On Wed, 2010-02-17 at 22:22 +0100, Koen Kooi wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 17-02-10 21:18, Tom Rini wrote:
>>> On Wed, 2010-02-17 at 08:59 +0000, git version control wrote:
>>>> Module: openembedded.git
>>>> Branch: org.openembedded.dev
>>>> Commit: 74501117c261f743c76ae3c2988cbcfdc141cf3a
>>>> URL:    http://gitweb.openembedded.net/?p=openembedded.git&a=commit;h=74501117c261f743c76ae3c2988cbcfdc141cf3a
>>>>
>>>> Author: Koen Kooi <koen@openembedded.org>
>>>> Date:   Tue Feb 16 13:08:53 2010 +0100
>>>>
>>>> opkg-native: bump to r522 to get a fix to remove duplicate messages from do_rootfs logs
>>>
>>> I'd like to RFC that we do something like:
>>> OPKGREV ?= "522"
>>> SRCREV_pn-opkg ?= "${OPKGREV}"
>>> SRCREV_pn-opkg-native ?= "${OPKGREV}"
>>> SRCREV_pn-opkg-sdk ?= "${OPKGREV}"
>>>
>>> And if -nogpg or what have you is broken, it either gets fixed or the
>>> distribution takes advantage of that ?=. 
>>
>> I haven't been able to properly test a target opkg yet, so no bump for
>> that. Unless people would like broken opkg binaries on their target ;)
> 
> Seriously tho, this isn't the first or fifth time the revs have gotten
> wildly out of sync.  I'm suggesting that we want to keep them together,
> intentionally.  We don't say we have different versions of gcc or bison
> between native and target.  This is possibly even more important to make
> sure all of the operations are right, all around.

Testing various things on target (upgrading >500 packages on one,
installing >1k packages on another) seems to show no (new) errors. I'll
do some more testing and bump the rev if things look OK.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLfQPTMkyGM64RGpERAvu/AJ9S6DSMrLKrO4BNlRhU4/n4gCGcTQCfRLOw
P88zmIMjuH0spzxXj3meKGA=
=gnRq
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-02-18  9:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Nhfko-0005KL-8Z@melo.openembedded.org>
2010-02-17 20:18 ` [oe-commits] Koen Kooi : opkg-native: bump to r522 to get a fix to remove duplicate messages from do_rootfs logs Tom Rini
2010-02-17 21:22   ` Koen Kooi
2010-02-17 21:43     ` Tom Rini
2010-02-18  9:09       ` Koen Kooi [this message]
2010-02-18 22:50         ` Graham Gower
2010-02-23 12:10     ` Florian Boor

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='hlj04i$926$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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