That's good news. How does one trigger a recompilation without a new source package, anyway?
-brad > -----Original Message----- > From: Goswin Brederlow > [mailto:[EMAIL PROTECTED] > Sent: Monday, May 05, 2003 7:47 PM > To: [email protected] > Cc: Romain Lerallut; Roland Rosenfeld; Tomas Guemes; Dpkg Development; > Bradley Bell; Alastair McKinstry > Subject: recent sgml problems (solved) > > > Hi, > > lately jade has been acting up on m68k and I suspect a bug in g++-3.2 > to miscompile it. For the time being i reverted jade back to > gcc-2.95/g++-2.95 for m68k. jade-1.2.1-29.3 is uploaded and should be > available soon. > > I looked through the list of sources depending on jade or > sgmltools-lite and checked for build failures. Here is the list of > packages that probably failed due to a broken jade: > > Package: privoxy Maintainer: Roland Rosenfeld <[EMAIL PROTECTED]> > Package: terraform Maintainer: Tomas Guemes <[EMAIL PROTECTED]> > Package: dpkg Maintainer: Dpkg Development > <[email protected]> > Package: gtkmm Maintainer: Bradley Bell <[EMAIL PROTECTED]> > Package: newt Maintainer: Alastair McKinstry > <[EMAIL PROTECTED]> > > Once jade is build for m68k these packages should be rebuild. > > MfG > Goswin > > PS: I tested with newt and that now builds. >
