From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: Ricardo Wurmus <rekado@elephly.net>,
31399@debbugs.gnu.org, 31399-done@debbugs.gnu.org
Subject: [bug#31399] [PATCH] import: elpa: Implement recursive import.
Date: Fri, 8 Jun 2018 14:59:59 +0200 [thread overview]
Message-ID: <idja7s5juwg.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <87sh5xlbv6.fsf@gmail.com>
Hi Oleg,
>> I’d find it clearer to have a first patch that moves code from cran.scm
>> to utils.scm, and a second patch containing the ELPA changes. No big
>> deal though.
>
> OK, splitted the patch. Also removed unused srfi-41.
>
>> Please double-check that tests/{elpa,cran}.scm still pass, but if they
>> do, I think you can go ahead and push.
>
> I tested both commits separately. Pushed as:
>
> - 74032da3a2ef3e99e89dd58701414004f5a6c061
> - ae9e5d6602544390fa5da0a87450405ebba012fd
Thank you!
> While I've tested, ‘test-tmp/db/’ directory was missing in my Guix Git
> repository (‘test-tmp’ directory was present), tests failed until I
> manually created by invoking ‘mkdir test-tmp/db’. I've tried to remove
> ‘test-tmp’, invoke ‘./configure --localstatedir=/var --prefix=’ and
> ‘make’, but it produced only ‘test-tmp’ directory.
This seems to be a problem that was introduced with commit
7f9d184d9b688d13ce76eefabaddcfa76bdde2b5.
--
Ricardo
next prev parent reply other threads:[~2018-06-08 13:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 8:37 [bug#31399] [PATCH] import: elpa: Implement recursive import Oleg Pykhalov
2018-05-25 12:00 ` Ludovic Courtès
2018-05-25 12:50 ` Ricardo Wurmus
2018-05-29 14:31 ` Ludovic Courtès
2018-05-30 16:35 ` Oleg Pykhalov
2018-06-01 20:40 ` Ludovic Courtès
2018-06-08 12:08 ` Oleg Pykhalov
2018-06-08 12:59 ` Ricardo Wurmus [this message]
2018-06-08 19:35 ` Ludovic Courtès
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=idja7s5juwg.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=31399-done@debbugs.gnu.org \
--cc=31399@debbugs.gnu.org \
--cc=go.wigust@gmail.com \
--cc=rekado@elephly.net \
/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.