From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Kevin Strasser <kevin.strasser@linux.intel.com>,
Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: [meta-oe][WIP][PATCH 7/8] ajenti: Bump SRCREV a bit got get revision included in some branch
Date: Thu, 2 Jan 2014 08:57:24 +0100 [thread overview]
Message-ID: <20140102075724.GC3717@jama> (raw)
In-Reply-To: <1388581046-8713-7-git-send-email-Martin.Jansa@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1772 bytes --]
On Wed, Jan 01, 2014 at 01:57:25PM +0100, Martin Jansa wrote:
> * old c08fb4da65923aebd09116750a1f43f13b98a51a exists only in 0.6.2 tag and latest
> bitbake refuses to fetch it
>
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
> meta-webserver/recipes-webadmin/ajenti/ajenti_git.bb | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/meta-webserver/recipes-webadmin/ajenti/ajenti_git.bb b/meta-webserver/recipes-webadmin/ajenti/ajenti_git.bb
> index 83e92f6..f499339 100644
> --- a/meta-webserver/recipes-webadmin/ajenti/ajenti_git.bb
> +++ b/meta-webserver/recipes-webadmin/ajenti/ajenti_git.bb
> @@ -9,7 +9,7 @@ DEPENDS += "python-pyopenssl python-lxml python-gevent python-greenlet \
>
> PV = "0.6.2+git${SRCPV}"
>
> -SRC_URI = "git://github.com/Eugeny/ajenti.git \
> +SRC_URI = "git://github.com/Eugeny/ajenti.git;branch=ajenti-0.6.x \
> file://0001-setup.py-remove-extra-data-files.patch \
> file://0002-plugins-hddstat-fix-disk-usage-check-to-work-with-bu.patch \
> file://0003-plugins-sysload-fix-to-work-with-busybox.patch \
> @@ -22,8 +22,7 @@ SRC_URI = "git://github.com/Eugeny/ajenti.git \
> DISTRO_FILES = "file://distro-detection-openembedded.patch \
> file://distributor-logo-openembedded.png"
This one wasn't merged, because the patches need to be rebased, is there
someone who cares about ajenti and will test it properly in runtime?
Paul? Kevin?
>
> -# Corresponds to the 0.6.2 tag
> -SRCREV = "c08fb4da65923aebd09116750a1f43f13b98a51a"
> +SRCREV = "411acfd0b96ad7a9bd79b3bdc1f9eef394f62198"
>
> S = "${WORKDIR}/git"
>
> --
> 1.8.4.3
>
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2014-01-02 7:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-01 12:57 [meta-oe][WIP][PATCH 1/8] ktap: upgrade to 0.4 Martin Jansa
2014-01-01 12:57 ` [meta-oe][WIP][PATCH 2/8] qtserialport-e: Fix branch param Martin Jansa
2014-01-01 12:57 ` [meta-oe][WIP][PATCH 3/8] qconnman*: " Martin Jansa
2014-01-01 12:57 ` [meta-oe][WIP][PATCH 4/8] navit: Fix build with newer freetype Martin Jansa
2014-01-01 12:57 ` [meta-oe][WIP][PATCH 5/8] libssh: Fix branch param and set PV in recipe Martin Jansa
2014-01-01 12:57 ` [meta-oe][WIP][PATCH 6/8] freerdp: Fix branch param and set better " Martin Jansa
2014-01-01 12:57 ` [meta-oe][WIP][PATCH 7/8] ajenti: Bump SRCREV a bit got get revision included in some branch Martin Jansa
2014-01-02 7:57 ` Martin Jansa [this message]
2014-01-02 20:28 ` Paul Eggleton
2014-01-01 12:57 ` [meta-oe][WIP][PATCH 8/8] cloud9: Fix branch param Martin Jansa
2014-01-01 18:18 ` [meta-oe][WIP][PATCH 1/8] ktap: upgrade to 0.4 Anders Darander
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=20140102075724.GC3717@jama \
--to=martin.jansa@gmail.com \
--cc=kevin.strasser@linux.intel.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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