[Bug 275688] Re: Please sync fpc 2.2.2-4 (universe) from Debian unstable (main)
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
[Bug 275688] Re: Please sync fpc 2.2.2-4 (universe) from Debian unstable (main)
** Bug watch added: Debian Bug tracker #506977 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506977 ** Also affects: fpc (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506977 Importance: Unknown Status: Unknown -- 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
[Bug 275688] Re: Please sync fpc 2.2.2-4 (universe) from Debian unstable (main)
Subscribed gNS group, as it also affects us. -- 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
[Bug 275688] Re: Please sync fpc 2.2.2-4 (universe) from Debian unstable (main)
Sorry, It being The copyright issue pre 2.2.2 -- 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
[Bug 275688] Re: Please sync fpc 2.2.2-4 (universe) from Debian unstable (main)
So far I have tested building 2.2.2-4ubuntu1 on gutsy, intrepid and hardy. Gutsy fails because of Processing fpcsrc/utils/Makefile.fpc Error: Target linux, package fcl-base not found Googling for that error it looks like that is due to a different location of the fpc source [0] Hardy and Intrepid build fine. See [1], including the logs. I did not even start building on Dapper because the build depends are not fulfilled (fp-compiler, fp-units-base and fp-utils) I am wondering thou, is this the way to go? Really trying to extract the relevant parts from the 2.2.2 version to patch the earlier releases is a bridge to far for me (with my current programming skills). Should the Dapper and Gutsy version just be changed to reflect the change in licensing? How would we achieve this anyway? I guess than gearhead and python-soappy also need relicensing (how does that work? I that feasible?) Although I am still willing to help, I could do with some more directions. I am pretty new to packaging (~3 packages) and am not really into programming. Rebuilding all the build depends in the different releases, right? And just to be sure that I understand the situation: All programs build with the old version of fpc can *only* be licensed under GPL (which version by the way?) All programs build with the 2.2.2 version of fpc can be licensed under GPL or LGPL. [0] http://www.mail-archive.com/[EMAIL PROTECTED]/msg08706.html [1] https://launchpad.net/~paul-climbing/+archive -- 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
[Bug 275688] Re: Please sync fpc 2.2.2-4 (universe) from Debian unstable (main)
(Afaik that bug is not fixed in 2.2.2, which is from Aug 11th, and this fix is from Aug 20th ) -- 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
[Bug 275688] Re: Please sync fpc 2.2.2-4 (universe) from Debian unstable (main)
I am looking into how to get sbuild to work... (of course it doesn't want to do what I want straight away), but in the mean time I like to note for this bug that with only the sync with debian bug #260464 appears to be back, as can be seen in the build log of lazarus [1]. When I look at the upstream bugreport [2], it looks like this bug is fixed upstream from fpc 2.3.1 Once I get sbuild to run I will give an additional debdiff on this problem but the debdiff attached to this bug *should* work (apart from the changelog). I will report back. Is there any way of marking in Launchpad that this bug is the reason why lazarus does not build in jaunty? [1] http://launchpadlibrarian.net/19834865/buildlog_ubuntu-jaunty-i386.lazarus_0.9.26-2_FAILEDTOBUILD.txt.gz [2] http://mantis.freepascal.org/view.php?id=11837 -- 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
[Bug 275688] Re: Please sync fpc 2.2.2-4 (universe) from Debian unstable (main)
I have build fpc in jaunty with the attached changes. Lazarus build fine in jaunty after that. I can also upload the .diff.gz, but that is quiet crowded with touched Makefiles. Just tell me if they are needed. ** Attachment added: Changes from 2.2.2-4 to 2.2.2-4ubuntu1 http://launchpadlibrarian.net/19872245/debian.ubuntu.diff -- 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
[Bug 275688] Re: Please sync fpc 2.2.2-4 (universe) from Debian unstable (main)
ACK of the sync request. Thanks, James -- 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
[Bug 275688] Re: Please sync fpc 2.2.2-4 (universe) from Debian unstable (main)
Note that if there are local mods, don't forget to send them upstream to FPC. The freeze for 2.2.4 starts mid december -- 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
[Bug 275688] Re: Please sync fpc 2.2.2-4 (universe) from Debian unstable (main)
Hi Paul, The documentation on SRUs is at http://wiki.ubuntu.com/StableReleaseUpdates which should get you started. Thanks, James -- 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
