unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Oleg Pyhalov <go.wigust@gmail.com>
To: Brian Leung <bkleung89@gmail.com>
Cc: 36999@debbugs.gnu.org
Subject: [bug#36999] [PATCH] gnu: Add emacs-forge.
Date: Sun, 18 Aug 2019 12:26:25 +0300	[thread overview]
Message-ID: <874l2erfi6.fsf@majordomo.ru> (raw)
In-Reply-To: <CAAc=MEyGTJ5rc1v_0rTXacx6ViXk6RUy-qVgwmj6b_pLarj8ng@mail.gmail.com> (Brian Leung's message of "Wed, 14 Aug 2019 08:08:23 +0200")

[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]

Hi Brian,

Apologies for a delay with response.

Brian Leung <bkleung89@gmail.com> writes:

> Hi Oleg,
>
> I've made a patch off the latest master branch with a version of emacs-ghub
> that should meet the requirements of emacs-forge.

Thank you!

[…]

>> I notice that emacs-forge, in its forge-pkg.el file, mentions newer
>> dependencies than what we currently have: ghub version 20190319, which
>> apparently contains a fix for a relevant bug; and Magit version 20190408.
>> I'm not sure how important the update to Magit is, and this newer version
>> of Magit also happens to depend on an additional package, libegit2. It
>> might be nice to update our version of ghub.

Unfortunately Magit update is needed, because on a GitLab instance you
could list issues but not open them to take a look on a content.

New Magit requires https://github.com/magit/libegit2 which I try to
build, but stuck.  I succeeded to build ‘libgit2.so’ and load it in
Emacs, but ‘featurep’ procedure says that feature is not loaded.

I think we should not merge partially working emacs-forge.

Regards,
Oleg.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2019-08-18  9:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-10 16:18 [bug#36999] [PATCH] gnu: Add emacs-forge Oleg Pykhalov
2019-08-11 17:39 ` Brian Leung
2019-08-14  6:08   ` Brian Leung
2019-08-18  9:26     ` Oleg Pyhalov [this message]
2019-10-05 19:19 ` [bug#36999] [PATCH 0/4] More test and then merge to master Oleg Pykhalov
2019-10-05 19:19   ` [bug#36999] [PATCH 1/4] gnu: emacs-magit: Update to 2.90.1-1.c761d28 Oleg Pykhalov
2019-10-05 19:19   ` [bug#36999] [PATCH 2/4] gnu: emacs-ghub: Update to 3.2.0-1.cf0b13a Oleg Pykhalov
2019-10-05 19:19   ` [bug#36999] [PATCH 3/4] gnu: emacs-closql: Update to 1.0.0-1.70b98db Oleg Pykhalov
2019-10-05 19:19   ` [bug#36999] [PATCH 4/4] gnu: Add emacs-forge Oleg Pykhalov
2019-10-13 19:45 ` bug#36999: emacs-forge pushed to master Oleg Pykhalov

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=874l2erfi6.fsf@majordomo.ru \
    --to=go.wigust@gmail.com \
    --cc=36999@debbugs.gnu.org \
    --cc=bkleung89@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).