Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Support]: downgrading a built-in package #404

Open
2 of 3 tasks
tsujp opened this issue Jan 18, 2025 · 0 comments
Open
2 of 3 tasks

[Support]: downgrading a built-in package #404

tsujp opened this issue Jan 18, 2025 · 0 comments

Comments

@tsujp
Copy link

tsujp commented Jan 18, 2025

Confirmation

  • I have checked the documentation (README, Wiki, docstrings, etc)
  • I am checking these without reading them.
  • I have searched previous issues to see if my question is a duplicate.

Elpaca Version

Elpaca 481d921 HEAD -> master, origin/master, origin/HEAD
installer: 0.8
emacs-version: GNU Emacs 31.0.50 (build 1, aarch64-apple-darwin23.5.0, NS appkit-2487.60 Version 14.5 (Build 23F79))
of 2025-01-12
git --version: git version 2.47.1

Operating System

macOS

Description

I've got a build of Emacs from upstream master (so 31.0.50) and that has Tramp 2.8.0pre, but I need to use Tramp 2.7.2 as the former has a bug in it. I saw the other thread on upgrading built-in packages, I tried those approaches to no avail.

How can I downgrade a built-in package when I use Elpaca?

@tsujp tsujp changed the title [Bug/Support]: [Support]: downgrading a built-in package Jan 18, 2025
progfolio added a commit that referenced this issue Feb 2, 2025
docs: document basic usage
elpaca-menu-functions: add elpaca-menu-lock-file
elpaca-load-lockfile: remove
elpaca-lock-file: user option to set lock file
elpaca-menu-lock-file: menu to defer to lock file recipes
elpaca--lock-file-init-p: predicate to exclude non-init elpacas
elpaca-lock-file-functions: filtering hook for elpaca-write-lock-file
elpaca-write-lock-file: command to write lock files

Related: #24 #151 #404 #405
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant