Re: reverting some csets that kill package upgrade paths

[Koen Kooi <k.kooi@student.utwente.nl>]

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*. This means
>> that 'opkg install<foo>' or 'opkg upgrade' doesn't work anymore. It
>> will abort saying to package<foo>  wants to overwrite files belonging
>> to<bar>. Depending on the way you build your images in OE, your
>> build will break.
>
> 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. So you can see why I get annoyed that a few days later it 
gets broken again by the same person.

regards,

Koen