Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
thg
thg
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 798
    • Issues 798
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

There will be about 1h of downtime on 2020-03-02 at 13:00 UTC+1 (change of servers and upgrade to Heptapod 0.20.0 final)

  • mercurial
  • TortoiseHg
  • thgthg
  • Issues
  • #5281

Closed
Open
Opened Nov 19, 2018 by Bitbucket Importer@bitbucket_importerOwner

Update with local changes (automerging) no longer works

Created originally on Bitbucket by f0ff886f (Matt Rusiniak)

This is bizarre, but for some reason one of our basic workflows has stopped working. Until today our normal workflow was:

Edit things locally, when we're ready to commit we pull the latest changes from the server, then we update to tip by right clicking the tip and selecting "Update", and in the update dialog we leave "Always merge" selected.

This is how the dialog looks:

Until today, it worked perfectly. We'd layer our changes on the latest revision before comitting, and that way we'd never have to deal with any rebasing or things like that (if there was a conflict when merge we'd resolve locally anyways since the update would fail).

Now, I get this dialog:

However, if I just go to the terminal and try using hg update, it works perfectly (and then TortoiseHg Workbench happily shows the change).

What's odd is this changed across all TortoiseHg versions (3.8.1, 4.6.1 and 4.8 in our pool of PCs)! Actually, I think the behaviour on non 4.8 was intended (due to some branching), so I will keep this report specific to 4.8. I'm sure its some ID10T problem, but do you have any idea what suddenly caused this? I've made no changes to the main repo server, and definitely I haven't touched other clients either.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: mercurial/tortoisehg/thg#5281