unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: poptsov.artyom@gmail.com (Artyom V. Poptsov)
Cc: 51998@debbugs.gnu.org
Subject: [bug#51998] [PATCH] gnu: Add guile-gitlab
Date: Thu, 25 Nov 2021 11:28:59 +0000	[thread overview]
Message-ID: <87h7c0mq2s.fsf@gnu.org> (raw)
In-Reply-To: <87ilwmzzi7.fsf@gmail.com> (Artyom V. Poptsov's message of "Sat,  20 Nov 2021 17:13:20 +0300")


Hello Artyom,

Thanks for this first contribution! I think that there is a small issue
with the library path. The gitlab.scm files is in:

--8<---------------cut here---------------start------------->8---
/gnu/store/xn0bnrh23iscxy7xsvzqffyjy4wqy1q6-guile-gitlab-0.1.0/share/guile-gitlab/gitlab.scm
--8<---------------cut here---------------end--------------->8---

whereas it should be in:

--8<---------------cut here---------------start------------->8---
/gnu/store/xn0bnrh23iscxy7xsvzqffyjy4wqy1q6-guile-gitlab-0.1.0/share/guile/site/2.2/gitlab.scm
--8<---------------cut here---------------end--------------->8---

I also have the following error when running gitlab-cli:

--8<---------------cut here---------------start------------->8---

           0 (scm-error misc-error #f "~A ~S" ("no code for modu…" …) …)

ERROR: In procedure scm-error:
no code for module (gitlab)
--8<---------------cut here---------------end--------------->8---

that should be solved by adjusting the library path.

Thanks,

Mathieu




  reply	other threads:[~2021-11-25 11:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-20 14:13 [bug#51998] [PATCH] gnu: Add guile-gitlab Artyom V. Poptsov
2021-11-25 11:28 ` Mathieu Othacehe [this message]
2021-11-26 19:20   ` Artyom V. Poptsov
2021-11-27 11:21     ` Mathieu Othacehe
2021-11-27 19:02       ` Artyom V. Poptsov
2021-11-28 10:04         ` bug#51998: " Mathieu Othacehe
2021-11-28 18:07           ` [bug#51998] " Artyom V. Poptsov
2021-11-28 21:36             ` Mathieu Othacehe

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h7c0mq2s.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=51998@debbugs.gnu.org \
    --cc=poptsov.artyom@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).