Bug#368310: upstream; to be fixed in 4.2.1

2006-06-09 Thread Philipp Kern
On Tue, 2006-05-30 at 22:27 -0400, Steve M. Robbins wrote: > Apparently Torbjorn didn't realize that an ABI change had taken place > with libgmpxx, and he didn't change the -version-info appropriately. > He's acknowledged this to me in private email. Could you please fix this ASAP? One possible

Bug#368310: upstream; to be fixed in 4.2.1

2006-05-30 Thread Steve M. Robbins
On Wed, May 31, 2006 at 04:00:52AM +0200, Philipp Kern wrote: > On Tue, 2006-05-30 at 21:00 -0400, Steve M. Robbins wrote: > > Unfortunately, release 4.2.1 has the same library version bug > > for libgmpxx. So we'll have to wait for 4.2.2. > > Ew, I tend to disagree. The changelog on their web pa

Bug#368310: upstream; to be fixed in 4.2.1

2006-05-30 Thread Philipp Kern
On Tue, 2006-05-30 at 21:00 -0400, Steve M. Robbins wrote: > Unfortunately, release 4.2.1 has the same library version bug > for libgmpxx. So we'll have to wait for 4.2.2. Ew, I tend to disagree. The changelog on their web page lists a "shared library version correct" as a bugfix and indeed the t

Bug#368310: upstream; to be fixed in 4.2.1

2006-05-30 Thread Steve M. Robbins
Hi all, You're right: 4.2.1 has been released. I didn't realize that because only a "release candidate" has been announced on the email list http://swox.com/list-archives/gmp-announce/2006-April/14.html Unfortunately, release 4.2.1 has the same library version bug for libgmpxx. So we'll

Bug#368310: upstream; to be fixed in 4.2.1

2006-05-30 Thread allomber
On Wed, May 24, 2006 at 01:26:21AM -0400, Steve M. Robbins wrote: > Hi, > > Just to note: a new upstream version 4.2.1 is at "release candidate" > status. I have alerted upstream about this problem and expect that it > will be addressed in the next upstream release. I'll leave it until > then.

Bug#368310: upstream; to be fixed in 4.2.1

2006-05-30 Thread Philipp Kern
On Wed, 2006-05-24 at 09:54 -0400, Steve M. Robbins wrote: > The SOVERSION will change. So, yes, I'm afraid it will require another > recompilation. Is there a chance to see an interim fix applied to the package until the new gmp upstream revision is released. (Like upload of the RC version with

Bug#368310: upstream; to be fixed in 4.2.1

2006-05-23 Thread Steve M. Robbins
Hi, Just to note: a new upstream version 4.2.1 is at "release candidate" status. I have alerted upstream about this problem and expect that it will be addressed in the next upstream release. I'll leave it until then. -Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "un