[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Issues with releasing bzip2 1.0.1



On Fri, Sep 15, 2000 at 11:44:59AM -0700, Philippe Troin wrote:
> Torsten Landschoff <torsten@pclab.ifg.uni-kiel.de> writes:
> 
> > On Fri, Sep 15, 2000 at 10:26:53AM -0700, Philippe Troin wrote:
> >  
> > > Quite a few packages depend on libbz2 0.95b.
> > > And 0.95d-3 has been released only a couple of days ago.
> > > For some reasons, libbz2-1.0.1 has to conflict with libbz2 << 0.95b-3.
> > 
> > Is there no way to make a new libbz2 package which does NOT conflict with
> > the new libbz2-1 package? That libbz2 package would only need the library
> > itself and that should not conflict. Looks like the cleanest solution to
> > me. 
> 
> No. The problem is that libbz2 << 0.95d-3 contained the bzip2
> documentation (which was a bad idea in the first place, but...)
> including info files and manpages. Obviously 1.0.1 also contains the
> same documentation. I moved the docs in the bzip2 package in 0.95-3
> hence the conflict.

Well, I don't understand.

First of all, this doesn't require a Conflicts: - it requires a
Replaces:.

Why couldn't you make a libbz2-doc package, say, that had a Replaces
libbz2 (<< 0.95b-3), and a libbz2.1 (i know, miserable unclear choice
of name, use something better) and likewise renamed source package for
the new ones?  Then the old libbz2 remains and applications can migrate
over.


Dan

/--------------------------------\  /--------------------------------\
|       Daniel Jacobowitz        |__|        SCS Class of 2002       |
|   Debian GNU/Linux Developer    __    Carnegie Mellon University   |
|         dan@debian.org         |  |       dmj+@andrew.cmu.edu      |
\--------------------------------/  \--------------------------------/



Reply to: