Message ID | 20220604152340.5447-1-dev@jpoiret.xyz |
---|---|
State | Accepted |
Headers | show |
Series | [bug#55795] gnu: emacs-next: Update to 0a5477b4. | expand |
Context | Check | Description |
---|---|---|
cbaines/comparison | success | View comparision |
cbaines/git branch | success | View Git branch |
cbaines/applying patch | success | View Laminar job |
cbaines/issue | success | View issue |
Am Samstag, dem 04.06.2022 um 17:23 +0200 schrieb Josselin Poiret: > * gnu/packages/emacs.scm (emacs-next): Update to > 0a5477b448e6b62bcedc1803e531ec7686eea48d, fixing emacs bug 55149 > that breaks magit among others. Is that bug present in 28.0.92? If not, I suggest using that instead of a random commit – it is a pre-release after all. Cheers
Hello Lily, Liliana Marie Prikler <liliana.prikler@gmail.com> writes: > Am Samstag, dem 04.06.2022 um 17:23 +0200 schrieb Josselin Poiret: >> * gnu/packages/emacs.scm (emacs-next): Update to >> 0a5477b448e6b62bcedc1803e531ec7686eea48d, fixing emacs bug 55149 >> that breaks magit among others. > Is that bug present in 28.0.92? If not, I suggest using that instead > of a random commit – it is a pre-release after all. Isn't our emacs package already 28.1, and emacs-next at a commit on master past 28.1? This just updates emacs-next further along master so that the fix commit 799c7e277fc6a37bd8b86fea7494ff6df63f3eb1 is included. Context: I'm using emacs-next-pgtk and magit broke because of that commit. Best,
Am Sonntag, dem 05.06.2022 um 10:36 +0200 schrieb Josselin Poiret: > Hello Lily, > > Liliana Marie Prikler <liliana.prikler@gmail.com> writes: > > Am Samstag, dem 04.06.2022 um 17:23 +0200 schrieb Josselin Poiret: > > > * gnu/packages/emacs.scm (emacs-next): Update to > > > 0a5477b448e6b62bcedc1803e531ec7686eea48d, fixing emacs bug 55149 > > > that breaks magit among others. > > Is that bug present in 28.0.92? If not, I suggest using that > > instead of a random commit – it is a pre-release after all. > > Isn't our emacs package already 28.1, and emacs-next at a commit on > master past 28.1? This just updates emacs-next further along master > so that the fix commit 799c7e277fc6a37bd8b86fea7494ff6df63f3eb1 is > included. Sorry, looks like I was a little confused back when I wrote that. I cleaned up your commit and pushed it. Thanks
diff --git a/gnu/packages/emacs.scm b/gnu/packages/emacs.scm index 78560b477d..ef24df8950 100644 --- a/gnu/packages/emacs.scm +++ b/gnu/packages/emacs.scm @@ -321,7 +321,7 @@ (define* (emacs-byte-compile-directory dir) (license license:gpl3+))) (define-public emacs-next - (let ((commit "38d87c43c2ad727406dcfe316aac5e24e202c251") + (let ((commit "0a5477b448e6b62bcedc1803e531ec7686eea48d") (revision "0")) (package (inherit emacs) @@ -337,7 +337,7 @@ (define-public emacs-next (file-name (git-file-name name version)) (sha256 (base32 - "0h206asgaqfzhz36p78n23yj4p7kbr6a1f0j0njzxf0ypqrmw9yr")))) + "0dqmrawkvbypxp8gcnspnhhmfamzp3l62gfgp1pw2l6svz58v991")))) (native-inputs (modify-inputs (package-native-inputs emacs) (prepend autoconf))))))