Hi, Rene Engelhard wrote: > But openoffice.org will still be coupled to the suitesparse transition as the > OOo package in testing depends on the old one and the new hunspell would > break it unless the new OOo also goes in (and OOo itself is besides > suitesparse also blocked by gcc-defaults/gcc-4.3/gnat-4.2/gnat-4.3/binutils) > > Opinions?
Now that suitesparse was forced in, can I do this now (hunspell 1.2.2 was released today incidentially). Note that xulrunner and OOo also will need bin-NMUs for the python transition. Regards, Rene -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
