Ed Tomlinson wrote:
> Bob Proulx wrote:
> > What is the output of this command?
> >
> > apt-cache policy bind9-host
>
> grover:/home/ed# apt-cache policy bind9-host
> bind9-host:
> Installed: 1:9.3.1-2
> Candidate: 1:9.3.1-2
> Version Table:
> 1:9.3.1-2 0
> 500 http://amd64.debian.net sid/main Packages
> *** 1:9.3.1-2 0
> 100 /var/lib/dpkg/status
Isn't that very interesting? It shows the 1:9.3.1-2 as installed but
different from the 1:9.3.1-2 that is available to install. I am
guessing it is different because the package md5sums are different
even though the version is the same. If apt had thought they were the
same then it would have showed them both under the same entry in the
version table.
> > I am guessing that there are multiple sources for bind9-host. They
> > are different. You are alternately installing first one and then the
> > other. I have seen this behavior from apt with other packages with
> > that problem. A local rebuild in a local depot was my problem.
> >
> > What is the output of this command?
> >
> > apt-get install --print-uris -d -y -qq bind9-host |awk '{print$1}' |xargs -l
> >
> > I am guessing that as you install first one and then the other that
> > the URL printed will be changing from one location to the next.
>
> grover:/home/ed# apt-get install --print-uris -d -y -qq bind9-host |awk '{print$1}' |xargs -l
> http://amd64.debian.net/debian/pool/main/b/bind9/bind9-host_9.3.1-2_amd64.deb
> grover:/home/ed#
>
> Which seems to show one url?
And after you installed it again what was the URL printed? Notice
that the suggestion was that it would change to a different one after
an installation. I was guessing it is toggling between two different
sources.
But seeing the apt-cache policy output I don't think that way now
because I did not see a second source in the output.
> Wonder if its worth removing the cached version?
Another poster helping you suggested 'apt-get clean' and you said it
had no effect. That command removes the cache version. So you have
already tried it.
What is in your /etc/apt/sources.list file? It is my last best guess
at the problem. I am still convinced you have two different sources
for this package.
Other than this I am sorry but personally I am out of guesses.
Bob
Attachment:
signature.asc
Description: Digital signature