Re: libgtop2 fixed packages available (solves applet mess).

[Sven Luther <sven.luther@wanadoo.fr>]

On Sun, Jun 08, 2003 at 02:09:42PM -0400, Colin Walters wrote:
> On Sun, 2003-06-08 at 13:15, Sven Luther wrote:
> 
> > I don't really know, you mean i should take the working 2.0.1-4 package,
> > add an epoch to the package name, apply the fix, and upload that, even
> > if there has already been a 2.0.2-1 in the archive, which caused all
> > this problem.
> 
> Yep, that's what I mean.
> 
> >  I don't really like using epochs, and forcing an epoch
> > upgrade by a NMU sound kind of rude to me, i don't want to do that.
> 
> We don't have much of a choice now.
> 
> > Maybe i could do what you suggest, and upload a 2.0.2.is_really_2.0.1-0.1
> > and let Noel to sort this out when he looks at the package again. 
> 
> That would probably work too, yeah.

Ok, i uploaded the ugly : 

Format: 1.7
Date: Sun,  8 Jun 2003 21:21:07 +0200
Source: libgtop2
Binary: libgtop2-daemon libgtop2-dev libgtop2
Architecture: source i386
Version: 2.0.2.is.2.0.1-1
Distribution: unstable
Urgency: low
Maintainer: Noel Koethe <noel@debian.org>
Changed-By: Sven Luther <luther@debian.org>
Description:
 libgtop2   - Libraries for gtop system monitoring library (part of Gnome 2)
 libgtop2-daemon - gtop daemon for monitoring remote machines (part of Gnome 2)
 libgtop2-dev - Dev libraries for gtop system monitoring library (part of Gnome 2
Closes: 195454 195623 195625 195665 195819 195867 196044
Changes:
 libgtop2 (2.0.2.is.2.0.1-1) unstable; urgency=low
 .
   * NMU with maintainer's knowledge, altough Noel will assuredly not like the
     way i did the upload, experimenting and Christian Marillat's and Coling
     Walters's advice showed me there is no other elegant solution. So i
     reverted the package to 2.0.1-4, applied the src/daemon/gnuserv.c buffer
     overflow fix from 2.0.2, and made a fake 2.0.2 package. Other alternative
     would have been using an epoch, which i consider ugly. The problem with
     2.0.2 is that buggy (even if Christian thinks it is a feature) libtool
     apparently did increase the soname, which is not needed here. Also
     the libgtop2 build system is broken, probably due to libtool too, because
     it will link libraries with already installed libraries and not with the
     ones currently building. This is mostly ok, but breaks when the soname
     changes.
     (Closes: #195454, #195623, #195625, #195665, #195819, #195867, #196044)
Files:
 b822f60f7fc3e214747b647b2caa5ffb 696 libs optional libgtop2_2.0.2.is.2.0.1-1.dsc
 aef883369dad6eb2daed0875bbbbae9f 1092764 libs optional libgtop2_2.0.2.is.2.0.1.orig.tar.gz
 a51672cb833553ca351c2f6d4d5b1075 111146 libs optional libgtop2_2.0.2.is.2.0.1-1.diff.gz
 1691e49c5d868cb66c2b9cdabcdfb1ba 247482 libs optional libgtop2_2.0.2.is.2.0.1-1_i386.deb
 342c9f5699d1008a57b900b03f88ea5d 62792 devel optional libgtop2-dev_2.0.2.is.2.0.1-1_i386.deb
 de384331b29447bebf34dc79fa6f1fc9 10634 utils optional libgtop2-daemon_2.0.2.is.2.0.1-1_i386.deb

This is maybe not the best solution, but it is the only thing i could do
apart from adding an epoch. I tried uploading a 2.0.2-1.1+isreally+2.0.1
kind of package, but there were diffs between 2.0.2 and 2.0.1 that diff
did not like (the .gmo thingies) so it was not possible.

Noel will have to clean up when he has time again, sorry for that, but
it will at least fix this for the many unstable users out there.

Friendly,

Sven Luther