Re: new freedoom packages for stable and oldstable to fix copyvio

2009-06-24 Thread Luk Claes
Jon Dowland wrote: I have uploaded the new packages to a temporary repository at : oldstable: stable: Please let me know if

Re: new freedoom packages for stable and oldstable to fix copyvio

2009-06-20 Thread Jon Dowland
On Sat, Jun 20, 2009 at 09:53:02AM +0100, Jon Dowland wrote: > > oldstable: > > > > There seems to be some graphic corruption in this one that I > forgot about. The lenny package seems fine though. I've > removed this one until I fi

Re: new freedoom packages for stable and oldstable to fix copyvio

2009-06-20 Thread Jon Dowland
On Sat, Jun 20, 2009 at 12:49:39AM +0100, Jon Dowland wrote: > I have uploaded the new packages to a temporary repository > at : > > oldstable: > There seems to be some graphic corruption in this one

Re: new freedoom packages for stable and oldstable to fix copyvio

2009-06-19 Thread Jon Dowland
I have uploaded the new packages to a temporary repository at : oldstable: stable: Please let me know if they are OK for uplo

Re: new freedoom packages for stable and oldstable to fix copyvio

2009-06-19 Thread Jon Dowland
On Fri, Jun 19, 2009 at 06:56:50PM +0100, Jon Dowland wrote: > I am preparing packages suitable for oldstable and stable > now. I will reply with interdiffs once I have prepared them. Etch attached. Essentially the same as lenny. diff -u freedoom-0.5/debian/changelog freedoom-0.5+dfsg1/debian/chan

Re: new freedoom packages for stable and oldstable to fix copyvio

2009-06-19 Thread jon+debian-release
On Fri, Jun 19, 2009 at 06:56:50PM +0100, Jon Dowland wrote: > I am preparing packages suitable for oldstable and stable > now. I will reply with interdiffs once I have prepared them. Lenny interdiff attached. Note that as alluded to in the copyright hunk, the orig tarball is modified by removing

new freedoom packages for stable and oldstable to fix copyvio

2009-06-19 Thread Jon Dowland
Hello release team, Somebody has reported a copyright violation in the Freedoom package (#533135), unfortunately the violation dates back to the 0.5-1 version of freedoom which is in oldstable and stable's version is also affected. The fix is relatively simple, at least: merely deleting the affec