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

Bug#569586: marked as done (FTBFS: compiler errors, when libc6-dev < 2.10.2-2)

Your message dated Tue, 16 Feb 2010 23:02:43 +0000
with message-id <E1NhWRH-0000Fh-EF@ries.debian.org>
and subject line Bug#569586: fixed in gmrun 0.9.2-2
has caused the Debian Bug report #569586,
regarding FTBFS: compiler errors, when libc6-dev < 2.10.2-2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

569586: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569586
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: gmrun
Version: 0.9.2-1
Tags: patch

gmrun fails to build from source when using the libc6 from Debian
stable. It appears that libc6 was changed in a non backwards-compatible
way sometime between 2.7 and 2.10.2.

Removing the 60-fix_gtkcompletionline.patch will allow it to compile in
stable, but then it won't compile in unstable/testing anymore. The
simplest solution would be for Build-Depends to require "libc6-dev (>=
2.10.2-2)". Or you could ammend the 60-fix_gtkcompletionline.patch to
check for libc6 version, and define my_alphasort accordingly.


Attachment: signature.asc
Description: PGP signature

--- End Message ---
--- Begin Message ---
Source: gmrun
Source-Version: 0.9.2-2

We believe that the bug you reported is fixed in the latest version of
gmrun, which is due to be installed in the Debian FTP archive:

  to main/g/gmrun/gmrun_0.9.2-2.debian.tar.gz
  to main/g/gmrun/gmrun_0.9.2-2.dsc
  to main/g/gmrun/gmrun_0.9.2-2_amd64.deb
  to main/g/gmrun/gmrun_0.9.2-2_i386.deb

A summary of the changes between this version and the previous one is

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 569586@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
Alexandre De Dommelin <adedommelin@tuxz.net> (supplier of updated gmrun package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)

Hash: RIPEMD160

Format: 1.8
Date: Tue, 09 Feb 2010 10:50:21 +0100
Source: gmrun
Binary: gmrun
Architecture: amd64 i386 source 
Version: 0.9.2-2
Distribution: unstable
Urgency: low
Maintainer: Alexandre De Dommelin <adedommelin@tuxz.net>
Changed-By: Alexandre De Dommelin <adedommelin@tuxz.net>
Closes: 568989 569586
 gmrun      - Featureful CLI-like GTK+ application launcher
 gmrun (0.9.2-2) unstable; urgency=low
   * New maintainer upload (Closes: #568989)
   * Fixes compiler error when libc6-dev < 2.10.2-2 (Closes: #569586)
 398308c27dae294853b64dab2bcdba4959ceda4c 1067 gmrun_0.9.2-2.dsc
 10bc2c20d88d1d40ea8e1a3e1b69720925550704 49112 gmrun_0.9.2-2_amd64.deb
 7d14c56b47ecdc48ea41edbda1b449865a6e4cbf 9540 gmrun_0.9.2-2.debian.tar.gz
 841c0d10468fc446a55520c90c438be732057412 47896 gmrun_0.9.2-2_i386.deb
 3571cec66a050fbcba40aacfe3cfbac3cdd8723c7f40ca33b997933d406f723c 9540 gmrun_0.9.2-2.debian.tar.gz
 3b82b0599f136e985cbdeaa949091a0a2747789712dd20e6a746f51668b2b338 49112 gmrun_0.9.2-2_amd64.deb
 dee5ee1bdb261d59b29aaa62f2b57cfda2ba3990f21e1753478c55aec3a2112c 47896 gmrun_0.9.2-2_i386.deb
 f00467c5686696c9d68c362fe54f76889a296a15f36b7aac319c4eec110a298a 1067 gmrun_0.9.2-2.dsc
 3d1907ab3f6464d755c65e136d32fd64 9540 x11 optional gmrun_0.9.2-2.debian.tar.gz
 75b42ffacd2cec15b97ad63d87c1e79e 49112 x11 optional gmrun_0.9.2-2_amd64.deb
 8f01436283b31e3d81cc74648c8978ba 47896 x11 optional gmrun_0.9.2-2_i386.deb
 8939d7f5d5b7bbfd29a523de365d2a7e 1067 x11 optional gmrun_0.9.2-2.dsc

Version: GnuPG v1.4.10 (GNU/Linux)


--- End Message ---

Reply to: