Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • C clpm
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 31
    • Issues 31
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • clpm
  • clpm
  • Issues
  • #53

Closed
Open
Created Jan 28, 2022 by Cameron Pittman@cameronpDeveloper

CLPM fails with contexts that start with `~`

The problem is either that CLPM fails to warn users when it cannot find the clpmfile given as context, or that it fails to properly handle contexts that use ~ instead of a full path to the home directory.

Steps to reproduce:

  1. Go to a repo. Change dependencies in an .asd file
  2. (clpm-client:activate-context #p"~/foo/bar/clpmfile")
  3. (clpm-client:install)
  4. Observe that CLPM wants to remove dependencies
  5. In a terminal in the same repo, run clpm bundle install. Note that it will not prompt to uninstall dependencies

Re-running step 2 with the full path (no ~) will result in expected behavior.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking