On 2022-05-22 14:14 +, Ryan Prior wrote:
> --- Original Message ---
> On Sunday, May 22nd, 2022 at 8:00 AM, Foo Chuan Wei
> wrote:
>
> > The shell in the environment where packages are built ignores SIGINT
> > and SIGQUIT. If I add `(invoke "sh" "-c" "trap")` to a custom build
> > pha
Hi
--- Original Message ---
On Sunday, May 22nd, 2022 at 3:49 PM, Théo Maxime Tyburn
wrote:
> Hi
>
> Ekaitz Zarraga eka...@elenq.tech writes:
>
> > Make sure the version of alembic we have packaged is the one Blender
> > expects.
> >
> > Sometimes the APIs change and that may led to t
Hi
Ekaitz Zarraga writes:
> Make sure the version of alembic we have packaged is the one Blender expects.
>
> Sometimes the APIs change and that may led to that kind of errors.
The version of alembic that blender 3.0.1 requires is the same we
have.
The problem might come from another version
We are pleased to announce the GNU Shepherd version 0.9.1. This is a
bug-fix release, including a backward-compatible interface change,
representing 18 commits by 2 people over 6 weeks.
• About
The GNU Daemon Shepherd or GNU Shepherd is a service manager written
in Guile that looks after th
--- Original Message ---
On Sunday, May 22nd, 2022 at 8:00 AM, Foo Chuan Wei
wrote:
> The shell in the environment where packages are built ignores SIGINT and
> SIGQUIT. If I add `(invoke "sh" "-c" "trap")` to a custom build phase
That executes a shell which traps and then immediately e
The shell in the environment where packages are built ignores SIGINT and
SIGQUIT. If I add `(invoke "sh" "-c" "trap")` to a custom build phase,
this output is produced during the build:
trap -- '' INT
trap -- '' QUIT
Why does the shell in the build environment need to ignore these two
sig
