All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burton, Ross" <ross.burton@intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libical: upgrade to 3.0.5
Date: Tue, 23 Jul 2019 22:12:14 +0100	[thread overview]
Message-ID: <CAJTo0LaH+-poVSJw-DPup=z2_73BLkMYfgLcCrKLujcknTwN6Q@mail.gmail.com> (raw)
In-Reply-To: <CAMKF1srgRYSK9DXBVet23Re8fpwxbrh38q4sKYG2eE-jF-vz1w@mail.gmail.com>

The last release of Orage was four years ago: I suggest removing that
from meta-xfce instead of keeping everyone else using an old version
of libical.

Ross

On Tue, 23 Jul 2019 at 22:04, Khem Raj <raj.khem@gmail.com> wrote:
>
> this is causing a failure in meta-xfce
>
> https://errors.yoctoproject.org/Errors/Details/253910/
>
> On Mon, Jul 22, 2019 at 6:12 PM Khem Raj <raj.khem@gmail.com> wrote:
> >
> > On Mon, Jul 22, 2019 at 6:05 PM Mittal, Anuj <anuj.mittal@intel.com> wrote:
> > >
> > > On Mon, 2019-07-22 at 17:59 -0700, Khem Raj wrote:
> > > > On Mon, Jul 22, 2019 at 4:17 PM Mittal, Anuj <anuj.mittal@intel.com>
> > > > wrote:
> > > > > On Mon, 2019-07-22 at 15:48 +0100, Ross Burton wrote:
> > > > > > -LICENSE = "LGPLv2.1 | MPL-1.0"
> > > >
> > > > this should be MPL-2.0 | LGPL-2.1
> > > >
> > > > > > -LIC_FILES_CHKSUM =
> > > > > > "file://COPYING;md5=d4fc58309d8ed46587ac63bb449d82f8 \
> > > > > > -
> > > > > > file://LICENSE;md5=d1a0891cd3e582b3e2ec8fe63badbbb6"
> > > > > > +LICENSE = "LGPLv2.1 | MPL-2"
> > > > > > +LIC_FILES_CHKSUM =
> > > > > > "file://LICENSE;md5=1910a2a76ddf6a9ba369182494170d87 \
> > > > > > +
> > > > > > file://LICENSE.LGPL21.txt;md5=933adb561f159e7c3da079536f0ed871 \
> > > > > > +
> > > > > > file://LICENSE.MPL2.txt;md5=9741c346eef56131163e13b9db1241b3"
> > > > >
> > > > > Should this be MPL-2.0 instead? This is causing warnings:
> > > >
> > > > the license is MPL-2.0 but the license file name is MPL2.txt so this
> > > > seems fine.
> > >
> > > I meant the field in LICENSE. Quoted the wrong text.
> >
> > reply quote confused me. yes it is wrong. It should be MPL-2.0
> >
> > >
> > > Thanks.


  reply	other threads:[~2019-07-23 21:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22 14:48 [PATCH] libical: upgrade to 3.0.5 Ross Burton
2019-07-22 23:17 ` Mittal, Anuj
2019-07-23  0:59   ` Khem Raj
2019-07-23  1:05     ` Mittal, Anuj
2019-07-23  1:12       ` Khem Raj
2019-07-23 21:03         ` Khem Raj
2019-07-23 21:12           ` Burton, Ross [this message]
2019-07-23 21:15             ` Khem Raj
2019-07-23 21:36               ` 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='CAJTo0LaH+-poVSJw-DPup=z2_73BLkMYfgLcCrKLujcknTwN6Q@mail.gmail.com' \
    --to=ross.burton@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@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.