From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Stefan Agner <stefan@agner.ch>
Cc: nolange79@gmail.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/dbus-broker: bump to release 32
Date: Thu, 11 Aug 2022 22:58:31 +0200 [thread overview]
Message-ID: <20220811225831.0e3d5fbc@windsurf> (raw)
In-Reply-To: <ca7d879728d7de4dc9636c3facd570c83860b9f6.1660131874.git.stefan@agner.ch>
On Wed, 10 Aug 2022 13:45:38 +0200
Stefan Agner <stefan@agner.ch> wrote:
> The new releases mostly contain bug fixes. The build system has been
> prepared to use AppArmor library, but since actual support is still
> missing it is not worth yet to enable build infrastructure in
> Buildroot.
>
> Signed-off-by: Stefan Agner <stefan@agner.ch>
In fact, no, I didn't apply: this patch break "make legal-info":
>>> dbus-broker 32 Collecting legal info
LICENSE: OK (sha256: 3cda3630283eda0eab825abe5ac84d191248c6b3fe1c232a118124959b96c6a4)
ERROR: No hash found for subprojects/c-dvar/AUTHORS
cp: cannot stat '/home/thomas/projets/buildroot/output/build/dbus-broker-32/subprojects/c-dvar/AUTHORS': No such file or directory
make: *** [package/dbus-broker/dbus-broker.mk:69: dbus-broker-legal-info] Error 1
Seems like the folders in subprojects/ have changed quite a bit, this
needs to be compared with version 29 to see how license information
needs to be updated.
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-08-11 20:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 11:45 [Buildroot] [PATCH] package/dbus-broker: bump to release 32 Stefan Agner
2022-08-11 20:56 ` Thomas Petazzoni via buildroot
2022-08-11 20:58 ` Thomas Petazzoni via buildroot [this message]
2022-08-12 7:50 ` 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=20220811225831.0e3d5fbc@windsurf \
--to=buildroot@buildroot.org \
--cc=nolange79@gmail.com \
--cc=stefan@agner.ch \
--cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox