<div class="gmail_quote">On Thu, Dec 15, 2011 at 11:11, Phil Blundell <span dir="ltr"><<a href="mailto:philb@gnu.org">philb@gnu.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Thu, 2011-12-15 at 13:08 +0000, Otavio Salvador wrote:<br>
> There was a 'dropbear-systemd' binary package on meta-oe versioned as<br>
> 'v1' and it has been merged on dropbear's bbappend; to fix the upgrade<br>
> path for the dropbear-systemd package on meta-oe we need to bump epoch<br>
> and to avoid messing it up this needs to go into OE-Core.<br>
<br>
</div>If it's just a single output binary at issue then setting PKGE for that<br>
one package would be less disruptive. I must admit I don't fully<br>
understand why this needs to be in oe-core at all though: what exactly<br>
is the "messing up" that would happen otherwise?<br></blockquote><div><br></div><div>I didn't know about PKGE; this works for this case :-D</div><div><br></div><div>Richard, please ignore this patch!</div><div>
</div></div>-- <br>Otavio Salvador O.S. Systems<br>E-mail: <a href="mailto:otavio@ossystems.com.br" target="_blank">otavio@ossystems.com.br</a> <a href="http://www.ossystems.com.br" target="_blank">http://www.ossystems.com.br</a><br>
Mobile: +55 53 9981-7854 <a href="http://projetos.ossystems.com.br" target="_blank">http://projetos.ossystems.com.br</a><br><br>