From: Holger Peters <holger.peters@posteo.de>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix@gnu.org
Subject: Re: Trouble packaging a ruby dependency
Date: Sat, 5 Dec 2020 08:05:16 +0100 [thread overview]
Message-ID: <95EA4BE9-6D20-4DE0-81B1-81325CB5B560@posteo.de> (raw)
In-Reply-To: <X8rOodwQl8IEiUFN@jasmine.lan>
Hi,
sorry I should have updated on this question.
After some more time investigating the issue I found that libgit2 was in an
outdated version and I submitted a patch to bump the version
https://issues.guix.gnu.org/44945
That’s why the build now succeeds.
I have submitted ruby-rugged for addition to guix here
https://issues.guix.gnu.org/44946
Holger
> Am 05.12.2020 um 01:04 schrieb Leo Famulari <leo@famulari.name>:
>
> On Sat, Nov 28, 2020 at 10:41:08PM +0100, Holger Peters wrote:
>> I have problems building `ruby-rugged'. The patch below is as far as I get,
>> however it fails with an error message I cannot quite debug. Maybe part of
>> the
>> problem is that `ruby-rugged' bundls libgit and I try to have it use the
>> system-provided on.
>>
>> +(define-public ruby-rugged
>
> I added your package based on Guix Git commit
> 86d635b85035086d21c319f31f628761df5c82e5 (gnu: ruby-regexp-parser:
> Update to 2.0.0.), and it built fine for me on x86_64.
>
> I'm not sure what went wrong, but please try again. If it still does not
> work, please let us know :)
prev parent reply other threads:[~2020-12-05 12:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 21:41 Trouble packaging a ruby dependency Holger Peters
2020-12-05 0:04 ` Leo Famulari
2020-12-05 7:05 ` Holger Peters [this message]
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=95EA4BE9-6D20-4DE0-81B1-81325CB5B560@posteo.de \
--to=holger.peters@posteo.de \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
/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.
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).