From: tom.zanussi@intel.com
To: openembedded-core@lists.openembedded.org, martin.jansa@gmail.com
Subject: [PATCH 0/1] lttng PE bump
Date: Wed, 16 Jan 2013 09:37:18 -0600 [thread overview]
Message-ID: <cover.1358350412.git.tom.zanussi@intel.com> (raw)
From: Tom Zanussi <tom.zanussi@intel.com>
This fixes the problem reported by Martin Jansa, which is due to a missing PE
in the new lttng-ust recipe when it was renamed:
ERROR: Package version for package lttng-ust-dbg went backwards which would break package feeds from (1:0.16-r1 to 0:2.1.0-r0)
ERROR: Package version for package lttng-ust-staticdev went backwards which would break package feeds from (1:0.16-r1 to 0:2.1.0-r0)
ERROR: Package version for package lttng-ust-dev went backwards which would break package feeds from (1:0.16-r1 to 0:2.1.0-r0)
ERROR: Package version for package lttng-ust-doc went backwards which would break package feeds from (1:0.16-r1 to 0:2.1.0-r0)
ERROR: Package version for package lttng-ust-locale went backwards which would break package feeds from (1:0.16-r1 to 0:2.1.0-r0)
ERROR: Package version for package lttng-ust went backwards which would break package feeds from (1:0.16-r1 to 0:2.1.0-r0)
The following changes since commit 7bfb98568a1d7ba8dbd95332d65cd19faec6c725:
bitbake: hig.py: refactor into individual components (2013-01-16 12:51:33 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib.git tzanussi/lttng-pe-bump
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=tzanussi/lttng-pe-bump
Tom Zanussi (1):
lttng-ust: bump PE
meta/recipes-kernel/lttng/lttng-ust_2.1.0.bb | 1 +
1 file changed, 1 insertion(+)
--
1.7.11.4
next reply other threads:[~2013-01-16 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 15:37 tom.zanussi [this message]
2013-01-16 15:37 ` [PATCH 1/1] lttng-ust: bump PE tom.zanussi
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=cover.1358350412.git.tom.zanussi@intel.com \
--to=tom.zanussi@intel.com \
--cc=martin.jansa@gmail.com \
--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