Ubuntu
mercurial package

Was Mercurial 3.8.3 accidentally placed in the 3.7.3 package?

Bug #1591748 reported by Jonathan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mercurial (Ubuntu)
New
Undecided
Unassigned

Bug Description

All of my mercurial tools are breaking due to version mismatches. I suspect it was due to the work done by the Debian guys on Friday with 3.8.3 put into unstable. Unless I'm doing something wrong. Here is the output I get:

$ lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04

$ sudo apt-get install mercurial=3.7.3-1ubuntu1
Reading package lists... Done
Building dependency tree
Reading state information... Done
mercurial is already the newest version (3.7.3-1ubuntu1).
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.

$ hg --version
Mercurial Distributed SCM (version 3.8.3)

$ apt-cache policy mercurial
mercurial:
  Installed: 3.7.3-1ubuntu1
  Candidate: 3.7.3-1ubuntu1
  Version table:
 *** 3.7.3-1ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
        100 /var/lib/dpkg/status

Expected:
 hg --version outputs 3.7.3

Instead
 hg --version outputs 3.8.3

See original description
Jonathan (desertshadow)
description: updated
Revision history for this message
Leaders and Company (leadersandco) wrote :

Upon uninstalling `mercurial` I found I still had `/usr/local/bin/hg` (dpkg -S still didn't know where it came from so I just renamed it). I verified with `which hg` I had fully uninstalled all versions. Then I reinstalled mercurial

However I still have this issue:

$ hg --version
Mercurial Distributed SCM (version 3.8.3)
$ which hg
/usr/bin/hg
$ dpkg -S /usr/bin/hg
mercurial: /usr/bin/hg
$ sudo apt-get install mercurial
Reading package lists... Done
Building dependency tree
Reading state information... Done
mercurial is already the newest version (3.7.3-1ubuntu1).
mercurial set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.

Revision history for this message
Javi Merino (cibervicho) wrote :

The hg that you found in /usr/local/bin/ was not installed by apt or dpkg, you have installed it manually by downloading the sources and running "make install". Just by renaming it you are not getting rid of your local installation of mercurial. Have a look at /usr/local/lib/python2.7/dist-packages , you will probably find mercurial and hgext directories there. Those are likely to be the ones your /usr/bin/hg is importing and why it's getting so confused.

Try getting rid of what you installed in /usr/local (specially in /usr/local/lib/python2.7/dist-packages/mercurial* and hgext*) and use only the packages provided by the distribution.

Revision history for this message
Leaders and Company (leadersandco) wrote :

That was the problem, thank you. I had to run

sudo -H pip uninstall mercurial

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.