-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ola Lundqvist wrote: | this is also a problem in other horde packages (but it's not horde which | ~ is to blame for this, it's php). There are similar report's on the | |> Ok. Is this a bug that will be fixed in php or should I do that. |> Thanks for the information by the way.
I think the php guy's call this 'feature'. Something breaks backward compatibilty in php 4.4 and I don't think this will be fixed. | horde BTS [1] and on horde's lists. The horde developer are quite fast | in fixing this problems, but not in horde2 / imp3 because they are to | old and horde3 / imp4 are released. | | |> Yes I know. I have been thinking of removing support for horde2/imp3 |> as it is not supported upstream. I have got some requests to still maintain |> it so I'll do that for some time at least. If it complies with the Debian Policy, the packages could be removed from etch and sid and just the sarge version remain. So the packages could be maintained until etch is released. People with etch / sid could use horde3 / imp4... by, Martin - -- Powered by Debian GNU / Linux -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDAMEqOvJj+wS6JuIRAtjgAKCn5lopgPZIRz5PENXjcsau8CUb/QCfZlBI 5bGsPKGFJEMsVBKj7zH6fu8= =KUH0 -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
