Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
S src
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Pmodules
  • src
  • Issues
  • #155

Closed
Open
Created Jan 24, 2022 by bliven_s@bliven_s

Dependency conflicts are not transitive

In order to specify module conflicts it's currently necessary to add the 'conflict' clause to the modulefiles of both packages. This can lead to bugs: today I noticed that anaconda is marked as conflicting with psi-python*, but not vice versa. This means that if anaconda is loaded before psi-python27 then no error is reported.

Is this something that pmodules should handle (by checking conflict lines of currently loaded packages during load operations), or is it just something to be aware of when writing module files?

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking