From: "Khem Raj" <raj.khem@gmail.com>
To: "Andreas Müller" <schnitzeltony@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [PATCH] networkmanager-openvpn: Fix packageing
Date: Wed, 7 Apr 2021 15:49:16 -0700 [thread overview]
Message-ID: <CAMKF1srYzaAF4zkGv0cz4k+Tt6LMv4-V0AhzeiqNsk5=NFtMaQ@mail.gmail.com> (raw)
In-Reply-To: <CALbNGRSTsAjv017jex=h0T8iZPWwHiAQ6j+h1LHyO4k+Z4SkNQ@mail.gmail.com>
yeah, it would be good, if you rebased your series on latest master or
master-next and resend it to avoid any rebasing mishaps.
On Wed, Apr 7, 2021 at 3:46 PM Andreas Müller <schnitzeltony@gmail.com> wrote:
>
> On Thu, Apr 8, 2021 at 12:26 AM Khem Raj <raj.khem@gmail.com> wrote:
> >
> > On Wed, Apr 7, 2021 at 3:18 PM Andreas Müller <schnitzeltony@gmail.com> wrote:
> > >
> > > Recent upgrade introduced:
> > > | ERROR: networkmanager-openvpn-1.8.14-r0 do_package: QA Issue: networkmanager-openvpn: Files/directories were installed but not shipped in any package:
> > > | /usr/share/metainfo
> > > | /usr/share/metainfo/network-manager-openvpn.metainfo.xml
> > >
> >
> > I wonder why my world build missed this. Is there any setting you are
> > use where this is triggered.
> I wondered either :) My guess was: I am not on the very very latest
> master of oe-core - maybe ${datadir}/metainfo was added to
> bitbake.conf meanwhile
>
> So before checking I decided to send this just in case openvpn-1.8.14
> becomes a candidate on elder branches: it is prepared to merge back.
>
> Andreas
next prev parent reply other threads:[~2021-04-07 22:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 22:18 [PATCH 1/6] mousepad: upgrade 0.5.3 -> 0.5.4 Andreas Müller
2021-04-07 22:18 ` [PATCH] networkmanager-openvpn: Fix packageing Andreas Müller
2021-04-07 22:26 ` [oe] " Khem Raj
2021-04-07 22:32 ` Martin Jansa
2021-04-07 22:40 ` Khem Raj
2021-04-07 22:46 ` Andreas Müller
2021-04-07 22:49 ` Khem Raj [this message]
2021-04-07 22:18 ` [PATCH 2/6] xfce4-battery-plugin: upgrade 1.1.3 -> 1.1.4 Andreas Müller
2021-04-07 22:18 ` [PATCH 3/6] gigolo: upgrade 0.5.1 -> 0.5.2 Andreas Müller
2021-04-07 22:18 ` [PATCH 4/6] thunar: upgrade 4.16.4 -> 4.16.6 Andreas Müller
2021-04-07 22:18 ` [PATCH 5/6] fluidsynth: upgrade 2.1.7 -> 2.2.0 Andreas Müller
2021-04-07 22:18 ` [PATCH 6/6] poppler: upgrade 21.03.0 -> 21.04.0 Andreas Müller
[not found] ` <1673B361F4D94ACE.4742@lists.openembedded.org>
2021-04-08 7:17 ` [oe] [PATCH 5/6] fluidsynth: upgrade 2.1.7 -> 2.2.0 Andreas Müller
2021-04-08 14:42 ` Khem Raj
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='CAMKF1srYzaAF4zkGv0cz4k+Tt6LMv4-V0AhzeiqNsk5=NFtMaQ@mail.gmail.com' \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=schnitzeltony@gmail.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 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.