Ian Bruce <[EMAIL PROTECTED]> writes:
> On Thu, 28 Sep 2006 03:45:16 -0700
> Ian Bruce <[EMAIL PROTECTED]> wrote:
>
>> So it seems that with the currently shipping versions of gzip (I tried
>> both "stable/updates" and "testing"), there is actually no way to
>> exactly replicate the compression pr
On Thu, Sep 28, 2006 at 06:50:53AM -0700, Ian Bruce wrote:
> It turns out that the zlib1g-dev package contains a program called
> "minigzip" in source form. This is what's needed; "minigzip -9"
> reproduces exactly the compression used by dpkg-deb, unlike regular
> gzip.
This may not produce iden
On Thu, 28 Sep 2006 03:45:16 -0700
Ian Bruce <[EMAIL PROTECTED]> wrote:
> So it seems that with the currently shipping versions of gzip (I tried
> both "stable/updates" and "testing"), there is actually no way to
> exactly replicate the compression produced by the standard package
> build system.
Followup to the other lists too...
On Thu, Sep 28, 2006 at 12:15:21PM +0100, Mark Brown wrote:
> On Thu, Sep 28, 2006 at 03:45:16AM -0700, Ian Bruce wrote:
>
> > It appears that dpkg-deb does not exec gzip, and it's not dynamically
> > linked with anything except glibc. I suppose that it's static
On Thu, Sep 28, 2006 at 03:45:16AM -0700, Ian Bruce wrote:
> It appears that dpkg-deb does not exec gzip, and it's not dynamically
> linked with anything except glibc. I suppose that it's statically linked
> against zlib1g or something like it. So the question is, how can the
> exact compression a
I'm working on a system for differential transport of deb packages using
zsync (client-side rsync). This involves decompressing the gzip'ed tar
archives in the package and then recompressing them later. In order that
the reconstructed package match the "Size" and "MD5sum" fields in the
Apt packages
6 matches
Mail list logo
