Well, In my opinion anything base on the older versions is not supported by FPC, and we prefer you remove them from Ubuntu versions that are not worth fixing, rather than relicense them. We didn't remove all older releases from our own site lightly, and the risk on confusion is too big.
Also because it would not be fair to the other party in the copyright dispute to have these versions longer in circulation in any form, the reengineering of the disputed code took quite long, and the FPC release that fixes it is also already over 4 months old. Moreover the relicensing option also was not properly verified or communicated with them, and just something proposed on the maillist, so you would do this on your own peril, and Ubuntu, and Ubuntu alone would be responsible for the consequences since FPC removed all disputed sources from its servers, and no longer distributes them. In summary, I don't think relicensing is a serious option, it is simply too sensitive legally, and the GPL option never should have mentioned, since not verified by legal council or with the other party. With respect to the building problems, could it be that the build system is poluted with an older install ? A FPC build should be always the same, so the logical conclusion is that there is something different on the buildmachines. (IOW a different version installed to bootstrap, one a full version, one only the cmdline compiler) -- Please sync fpc 2.2.2-4 (universe) from Debian unstable (main) https://bugs.launchpad.net/bugs/275688 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
