Bug#506977: Bug #506977 FPC: copyright infringement in pre 2.2.2 sources
On Wed, Nov 26, 2008 at 10:56:07PM +0100, Torsten Werner wrote: my suggestion is to remove fpc from oldstable and stable but unblock the unstable version 2.2.2-4 for lenny and trigger binNMUs for lazarus. What do you think? What is the correct way to remove packages from (old)stable? Should I file a bug report against ftp.debian.org or is it done by the SRM? That's SRM stuff, so you need to file the bug against release.debian.org instead of ftp.debian.org. Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#506977: Bug #506977 FPC: copyright infringement in pre 2.2.2 sources
reassign 506977 release.debian.org thanks On Thursday 27 November 2008 12:05, Frank Lichtenheld wrote: What is the correct way to remove packages from (old)stable? Should I file a bug report against ftp.debian.org or is it done by the SRM? That's SRM stuff, so you need to file the bug against release.debian.org instead of ftp.debian.org. From: Paul Gevers [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] In Ubuntu I checked that the following packages builddepend on FPC: lazarus imapcopy hedgewars libhdate gearhead m-tx python-soappy poker-network I assume, but have not check yet, that the same goes for Debian. Looks like quite a lot of packages seem to have go. The removal request looks reasonable to me :( regards, Holger pgpuz2aiHJ6KH.pgp Description: PGP signature
Bug#506977: Bug #506977 FPC: copyright infringement in pre 2.2.2 sources
In Ubuntu I checked that the following packages builddepend on FPC: lazarus imapcopy hedgewars libhdate gearhead m-tx python-soappy poker-network I assume, but have not check yet, that the same goes for Debian. Looks like quite a lot of packages seem to have go. The removal request looks reasonable to me :( Yesterday I found out that python-soappy and poker-network do NOT build depend on fpc. That was a mistake because reverse-build-depends fpc gives more output than only fpc (i.e. it reverse build depend on python-fpconst) Paul signature.asc Description: OpenPGP digital signature
Bug#506977: Bug #506977 FPC: copyright infringement in pre 2.2.2 sources
Hi, my suggestion is to remove fpc from oldstable and stable but unblock the unstable version 2.2.2-4 for lenny and trigger binNMUs for lazarus. What do you think? What is the correct way to remove packages from (old)stable? Should I file a bug report against ftp.debian.org or is it done by the SRM? Cheers, Torsten On Wed, Nov 26, 2008 at 8:51 PM, Marco van de Voort [EMAIL PROTECTED] wrote: Hello, Note: I'm the FPC core developer that also features in the Ubuntu correspondance. Carlos (the maintainer of this port) can confirm that, or have a look here: http://www.freepascal.org/aboutus.var The probable infringement was brought to our attention in early 2007. The infringement was made amenable mostly due to trivial means (variable names, fairly small procedures that were the same). The other side was really cooperative, and gave us time to clean up massively, without having to immediately pull all sources, and we employed at tool to identify potential problem sources, and found a lot more. So we cut real wide, and reengineered all potentially infringing code. (all in all a nontrivial amount). However because the infringement was so trivial, and relicensing counterproductive and confusion, it was decided to pull all releases. So in august, after 2.2.2 came out, we removed all older releases from our site, and assumed the mentioning of the copyright problems in our release manifest would be enough to warrant a swift upgrade. I hope it need no explanation that that was a pretty painful step, removing 10 years of history of our project. However, here we are now, 3-4 months after the release and the heads up, and the infringing code is still served from Debian servers. We are not happy with this. Note that it is also not fair to the other party who has been patient, and now could see the code still floating around. In short: please remove the old versions as soon as possible, or upgrade. Marco. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
