From: Joe MacDonald <Joe_MacDonald@mentor.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-networking][PATCH v2] Samba: use built-in libtevent
Date: Fri, 24 Feb 2017 22:42:18 -0500 [thread overview]
Message-ID: <20170225034218.GK8436@mentor.com> (raw)
In-Reply-To: <f9cd7853-8802-4b7d-a16c-01d35461b7e5@email.android.com>
[-- Attachment #1: Type: text/plain, Size: 3094 bytes --]
[Re: [oe] [meta-networking][PATCH v2] Samba: use built-in libtevent] On 17.02.24 (Fri 22:33) MacDonald, Joe wrote:
> Yeah. If you're near a keyboard, please go ahead and revert otherwise
> I'll get to in later on tonight.
Bah. This isn't just the revert I'd been hoping for. Samba, as usual,
is a pain. My builds without gvfs are still happy, but reverting the
patch breaks all builds, AFAICT, so I'm going to leave this alone until
I sort out what the correct repair job looks like here. Unless someone
comes up with a solution before I get to it. The weekend is rather full
right now, I'm afraid.
-J.
>
> On Feb 24, 2017 5:01 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
> Joe?
>
> On Fri, Feb 24, 2017 at 10:37 PM, Andreas Müller <schnitzeltony@googlemail.com<mailto:schnitzeltony@googlemail.com>> wrote:
> On Mon, Feb 20, 2017 at 5:08 PM, Szombathelyi György <gyurco@freemail.hu<mailto:gyurco@freemail.hu>> wrote:
> > Hi,
> >
> > If there's no solution to resolve the conflict between the internal tevent and the external one, then maybe putting the libtevent-internal.h from the external lib to the samba tree would be a way to go.
> >
> > Br,
> > György
> > -------- Eredeti levél --------
> > Feladó: Andreas Müller <schnitzeltony@googlemail.com<http://googlemail.com>>
> > Dátum: 2017 február 20 12:52:18
> > Tárgy: Re: [oe] [meta-networking][PATCH v2] Samba: use built-in libtevent
> > Címzett: openembedded-devel@lists.openembedded.org<http://lists.openembedded.org> <openembedded-devel@lists.openembedded.org<http://lists.openembedded.org>>
> >
> > > In last build I've noticed only this new issue related to samba:
> > >
> > > ctdb-2.5.6: ctdb rdepends on samba, but it isn't a build dependency, missing samba in DEPENDS or PACKAGECONFIG? [build-deps]
> > >
> > > Maybe this dependency was created from samba being libldb provider in
> > > this build.
> > >
> > > gvfs and whole meta-gnome layers is still included in my world, maybe it
> > > didn't fail because some gvfs dependency was already failing or one of
> > > samba related changes in master-next is fixing this one.
> > >
> > Some background: During last weekend I prepared a series based on
> > master-next unblacklisting. First target is to build a xfce-image
> > again [1]. Last step yesterday evening should be rebasing against
> > latest master-next and run a test build. That failed for gvfs - so I
> > stopped sending stuff. Now I know why gvfs fails...
> >
> > How do we proceed with this patch?
> >
> > [1] https://github.com/schnitzeltony/meta-openembedded/tree/work-2017-02
> >
> Just notices that this patch made it into master breaking at least gvfs. Revert?
>
> Andreas
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org<mailto:Openembedded-devel@lists.openembedded.org>
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>
>
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
next prev parent reply other threads:[~2017-02-25 3:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 22:33 [meta-networking][PATCH v2] Samba: use built-in libtevent MacDonald, Joe
2017-02-25 3:42 ` Joe MacDonald [this message]
2017-02-25 8:20 ` Martin Jansa
2017-02-27 13:29 ` Joe MacDonald
-- strict thread matches above, loose matches on Subject: below --
2017-02-11 14:17 Gyorgy Szombathelyi
2017-02-20 12:04 ` Andreas Müller
2017-02-20 12:17 ` Martin Jansa
2017-02-20 12:51 ` Andreas Müller
2017-02-20 13:15 ` Martin Jansa
2017-02-20 16:08 ` Szombathelyi György
2017-02-24 21:37 ` Andreas Müller
2017-02-24 22:00 ` Martin Jansa
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=20170225034218.GK8436@mentor.com \
--to=joe_macdonald@mentor.com \
--cc=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