GNU bug report logs -
#34865
[PATCH] Add emacs-zones.
Previous Next
Reported by: Brian Leung <bkleung89 <at> gmail.com>
Date: Fri, 15 Mar 2019 00:34:01 UTC
Severity: normal
Tags: patch
Done: Oleg Pykhalov <go.wigust <at> gmail.com>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 34865 in the body.
You can then email your comments to 34865 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
guix-patches <at> gnu.org
:
bug#34865
; Package
guix-patches
.
(Fri, 15 Mar 2019 00:34:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Brian Leung <bkleung89 <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
guix-patches <at> gnu.org
.
(Fri, 15 Mar 2019 00:34:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
See attached.
[Message part 2 (text/html, inline)]
[0001-gnu-Add-emacs-zones.patch (text/x-patch, attachment)]
Information forwarded
to
guix-patches <at> gnu.org
:
bug#34865
; Package
guix-patches
.
(Sat, 16 Mar 2019 10:57:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 34865 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hello Brian,
Could we use emacs-zones from Elpa? See
https://elpa.gnu.org/packages/zones.html . ‘guix import elpa
emacs-zones’ will produce a decent ‘origin’ record to pull a source.
Please, don't forget to add a changelog entry to commit message:
* gnu/packages/emacs-xyz.scm (emacs-zones): New variable.
If you use Magit you could type ‘add’ to paste a yasnippet from
‘etc/snippets/’ Guix Git repository. Add this directory to
‘yas-snippet-dirs’, see
https://www.gnu.org/software/guix/manual/en/html_node/The-Perfect-Setup.html
Thanks,
Oleg.
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
guix-patches <at> gnu.org
:
bug#34865
; Package
guix-patches
.
(Fri, 22 Mar 2019 21:38:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 34865 <at> debbugs.gnu.org (full text, mbox):
Hi Oleg,
Oleg Pykhalov <go.wigust <at> gmail.com> skribis:
> Could we use emacs-zones from Elpa? See
> https://elpa.gnu.org/packages/zones.html . ‘guix import elpa
> emacs-zones’ will produce a decent ‘origin’ record to pull a source.
My understanding is that ELPA and MELPA tarballs are not necessarily
persistent and immutable, and that we generally prefer referring
directly to the upstream repo.
Or am I confusing things?
Ludo’.
Information forwarded
to
guix-patches <at> gnu.org
:
bug#34865
; Package
guix-patches
.
(Sun, 24 Mar 2019 20:02:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 34865 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi Ludovic,
Ludovic Courtès <ludo <at> gnu.org> writes:
[…]
>> Could we use emacs-zones from Elpa? See
>> https://elpa.gnu.org/packages/zones.html . ‘guix import elpa
>> emacs-zones’ will produce a decent ‘origin’ record to pull a source.
>
> My understanding is that ELPA and MELPA tarballs are not necessarily
> persistent and immutable, and that we generally prefer referring
> directly to the upstream repo.
Ouch, I thought ELPA is persistent. That's a significant argument to
not use ELPA for our purposes :-( .
> Or am I confusing things?
We preferred ELPA over GitHub's Git repositories in emacs-xys.scm
(emacs.scm in past), didn't we?
Oleg.
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
guix-patches <at> gnu.org
:
bug#34865
; Package
guix-patches
.
(Tue, 26 Mar 2019 09:40:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 34865 <at> debbugs.gnu.org (full text, mbox):
Hi Oleg,
Oleg Pykhalov <go.wigust <at> gmail.com> skribis:
> Ludovic Courtès <ludo <at> gnu.org> writes:
>
> […]
>
>>> Could we use emacs-zones from Elpa? See
>>> https://elpa.gnu.org/packages/zones.html . ‘guix import elpa
>>> emacs-zones’ will produce a decent ‘origin’ record to pull a source.
>>
>> My understanding is that ELPA and MELPA tarballs are not necessarily
>> persistent and immutable, and that we generally prefer referring
>> directly to the upstream repo.
>
> Ouch, I thought ELPA is persistent. That's a significant argument to
> not use ELPA for our purposes :-( .
>
>> Or am I confusing things?
>
> We preferred ELPA over GitHub's Git repositories in emacs-xys.scm
> (emacs.scm in past), didn't we?
Hmmm, not sure, Ricardo, what’s the story? :-)
Ludo’.
Information forwarded
to
guix-patches <at> gnu.org
:
bug#34865
; Package
guix-patches
.
(Tue, 26 Mar 2019 10:57:01 GMT)
Full text and
rfc822 format available.
Message #20 received at 34865 <at> debbugs.gnu.org (full text, mbox):
Ludovic Courtès <ludo <at> gnu.org> writes:
> Hi Oleg,
>
> Oleg Pykhalov <go.wigust <at> gmail.com> skribis:
>
>> Ludovic Courtès <ludo <at> gnu.org> writes:
>>
>> […]
>>
>>>> Could we use emacs-zones from Elpa? See
>>>> https://elpa.gnu.org/packages/zones.html . ‘guix import elpa
>>>> emacs-zones’ will produce a decent ‘origin’ record to pull a source.
>>>
>>> My understanding is that ELPA and MELPA tarballs are not necessarily
>>> persistent and immutable, and that we generally prefer referring
>>> directly to the upstream repo.
>>
>> Ouch, I thought ELPA is persistent. That's a significant argument to
>> not use ELPA for our purposes :-( .
I only know that MELPA isn’t immutable. I assumed that ELPA is fine.
>> We preferred ELPA over GitHub's Git repositories in emacs-xys.scm
>> (emacs.scm in past), didn't we?
>
> Hmmm, not sure, Ricardo, what’s the story? :-)
I don’t think we did. I can’t think of even one case where we switched
from git-fetch from GitHub to url-fetch from ELPA.
git-fetch is the preferred way when there are no stable tarballs.
--
Ricardo
Information forwarded
to
guix-patches <at> gnu.org
:
bug#34865
; Package
guix-patches
.
(Wed, 27 Mar 2019 10:58:01 GMT)
Full text and
rfc822 format available.
Message #23 received at 34865 <at> debbugs.gnu.org (full text, mbox):
Hello,
Ricardo Wurmus <rekado <at> elephly.net> skribis:
> Ludovic Courtès <ludo <at> gnu.org> writes:
[...]
>>>>> Could we use emacs-zones from Elpa? See
>>>>> https://elpa.gnu.org/packages/zones.html . ‘guix import elpa
>>>>> emacs-zones’ will produce a decent ‘origin’ record to pull a source.
>>>>
>>>> My understanding is that ELPA and MELPA tarballs are not necessarily
>>>> persistent and immutable, and that we generally prefer referring
>>>> directly to the upstream repo.
>>>
>>> Ouch, I thought ELPA is persistent. That's a significant argument to
>>> not use ELPA for our purposes :-( .
>
> I only know that MELPA isn’t immutable. I assumed that ELPA is fine.
[...]
> git-fetch is the preferred way when there are no stable tarballs.
So, Oleg, I think you can go either way, but fetching over Git is
probably safer.
Can you apply the patch?
Thanks,
Ludo’.
Reply sent
to
Oleg Pykhalov <go.wigust <at> gmail.com>
:
You have taken responsibility.
(Wed, 27 Mar 2019 19:28:01 GMT)
Full text and
rfc822 format available.
Notification sent
to
Brian Leung <bkleung89 <at> gmail.com>
:
bug acknowledged by developer.
(Wed, 27 Mar 2019 19:28:02 GMT)
Full text and
rfc822 format available.
Message #28 received at 34865-done <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hello,
Ludovic Courtès <ludo <at> gnu.org> writes:
[…]
>>>>>> Could we use emacs-zones from Elpa? See
>>>>>> https://elpa.gnu.org/packages/zones.html . ‘guix import elpa
>>>>>> emacs-zones’ will produce a decent ‘origin’ record to pull a source.
>>>>>
>>>>> My understanding is that ELPA and MELPA tarballs are not necessarily
>>>>> persistent and immutable, and that we generally prefer referring
>>>>> directly to the upstream repo.
>>>>
>>>> Ouch, I thought ELPA is persistent. That's a significant argument to
>>>> not use ELPA for our purposes :-( .
>>
>> I only know that MELPA isn’t immutable. I assumed that ELPA is fine.
>
> [...]
>
>> git-fetch is the preferred way when there are no stable tarballs.
>
> So, Oleg, I think you can go either way, but fetching over Git is
> probably safer.
>
> Can you apply the patch?
OK, pushed as c881ed8698517a2c2007c2fdc3a7aeec52ff109c with a source
fetching over Git.
Thanks,
Oleg.
[signature.asc (application/pgp-signature, inline)]
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Thu, 25 Apr 2019 11:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 6 years and 109 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.