On Sun, Jul 17, 2005 at 02:12:26PM +0200, Vincent Lefevre <[EMAIL PROTECTED]> wrote: > On 2005-07-17 12:09:46 +0200, Mike Hommey wrote: > > If i got it correctly, this bug got introduced because of the changes to > > the security model for XUL applications... so, for once, we can't really > > blame the "it should have been a bug-fix release only", since it is what > > it was, except that security fixes has side effects. > > The Debian changelog just says: > > * New upstream release, fixes security issues. (Closes: #318061) > * debian/rules: Disable freetype in the build for the time being. This > *might* break printing in some cases. > * gfx/idl/nsIFreeType2.idl, gfx/src/freetype/nsFreeType.cpp, > gfx/src/freetype/nsFreeType.h, gfx/src/ps/nsFontMetricsPS.cpp, > gfx/src/ps/nsFontMetricsPS.h, gfx/src/x11shared/nsFontFreeType.cpp, > gfx/src/x11shared/nsFontFreeType.h, > layout/svg/renderer/src/libart/nsSVGLibartGlyphMetricsFT.cpp: Patch > from bz#234035 to try to get building with the new freetype. (Closes: > #314243) > > I can see nothing there that this can break extensions. > > And if due to the change of the security model for XUL applications, > it is known to break some extensions, I really think that the conflict > should be marked in the packages (in mozilla-firefox, since this is > where the change happens). Hence the bug. > > In a similar way, if a library changes its ABI, one doesn't expect the > packages that use it to silently break just because of the upgrade.
You don't expect the package to have conflicts with all current packages depending on it either. And it doesn't affect all extensions. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
