Bug#317976: rsync: Uses local copy of zlib
On Wed 13 Jul 2005, Mark Brown wrote: On Tue, Jul 12, 2005 at 08:21:46PM +0200, Paul Slootman wrote: Please, *please* look at existing bugs before sending in a bug report. E.g. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=32379 I did look at the existing reports, and that (and the one merged with it) is the only report about the use of zlib. As you will have seen from reading the bug report I am concerned about a different issue, the fact that rsync includes and uses a private copy of the zlib source code. It would be nice if rsync linked against the shared zlib instead of linking in its own static copy. This to me implies that that bug report is also concerned about rsync using its own (static) copy of zlib... Paul Slootman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317976: rsync: Uses local copy of zlib
On Wed, Jul 13, 2005 at 09:54:26AM +0200, Paul Slootman wrote: It would be nice if rsync linked against the shared zlib instead of linking in its own static copy. This to me implies that that bug report is also concerned about rsync using its own (static) copy of zlib... Static linking and including a redundant copy of the source code are distinct problems - packages can link against the static copy of the library provided by the -dev package (some packages do actually do this). -- You grabbed my hand and we fell into it, like a daydream - or a fever. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317976: rsync: Uses local copy of zlib
On Wed 13 Jul 2005, Mark Brown wrote: On Wed, Jul 13, 2005 at 09:54:26AM +0200, Paul Slootman wrote: It would be nice if rsync linked against the shared zlib instead of linking in its own static copy. This to me implies that that bug report is also concerned about rsync using its own (static) copy of zlib... Static linking and including a redundant copy of the source code are distinct problems - packages can link against the static copy of the library provided by the -dev package (some packages do actually do this). I think you're missing the word own. As in own static copy. Linking in an external static copy of zlib wouldn't be described as own static copy IMHO. Paul Slootman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317976: rsync: Uses local copy of zlib
Package: rsync Version: 2.6.5-1 Severity: important The upstream rsync package includes a copy of zlib and unconditionally uses it during the build. This means that any security updates to zlib need to be independantly applied to this package. Ideally the configure script should detect if zlib is present on the system and only use the local copy if there's nothing suitable on the system already. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-powerpc Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages rsync depends on: ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libpopt01.7-5lib for parsing cmdline parameters rsync recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
