On 02/14/2011 02:48 PM, Bernhard R. Link wrote:
* Jeffrey B. Green<j...@kikisoso.org> [110213 21:15]:
- something else?
what should it check for?
Basically it is a tool for checking that the local db/packages.db is in
synchronization with the Packages file(s) on the master repository if
exact synchronization is desired. Or how they differ if differences are
part of the local repo. (I'm assuming the Packages files are a reference
point since they are downloaded when (re)building the db/packages.db
file.) The local version of the Packages file(s) apparently are built
from the information in the db/packages.db file (and possibly other
databases).
That sounds a bit like the above. Could you try if that is what you
want? (i.e. add a '-' as first part of Update:, run checkupdate and
remove the '-' again).
After building 4.4 and installing it, I would have to say no it is not
the same. The 'sourcemissing' deals with source files which is not what
I'm talking about here. And the 'checkupdate' with the magic '-' is
unclear as to what exactly it is telling me. I tried it with a fresh
update of a squeeze:contrib:powerpc repository and it (the checkupdate
run) listed several packages that were there and change status, e.g.
Updates needed for 'squeeze|contrib|powerpc':
'acx100-source': '20080210-1.1' will be kept (best new: '20080210-1.1')
'alien-arena': '7.40-2' will be kept (best new: '7.40-2')
'alien-arena-browser': '7.0-1' will be kept (best new: '7.0-1')
'alien-arena-common': '7.40-2' will be kept (best new: '7.40-2')
'alien-arena-dbg': '6.10-2' will be kept (best new: '6.10-2')
'alien-arena-server': '7.40-2' will be kept (best new: '7.40-2')
'alien-arena-server-dbg': '6.10-2' will be kept (best new: '6.10-2')
'alsa-firmware-loaders': '1.0.23-3+b1' will be kept (best new:
'1.0.23-3+b1')
...
As can be seen, this is not really a consistency check but a report of
what will be changed, or not changed. If indeed it is also a consistency
check, then that should be said in the man page (with a short discussion
regarding how consistency is determined).
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. I'm not seeing how the
procedure that you outlined solves that problem. If it does, then it
needs more explanation.
(I probably should have suggested 'checkpackages' rather than
'checkrelease' for the consistency check action.)
regards,
-jeff
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
