From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: guix-devel@gnu.org
Subject: Re: Problem with emacs-libgit
Date: Tue, 17 May 2022 07:02:49 -0500 [thread overview]
Message-ID: <87wnekgydy.fsf@gmail.com> (raw)
In-Reply-To: <87r14tb0to.fsf@rohleder.de> (Michael Rohleder's message of "Mon, 16 May 2022 23:54:27 +0200")
Michael Rohleder writes:
> This looks like https://issues.guix.gnu.org/55427
I tried to update emacs yesterday and ran into this issue, and a few
other issues with emacs packages as well. I was surprised that we merged
an update to emacs when some packages (well used ones at that) were
failing to build.
I realize emacs has a large tree of packages depending on it, but I've
always been taught to check to ensure everything remains building. This
makes sense to me because I thought one of the reasons a distribution
exists is to handle the integration of everything for its users. This
seems like it breaks that ethos.
Can anyone point me to some documentation or explain how these decisions
are made? All I could find was this:
For important changes, check that dependent packages (if applicable)
are not affected by the change
https://guix.gnu.org/en/manual/devel/en/guix.html#Submitting-Patches
Thank you to all the contributors.
--
Katherine
next prev parent reply other threads:[~2022-05-17 13:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 20:31 Problem with emacs-libgit Zelphir Kaltstahl
2022-05-16 21:54 ` Michael Rohleder
2022-05-17 12:02 ` Katherine Cox-Buday [this message]
2022-05-17 7:29 ` Zhu Zihao
2022-05-17 19:49 ` Zelphir Kaltstahl
2022-05-17 9:27 ` Maxime Devos
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=87wnekgydy.fsf@gmail.com \
--to=cox.katherine.e@gmail.com \
--cc=guix-devel@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).