From: "Miguel Ángel Moreno" <mail@migalmoreno.com>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: mail@migalmoreno.com, 62199@debbugs.gnu.org,
"Ludovic Courtès" <ludo@gnu.org>,
"Andrew Tropin" <andrew@trop.in>
Subject: [bug#62199] [PATCH v5] gnu: Add emacs-fdroid.
Date: Sun, 11 Feb 2024 21:41:45 +0100 [thread overview]
Message-ID: <864jeeivhy.fsf@migalmoreno.com> (raw)
In-Reply-To: <f2250dc30aa1a6cdff6279e10b49906208df0cef.camel@gmail.com> (Liliana Marie Prikler's message of "Mon, 28 Aug 2023 21:42:20 +0200")
On 2023-08-28 21:42, Liliana Marie Prikler wrote:
> Am Montag, dem 28.08.2023 um 07:46 +0400 schrieb Andrew Tropin:
>> On 2023-08-28 07:44, Andrew Tropin wrote:
>>
>> > On 2023-08-26 18:10, Miguel Ángel Moreno wrote:
>> > > Thanks for the heads up. It seems like the googletest package is
>> > > the culprit of this issue. As I alluded to earlier, can we
>> > > proceed without the fdroidcl input in that case? Given as it's
>> > > been almost 6 months since this issue was raised.
>> >
>> > Seems as a reasonable option for me.
>>
>> Added Liliana to Cc.
> I mean, if emacs-xyz doesn't work, you could try moving the package to
> (gnu packages android). More importantly, the home-page and origin URL
> appear to be dead from my end, so they need updating :(
>
> As for the package itself, I'd prefer if it was working out of the box,
> but I'm willing to commit v1 if we're sure that we've exhausted all
> other reasonable options.
>
> Cheers
Hi,
Since the package still didn't build with v5, I sent a v6 with your
proposed solution, included it in (gnu packages android) and amended the
source and home-page. It now builds fine for me, even with the froidcl
input.
--
Best regards,
Miguel Ángel Moreno
next prev parent reply other threads:[~2024-02-12 6:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 12:14 [bug#62199] [PATCH] gnu: Add emacs-fdroid conses
2023-03-20 22:54 ` Sergey Trofimov
2023-03-21 7:50 ` conses
2023-03-21 8:21 ` Sergey Trofimov
2023-03-21 8:55 ` Sergey Trofimov
2023-03-21 9:02 ` Nicolas Goaziou
2023-03-21 7:47 ` [bug#62199] [PATCH v2] " conses
2023-03-21 9:24 ` [bug#62199] [PATCH v3] " conses
2023-03-21 9:30 ` Nicolas Goaziou
2023-03-21 10:41 ` [bug#62199] [PATCH v4] " conses
2023-03-24 9:19 ` Nicolas Goaziou via Guix-patches
2023-06-08 19:12 ` Miguel Ángel Moreno
2023-06-08 19:10 ` [bug#62199] [PATCH v5] " Miguel Ángel Moreno
2023-06-10 19:43 ` Nicolas Goaziou
2023-06-13 10:50 ` Andrew Tropin
2023-06-21 9:59 ` Miguel Ángel Moreno
2023-08-20 17:40 ` Miguel Ángel Moreno
2023-08-24 13:58 ` Andrew Tropin
2023-08-26 16:10 ` Miguel Ángel Moreno
2023-08-28 3:44 ` Andrew Tropin
2023-08-28 3:46 ` Andrew Tropin
2023-08-28 19:42 ` Liliana Marie Prikler
2024-02-11 20:41 ` Miguel Ángel Moreno [this message]
2024-02-11 20:38 ` [bug#62199] [PATCH v6] " Miguel Ángel Moreno
2024-02-18 14:57 ` bug#62199: " Ludovic Courtès
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=864jeeivhy.fsf@migalmoreno.com \
--to=mail@migalmoreno.com \
--cc=62199@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=liliana.prikler@gmail.com \
--cc=ludo@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.
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).