From: ng0 <contact.ng0@cryptolab.net>
To: Catonano <catonano@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: gspell
Date: Wed, 22 Feb 2017 14:43:29 +0000 [thread overview]
Message-ID: <20170222144329.tx3mx3ss6yix57pp@wasp> (raw)
In-Reply-To: <CAJ98PDz4LRx4rPAYw7iEv+ud5fvpY9wz0c5KbZYnJXZ9LmxfVg@mail.gmail.com>
On 17-02-22 15:17:32, Catonano wrote:
> 2017-02-22 14:52 GMT+01:00 ng0 <contact.ng0@cryptolab.net>:
>
> > On 17-02-22 13:44:25, Catonano wrote:
> > > This package doesn't build
> > >
> > > https://gitlab.com/humanitiesNerd/guix-hacks/blob/polari/
> > gnu/packages/gnome.scm#L622
> >
> > if this is equivalent to the master tree, can you rebase and send an
> > patch in the format of git format-patch so that it can be reproduced?
> > That's easier to help with.
> >
>
> Well, it seems that the master branch did prrogress some, since when I made
> my branch
>
> Now, when I "git rebase master" I get
>
> $ git rebase master
> /home/catonano/.guix-profile/libexec/git-core/git-sh-setup: riga 46:
> /home/catonano/.guix-profile/libexec/git-core:
> /home/catonano/.guix-profile/libexec/git-core:
> /home/catonano/.guix-profile/libexec/git-core/git-sh-i18n: File o directory
> non esistente
>
> "riga" is "line"
>
> What does this mean ?
A premature fix is to export GIT_EXEC_PATH="/home/ng0/.guix-profile/libexec/git-core"
this was introduced some commits ago by David.
prev parent reply other threads:[~2017-02-22 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 12:44 gspell Catonano
2017-02-22 13:52 ` gspell ng0
2017-02-22 14:17 ` gspell Catonano
2017-02-22 14:43 ` ng0 [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=20170222144329.tx3mx3ss6yix57pp@wasp \
--to=contact.ng0@cryptolab.net \
--cc=catonano@gmail.com \
--cc=help-guix@gnu.org \
/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).