All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
	Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com>
Subject: Re: [PATCH][meta-oe] libnotify: update to 0.7.8
Date: Tue, 23 Apr 2019 15:55:28 +0200	[thread overview]
Message-ID: <CANNYZj9s4bvY8zQCdL9ionVNeed99w204XUat2G_TVVsoM73_w@mail.gmail.com> (raw)
In-Reply-To: <CAJTo0LZ6B3cRwnxskoLap6gRmyPKCcjhf9HxiLKKYU9KxiJFSw@mail.gmail.com>

I would need to see the patch-in-progress to make a meaningful comment.

Alex

On Tue, 23 Apr 2019 at 15:54, Burton, Ross <ross.burton@intel.com> wrote:
>
> CCing Alex who has been working on the gtk-doc/meson stuff a lot.
>
> Ross
>
> On Tue, 23 Apr 2019 at 14:50, Oleksandr Kravchuk
> <open.source@oleksandr-kravchuk.com> wrote:
> >
> > On 23/04/2019 13:59, Burton, Ross wrote:
> > > Fancy following this up with a Meson port?
> > >
> > > Ross
> > >
> > > On Mon, 22 Apr 2019 at 23:37, Oleksandr Kravchuk
> > > <open.source@oleksandr-kravchuk.com> wrote:
> > >> Signed-off-by: Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com>
> > >> ---
> > >>  .../libnotify/{libnotify_0.7.7.bb => libnotify_0.7.8.bb}      | 4 ++--
> > >>  1 file changed, 2 insertions(+), 2 deletions(-)
> > >>  rename meta/recipes-gnome/libnotify/{libnotify_0.7.7.bb => libnotify_0.7.8.bb} (80%)
> > >>
> > >> diff --git a/meta/recipes-gnome/libnotify/libnotify_0.7.7.bb b/meta/recipes-gnome/libnotify/libnotify_0.7.8.bb
> > >> similarity index 80%
> > >> rename from meta/recipes-gnome/libnotify/libnotify_0.7.7.bb
> > >> rename to meta/recipes-gnome/libnotify/libnotify_0.7.8.bb
> > >> index 6c299bc175..82c137ca33 100644
> > >> --- a/meta/recipes-gnome/libnotify/libnotify_0.7.7.bb
> > >> +++ b/meta/recipes-gnome/libnotify/libnotify_0.7.8.bb
> > >> @@ -10,8 +10,8 @@ inherit gnomebase gtk-doc distro_features_check gobject-introspection
> > >>  # depends on gtk+3
> > >>  ANY_OF_DISTRO_FEATURES = "${GTK3DISTROFEATURES}"
> > >>
> > >> -SRC_URI[archive.md5sum] = "e9d911f6a22435e0b922f2fe71212b59"
> > >> -SRC_URI[archive.sha256sum] = "9cb4ce315b2655860c524d46b56010874214ec27e854086c1a1d0260137efc04"
> > >> +SRC_URI[archive.md5sum] = "babb4b07b5f21bef42a386d3d7019599"
> > >> +SRC_URI[archive.sha256sum] = "69209e0b663776a00c7b6c0e560302a8dbf66b2551d55616304f240bba66e18c"
> > >>
> > >>  # there were times, we had two versions of libnotify (oe-core libnotify:0.6.x /
> > >>  # meta-gnome libnotify3: 0.7.x)
> > >> --
> > >> 2.17.1
> > >>
> > >> --
> > >> _______________________________________________
> > >> Openembedded-core mailing list
> > >> Openembedded-core@lists.openembedded.org
> > >> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> >
> > 2019-04-23 13:41:30,546:scangobj.py:execute_command:1200:WARNING:Running
> > scanner failed: [Errno 2] No such file or directory:
> > '/home/sashko/projects/yocto/open-embedded/build/tmp/work/i586-poky-linux/libnotify/0.7.8-r0/build/gtkdoc-qemuwrapper':
> > '/home/sashko/projects/yocto/open-embedded/build/tmp/work/i586-poky-linux/libnotify/0.7.8-r0/build/gtkdoc-qemuwrapper',
> > command:
> > /home/sashko/projects/yocto/open-embedded/build/tmp/work/i586-poky-linux/libnotify/0.7.8-r0/build/gtkdoc-qemuwrapper
> > ./libnotify-scan
> >
> > Is it worth fixing?
> >


      reply	other threads:[~2019-04-23 13:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-22 22:36 [PATCH][meta-oe] libnotify: update to 0.7.8 Oleksandr Kravchuk
2019-04-23 11:59 ` Burton, Ross
2019-04-23 13:44   ` Oleksandr Kravchuk
2019-04-23 13:53     ` Burton, Ross
2019-04-23 13:55       ` Alexander Kanavin [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=CANNYZj9s4bvY8zQCdL9ionVNeed99w204XUat2G_TVVsoM73_w@mail.gmail.com \
    --to=alex.kanavin@gmail.com \
    --cc=open.source@oleksandr-kravchuk.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@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 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.