Pinning Magit to Melpa Stable
Jonas Bernoulli edited this page Mar 25, 2022
·
1 revision
To pin Magit and some related packages to Melpa-Stable, you have to do the following.
- If you haven’t added Melpa-Stable to
package-archives
yet, then you have to do so now. Add Melpa-Stable the same way you have added Melpa. The simplest form to do so is:(add-to-list 'package-archives '("melpa-stable" . "https://stable.melpa.org/packages/") t)
- Add Magit and the other packages to
package-pinned-packages
.(add-to-list 'package-pinned-packages '(magit . "melpa-stable")) (add-to-list 'package-pinned-packages '(ghub . "melpa-stable")) (add-to-list 'package-pinned-packages '(git-commit . "melpa-stable")) (add-to-list 'package-pinned-packages '(magit-popup . "melpa-stable")) (add-to-list 'package-pinned-packages '(with-editor . "melpa-stable"))
Right now these other packages still support Emacs
24.4
and24.5
, but that might change, so it is better to pin them now too. - Uninstall and then reinstall the pinned packages.
M-x package-delete RET magit RET M-x package-delete RET ghub RET M-x package-delete RET git-commit RET M-x package-delete RET magit-popup RET M-x package-delete RET with-editor RET M-x package-install RET magit RET
This is necessary because otherwise you would get stuck on snapshot versions such as
20180601.1234
, instead of “downgrading” to2.13.0
. Eventually a2.13.1
bugfix release will be created and if you haven’t installed2.13.0
by then, then you will be stock on a snapshot version (because Melpa-style snapshot version strings are always higher versions according toversion<
et al. than any released version).