Bug#586930: [Jppy-devel] Bug#586930: Bug#586930: python2.6 linkage

2010-08-04 Thread Norbert Preining
On Mi, 04 Aug 2010, Jakub Wilk wrote: > * Norbert Preining , 2010-08-05, 00:27: >> Hi Jakub, Sorry, I mixed the names, I meant Maximiliano ... >> On So, 01 Aug 2010, Jakub Wilk wrote: >>> I went this way. The attached patch simply reorders PYVERS, so that >>> the default version is used as the

Bug#586930: [Jppy-devel] Bug#586930: python2.6 linkage

2010-08-04 Thread Jakub Wilk
* Norbert Preining , 2010-08-05, 00:27: Hi Jakub, On So, 01 Aug 2010, Jakub Wilk wrote: I went this way. The attached patch simply reorders PYVERS, so that the default version is used as the last one. Thanks for the NMU, but could you please keep the tradition (or should I say requirement) to

Bug#586930: [Jppy-devel] Bug#586930: python2.6 linkage

2010-08-04 Thread Norbert Preining
Hi Jakub, On So, 01 Aug 2010, Jakub Wilk wrote: > I went this way. The attached patch simply reorders PYVERS, so that the > default version is used as the last one. Thanks for the NMU, but could you please keep the tradition (or should I say requirement) to send a debdiff before doing this kind

Bug#586930: python2.6 linkage

2010-08-01 Thread Jakub Wilk
* Maximiliano Curia , 2010-07-31, 20:08: The problem is that the packages compiles twice, once for every supported python version. But things like plugins have a static destination (not dependant of the python version), so its overwritten. This is not bad per se, as long it's not the default ve

Bug#586930: python2.6 linkage

2010-08-01 Thread Jakub Wilk
* Maximiliano Curia , 2010-07-31, 20:08: The problem is that the packages compiles twice, once for every supported python version. But things like plugins have a static destination (not dependant of the python version), so its overwritten. This is not bad per se, as long it's not the default ver

Bug#586930: python2.6 linkage

2010-07-31 Thread Maximiliano Curia
Hola Jakub Wilk! El 01/08/2010 a las 00:43 escribiste: > * Maximiliano Curia , 2010-07-31, 19:17: >> The problem is that the packages compiles twice, once for every >> supported python version. But things like plugins have a static >> destination (not dependant of the python version), so its o

Bug#586930: python2.6 linkage

2010-07-31 Thread Jakub Wilk
* Maximiliano Curia , 2010-07-31, 19:17: The problem is that the packages compiles twice, once for every supported python version. But things like plugins have a static destination (not dependant of the python version), so its overwritten. This is not bad per se, as long it's not the default v

Bug#586930: python2.6 linkage

2010-07-31 Thread Maximiliano Curia
Hi, The problem is that the packages compiles twice, once for every supported python version. But things like plugins have a static destination (not dependant of the python version), so its overwritten. The simplest solution would be to support only one python version at any given time. Other opt