Re: [yocto] [OE-core] [prelink-cross] Bug 13529 add SPDX identifier

[Yann CARDAILLAC]

On Mon, Oct 21, 2019 at 4:35 PM Mark Hatle 
wrote:

> On 10/21/19 4:43 AM, Yann CARDAILLAC wrote:
> > Hi Mark Hatle, Jakub Jelinek,
>
> Jakub is no longer supporting this code, but he may have valuable insights
> into
> licensing.
>
> > I'm currently beginning the work on bug 13529:
> >
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=13529
> >
> > The purpose is to add SPDX identifier to scripts and sources.
> >
> > Most of the sources have licences on the sources, however some of them
> don't,
> > and I've question about others :
> >
> > - src/sha.c do not shall it be GPLV2-or-later as most of the other?
>
> /* sha.c - Functions to compute the SHA1 hash (message-digest) of files
>or blocks of memory.  Complies to the NIST specification FIPS-180-1.
>
>Copyright (C) 2000, 2001, 2003 Scott G. Miller
>
>Credits:
>   Robert Klep   -- Expansion function fix
>NOTE: The canonical source of this file is maintained in GNU coreutils.
> */
>
> The last line is the key.  This apparently came from GNU coreutils.
>
> From the SCM logs, sha.c was introduced in approx 2003-07-01 from what it
> looks
> like.  So it's a pretty old version.  You will need to do some detective
> work,
> and find older versions of coreutils until you find the one that
> corresponds to
> the code that was checked in.  Start back in 2003 and work backwards as
> necessary.  (The version that matches to the original 2003-07-01 should be
> the
> reasonable license to use.)
>

Ok I found it ! https://github.com/coreutils/coreutils/blob/v4.5.8/lib/sha.c

from : https://github.com/coreutils/coreutils/blob/v4.5.8/COPYING it looks
like it's only GPLV2


> > - how to licence m4/libelf.m4 ? I'd prefer you to tell me exactly what
> to add in
> > order to avoid errors
>
> The original version of the m4/libelf.m4 was introduced 2001-09-27.  It
> appears
> to me that it was written as part of the prelinker, so would be under the
> overall license of the prelinker.
>
> Based on this, my assumption is that it is GPL-2.0
>
> I do not see any 'or-later' clauses anywhere.
>
> I have just add  "dnl SPDX-License-Identifier: GPL-2.0-only" bellow the
"Written by" comment, however should it also be in the resulting template?
I can add it also at first line of the resulting file if necessary ?


> - what about *.C files ? They don't have licence header, they look like C
> file
> > to me so I'd probably add :
> > // SPDX-License-Identifier: GPL-2.0-or-later
>
> There are each simply test cases.  They would be covered by the overall
> 'COPYING' for the package.  Thus GPL-2.0
>
> > - what about testsuite/ files ?
>
> Same, no specifically stated license will be GPL-2.0.
>
> Done !

> > Shall every thing just be GPL-2.0-or-later?
>
> Also just to be clear.  As I am NOT the original author of this work, I
> won't
> accept a patch to remove any existing license text from the headers in this
> software, but I will accept the SPDX-License-Identifier to be added in
> addition
> to the existing license text.
>
>
If an existing file does not have any License text in it, then we will need
> to
> assume that the COPYING file covers all software unless there is some
> indicator
> it comes from another source with a different license.  For items w/o
> existing
> licenses, just adding the SPDX-License-Identifier will be acceptable.
>
> So in a header similar to:
>
> /* Copyright (C) 2001, 2002, 2003, 2007 Red Hat, Inc.
>Written by Jakub Jelinek , 2001.
>
>This program is free software; you can redistribute it and/or modify
>it under the terms of the GNU General Public License as published by
>the Free Software Foundation; either version 2, or (at your option)
>any later version.
>
>This program is distributed in the hope that it will be useful,
>but WITHOUT ANY WARRANTY; without even the implied warranty of
>MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
>GNU General Public License for more details.
>
>You should have received a copy of the GNU General Public License
>along with this program; if not, write to the Free Software Foundation,
>Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.  */
>
> please add the header between the 'Written by' and the existing license
> text,
> such as:
>
> /* Copyright (C) 2001, 2002, 2003, 2007 Red Hat, Inc.
>Written by Jakub Jelinek , 2001.
>
>SPDX-License-Identifier: GPL-2.0-or-later
>
>This program is free software; you can redistribute it and/or modify
>it under the terms of the GNU General Public License as published by
>
>
Here's the first attempt of the patch, feel free to give me any advice on
how to improve it!

Regards,

-- 
[image: SMILE] 

20 rue des Jardins
92600 Asnières-sur-Seine
*Yann CARDAILLAC*
Ingénieur Systèmes Embarqués

[image: email] yann.cardail...@smile.fr
[image: url] http://www.smile.eu

[image: Twitter]  [image: Facebook]

Re: [yocto] [PATCH] [auto-upgrade-helper] Add SPDX identifier to auto-upgrade-helper

[Alexander Kanavin]

Thanks, patch applied and pushed.

Alex

On Mon, 21 Oct 2019 at 14:46, Yann CARDAILLAC 
wrote:

> Hi guys,
>
> I'm working on bug :
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13531
>
> I've add GPLV2-or-later to all the sources, is there any modification you
> want to add?
>
> Best regards,
>
> Yann CARDAILLAC
> --
> [image: SMILE] 
>
> 20 rue des Jardins
> 92600 Asnières-sur-Seine
> *Yann CARDAILLAC*
> Ingénieur Systèmes Embarqués
>
> [image: email] yann.cardail...@smile.fr
> [image: url] http://www.smile.eu
>
> [image: Twitter]  [image: Facebook]
>  [image: LinkedIn]
>  [image: Github]
> 
>
>
> [image: eco] Pour la planète, n'imprimez ce mail que si c'est nécessaire
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [layerindex-web] Add SPDX Identifier

[Yann CARDAILLAC]

On Mon, Oct 21, 2019 at 9:37 PM Paul Eggleton 
wrote:

> On Tuesday, 22 October 2019 4:15:03 AM NZDT Yann CARDAILLAC wrote:
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=13527
> >
> > I'm beginning the work of updating the layerindex-web repo, this one is a
> > bit tricky, how should I treat the files generated using Django ?
>
> I believe the correct license for Django-derived files is BSD-3-Clause:
>
>   https://github.com/django/django/blob/master/LICENSE
>
> > I've yet to do html, txt and sh files, do you have any advices before I
> > start?
>
> Note that some of the templates used for authentication originally came
> from
> here:
>
>   https://github.com/macdhuibh/django-registration-templates
>
> The LICENSE file indicates MIT for those though.
>
> The txt files are tricky because any stray newlines will affect
> formatting. I
> would probably avoid touching them.
>
> I did not yet add MIT to html files, I don't really know if that makes
sense or not?  I didn't do that because it seemed a bit weird to me, but I
don't know what to think of that. Most of the time you'll find copyright on
the footer of the page, but I'm not sure about Licensing those.

So here is a first iteration of the patch without htmls file licensed.

Regards,

-- 
[image: SMILE] 

20 rue des Jardins
92600 Asnières-sur-Seine
*Yann CARDAILLAC*
Ingénieur Systèmes Embarqués

[image: email] yann.cardail...@smile.fr
[image: url] http://www.smile.eu

[image: Twitter]  [image: Facebook]
 [image: LinkedIn]
 [image: Github]



[image: eco] Pour la planète, n'imprimez ce mail que si c'est nécessaire
From e46cd0244aa8134318236a2f1aee96682e09715b Mon Sep 17 00:00:00 2001
From: Yann CARDAILLAC 
Date: Tue, 22 Oct 2019 15:17:21 +0200
Subject: [PATCH] add SPDX License identifier

Signed-off-by: Yann CARDAILLAC 
---
 __init__.py | 2 ++
 check_requirements.sh   | 1 +
 docker/connectivity_check.sh| 1 +
 docker/git-proxy| 1 +
 docker/migrate.sh   | 1 +
 docker/refreshlayers.sh | 1 +
 docker/settings.py  | 1 +
 docker/updatelayers.sh  | 1 +
 dockersetup.py  | 1 +
 layerindex/__init__.py  | 1 +
 layerindex/admin.py | 1 +
 layerindex/auth_forms.py| 1 +
 layerindex/auth_views.py| 1 +
 layerindex/bulkchange.py| 1 +
 layerindex/context_processors.py| 1 +
 layerindex/forms.py | 1 +
 layerindex/layerconfparse.py| 1 +
 layerindex/middleware.py| 1 +
 layerindex/migrations/0001_initial.py   | 1 +
 layerindex/migrations/0002_distro.py| 1 +
 layerindex/migrations/0003_auto_20161011_0304.py| 1 +
 layerindex/migrations/0004_layerdependency_required.py  | 1 +
 layerindex/migrations/0005_layerupdate.py   | 1 +
 layerindex/migrations/0006_change_branch_meta.py| 1 +
 layerindex/migrations/0007_layeritem_status_noupdate.py | 1 +
 layerindex/migrations/0008_yp_compatible.py | 1 +
 layerindex/migrations/0009_layerbranch_collection.py| 1 +
 layerindex/migrations/0010_add_dependencies.py  | 1 +
 layerindex/migrations/0011_source.py| 1 +
 layerindex/migrations/0012_layeritem_vcs_commit_url.py  | 1 +
 layerindex/migrations/0013_patch.py | 1 +
 layerindex/migrations/0014_sitenotice.py| 1 +
 layerindex/migrations/0015_comparison.py| 1 +
 layerindex/migrations/0016_classicrecipe_delete.py  | 1 +
 layerindex/migrations/0017_classicrecipe_needs_attention.py | 1 +
 layerindex/migrations/0018_layerrecipeextraurl.py   | 1 +
 layerindex/migrations/0019_layeritem_classic_comparison.py  | 1 +
 layerindex/migrations/0020_update_manual.py | 1 +
 layerindex/migrations/0021_layerupdate_add_layer_branch.py  | 1 +
 layerindex/migrations/0022_layerupdate_set_layer_branch.py  | 1 +
 layerindex/migrations/0023_layerupdate_layer_branch_finalise.py | 1 +
 layerindex/migrations/0024_layerupdate_vcs_revs.py  | 1 +
 layerindex/migrations/0025_update_re

[yocto] [PATCH][opkg] bug 13528 add SPDX id to opkg

[Yann CARDAILLAC]

Hi,

I'm working on bug : https://bugzilla.yoctoproject.org/show_bug.cgi?id=13528

I've a first patch proposal. Note that I didn't knew what to do with
m4/gpgme.m4 the license header seems pretty weird to me...

Regards,

-- 
[image: SMILE] 

20 rue des Jardins
92600 Asnières-sur-Seine
*Yann CARDAILLAC*
Ingénieur Systèmes Embarqués

[image: email] yann.cardail...@smile.fr
[image: url] http://www.smile.eu

[image: Twitter]  [image: Facebook]
 [image: LinkedIn]
 [image: Github]



[image: eco] Pour la planète, n'imprimez ce mail que si c'est nécessaire
From 8e2c4d34a81e703df8c31163ef4bbec09f96be63 Mon Sep 17 00:00:00 2001
From: Yann CARDAILLAC 
Date: Tue, 22 Oct 2019 16:49:42 +0200
Subject: [PATCH] add SPDX License identifier

Signed-off-by: Yann CARDAILLAC 
---
 intercept/depmod | 1 +
 intercept/ldconfig   | 1 +
 intercept/update-modules | 1 +
 libopkg/cksum_list.c | 2 ++
 libopkg/cksum_list.h | 2 ++
 libopkg/conffile.c   | 2 ++
 libopkg/conffile.h   | 2 ++
 libopkg/conffile_list.c  | 2 ++
 libopkg/conffile_list.h  | 2 ++
 libopkg/file_list.c  | 2 ++
 libopkg/file_list.h  | 2 ++
 libopkg/file_util.c  | 2 ++
 libopkg/file_util.h  | 2 ++
 libopkg/hash_table.c | 2 ++
 libopkg/hash_table.h | 2 ++
 libopkg/list.h   | 2 ++
 libopkg/md5.c| 3 +++
 libopkg/md5.h| 3 +++
 libopkg/nv_pair.c| 2 ++
 libopkg/nv_pair.h| 2 ++
 libopkg/nv_pair_list.c   | 2 ++
 libopkg/nv_pair_list.h   | 2 ++
 libopkg/opkg.c   | 2 ++
 libopkg/opkg.h   | 2 ++
 libopkg/opkg_archive.c   | 2 ++
 libopkg/opkg_archive.h   | 2 ++
 libopkg/opkg_cmd.c   | 2 ++
 libopkg/opkg_cmd.h   | 2 ++
 libopkg/opkg_conf.c  | 2 ++
 libopkg/opkg_conf.h  | 2 ++
 libopkg/opkg_configure.c | 2 ++
 libopkg/opkg_configure.h | 2 ++
 libopkg/opkg_download.c  | 2 ++
 libopkg/opkg_download.h  | 2 ++
 libopkg/opkg_download_curl.c | 2 ++
 libopkg/opkg_download_wget.c | 2 ++
 libopkg/opkg_gpg.c   | 2 ++
 libopkg/opkg_gpg.h   | 2 ++
 libopkg/opkg_install.c   | 2 ++
 libopkg/opkg_install.h   | 2 ++
 libopkg/opkg_message.c   | 2 ++
 libopkg/opkg_message.h   | 2 ++
 libopkg/opkg_openssl.c   | 2 ++
 libopkg/opkg_openssl.h   | 2 ++
 libopkg/opkg_remove.c| 2 ++
 libopkg/opkg_remove.h| 2 ++
 libopkg/opkg_solver.h| 2 ++
 libopkg/opkg_utils.c | 2 ++
 libopkg/opkg_utils.h | 2 ++
 libopkg/opkg_verify.c| 2 ++
 libopkg/opkg_verify.h| 2 ++
 libopkg/parse_util.c | 2 ++
 libopkg/parse_util.h | 2 ++
 libopkg/pkg.c| 2 ++
 libopkg/pkg.h| 2 ++
 libopkg/pkg_depends.c| 2 ++
 libopkg/pkg_depends.h| 2 ++
 libopkg/pkg_dest.c   | 2 ++
 libopkg/pkg_dest.h   | 2 ++
 libopkg/pkg_dest_list.c  | 2 ++
 libopkg/pkg_dest_list.h  | 2 ++
 libopkg/pkg_extract.c| 2 ++
 libopkg/pkg_extract.h| 2 ++
 libopkg/pkg_hash.c   | 2 ++
 libopkg/pkg_hash.h   | 2 ++
 libopkg/pkg_parse.c  | 2 ++
 libopkg/pkg_parse.h  | 2 ++
 libopkg/pkg_src.c| 2 ++
 libopkg/pkg_src.h| 2 ++
 libopkg/pkg_src_list.c   | 2 ++
 libopkg/pkg_src_list.h   | 2 ++
 libopkg/pkg_vec

[yocto] Yocto Project Status WW43’19

[Stephen K Jolley]

Current Dev Position: YP 3.1 M1

Next Deadline: YP 3.0 Final Release 25th Oct

SWAT Team Rotation:

   -

   SWAT lead is currently: Paul
   -

   SWAT team rotation: Ross -> Amanda on Oct. 25, 2019
   -

   SWAT team rotation: Amanda -> Armin on Nov. 1, 2019
   -

   https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Next Team Meetings:

   -

   Bug Triage meeting Thursday Oct. 24th at 7:30am PDT (
   https://zoom.us/j/454367603)
   -

   Monthly Project Meeting Tuesday Nov. 5th at 8am PDT (
   https://zoom.us/j/990892712) 
   -

   Weekly Engineering Sync Tuesday Oct. 22th at 8am PDT (
   https://zoom.us/j/990892712) 
   -

   Twitch - Next event is Tuesday Nov. 12th at 8am PDT (
   https://www.twitch.tv/yocto_project)


Key Status/Updates:

   -

   YP 3.0 as been approved by the TSC and should be released later this
   week. Only the final tweaks to the release notes remain.
   -

   Master has continued taking patches for post 3.0.
   -

   There are a number of intermittent failures on the autobuiler which are
   causing concern, there is a separate email about this.
   -

   YP  2.6.4 was built and submitted to QA
   -

   YP 2.7.2 was not built due to a remaining bug which needs to be resolved
   first
   -

   Next week is ELC-E and therefore may be quiet on the mailing lists with
   patch merging being delayed.
   -

   We have begun collecting ideas for YP 3.1 in this document:
   
https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjnABc/edit?usp=sharing
   -

   If anyone has any status items for the project they’d like to add to the
   weekly reports, please email Richard+Stephen.


Planned Releases for YP 3.0:

   -

   YP 3.0 Final Release 25th Oct


Planned upcoming dot releases:

   -

   YP 2.7.2 (Warrior) is planned this week (assuming the remaining bug is
   resolved).
   -

   YP 2.6.4 (Thud) is in QA..


Tracking Metrics:

   -

   WDD 2498 (last week 2528) (
   https://wiki.yoctoproject.org/charts/combo.html)
   -

   Poky Patch Metrics
   -

  Total patches found: 1432 (last week 1445)
  -

  Patches in the Pending State: 578 (41%) [last week 586 (41%)]


Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features

The Yocto Project’s technical governance is through its Technical Steering
Committee, more information is available at:

https://wiki.yoctoproject.org/wiki/TSC

The Status reports are now stored on the wiki at:
https://wiki.yoctoproject.org/wiki/Weekly_Status

[If anyone has suggestions for other information you’d like to see on this
weekly status update, let us know!]

Thanks,



*Stephen K. Jolley*

*Yocto Project Program Manager*

*7867 SW Bayberry Dr., Beaverton, OR 97007*

(*Cell*:(208) 244-4460

* *Email*: *s
jolley.yp...@gmail.com *
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Canceled event with note: Yocto Project Technical Team Meeting / Engineering Sync @ Tue Oct 29, 2019 8am - 9am (PDT) (yocto@yoctoproject.org)

[theyoctoproject]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20191029T08
DTEND;TZID=America/Los_Angeles:20191029T09
DTSTAMP:20191022T150510Z
ORGANIZER;CN=theyoctoproj...@gmail.com:mailto:theyoctoproj...@gmail.com
UID:74pj8d1h6op62b9j74omcb9kcpgjgb9oclhj0b9jcos3io9h61ijgd1nc4_R20190827T15
 0...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=kh
 em_...@comcast.com;X-NUM-GUESTS=0:mailto:khem_...@comcast.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ni
 ck.pongr...@singlewire.com;X-NUM-GUESTS=0:mailto:nick.pongratz@singlewire.c
 om
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=br
 uce.ashfi...@gmail.com;X-NUM-GUESTS=0:mailto:bruce.ashfi...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=hn
 j...@triax.com;X-NUM-GUESTS=0:mailto:h...@triax.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=la
 zaros.lazari...@atos.net;X-NUM-GUESTS=0:mailto:lazaros.lazari...@atos.net
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=er
 ik.hoogev...@outlook.com;X-NUM-GUESTS=0:mailto:erik.hoogev...@outlook.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ru
 dolf.str...@gmail.com;X-NUM-GUESTS=0:mailto:rudolf.str...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ma
 nju...@xilinx.com;X-NUM-GUESTS=0:mailto:manju...@xilinx.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=kh
 em_...@cable.comcast.com;X-NUM-GUESTS=0:mailto:khem_...@cable.comcast.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ro
 b.rans...@windriver.com;X-NUM-GUESTS=0:mailto:rob.rans...@windriver.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=bi
 kram_bh...@mentor.com;X-NUM-GUESTS=0:mailto:bikram_bh...@mentor.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=yo
 c...@yoctoproject.org;X-NUM-GUESTS=0:mailto:yocto@yoctoproject.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=oa
 ndreas...@luxoft.com;X-NUM-GUESTS=0:mailto:oandreas...@luxoft.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ya
 nnick.koeh...@hpe.com;X-NUM-GUESTS=0:mailto:yannick.koeh...@hpe.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=st
 ephen.k.jol...@intel.com;X-NUM-GUESTS=0:mailto:stephen.k.jol...@intel.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=as
 ei...@ciena.com;X-NUM-GUESTS=0:mailto:asei...@ciena.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=jd
 ma...@kudzu.us;X-NUM-GUESTS=0:mailto:jdma...@kudzu.us
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=jo
 nathan.h...@sdl.usu.edu;X-NUM-GUESTS=0:mailto:jonathan.h...@sdl.usu.edu
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=dw
 atk...@sierrawireless.com;X-NUM-GUESTS=0:mailto:dwatk...@sierrawireless.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;CN=theyoc
 toproj...@gmail.com;X-NUM-GUESTS=0:mailto:theyoctoproj...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ra
 j.k...@gmail.com;X-NUM-GUESTS=0:mailto:raj.k...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ra
 ymond@intel.com;X-NUM-GUESTS=0:mailto:raymond@intel.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=th
 ore.boeckelm...@inoex.de;X-NUM-GUESTS=0:mailto:thore.boeckelm...@inoex.de
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=rc
 alh...@shotspotter.com;X-NUM-GUESTS=0:mailto:rcalh...@shotspotter.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=na
 ndo...@gmail.com;X-NUM-GUESTS=0:mailto:nando...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ar
 avindhlal...@embedur.com;X-NUM-GUESTS=0:mailto:aravindhlal...@embedur.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=sj
 olley.yp...@gmail.com;X-NUM-GUESTS=0:mailto:sjolley.yp...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=pa
 trick.schnei...@bhtronik.de;X-NUM-GUESTS=0:mailto:patrick.schneider@bhtroni
 k.de
RECURRENCE-ID;TZID=America/Los_Angeles:20191029T08
CREATED:20180524T181406Z
DESCRIPTION:The Yocto Project hosts a technical call. All community mem
 bers are inv

[yocto] toaster - in build watching mode

[Mark Hatle]

I'm using toaster in a build watching mode and I'm getting errors to the console
log such as:

File:
'/home/jenkins/workspace/OEBuild/build-32/oe-core/meta/classes/toaster.bbclass',
lineno: 130, function: toaster_package_dumpdata
 0126:lpkgdata = {}
 0127:datadir = os.path.join(pkgdatadir, 'runtime')
 0128:
 0129:# scan and send data for each generated package
 *** 0130:for datafile in os.listdir(datadir):
 0131:if not datafile.endswith('.packaged'):
 0132:lpkgdata = _toaster_load_pkgdatafile(datadir, datafile)
 0133:# Fire an event containing the pkg data
 0134:bb.event.fire(bb.event.MetadataEvent("SinglePackageInfo",
lpkgdata), d)
Exception: FileNotFoundError: [Errno 2] No such file or directory:
'/home/jenkins/workspace/OEBuild/builds/build-32/tmp-glibc/work/core2-64-oe-linux/libxfixes/1_5.0.3-r0/pkgdata/runtime'


Also lots of messages like:

NOTE: We did not find one recipe for theconfiguration data package libxml2
Recipe matching query does not exist.
NOTE: We did not find one recipe for theconfiguration data package libx11-6
Recipe matching query does not exist.
NOTE: We did not find one recipe for theconfiguration data package
wpa-supplicant Recipe matching query does not exist.


In the toaster itself, I see the % status of the current build (which appears to
be correct).  However, during the build I didn't get any per task information
like I remembered seeing in the past.  Has this changed, or do we have a bug
somewhere?

--Mark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [OE-core] [prelink-cross] Bug 13529 add SPDX identifier

[Mark Hatle]

I need to look through it further, but everything I looked at (and your comments
below) look good to me.

I'll try to get this merge soon.  (If you don't see it get merged, please ping
me.)  I'm preparing for ELC-E and am short on time right now.

--Mark

On 10/22/19 4:28 AM, Yann CARDAILLAC wrote:
> 
> 
> On Mon, Oct 21, 2019 at 4:35 PM Mark Hatle  > wrote:
> 
> On 10/21/19 4:43 AM, Yann CARDAILLAC wrote:
> > Hi Mark Hatle, Jakub Jelinek,
> 
> Jakub is no longer supporting this code, but he may have valuable 
> insights into
> licensing.
> 
> > I'm currently beginning the work on bug 13529:
> >
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=13529
> >
> > The purpose is to add SPDX identifier to scripts and sources.
> >
> > Most of the sources have licences on the sources, however some of them 
> don't,
> > and I've question about others :
> >
> > - src/sha.c do not shall it be GPLV2-or-later as most of the other?
> 
> /* sha.c - Functions to compute the SHA1 hash (message-digest) of files
>    or blocks of memory.  Complies to the NIST specification FIPS-180-1.
> 
>    Copyright (C) 2000, 2001, 2003 Scott G. Miller
> 
>    Credits:
>       Robert Klep mailto:rob...@ilse.nl>>  -- Expansion
> function fix
>    NOTE: The canonical source of this file is maintained in GNU coreutils.
> */
> 
> The last line is the key.  This apparently came from GNU coreutils.
> 
> >From the SCM logs, sha.c was introduced in approx 2003-07-01 from what 
> it looks
> like.  So it's a pretty old version.  You will need to do some detective 
> work,
> and find older versions of coreutils until you find the one that 
> corresponds to
> the code that was checked in.  Start back in 2003 and work backwards as
> necessary.  (The version that matches to the original 2003-07-01 should 
> be the
> reasonable license to use.)
> 
> 
> Ok I found it ! https://github.com/coreutils/coreutils/blob/v4.5.8/lib/sha.c
> 
> from : https://github.com/coreutils/coreutils/blob/v4.5.8/COPYING it looks 
> like
> it's only GPLV2
> 
> 
> > - how to licence m4/libelf.m4 ? I'd prefer you to tell me exactly what 
> to
> add in
> > order to avoid errors
> 
> The original version of the m4/libelf.m4 was introduced 2001-09-27.  It 
> appears
> to me that it was written as part of the prelinker, so would be under the
> overall license of the prelinker.
> 
> Based on this, my assumption is that it is GPL-2.0
> 
> I do not see any 'or-later' clauses anywhere.
> 
> I have just add  "dnl SPDX-License-Identifier: GPL-2.0-only" bellow the 
> "Written
> by" comment, however should it also be in the resulting template? 
> I can add it also at first line of the resulting file if necessary ?
> 
> 
> > - what about *.C files ? They don't have licence header, they look like 
> C file
> > to me so I'd probably add :
> > // SPDX-License-Identifier: GPL-2.0-or-later
> 
> There are each simply test cases.  They would be covered by the overall
> 'COPYING' for the package.  Thus GPL-2.0
> 
> > - what about testsuite/ files ?
> 
> Same, no specifically stated license will be GPL-2.0.
> 
> Done ! 
> 
> > Shall every thing just be GPL-2.0-or-later?
> 
> Also just to be clear.  As I am NOT the original author of this work, I 
> won't
> accept a patch to remove any existing license text from the headers in 
> this
> software, but I will accept the SPDX-License-Identifier to be added in 
> addition
> to the existing license text.
>  
> 
> If an existing file does not have any License text in it, then we will 
> need to
> assume that the COPYING file covers all software unless there is some 
> indicator
> it comes from another source with a different license.  For items w/o 
> existing
> licenses, just adding the SPDX-License-Identifier will be acceptable.
> 
> So in a header similar to:
> 
> /* Copyright (C) 2001, 2002, 2003, 2007 Red Hat, Inc.
>    Written by Jakub Jelinek mailto:ja...@redhat.com>>, 
> 2001.
> 
>    This program is free software; you can redistribute it and/or modify
>    it under the terms of the GNU General Public License as published by
>    the Free Software Foundation; either version 2, or (at your option)
>    any later version.
> 
>    This program is distributed in the hope that it will be useful,
>    but WITHOUT ANY WARRANTY; without even the implied warranty of
>    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
>    GNU General Public License for more details.
> 
>    You should have received a copy of the GNU General Public License
>    along with this program; if not, write to the Free Software Foundation,
>    Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.  */
> 
> please add the header between the 'Written