> Debian wants to be able to build from source, and be able to change the > source; if this cannot be done, then lxml has to be removed from Debian.
It can be done, lxml should generally work just fine with the latest release version of Cython. It's just that using a different version won't yield the same C sources, so even small source changes won't result in a local change in the binary. And releasing lxml with a specific Cython version won't solve the problem as Debian would want to build it with the Cython version it ships, as would Ubuntu, and Redhat, and ... > It's unfortunate that lxml relies on such unstable software. gcc generates different code depending on which version is used. Sometimes, using one gcc version can result in a crash, while other gcc versions work just fine. Does that make GCC unstable software? Updating GCC can lead to non-local changes in binaries, just like updating Cython does. I think the only difference is that GCC is a much slower moving target than Cython. -- [jaunty] lxml FTBFS on all platforms https://bugs.launchpad.net/bugs/308633 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
