On Sun, 16 Oct 2011 12:26:02 +0100
Javi Merino <[email protected]> wrote:
> On 16/10/11 11:01, clayton wrote:
> > Package: mercurial
> > Version: 1.3.1-1~bpo50+2
> > Severity: important
>
> I don't know how you are doing the upgrade, but mercurial in squeeze
> is 1.6.4-1.
Very simple:
apt-get install mercurial
After it was removed automatically by the dist-upgrade process. I am
not sure how the above "Version: 1.3.1-1~bpo50+2" was generated, but
the mercurial package was not actually installed when I ran reportbug.
Perhaps that information comes from the last version of mercurial that
was actually installed on the machine, which would indeed have been the
Lenny version.
> > The following packages have unmet dependencies:
> > mercurial : Depends: python (< 2.6) but 2.6.6-3+squeeze6 is to be
> > installed Depends: mercurial-common (= 1.3.1-1~bpo50+2) but it is
> > not going to be installed
>
> That's the mercurial in lenny. In squeeze mercurial depends on
> python < 2.7 .
>
> Can you run "apt-cache policy mercurial" ?
# apt-cache policy mercurial
mercurial:
Installed: 1.8.3-1~bpo60+1
Candidate: 1.8.3-1~bpo60+1
Package pin: (not found)
Version table:
*** 1.8.3-1~bpo60+1 900
100 http://backports.debian.org/debian-backports/
squeeze-backports/main amd64 Packages 100 /var/lib/dpkg/status
1.6.4-1 900
500 http://ftp.us.debian.org/debian/ squeeze/main amd64 Packages
So why was apt not installing 1.6.4, since 1.3.1 is not even visible
in the repos? Still sounds like something is wrong to me.
Clayton
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
