From: Martin Flack <martin.flack@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 39775@debbugs.gnu.org
Subject: bug#39775: guix pull - error: lmdbxx: unbound variable
Date: Tue, 25 Feb 2020 10:29:18 -0700 [thread overview]
Message-ID: <CALNvAbfrmmsVrbW5PgUmmJqV4GMx4oMc8b-r5hi4cGh-_gvEfg@mail.gmail.com> (raw)
In-Reply-To: <CAJ3okZ2i-424Qeft-Oqso8WnZxQ9T1riVvGCWK2SHGnQxjj79g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
Ah, you can close this, sorry!
I think the problem was I had copied gnu/packages/databases.scm to a
custom GUIX_PACKAGE_PATH in order to apply a patch from the mailing lists,
without keeping it up-to-date with the rest of the contents of the file as
guix had further commits over time. I know there must be a way to do that
more cleanly where (a) you only override the necessary packages and (b)
somehow it becomes moot or you get notified when that package is upgraded
in mainline; but I have not yet learned how to do that! (Any tutorial?)
Cheers,
Martin
On Tue, Feb 25, 2020 at 8:13 AM zimoun <zimon.toutoune@gmail.com> wrote:
> Dear,
>
> On Tue, 25 Feb 2020 at 06:45, Martin Flack <martin.flack@gmail.com> wrote:
>
> > 1 package in profile
> >
> > Backtrace:
> > 1 (primitive-load "/home/mflack/.config/guix/current/bin/…")
> > In guix/ui.scm:
> > 1824:12 0 (run-guix-command _ . _)
> >
> > guix/ui.scm:1824:12: In procedure run-guix-command:
> > error: lmdbxx: unbound variable
>
> Could you provide the output of "guix describe" ? I mean from which
> commit do you pull?
>
> (I am not seeing this error.)
>
>
> All the best,s
> simon
>
--
Martin
[-- Attachment #2: Type: text/html, Size: 1824 bytes --]
next prev parent reply other threads:[~2020-02-25 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 5:43 bug#39775: guix pull - error: lmdbxx: unbound variable Martin Flack
2020-02-25 15:13 ` zimoun
2020-02-25 17:29 ` Martin Flack [this message]
2020-02-25 17:35 ` zimoun
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=CALNvAbfrmmsVrbW5PgUmmJqV4GMx4oMc8b-r5hi4cGh-_gvEfg@mail.gmail.com \
--to=martin.flack@gmail.com \
--cc=39775@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.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.