From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: Afshin Pir <Afshin.Pir@gallagher.com>,
"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] Update schedule of sources.buildroot.org
Date: Thu, 24 Aug 2023 23:16:15 +0200 [thread overview]
Message-ID: <20230824231615.44df3647@windsurf> (raw)
In-Reply-To: <87y1i0cfjz.fsf@48ers.dk>
On Thu, 24 Aug 2023 23:10:24 +0200
Peter Korsgaard <peter@korsgaard.com> wrote:
> I'm back and now had time to investigate. The problem is the following
> commit that got added at the end of July:
>
> commit 08171f1fd0c31165a39d79389300ddf9adb5bbb6
> Author: Bernd Kuhls <bernd@kuhls.net>
> Date: Sun Jul 16 09:28:33 2023 +0200
>
> support/dependencies/dependencies.sh: require IPC::Cmd perl package for libopenssl
>
> The machine handling s.b.o did not have the IPC::Cmd perl module
> installed, so all the source update runs would fail. I've now installed
> that and started a s.b.o update.
Thanks for fixing this!
Do you think the script could somehow be robustified to let us know
when it doesn't manage to do its job as expected?
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:[~2023-08-24 21:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 4:36 [Buildroot] Update schedule of sources.buildroot.org Afshin Pir
2023-08-01 10:11 ` Thomas Petazzoni via buildroot
2023-08-01 21:30 ` Afshin Pir
2023-08-02 22:30 ` Afshin Pir
2023-08-03 18:51 ` Yann E. MORIN
2023-08-24 21:10 ` Peter Korsgaard
2023-08-24 21:16 ` Thomas Petazzoni via buildroot [this message]
2023-08-24 21:23 ` Peter Korsgaard
2023-08-24 21:26 ` Thomas Petazzoni via buildroot
2023-08-25 6:56 ` Peter Korsgaard
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=20230824231615.44df3647@windsurf \
--to=buildroot@buildroot.org \
--cc=Afshin.Pir@gallagher.com \
--cc=peter@korsgaard.com \
--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 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.