[bug#30153] [PATCH] gnu: emacs-org: Update to 20180115.

[Nicolas Goaziou <mail@nicolasgoaziou.fr>]

Hello,

Vasile Dumitrascu <va511e@yahoo.com> writes:

>   First, please ignore the initial patch, as the commit was done on a
> wrong file version. Second, please find attached the correct patch that
> updates emacs-org and changes the source repository to the original
> orgmode.org as elpa does not track and have all the updates published
> officially.
>
>   I think tracking directly the orgmode repo should be better than
> tracking a elpa. Currently for example, in the original repo there are
> releases that are not present in elpa.

Thank you.

However, so far, I only published tagged releases. For example, the
latest tagged release (aka Org 9.1.6) is org-20180103.tar. Other
releases are cuts from the stable branch. IMO, we should keep it that
way.

There is an issue with Org repo and ELPA at the moment, but they should
usually be mirrors. IIUC, keeping ELPA as the source allows the ELPA
updater to function properly. So, perhaps we should temporarily move to
orgmode.org, until mirroring is fixed, then switch back to ELPA.

>      ;; emacs-org-contrib inherits from this package.  Please update its sha256
>      ;; checksum as well.

Per comment, you need to update emacs-org-contrib package as well.

> -    (version "20171205")
> +    (version "20180115")

See above. It should probably be org-20180103.tar.

>      (source (origin
>                (method url-fetch)
> -              (uri (string-append "http://elpa.gnu.org/packages/org-"
> +              (uri (string-append "http://orgmode.org/elpa/org-"

"https://orgmode.org/elpa/org-"

>                                    version ".tar"))
>                (sha256
>                 (base32
> -                "0a1rm94ci47jf5579sxscily680ysmy3hnxjcs073n45nk76za04"))))
> +                "1zc75kxbx9bk1xag46s027a290fnva1id8vv92lz9i5nkqnrm430"))))
>      (build-system emacs-build-system)
>      (home-page "http://orgmode.org/")

Albeit not directly related to your patch, this should also be fixed
(http -> https).

Regards,

-- 
Nicolas Goaziou                                                0x80A93738