From: Martin Jansa <martin.jansa@gmail.com>
To: Javier Viguera <javier.viguera@digi.com>
Cc: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-networking][dylan][PATCH] vsftpd: fix compile-time dependence
Date: Thu, 1 Aug 2013 16:08:27 +0200 [thread overview]
Message-ID: <20130801140827.GQ3280@jama> (raw)
In-Reply-To: <51FA6846.1070006@digi.com>
[-- Attachment #1: Type: text/plain, Size: 2596 bytes --]
On Thu, Aug 01, 2013 at 03:53:10PM +0200, Javier Viguera wrote:
> Hi Martin,
>
> I just subscribed to the list so I didn't know it was already fixed.
>
> Anyway:
>
> # git branch -a --contains 46354a697c18a64c5836159adf8dbd92e6547e85
>
> shows that it's only fixed on *master*.
>
> I was bitten by this using stable dylan branches, that's why my patch
> was sent to apply on dylan.
Backports for dylan need to be marked as such (see README in root of
meta-oe).
> Could this fix be backported to dylan?
It's already in my branch with fixes for backport to dylan
http://git.openembedded.org/meta-openembedded-contrib/log/?h=jansa/dylan-backports
>
> -
> Regards,
>
> Javier Viguera
>
>
> On 01/08/13 15:47, Martin Jansa wrote:
> > On Thu, Aug 01, 2013 at 03:39:01PM +0200, Javier Viguera wrote:
> >> vsftpd links with openssl libraries (libssl and libcrypto) so there is a
> >> compile-time dependence on openssl package.
> >>
> >> Signed-off-by: Javier Viguera <javier.viguera@digi.com>
> >> ---
> >> meta-networking/recipes-daemons/vsftpd/vsftpd_2.3.5.bb | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/meta-networking/recipes-daemons/vsftpd/vsftpd_2.3.5.bb b/meta-networking/recipes-daemons/vsftpd/vsftpd_2.3.5.bb
> >> index c02ee9c..f146910 100644
> >> --- a/meta-networking/recipes-daemons/vsftpd/vsftpd_2.3.5.bb
> >> +++ b/meta-networking/recipes-daemons/vsftpd/vsftpd_2.3.5.bb
> >> @@ -4,7 +4,7 @@ SECTION = "network"
> >> LICENSE = "GPLv2"
> >> LIC_FILES_CHKSUM = "file://COPYING;md5=a6067ad950b28336613aed9dd47b1271"
> >>
> >> -DEPENDS = "libcap"
> >> +DEPENDS = "libcap openssl"
> >>
> >
> > It was fixed a month ago:
> >
> > commit 46354a697c18a64c5836159adf8dbd92e6547e85
> > Author: Martin Jansa <martin.jansa@gmail.com>
> > Date: Tue Jul 2 20:31:56 2013 +0200
> >
> > vsftpd: add missing dependency on openssl
> >
> > And current vsftpd is 3.0.0:
> >
> > commit 441502b68d03a4ce7796436a53c5e95399724ad2
> > Author: Roy.Li <rongqing.li@windriver.com>
> > Date: Fri Jul 19 10:19:25 2013 +0800
> >
> > Upgrade vsftpd to 3.0.0
> >
> >
> >> SRC_URI = "https://security.appspot.com/downloads/vsftpd-${PV}.tar.gz \
> >> file://makefile-destdir.patch \
> >> _______________________________________________
> >> 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: 205 bytes --]
prev parent reply other threads:[~2013-08-01 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 13:39 [meta-networking][dylan][PATCH] vsftpd: fix compile-time dependence Javier Viguera
2013-08-01 13:47 ` Martin Jansa
2013-08-01 13:53 ` Javier Viguera
2013-08-01 14:08 ` Martin Jansa [this message]
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=20130801140827.GQ3280@jama \
--to=martin.jansa@gmail.com \
--cc=javier.viguera@digi.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 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.