Re: Removing w32 specific Python code from a package

2009-02-27 Thread Adeodato Simó
* Stephan Peijnik [Fri, 27 Feb 2009 10:07:40 +0100]: > On Thu, 2009-02-26 at 16:27 +0100, Adeodato Simó wrote: > > * Stephan Peijnik [Thu, 26 Feb 2009 15:46:58 +0100]: > > > Now as python-pyglet needs to be repacked because it is not entirely > > > free anyways I thought I could get rid of this p

Re: Removing w32 specific Python code from a package

2009-02-27 Thread Stephan Peijnik
On Thu, 2009-02-26 at 16:27 +0100, Adeodato Simó wrote: > * Stephan Peijnik [Thu, 26 Feb 2009 15:46:58 +0100]: > > > Now as python-pyglet needs to be repacked because it is not entirely > > free anyways I thought I could get rid of this problem by simply > > removing the w32-specifics when repacka

Re: Removing w32 specific Python code from a package

2009-02-26 Thread Adeodato Simó
* Stephan Peijnik [Thu, 26 Feb 2009 15:46:58 +0100]: > Now as python-pyglet needs to be repacked because it is not entirely > free anyways I thought I could get rid of this problem by simply > removing the w32-specifics when repackaging the dfsg version of the > tarball. What about just not insta

Removing w32 specific Python code from a package

2009-02-26 Thread Stephan Peijnik
Hello debian-python and DPMT, I have just noticed that a bug against one of the packages I help maintaining was reported [0] over at Launchpad that is caused by w32-specific code shipping with my package (python-pyglet). Now as python-pyglet needs to be repacked because it is not entirely free an