From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 43292@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: [bug#43292] [PATCH] gnu: emacs-org-contrib: Fix hash for version 20200907.
Date: Wed, 09 Sep 2020 16:05:08 +0200 [thread overview]
Message-ID: <87k0x3m4ff.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <a791e620a6b4c532ba9262c7f936c5ba@tobias.gr> (Tobias Geerinckx-Rice's message of "Wed, 09 Sep 2020 15:35:07 +0200")
Tobias Geerinckx-Rice <me@tobias.gr> writes:
> Nicolas,
>
> On 2020-09-09 15:23, Nicolas Goaziou wrote:
>> Package is updated automatically either every Monday, provided there is
>> at least a pending commits since last update, or whenever a new Org is
>> released.
>>
>> When new Org is released on a Monday, two updates happen the same day,
>> and therefore share the same version. It is unfortunate, but quite rare
>> in practice, and when the day is over, the source file cannot change
>
> Thanks for taking the time to explain.
>
> It seems like the best ‘fix’ is for distributions (that don't like
> in-place updates) to simply wait a day after such a release. Would
> that make sense?
Indeed. Never updating emacs-org or emacs-org-contrib on a Monday should
prevent this kind of issue.
Regards,
next prev parent reply other threads:[~2020-09-09 14:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 11:35 [bug#43292] [PATCH] gnu: emacs-org-contrib: Fix hash for version 20200907 zimoun
2020-09-09 11:50 ` Tobias Geerinckx-Rice via Guix-patches via
2020-09-09 12:03 ` zimoun
2020-09-09 13:23 ` Nicolas Goaziou
2020-09-09 13:35 ` Tobias Geerinckx-Rice via Guix-patches via
2020-09-09 14:05 ` Nicolas Goaziou [this message]
2020-09-09 14:00 ` zimoun
2020-09-09 12:33 ` bug#43292: " Tobias Geerinckx-Rice via Guix-patches via
2020-09-09 12:56 ` [bug#43292] " zimoun
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=87k0x3m4ff.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=43292@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=zimon.toutoune@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).