On 2000-04-27 11:46:54 -0600, Jason Gunthorpe wrote: > > On Thu, 27 Apr 2000, Matthew Hawkins wrote: > > > Well the local /var/state/apt/lists/ keeps it uncompressed, I can't > > really show that the files are different if I quote one compressed and > > the other uncompressed now, can I? > > gzip -d foo | wc -c
You complained that I showed the uncompressed version as apt takes the compressed one. Now you insist I use it. Please be a little more consistent. > or md5sum is good too. If I md5sum two files, one of which is compressed and the other not - the sum will be different. What's the point to that? I already _know_ the files are different. They're different sizes for crying out loud! > > Well whatever is on the mirror is what it _didn't_ download, hence the bug > > report! :-) > > It has to! It cannot make this up! It goes to the network and pulls down > whatever is there. *IT CANNOT CREATE A PACKAGE FILE FROM THIN AIR* :> I'm not saying it created a package file out of thin air, I'm saying it is not getting the UPDATED file. It already has a file, it's x bytes long as is the same file on a particular debian mirror site which hadn't been updated for a while. No doubt that was the file gotten on a particular run of apt-get update a few days previously. Now, on the local company mirror - also listed in sources.list - is a NEWER Packages file which, funnily enough, is the same size as the same Packages file on a different debian mirror which HAS been updated that day. Apt-get on the client machine is not updating its local status lists with this newer Packages file. It is simply keeping its existing one. What part of this is difficult to understand? > It *has* to have come from the network, which means it is either the > remote site or a busted transparent proxy (ugh). The file name is directly > taken from the URL that was used to get the file, they are never renamed > or otherwise mangled. So if the filename says topic.com it came from > topic.com. Sure it came from the local company mirror. THREE DAYS BEFOREHAND. I want TODAYS packages, the Package lists of which exist on the local company mirror. I already downloaded the updates from three days ago, three days ago! The packages files for today exist on the site listed in sources.list. apt-get is not getting them. I've given ls -l listings of the client running apt-get, the local company mirror, and two separate official debian mirrors. I've given my sources.list file, apt.conf, stated I don't have http_proxy set. Surely there's enough information there to see that there is a problem with apt? What more do you want? Oh, btw it's the same story today, and I've doublechecked the proxy logs from the proxy listed in apt.conf - it's not being hit for the local company mirror and apt isn't getting the updated packages files that exist on that mirror. There is a problem with apt. -- Matt
