From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15331] New: Warning on python-flit-core license when generating legal info
Date: Fri, 10 Feb 2023 10:13:15 +0000 [thread overview]
Message-ID: <bug-15331-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15331
Bug ID: 15331
Summary: Warning on python-flit-core license when generating
legal info
Product: buildroot
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: trivial
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: alexis.lothore@bootlin.com
CC: buildroot@uclibc.org
Target Milestone: ---
Created attachment 9506
--> https://bugs.busybox.net/attachment.cgi?id=9506&action=edit
Modified defconfig to reproduce the issue
The legal-info target emits a warning on python-flit-core:
WARNING: python-flit-core-3.8.0: cannot save license
(HOST_PYTHON_FLIT_CORE_LICENSE_FILES not defined)
Steps to reproduce:
- clone buildroot
- make qemu_x86_64_defconfig
- in menuconfig, enable python3, a python package having flit as setup type
(e.g.: argon2_cffi)
- make legal-info
Host OS : Archlinux (Linux arch-bootlin-alexis 6.1.9-arch1-2 #1 SMP
PREEMPT_DYNAMIC Fri, 03 Feb 2023 18:49:53 +0000 x86_64 GNU/Linux)
Buildroot version : master (e2fd606b91784ced64c7312e02fcbf95f3e736d6)
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-02-10 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 10:13 bugzilla [this message]
2023-02-10 10:13 ` [Buildroot] [Bug 15331] Warning on python-flit-core license when generating legal info bugzilla
2023-02-10 10:40 ` bugzilla
2023-02-10 15:52 ` bugzilla
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=bug-15331-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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.