Baurzhan Ismagulov <[EMAIL PROTECTED]> writes:
> Hello Goswin,
>
> On Tue, Aug 01, 2006 at 03:26:02PM +0200, Goswin von Brederlow wrote:
>> Add '--ignore-missing-release' to your options. That should turn the
>> error into warnings.
>
> thanks much, this works! I still don't understand how this works,
> though. The man page says "Don't fail if the Release file is missing",
> but I do have that file, which is confusing. Before I can suggest any
> improbement, could you perhaps point me to a short current overview of
> how this works (what is meant by signature (seems not to mean a hash
> encoded with a private key), who checks which signature, and so on)?
>
> With kind regards,
> Baurzhan.
This is a sideeffect of the support for missing Release files. When
the file is missing the md5sums and sizes for Packages files are
unknown. So the --ignore-missing-release option disables the md5sum
and size check for the Packages files as well as not failing when
Release file can't be found. In your case the Release file can be
found but contains no usefull information (for debmirror), which is
pretty much the same as no Release file. The same code path applies.
A proper Debian archive has the following signatures:
Release.gpg: detached gpg signature for Release
Release: md5sum/size for Packages and Sources files
Packages/Sources: md5sum/size for debs and sources
--ignore-release-gpg ignores any failures related to Release.gpg and
--ignore-missing-release any failures related to Release. For both
downloading and content. Debmirror will always try to use them even
with the options, it just ignores failures.
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
