Did you fail to read any of the other bugs that are caused by the C++ ABI transition (#324874, #327017, #327365 or even #327826) and think this might better fit with one of them? All of them mention the fact that fwbuilder is broken because of the C++ ABI transition. Why did this require yet another bug report?

Adeodato Simó wrote:

Package: fwbuilder
Version: 2.0.7-1
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/msg00000.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.



Reply via email to