Bug#327967: marked as done (gpgkeys: uninstallable; needs rebuild for the Qt/KDE transition)
Your message dated Mon, 12 Jun 2006 16:17:10 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#327967: fixed in kwavecontrol 0.4.2-1 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: gpgkeys Version: 0.3.1-3 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. ---End Message--- ---BeginMessage--- Source: kwavecontrol Source-Version: 0.4.2-1 We believe that the bug you reported is fixed in the latest version of kwavecontrol, which is due to be installed in the Debian FTP archive: kwavecontrol_0.4.2-1.diff.gz to pool/main/k/kwavecontrol/kwavecontrol_0.4.2-1.diff.gz kwavecontrol_0.4.2-1.dsc to pool/main/k/kwavecontrol/kwavecontrol_0.4.2-1.dsc kwavecontrol_0.4.2-1_i386.deb to pool/main/k/kwavecontrol/kwavecontrol_0.4.2-1_i386.deb kwavecontrol_0.4.2.orig.tar.gz to pool/main/k/kwavecontrol/kwavecontrol_0.4.2.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Morten Hustveit [EMAIL PROTECTED] (supplier of updated kwavecontrol 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 [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 12 Jun 2006 23:33:20 +0200 Source: kwavecontrol Binary: kwavecontrol Architecture: source i386 Version: 0.4.2-1 Distribution: unstable Urgency: low Maintainer: Morten Hustveit [EMAIL PROTECTED] Changed-By: Morten Hustveit [EMAIL PROTECTED] Description: kwavecontrol - Wireless device monitoring application for KDE Closes: 217710 224932 327967 355839 Changes: kwavecontrol (0.4.2-1) unstable; urgency=low . * New upstream release (Closes: #217710, #224932). * Removed debmake build-dependency (Closes: #327967). * Updated config.guess and config.sub (Closes: #355839). Files: c1df8e20c524ff9fcb0f9091833a6aea 616 net optional kwavecontrol_0.4.2-1.dsc de1cf7afb282dfc6c21d56ce7139c2eb 589909 net optional kwavecontrol_0.4.2.orig.tar.gz 2027984ad9ff4a3565272518cf47dc7d 187593 net optional kwavecontrol_0.4.2-1.diff.gz cce6d398f9cae8dd67ce39802009e619 121316 net optional kwavecontrol_0.4.2-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEjfCv4996V3ZlqLcRAmYwAJ9eaA02TOIFpdS+77LGz9lv3USYkwCdGH/L ystQ5DYCy6SmIWOe0VhwO0A= =YCFh -END PGP SIGNATURE- ---End Message---
Bug#327967: marked as done (gpgkeys: uninstallable; needs rebuild for the Qt/KDE transition)
Your message dated Tue, 27 Sep 2005 03:02:05 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#327967: fixed in gpgkeys 0.3.1-4 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 12 Sep 2005 23:48:17 + From [EMAIL PROTECTED] Mon Sep 12 16:48:17 2005 Return-path: [EMAIL PROTECTED] Received: from 84-120-66-144.onocable.ono.com (chistera.yi.org) [84.120.66.144] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1EEy25-0003R0-00; Mon, 12 Sep 2005 16:48:17 -0700 Received: from userid 1000 by chistera.yi.org with local (Exim 4.52) id 1EEy1a-0002Ri-1a for [EMAIL PROTECTED]; Tue, 13 Sep 2005 01:47:46 +0200 From: Adeodato =?utf-8?B?U2ltw7M=?= [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: gpgkeys: uninstallable; needs rebuild for the Qt/KDE transition Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit Message-Id: [EMAIL PROTECTED] Date: Tue, 13 Sep 2005 01:47:46 +0200 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-6.8 required=4.0 tests=BAYES_00,FROM_ENDS_IN_NUMS, HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 Package: gpgkeys Version: 0.3.1-3 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. --- Received: (at 327967-close) by bugs.debian.org; 27 Sep 2005 10:08:05 + From [EMAIL PROTECTED] Tue Sep 27 03:08:05 2005 Return-path: [EMAIL PROTECTED] Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian)) id 1EKCHl-0007h2-00; Tue, 27 Sep 2005 03:02:05 -0700 From: Peter Mathiasson [EMAIL PROTECTED] To: [EMAIL PROTECTED] X-Katie: $Revision: 1.56 $ Subject: Bug#327967: fixed in gpgkeys 0.3.1-4 Message-Id: [EMAIL PROTECTED] Sender: Archive Administrator [EMAIL PROTECTED] Date: Tue, 27 Sep 2005 03:02:05 -0700 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 Source: gpgkeys Source-Version: 0.3.1-4 We believe that the bug you reported is fixed in the latest version of gpgkeys, which is due to be installed in the Debian FTP archive: gpgkeys_0.3.1-4.diff.gz to pool/main/g/gpgkeys/gpgkeys_0.3.1-4.diff.gz gpgkeys_0.3.1-4.dsc to pool/main/g/gpgkeys/gpgkeys_0.3.1-4.dsc gpgkeys_0.3.1-4_i386.deb to
