On Mon, Aug 8, 2011 at 09:11, Eric Cooper wrote:
> I don't see any obvious difference in behavior when using localhost
> vs. kcita. It's possible that you simply hit a mirror site during a
> time when the InRelease file was inconsistent with the Packages files
> -- this issue has come up a lot re
I don't see any obvious difference in behavior when using localhost
vs. kcita. It's possible that you simply hit a mirror site during a
time when the InRelease file was inconsistent with the Packages files
-- this issue has come up a lot recently due to some older mirror
scripts not yet updated.
> Checking the computer that runs approx I see that I'm using localhost instead
> of the name of the host itself that points to the IP for the local network on
> the sources.list and here an update on aptitude works as expected (I have some
> packages for upgrade and few on the obsolete section). S
Package: approx
Version: 5.1-1
Severity: normal
I'm using approx for my local network were I have several computers using it.
Today, doing an update on aptitude from one of the machine I found no package
to be upgraded an most of the ones installed appearing on the "Obsolete and
Locally Created P
4 matches
Mail list logo