Subject: Bug#3529: libgr and zlib1 collide, but don't conflict!

From: Mark Eichin <[email-masked]>
Date: 05 Jul 1996 23:35:49 -0400

Package: libgr-dev
Version: 2.0.5-3

Package: zlib1-dev
Version: 1.02-3

libgr-dev has libgz.a and libgz.so.
zlib1-dev has libz.a and libgz.so.
*both* have zlib.h and zconf.h.

They are *different* versions, with incompatible function names
(apparently zlib1 changed from deflateInit to deflateInit_, which
certainly broke my code :-) and if you would please straighten this
out among yourselves, please... or at least conflict with each other
(though that would be ugly.) Suggestion: perhaps if libgr is providing
libgz, it could provide gzlib.h, instead of zlib.h?

Why do I care? CVS (internal release, it's probably not yet in the
public version) now uses zlib for compression. (It kind of makes sense
for CVS and other network programs to depend on zlib1, rather than
pulling in a whole slew of graphics formats... but as long as I can
get it in some form, I'm happy :-)

---

From: "Darren/Torin/Who Ever..." <[email-masked]>
Date: 05 Jul 1996 23:43:51 -0700

-----BEGIN PGP SIGNED MESSAGE-----

>*both* have zlib.h and zconf.h.

libgr is OBSOLETE.  What do I have to do to get it moved there?

Darren
- -- 
<[email-masked]> <http://www.daft.com/~torin> <[email-masked]> <[email-masked]>
Darren Stalder/2608 Second Ave, @282/Seattle, WA 98121-1212/USA/+1-800-921-4996
@ Do you have your clothes on? I probably don't. Take yours off. Feel better. @
@ Sysadmin, webweaver, postmaster for hire.  C/Perl/CGI programmer and tutor. @

---

From: Rob Browning <[email-masked]>
Date: 06 Jul 1996 19:57:30 -0500

> *both* have zlib.h and zconf.h.

libgr is obsolete.  It has been phased out in favor of a separate
libtiff, libpng, libjpeg, zlib, etc.

Just

dpkg --purge libgr

and you'll feel much better.  That is, unless you're using my gimp
package which still depends on libgr...I know, I'm working on it.

--
Rob

---

From: Mark Eichin <[email-masked]>
Date: 06 Jul 1996 23:16:25 -0400

Ok, I get the message :-)

(Hmm. I suppose this doesn't happen often enough for dpkg to support
it, some way of having a libgr.deb that doesn't actually install
itself... naah, that's probably better for dselect to handle.)

FYI using the matching headers did the right thing with my code.

Thanks, and feel free to close this at your convenience.

---

From: Michael Alan Dorman <[email-masked]>
Date: Mon, 08 Jul 1996 09:20:10 -0400

Well, first, zlib doesn't create libgz, it creates libz.  Really.
Honest.  They quit using libgz a while ago, which is one of the
reasons libgr is so out of date.

As for the other, fsck, fsck, fsck---I thought libgr put all of its
files in special places (/usr/include/libgr or some such), while zlib
puts all of its files in normal places (/usr/include), thereby making
them not actually conflict.

The real solution is for gimp to get recompiled (now that a dedicated
libtiff is out), and for us to finally trash libgr.  I'll release a
new zlib1-dev, though, that'll conflict with just libgr-dev.  Other
than that, there shouldn't be any collision.

Mike.
--
"Don't let me make you unhappy by failing to be contrary enough...."

---

From: Ian Jackson <[email-masked]>
Date: Wed, 10 Jul 96 13:32 BST

> libgr is OBSOLETE.  What do I have to do to get it moved there?

I see that it has already been removed from rex - only the msdos
symlinks remain, and that'll go when the cron job runs.

I presume that it should be removed from buzz-fixed too ?  If so then
Guy needs to build a mechanism into the script he's writing to create
buzz-fixed to allow it to remove packages.

Ian.

---

From: Guy Maor <[email-masked]>
Date: Wed, 10 Jul 1996 09:41:02 -0500 (CDT)

> buzz-fixed to allow it to remove packages.

libgr is only obsolete if libtiff is available.  So do we then put
libtiff in the buzz-updates also?  The real question is how to
determine what changes are important enough to warrant a buzz update.
That's a rather open question.

Guy

---

From: "Darren/Torin/Who Ever..." <[email-masked]>
Date: 12 Jul 1996 00:24:13 -0700

-----BEGIN PGP SIGNED MESSAGE-----

>That's a rather open question.

libtiff3, libtiff3-dev, and libtiff3-gif are all available.
I'll mark the bugs for libgr as done.  (right?)

Darren
- --