From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] dropbear: bump epoch to fix upgrade path in meta-oe
Date: Thu, 15 Dec 2011 13:11:37 +0000 [thread overview]
Message-ID: <1323954698.24417.211.camel@phil-desktop> (raw)
In-Reply-To: <1323954515-15604-1-git-send-email-otavio@ossystems.com.br>
On Thu, 2011-12-15 at 13:08 +0000, Otavio Salvador wrote:
> There was a 'dropbear-systemd' binary package on meta-oe versioned as
> 'v1' and it has been merged on dropbear's bbappend; to fix the upgrade
> path for the dropbear-systemd package on meta-oe we need to bump epoch
> and to avoid messing it up this needs to go into OE-Core.
If it's just a single output binary at issue then setting PKGE for that
one package would be less disruptive. I must admit I don't fully
understand why this needs to be in oe-core at all though: what exactly
is the "messing up" that would happen otherwise?
p.
next prev parent reply other threads:[~2011-12-15 13:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 13:08 [PATCH] dropbear: bump epoch to fix upgrade path in meta-oe Otavio Salvador
2011-12-15 13:11 ` Phil Blundell [this message]
2011-12-15 13:14 ` Otavio Salvador
2011-12-15 13:45 ` Otavio Salvador
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=1323954698.24417.211.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-core@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