I had a bunch of errors in the output of sudo apt-get update: duplicate entries and 404 not found errors.
Figured those out, I hope: I removed PPAs that didn't have any packages associated with them, then I removed out a duplicate entry in /etc/apt/sources.list.
It seems I have royally buggered it up. Now most of the lines say Ign when I do sudo apt-get update.
How do I go about straightening out what I have screwed up? I need to get rid of these Igns that are all over the place. There are about 50% (eyeball guess) Igns!
2 Answers
When you use apt-get update it verifies if the same update indexes need downloading, if not it does not download the same updated indexes again.
Hitmeans apt checked the timestamps on package list, those match and there are no changes.Ignmeans there are no changes in the pdiff index file, it wont bother downloading it again.Getmeans apt checked the timestamps on package list, there were changes and will be downloaded.
Nothing to be scared of, it just means there is no need to download updated indexes again, the ones you have are current.
6The correct answer of this question is:
Ignmeansapttried to download something (such as translation orInReleasefile) but didn't find, but that can be ignored, so proceed to the next thing. Because translation can be secondary priority and ifInReleasefile can't be found, it uses other method for authentication like usingReleaseandRelease.gpgpair.Hitmeansaptneeded to download aReleasefile orInReleasefile (because somehow it got deleted) and once it is downloaded, it checked the checksum of the Index file in it and found that the checksum mentioned there matches the checksum of the Package file already downloaded that is in/var/lib/apt/lists. That's why it's aHit. So, it won't download thePackagefile again.
Found the answer from:
- How do Ign and Hit affect apt-get update
- My personal experiment with a local repository by turning off all other repositories.
