Even in Jaunty fpc is not synced to the current version in Debian. Does
anybody know why not? I thought that Jaunty would be synced with Debian
unstable, or is that not done with packages that have a Ubuntu packaged
version? If the latter is the case, could we just request a sync from
debian for
Hi,
fpc hasn't been synced yet as there are Ubuntu modifications to
the current package. The person that did those modifications stated
that it is safe to sync the package as Debian has a fixed version, so we
can go ahead and sync.
For an SRU it needs someone to investigate the status on each
Note that then the 2.2.0 package should be modified to reflect the
changed copyright situation of 2.2.0, e.g. add a prominent notice that
it can only be used to make GPL apps, contrary to what the docs say, or
wholly retracted the package for a release cycle.
This is the reason why FPC Core has
Something must happen either way for intrepid. Either change 2.2.0
package to reflect the license change as a result of potential
infringement, or use the 3 month old 2.2.2 fixes release.
In retrospect, maybe we should have given more of a heads-up after 2.2.2
release, but we thought POTENTIAL
Yes, this needs to be fixed in intrepid. However, it also needs to be
fixed in Dapper, Gutsy, and Hardy. It should be fixed by sync/merge for
Jaunty. The fix for older releases requires a fair bit of investigation
against rdepends to determine how many packages need adjustment, and
what sort of
Well I expected so much. Which is why I suggested the option of the
prominent notice.
(and IMHO that still means that 2.2.2 should come ASAP, removing the
entire 13 year old release history of our own FTP sites was not a step
we took lightly, and it is then most annoying to see the package still
First, FPC is perfectly usable by itself and comes with an IDE.
Second Lazarus is an advanced IDE to generate programs. While Lazarus
itself is GPL, the programs that it generates are not subject to the
GPL, but to LGPL with modifications, as the normal FPC license. So there
people could surely
Won't Fixing for Intrepid. Should be looked at for Jaunty. If
warranted, you might consider asking for a backport after it's in
Jaunty.
** Changed in: fpc (Ubuntu Intrepid)
Status: Incomplete = Won't Fix
--
Please sync fpc 2.2.2-3 (universe) with patch from bug #260464
Looking at upstream changes, there are several core adjustments which
would require additional investigations and probably newer upstream
versions for it rdepends. Unless you can provide a solid plan to
successfully transition interested packages in time for the release
(a.k.a VERY soon!), I'd
hm... there are a number of packages that need fpc (via fp-compiler) as
build-dependency, like libhdate, imapcopy, hedgewars, gearhead.
I don't think it's a good idea to make intrusive changes to the
toolchain that late in the cycle, so -1 from me.
--
Please sync fpc 2.2.2-3 (universe) with
I meanwhile verified, and Lazarus 0.9.26 will need fpc 2.2.2
--
Please sync fpc 2.2.2-3 (universe) with patch from bug #260464
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
Hi,
I can't find a changelog in the package, however I can see the changes are
pretty big. This doesn't qualify for an autmatic feature freeze exception in
my opinion. I'm preparing the information to request one. It would be good
to know what testing you have done.
I found the following
** Attachment added: fpc.diffstat
http://launchpadlibrarian.net/18398099/fpc.diffstat
--
Please sync fpc 2.2.2-3 (universe) with patch from bug #260464
https://bugs.launchpad.net/bugs/275688
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: fpc.build
http://launchpadlibrarian.net/18399406/fpc.build
--
Please sync fpc 2.2.2-3 (universe) with patch from bug #260464
https://bugs.launchpad.net/bugs/275688
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can't find a changelog in the package, however I can see the changes are
pretty big.
I'm afraid that indeed the changes are pretty big and that because
upstream and debian maintenance are intermixed, the debian package does
not excel in clean packaging. And unfortunately I did not find a
On Fri, 2008-10-10 at 15:14 +, Paul Gevers wrote:
I can't find a changelog in the package, however I can see the changes are
pretty big.
I'm afraid that indeed the changes are pretty big and that because
upstream and debian maintenance are intermixed, the debian package does
not excel
I have provided the information that is usually required. If anyone
on the release team needs any more they will ask, and it would be
great if you could find it for them.
Thanks.
Any testing you can do with the updated package would be great. The
perfect test would be rebuilding everything
On Fri, 2008-10-10 at 15:46 +, Paul Gevers wrote:
Last time I looked (several weeks ago) the only package I could find
that depends on fpc is lazarus. The next (hopefully) package that
depends on fpc will be winff. So unfortunately, I can not do much
testing there.
No, that's a good thing
Possible CodeGear Copyright infringements in the source were reworked
using cleanroom approach.
So I am not sure if this qualifies for a feature freeze exception.
(I assume this is about 2.2.0 or earlier -2.2.2 versions, and not within
patchlevels of 2.2.2)
The above problems make the only
Hi,
bug #260464 is fixed, and the changelog entry says that the package is
safe to sync as Debian has the fixed version, is this not correct? Why?
Please file a separate bug for lazarus. If they need to go in together
then please state that in the bugs.
Also, fpc is a new upstream version, so
According to the debian/changelog upstream fixed some things and reworked some
problematic elements:
* new upstream release
- shlobj changes
- fix for wince library support
- fix for windows 64 bit support for 2GB memory
- Documentation was updated completely to conform to the
** Summary changed:
- Please sync fpc 2.2.2-3 (universe) with patch from bug #260464 and lazarus
0.9.24-0-12 (universe) from Debian unstable (main)
+ Please sync fpc 2.2.2-3 (universe) with patch from bug #260464
--
Please sync fpc 2.2.2-3 (universe) with patch from bug #260464
** Attachment added: The diff.gz for my build of fpc.
http://launchpadlibrarian.net/18025513/fpc_2.2.2-3ubuntu1.diff.gz
--
Please sync fpc 2.2.2-3 (universe) with patch from bug #260464 and lazarus
0.9.24-0-12 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/275688
** Tags added: update
--
Please sync fpc 2.2.2-3 (universe) with patch from bug #260464 and lazarus
0.9.24-0-12 (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
** Attachment added: Or maybe better, a debdiff versus the Debian package
http://launchpadlibrarian.net/18025718/fpc_2.2.2-3ubuntu1_debdiff
** Tags added: patch
** Description changed:
Binary package hint: fpc
I am trying to package WinFF (bug #172804) but it fails to build on
25 matches
Mail list logo
