* [PATCH] dropbear: bump epoch to fix upgrade path in meta-oe @ 2011-12-15 13:08 Otavio Salvador 2011-12-15 13:11 ` Phil Blundell 0 siblings, 1 reply; 4+ messages in thread From: Otavio Salvador @ 2011-12-15 13:08 UTC (permalink / raw) To: openembedded-core 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. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> --- meta/recipes-core/dropbear/dropbear.inc | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/meta/recipes-core/dropbear/dropbear.inc b/meta/recipes-core/dropbear/dropbear.inc index 1894715..073ac13 100644 --- a/meta/recipes-core/dropbear/dropbear.inc +++ b/meta/recipes-core/dropbear/dropbear.inc @@ -11,6 +11,8 @@ DEPENDS = "zlib" RPROVIDES = "ssh sshd" DEPENDS += "${@base_contains('DISTRO_FEATURES', 'pam', 'libpam', '', d)}" +PE = "1" + SRC_URI = "http://matt.ucc.asn.au/dropbear/releases/dropbear-${PV}.tar.gz \ file://urandom-xauth-changes-to-options.h.patch \ file://dropbear-0.53.1-static_build_fix.patch \ -- 1.7.2.5 ^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH] dropbear: bump epoch to fix upgrade path in meta-oe 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 2011-12-15 13:14 ` Otavio Salvador 0 siblings, 1 reply; 4+ messages in thread From: Phil Blundell @ 2011-12-15 13:11 UTC (permalink / raw) To: Patches and discussions about the oe-core layer 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. ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] dropbear: bump epoch to fix upgrade path in meta-oe 2011-12-15 13:11 ` Phil Blundell @ 2011-12-15 13:14 ` Otavio Salvador 2011-12-15 13:45 ` Otavio Salvador 0 siblings, 1 reply; 4+ messages in thread From: Otavio Salvador @ 2011-12-15 13:14 UTC (permalink / raw) To: Patches and discussions about the oe-core layer [-- Attachment #1: Type: text/plain, Size: 993 bytes --] On Thu, Dec 15, 2011 at 11:11, Phil Blundell <philb@gnu.org> wrote: > 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? > I didn't know about PKGE; this works for this case :-D Richard, please ignore this patch! -- Otavio Salvador O.S. Systems E-mail: otavio@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br [-- Attachment #2: Type: text/html, Size: 1551 bytes --] ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] dropbear: bump epoch to fix upgrade path in meta-oe 2011-12-15 13:14 ` Otavio Salvador @ 2011-12-15 13:45 ` Otavio Salvador 0 siblings, 0 replies; 4+ messages in thread From: Otavio Salvador @ 2011-12-15 13:45 UTC (permalink / raw) To: Patches and discussions about the oe-core layer [-- Attachment #1: Type: text/plain, Size: 790 bytes --] On Thu, Dec 15, 2011 at 11:14, Otavio Salvador <otavio@ossystems.com.br>wrote: > On Thu, Dec 15, 2011 at 11:11, Phil Blundell <philb@gnu.org> wrote: >> >> 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? >> > > I didn't know about PKGE; this works for this case :-D > It seems setting: PKGE_${PN}-systemd = "1" in the bbappend doesn't work. Any clue? -- Otavio Salvador O.S. Systems E-mail: otavio@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br [-- Attachment #2: Type: text/html, Size: 1581 bytes --] ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-12-15 13:52 UTC | newest] Thread overview: 4+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 2011-12-15 13:14 ` Otavio Salvador 2011-12-15 13:45 ` Otavio Salvador
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.