On 02/22/2011 03:42 PM, Bernhard R. Link wrote:
* Jeffrey B. Green<j...@kikisoso.org> [110222 20:09]:
The problem that I had originally was that the files related to the
release were indeed downloaded via an 'update' however the information
that was kept in the db/packages.db was wrong and consequently the
distribution Packages file was incorrect.
What exactly was incorrect? I'm out of guesses. There is no way to check
against something without knowing what this something is.
In this particular case, the Filename entry was wrong for the armel
Packages file, e.g. it was (or similar...I had removed the defective
Packages file)
Filename: pool/main/a/aptitude/aptitude_0.6.3-3.2_i386.deb
Obviously not the right file for an armel package. Atitude was then
doing things differently which was how I was alerted to the inconsistency.
Admittedly, this may just be a bug in some other command that caused it
(such as the pull, maybe not), however there is no guarantee that after
fixing the (possible) bug, another may not be introduced by some other
means. The point being that some sort of integrity check between what a
master repository says is in the release, be it filename, md5 checksum,
or whatever, and what the local repository says is in it needs to be
possible, as in a tool to compare. Properly it should be against the db
files since I'm assuming those are the local masters. That is a bit more
work than comparing master packages and release files against local
versions which could probably be done with a perl script. The perl
script then would probably not be capable in helping fix any
inconsistencies discovered.
I don't know. Is this idea getting any clearer?
regards,
-jeff
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
