Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Carsten Haitzler (The Rasterman) <raster@rasterman.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: reverting some csets that kill package upgrade paths
Date: Sun, 26 Apr 2009 11:59:41 +1000	[thread overview]
Message-ID: <20090426115941.364c5618.raster@rasterman.com> (raw)
In-Reply-To: <200904252356.18619.marcin@juszkiewicz.com.pl>

On Sat, 25 Apr 2009 23:56:17 +0200 Marcin Juszkiewicz
<marcin@juszkiewicz.com.pl> said:

> Dnia sobota, 25 kwietnia 2009 o 23:37:14 Koen Kooi napisał(a):
> > On 25-04-09 23:18, Marcin Juszkiewicz wrote:
> 
> > >> So suddenly the library packages (or plugin packages, but no
> > >> difference in this case) have a new name, but don't set RPROVIDES
> > >> or RREPLACES to the old packages containing *the same files*.
> 
> > > Provide a patch which will add such ones?
> 
> > Well, I verified that e-wm started in beagleboard-demo-image in a
> > build from scratch and in an upgraded images 2 days ago, so any
> > problems those 3 patches were supposed to fix weren't that critical.
> > *After* those 3 patches I have a broken build and broken upgrade
> > paths, while *before* things were working for me.
> 
> > I actually tested the changes I made for build from scratch as well
> > as upgrading an image. While upgrading I actually noticed the ecore
> > bug which was present. I could have revert the SRCREV bump, but I
> > went ahead and fixed it. 
> 
> But origin/org.openembedded.dev is not koen/org.openembedded.dev - you 
> are *not the only user* of that branch (asterisks added because it looks 
> like you like them). And we have a weekend now - you should wait and 
> check what would other say about those 3 changsets. As I said: 
> origin/org.openembedded.dev is not your sandbox - we also like to play 
> there.

true - not the onyl user.. but if it breaks for him.. that is a break - and
something to fix. if changes broke something - fix the changes or revert. i
guess this thread is about screaming "revert!" in  hopes that the changes will
get fixed asap before a revert actually happens (and you start some
commit/revert war) :)

-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    raster@rasterman.com




  reply	other threads:[~2009-04-26  2:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-24 17:32 reverting some csets that kill package upgrade paths Koen Kooi
2009-04-24 17:55 ` Philip Balister
2009-04-24 19:03   ` Koen Kooi
2009-04-24 19:14     ` Tom Rini
2009-04-24 19:24       ` Tom Rini
2009-04-24 19:47         ` Koen Kooi
2009-04-24 19:39       ` Koen Kooi
2009-04-24 19:32     ` Tom Rini
2009-04-24 19:48       ` Koen Kooi
2009-04-24 19:53       ` Koen Kooi
2009-04-25 20:40         ` Marcin Juszkiewicz
2009-04-24 20:40       ` Philip Balister
2009-04-27  3:22         ` Tom Rini
2009-04-25 21:18 ` Marcin Juszkiewicz
2009-04-25 21:37   ` Koen Kooi
2009-04-25 21:56     ` Marcin Juszkiewicz
2009-04-26  1:59       ` Carsten Haitzler [this message]
2009-04-26  9:27   ` Koen Kooi
2009-04-27  8:46     ` Marcin Juszkiewicz
2009-04-26  1:53 ` Carsten Haitzler
  -- strict thread matches above, loose matches on Subject: below --
2009-04-24 17:23 Koen Kooi

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=20090426115941.364c5618.raster@rasterman.com \
    --to=raster@rasterman.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