From: Ricardo Wurmus <rekado@elephly.net>
To: ng0@crash.cx
Cc: 30401@debbugs.gnu.org
Subject: bug#30401: gitolite some important hooks not working
Date: Sun, 11 Feb 2018 22:18:39 +0100 [thread overview]
Message-ID: <87r2pri5sg.fsf@elephly.net> (raw)
In-Reply-To: <87h8qquxzj.fsf@abyayala.i-did-not-set--mail-host-address--so-tickle-me>
ng0@crash.cx writes:
> A paste that lost its formatting but speaks for itself:
>
> Counting objects: 4, done.
> Delta compression using up to 4 threads.
> Compressing objects: 100% (3/3), done.
> Writing objects: 100% (4/4), 1.03 KiB | 1.03 MiB/s, done.
> Total 4 (delta 0), reused 0 (delta 0)
> remote: Can't locate Data/Dumper.pm in @INC (you may need to
> install the Data::Dumper module) (@INC contains:
> /gnu/store/v3k3dmkdaz3giap6ir06dj12sid42086-gitolite-3.6.6/share/gitolite/lib
> /home/git/.guix-profile/lib/perl5/site_perl /etc/perl
> /usr/local/lib/x86_64-linux-gnu/perl/5.24.1
> /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24
> /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24
> /usr/share/perl/5.24 /usr/local/lib/site_perl
> /usr/lib/x86_64-linux-gnu/perl-base .) at
Have you tried propagating the perl-data-dumper package? Or did you try
wrapping the executable in the PERL5LIB environment variable after
adding the package?
> Installing the module + perl into the profile didn't help either.
The gitolite executables need to be made aware of the location of the
Perl modules, so it’s expected that this wouldn’t help.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2018-02-11 23:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 12:52 bug#30401: gitolite some important hooks not working ng0
2018-02-09 15:50 ` Clément Lassieur
2018-02-11 21:18 ` Ricardo Wurmus [this message]
2018-02-11 23:12 ` ng0
2018-02-12 15:07 ` Ricardo Wurmus
2021-11-24 23:47 ` 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=87r2pri5sg.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=30401@debbugs.gnu.org \
--cc=ng0@crash.cx \
/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.