Max Bowsher wrote:
> I am trying to use --ignore-missing-release to support the use-case of
> mirroring lenny/updates and squeeze/updates from security.debian.org
> into a mirror which still contains the final state of etch/updates
> (which I want to keep).
>
> It works, but I have to use --nocleanup because debmirror (shown here
> without --nocleanup and with --dry-run) wants to delete things that it
> should not:
>
> ...
> Cleanup mirror.
> deleting .temp/dists/etch/updates/Release
> deleting .temp/dists/etch/updates/Release.gpg
> deleting dists/etch/updates/Release.gpg
> All done.
> ...
>
> ("dists/etch/updates/Release" is being registered in %files as -1 by
> http_get()'s failure logging, hence not appearing above.)
>
> I think that in --ignore-missing-release mode, missing remote Release
> and Release.gpg should be registered as present/needed - for example:This seems to be scope-creep for --ignore-missing-release. Its purpose is to allow mirroring of repositories that do not have any Release file at all. It does not seem wise to use --ignore-missing-release against a mirror that has a Release file, as that will avoid downloading those Release files, which are crucial for gpg verification. The --debmarshal option already provides a way to archive the old state of a mirror. -- see shy jo
signature.asc
Description: Digital signature
