Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D
dune-common
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 42
    • Issues 42
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 24
    • Merge Requests 24
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Core Modules
  • dune-common
  • Issues
  • #9

Closed
Open
Opened Jan 05, 2016 by Dominic Kempf@dominic
  • Report abuse
  • New issue
Report abuse New issue

dunecontrol [IMO] overeagerly checks for version matches

A typical workflow of mine is to type things like this:

dunecontrol exec git checkout releases/2.4
dunecontrol exec git checkout master

This works perfectly fine, if all modules are on compatible branches. However, if they are not, dunecontrol errors out instead of just executing the command.

This would not be very disturbing, if it would not occur in the following scenario: I switch to release branch of all modules until I encounter one that does not have a branch of that name. dunecontrol then errors out and I end up with only half of my modules being switched, resulting in incompatible branches...

In this case, I consider this a bug.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
No due date
1
Labels
buildsystem
Assign labels
  • View project labels
Reference: core/dune-common#9