From: Tim Howes via Guix-patches via <guix-patches@gnu.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 43208@debbugs.gnu.org
Subject: [bug#43208] [PATCH] gnu: emacs-ess: Update to 20.09.
Date: Tue, 8 Sep 2020 12:22:08 -0700 [thread overview]
Message-ID: <47d58bad-6a89-d342-4a16-72c2c5500d6b@lavabit.com> (raw)
In-Reply-To: <87pn6zs57k.fsf@nicolasgoaziou.fr>
> BTW, when trying to build the package, I get the following failure:
>
> INFO Scraping files for ess-autoloads.el...
> .../lisp/ess-autoloads.el locked by nixbld@localh... (pid 103): (s, q, p, ?)?
> Cannot resolve lock conflict in batch mode
> make[1]: *** [Makefile:62: ess-autoloads.el] Error 255
>
> Can you build the package successfully?
It builds successfully sometimes, but fails sporadically due to this
file locking issue. It seems like, the way the Makefile is set up, it's
trying to build the ess-autoloads target multiple times in parallel,
which is causing it to fail if two processes are trying to write to the
file at the same time. I'll take a look later to see if I can prevent
the problem.
Thanks,
Tim
next prev parent reply other threads:[~2020-09-08 19:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 23:50 [bug#43208] [PATCH] gnu: emacs-ess: Update to 20200903.1516 Tim Howes via Guix-patches via
2020-09-05 13:35 ` Nicolas Goaziou
2020-09-05 17:58 ` Tim Howes via Guix-patches via
2020-09-05 21:45 ` [bug#43208] [PATCH] gnu: emacs-ess: Update to 20.09 Tim Howes via Guix-patches via
2020-09-06 8:02 ` Nicolas Goaziou
2020-09-08 19:22 ` Tim Howes via Guix-patches via [this message]
2020-09-24 15:20 ` Ludovic Courtès
2020-09-26 9:40 ` [bug#43208] [PATCH v3] gnu: emacs-ess: Update to 18.10.2-0.24da603 Tim Howes via Guix-patches via
2020-09-26 11:02 ` bug#43208: " Nicolas Goaziou
2020-09-06 0:57 ` [bug#43208] [PATCH] gnu: emacs-ess: Update to 20.09 Tim Howes via Guix-patches via
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=47d58bad-6a89-d342-4a16-72c2c5500d6b@lavabit.com \
--to=guix-patches@gnu.org \
--cc=43208@debbugs.gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=timhowes@lavabit.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.