As far as I know, there are two ways how something like this could happen.
The packages listing on the mirror ("Packages[.gz|.bz2]" file in the folder corresponding to your distribution and architecture) you were using was wrong, for whatever reason. Maybe a synchronization script screwed up somewhere.
Or maybe you forgot to update your local package listings, by running "apt-get update" or something equivalent, before you tried to install.
In the latter case it would not be a bug of APT itself. If you were using some graphical frontend, it may be a bug of the frontend, since they should probably do the update of the package listings automatically for you.
I think it would also be good to know how you tried to install the packages (apt-get, synaptic, aptitude, adept, ...).
Could you provide those 2 informations, i.e. if your local package listing was up to date, and what tool you used?
I am inclined to set this bug to incomplete. I think I will do that in a few days, if nobody objects until then.
As far as I know, there are two ways how something like this could happen.
The packages listing on the mirror ("Packages[ .gz|.bz2] " file in the folder corresponding to your distribution and architecture) you were using was wrong, for whatever reason. Maybe a synchronization script screwed up somewhere.
Or maybe you forgot to update your local package listings, by running "apt-get update" or something equivalent, before you tried to install.
In the latter case it would not be a bug of APT itself. If you were using some graphical frontend, it may be a bug of the frontend, since they should probably do the update of the package listings automatically for you.
I think it would also be good to know how you tried to install the packages (apt-get, synaptic, aptitude, adept, ...).
Could you provide those 2 informations, i.e. if your local package listing was up to date, and what tool you used?
I am inclined to set this bug to incomplete. I think I will do that in a few days, if nobody objects until then.