> It seems that approx may have some issues when trying to download
> Packages.bz2, while it doesn't have problems with Packages.gz files
> (even when both the files are there):
This is intentional behavior (see the function "should_deny" and its
comment in approx.ml if you're really interested.) The reason has to
do with handling pdiffs. Approx has to decompress the Packages file,
apply the pdiffs, and recompress it so that the result matches the
checksum (md5, sha256, etc.) in the archive. I found that it was much
too slow to do that for .bz2 files, so approx only retrieves the .gz
version and pretends that the .bz2 version doesn't exist.
Unless this behavior is causing some more serious problem for you, I'd
like to close this (or demote it to wishlist if you need to be able to
fetch Packages.bz2 files through the approx server for some reason.)
> BTW, would something like
>
> ,----
> | --- approx-4.2.orig/util.ml
> | +++ approx-4.2/util.ml
> | @@ -147,7 +147,10 @@ let gensym str =
> | let rm file = try Sys.remove file with _ -> ()
> |
> | let decompressors =
> | - [(".gz", "/bin/gunzip --stdout"); (".bz2", "/bin/bunzip2 --stdout")]
> | + [(".gz", "/bin/gunzip --stdout");
> | + (".bz2", "/bin/bunzip2 --stdout");
> | + (".lzma", "/usr/bin/lzma --stdout");
> | + (".xz", "/usr/bin/xz --stdout");]
> |
> | let is_compressed file =
> | match extension file with
> `----
>
> be incorporated in approx?
Approx already knows about these extensions (see release.ml) so that
it can recognize tarballs in the new 3.0 source format. But I'm not
aware of those compression schemes being used for Packages files in
any repositories.
Cheers,
Eric
--
Eric Cooper e c c @ c m u . e d u
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
