Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.cmdline beat.cmdline
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 22
    • Issues 22
    • 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
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.cmdlinebeat.cmdline
  • Issues
  • #57
Closed
Open
Issue created Mar 07, 2019 by Jaden DIEFENBAUGH@jdiefenbaughContributor

Not compatible with newest bob-devel version

See beat.editor#202 (closed) for how I found this & a hack to fix it

Using the default conda environment creation config, beat.cmdline can't be installed to the same environment as bob-devel=2019.2.11. This also pops up when trying to create an environment for beat.web using conda env create -f dev.yml:

Collecting package metadata: done
Solving environment: failed

UnsatisfiableError: The following specifications were found to be in conflict:
  - beat.cmdline
  - bob-devel=2019.02.11
Use "conda search <package> --info" to see the dependencies for each package.

This marks the third place this issue has shown up, and so I'm opening an issue in this package. I'll mark it as critical because this is an issue in the CI as well.

Assignee
Assign to
Time tracking