* Jeff Green <[email protected]> [110213 17:39]:
> During the squeeze upgrade period I'd discovered an inconsistency that had
> entered into my repository mirror. I suspect it happened when I did a pull for
> the armel packages and didn't specify it correctly. Consequently the wrong
> packages were then deemed part of the armel release. I was pretty quick in
> tracking down the problem after the signs pointed to the repository, however
> until that happened I was naively assuming the repository was valid.
>
> As I see it so far, the "checks" that are provided check for internal
> consistency
> but not necessarily consistency with respect to an outside source. I propose a
> "checkrelease" action that will provide information with respect to
> differences
> between the local release file and the remote or master release file.
> Obviously
> this action can possibly produce too much info and so enough controls need to
> be
> available to customize the information provided.
I do not think I understand what this check is supposed to check at all.
Is it:
- checking all packages in a distribution have a source package in that
distribution?
i.e. what 'reprepro sourcemissing' does (introduced in 4.3.0)?
- checking everything can be get from some other distribution/remote?
i.e. something like temporarily chaning the update/pull rule to start
with a delete rule ("-") and running checkpull/checkupdate and only
showing which packages would be deleted?
- something else?
what should it check for?
Bernhard R. Link
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
