diff options
author | Georgi Georgiev <310867+chutzimir@users.noreply.github.com> | 2022-05-23 13:42:53 +0300 |
---|---|---|
committer | Georgi Georgiev <310867+chutzimir@users.noreply.github.com> | 2022-05-23 13:45:45 +0300 |
commit | 3cbdd0c98d72d05993c5aa51ca445e545819ee9d (patch) | |
tree | a4175d56d9a3b173516f2b2849205374f3730209 | |
parent | 3f290988228341c5e3cec79d79a25be95521c861 (diff) |
Skip downloading the non-existent uncompressed `Packages` file
Let's skip downloading the non-existent uncompressed Packages file as it
is failing 100% of the time anyway.
It seems that the `Release` file under the binary directory is necessary
in some situations, even though it is documented as unnecessary in
https://wiki.debian.org/DebianRepository/Format#Legacy_per-component-and-architecture_Release_files
> Legacy per-component-and-architecture Release files
> Servers may provide legacy Release files in
> "dists/$DIST/$COMP/binary-$ARCH/Release".
>
> It should contain only the following fields:
>
> - Archive (old name for Suite)
> - Origin
> - Label
> - Acquire-By-Hash (optional)
> - Component: $COMP (singular variant of Components)
> - Architecture: $ARCH (current architecture)
>
> Clients must not use them.
-rwxr-xr-x | apt-mirror | 4 |
1 files changed, 3 insertions, 1 deletions
@@ -566,7 +566,9 @@ sub find_metadata_in_release ) or ( $filename =~ m{^${component_regex}/Contents-${arch_regex}${compressed_extension_regex}} ) or ( - $filename =~ m{^${component_regex}/binary-${arch_regex}} #Need all files in this folder for netboot. + $filename =~ m{^${component_regex}/binary-${arch_regex}/Packages${compressed_extension_regex}} + ) or ( + $filename =~ m{^${component_regex}/binary-${arch_regex}/Release$} # Needed for netboot. ) or ( $filename =~ m{^${component_regex}/cnf/Commands-${arch_regex}${compressed_extension_regex}} ) or ( |