From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-webserver][PATCH 2/2] nginx: add stable version 1.8.1 as alternative to the mainline version 1.9.x
Date: Thu, 3 Mar 2016 10:07:34 +0100 [thread overview]
Message-ID: <20160303090734.GB2569@jama> (raw)
In-Reply-To: <1455622845-14510-3-git-send-email-pascal.bach@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 2307 bytes --]
On Tue, Feb 16, 2016 at 12:40:45PM +0100, Pascal Bach wrote:
> The 1.8 branch is the current stable branch of nginx.
> This means the branch doesn't get new features, but is still supported with bugfixes.
>
> Depending on the use case it is more suitable to use on an embedded device
> than the 1.9 branch which adds new features with every release.
NOTE: recipe nginx-1.8.1-r0: task do_configure: Started
ERROR: nginx-1.8.1-r0 do_configure: QA Issue: nginx: The
LIC_FILES_CHKSUM does not match for
file://LICENSE;md5=0bb58ed0dfd4f5dbece3b52aba79f023
nginx: The new md5 checksum is 3845852aedfa8d6d7765f55d06cc3ebd
nginx: Check if the license information has changed in
/home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5te-oe-linux-gnueabi/nginx/1.8.1-r0/nginx-1.8.1/LICENSE
to verify that the LICENSE value "BSD-2-Clause" remains valid
[license-checksum]
ERROR: nginx-1.8.1-r0 do_configure: Fatal QA errors found, failing task.
ERROR: nginx-1.8.1-r0 do_configure: Function failed: do_qa_configure
ERROR: Logfile of failure stored in:
/home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5te-oe-linux-gnueabi/nginx/1.8.1-r0/temp/log.do_configure.26965
NOTE: recipe nginx-1.8.1-r0: task do_configure: Failed
ERROR: Task 21522
(/home/jenkins/oe/world/shr-core/meta-openembedded/meta-webserver/recipes-httpd/nginx/nginx_1.8.1.bb,
do_configure) failed with exit code '1'
> ---
> meta-webserver/recipes-httpd/nginx/nginx_1.8.1.bb | 4 ++++
> 1 file changed, 4 insertions(+)
> create mode 100644 meta-webserver/recipes-httpd/nginx/nginx_1.8.1.bb
>
> diff --git a/meta-webserver/recipes-httpd/nginx/nginx_1.8.1.bb b/meta-webserver/recipes-httpd/nginx/nginx_1.8.1.bb
> new file mode 100644
> index 0000000..ec3aef2
> --- /dev/null
> +++ b/meta-webserver/recipes-httpd/nginx/nginx_1.8.1.bb
> @@ -0,0 +1,4 @@
> +require nginx.inc
> +
> +SRC_URI[md5sum] = "2e91695074dbdfbf1bcec0ada9fda462"
> +SRC_URI[sha256sum] = "8f4b3c630966c044ec72715754334d1fdf741caa1d5795fb4646c27d09f797b7"
> --
> 2.1.4
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2016-03-03 9:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 11:40 [meta-webserver][PATCH 0/2] nginx: make mainline and stable version available Pascal Bach
2016-02-16 11:40 ` [meta-webserver][PATCH 1/2] nginx: split parts out of the recipe into nginx.inc Pascal Bach
2016-02-16 11:40 ` [meta-webserver][PATCH 2/2] nginx: add stable version 1.8.1 as alternative to the mainline version 1.9.x Pascal Bach
2016-03-03 9:07 ` Martin Jansa [this message]
2016-02-16 11:51 ` [meta-webserver][PATCH 0/2] nginx: make mainline and stable version available Otavio Salvador
2016-02-17 14:24 ` Pascal Bach
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=20160303090734.GB2569@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@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