All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: Stefan Agner <stefan@agner.ch>
Cc: openembedded-devel@lists.openembedded.org,
	Marcel Ziswiler <marcel@ziswiler.com>,
	angstrom-distro-devel@linuxtogo.org
Subject: Re: license_create_manifest fails on jethro
Date: Fri, 11 Mar 2016 10:56:23 -0600	[thread overview]
Message-ID: <56E2F8B7.3010606@linux.intel.com> (raw)
In-Reply-To: <1d5cc52037d090b4f12b24f85bc361f6@agner.ch>

[-- Attachment #1: Type: text/plain, Size: 3242 bytes --]

Hi Stefan,

Seems that LICENSE_DIRECTORY set is causing this trouble i don't
understand why? because i expanded LICENSE_DIRECTORY for copy licenses
but if you revert the commit and works the new code needs to be
compatible. Could you give me the instructions for reproduce your case?

For the license warnings is related to the same LICENSE_DIRECTORY thing
because it wasn't able to collect (copy) the licenses.

	alimon

- Resending... due to a list unsubscription.

On 03/10/2016 09:12 PM, Stefan Agner wrote:
> Hi Anibal,
> 
> I think the patch a7976cbae3 ("license_class: Reimplemented manifest
> creation in python") broke Ångstroms way of deploying license files.
> With jethro I get the following error when building the _second_
> machine:
> 
> ERROR: Error executing a python function in
> /build/ags/oe-core_V2.6/build/../stuff/meta-toradex/recipes/images/console-trdx-image.bb:
> 
> The stack trace of python calls that resulted in this exception/failure
> was:
> File: 'license_create_manifest', lineno: 110, function: <module>
>      0106:
>      0107:                        os.link(pkg_license,
> pkg_rootfs_license)
>      0108:
>      0109:
>  *** 0110:license_create_manifest(d)
>      0111:
> File: 'license_create_manifest', lineno: 86, function:
> license_create_manifest
>      0082:                pkg_rootfs_license_dir =
> os.path.join(rootfs_license_dir, pkg)
>      0083:                os.makedirs(pkg_rootfs_license_dir)
>      0084:                pkg_license_dir =
> os.path.join(d.getVar('LICENSE_DIRECTORY', True),
>      0085:                                           
> pkg_dic[pkg]["PN"])
>  *** 0086:                licenses = os.listdir(pkg_license_dir)
>      0087:                for lic in licenses:
>      0088:                    rootfs_license =
> os.path.join(rootfs_license_dir, lic)
>      0089:                    pkg_license =
> os.path.join(pkg_license_dir, lic)
>      0090:                    pkg_rootfs_license =
> os.path.join(pkg_rootfs_license_dir, lic)
> Exception: OSError: [Errno 2] No such file or directory:
> '/build/ags/oe-core_V2.6/build/out-glibc/deploy/licenses/colibri_imx7/alsa-utils'
> 
> ERROR: Function failed: license_create_manifest
> ERROR: Logfile of failure stored in:
> /build/ags/oe-core_V2.6/build/out-glibc/work/colibri_imx7-angstrom-linux-gnueabi/console-trdx-image/V2.6-r0/temp/log.do_rootfs.29351
> ERROR: Task 7
> (/build/ags/oe-core_V2.6/build/../stuff/meta-toradex/recipes/images/console-trdx-image.bb,
> do_rootfs) failed with exit code '1'
> 
> It might relate to how Ångström configures the LICENSE_DIRECTORY
> variable (by including MACHINE_ARCH, see
> https://github.com/Angstrom-distribution/meta-angstrom/blob/angstrom-v2015.12-yocto2.0/conf/distro/include/angstrom-core-tweaks.inc):
> LICENSE_DIRECTORY = "${DEPLOY_DIR}/licenses/${MACHINE_ARCH}"
> 
> I am not sure what exactly causes the issue, but after reverting your
> patch two consecutive builds of different machines succeeded...
> 
> However, I still get a lot of warnings such as:
> WARNING: The license listed LGPLv2.1 was not in the licenses collected
> for systemd
> 
> Any ideas?
> 
> --
> Stefan
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2016-03-11 16:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11  3:12 license_create_manifest fails on jethro Stefan Agner
2016-03-11 16:56 ` Aníbal Limón [this message]
2016-03-11 17:00   ` Aníbal Limón
2016-03-11 18:43     ` Stefan Agner

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=56E2F8B7.3010606@linux.intel.com \
    --to=anibal.limon@linux.intel.com \
    --cc=angstrom-distro-devel@linuxtogo.org \
    --cc=marcel@ziswiler.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=stefan@agner.ch \
    /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.