From: Peter Seiderer <ps.report@gmx.net>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1] package/util-linux: bump version to 2.37.3 (fixes CVE-2021-3996, CVE-2021-3995)
Date: Tue, 25 Jan 2022 21:11:08 +0100 [thread overview]
Message-ID: <20220125211108.1143b77b@gmx.net> (raw)
In-Reply-To: <20220125001222.582e094a@windsurf>
Hello Thomas,
On Tue, 25 Jan 2022 00:12:22 +0100, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> On Mon, 24 Jan 2022 22:07:07 +0100
> Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
>
> > Applied to master, thanks.
>
> And I reverted, because it breaks the build:
>
> http://autobuild.buildroot.net/?reason=%util-linux-2.37.3
>
> (I didn't investigate, it's too late here.)
The failure is
make[3]: *** No rule to make target 'disk-utils/raw.8', needed by 'all-am'. Stop.
upstream known [1] and [2] (and fixed in the next release), seems to be a packaging
error and could be fixed/work-around (or hacked) by (will install an empty man page
to staging/target):
touch build/util-linux-2.37.3/disk-utils/raw.8
Can send an updated patch with this fix(?)...
Regards,
Peter
[1] https://github.com/util-linux/util-linux/issues/1579
[2] https://github.com/util-linux/util-linux/issues/1577
>
> Best regards,
>
> Thomas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-01-25 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 20:16 [Buildroot] [PATCH v1] package/util-linux: bump version to 2.37.3 (fixes CVE-2021-3996, CVE-2021-3995) Peter Seiderer
2022-01-24 21:07 ` Thomas Petazzoni
2022-01-24 23:12 ` Thomas Petazzoni
2022-01-25 20:11 ` Peter Seiderer [this message]
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=20220125211108.1143b77b@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@buildroot.org \
--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