Bernhard,
On 02/28/2011 01:19 PM, Bernhard R. Link wrote:
* Jeffrey B. Green<j...@kikisoso.org> [110223 14:33]:
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
An totally wrong filename the 'check' command should have found.
I've added an test for wrong architectures.
Admittedly, this may just be a bug in some other command that caused it
(such as the pull, maybe not)
There should be no way (except perhaps some low-level '_addpackage') to
get a package of the wrong architecture somewhere. If you have any idea how
to get there I'd very interested.
I did a "fill" from the i386 arch which I assume is how they got there.
It may have been a dumb thing to try, but I was assuming that
non-appropriate arch files would not "fill", so to speak. I was wrong,
or at least I was wrong if that is where they came from. If the errant
files came from somewhere else, then I'm not sure where they came from.
With the squeeze package, I can do a "flood" in order to fill a
distribution with the all.deb packages.
-jeff
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
