Bug#635474: Bug#635476: duplicated library code

2013-05-22 Thread Dmitry Shachnev
On Wed, May 22, 2013 at 5:53 AM, Ben Finney ben+deb...@benfinney.id.au wrote: On 21-May-2013, Barry Warsaw wrote: On May 21, 2013, at 01:30 PM, Ben Finney wrote: Barry Warsaw wrote: Can't we get coverage 3.6 into Debian, with enabled Python 3 support now? If you can see a way to do it

Bug#635476: duplicated library code

2013-05-22 Thread Barry Warsaw
On May 22, 2013, at 03:21 PM, Dmitry Shachnev wrote: I can try to package the first one (hotkeys), but probably I won't have time for it until next week. That would be great. I personally have no interest or time to package JavaScript stuff, and I definitely don't want to be a maintainer for

Bug#635476: duplicated library code

2013-05-21 Thread Barry Warsaw
On May 21, 2013, at 01:30 PM, Ben Finney wrote: I'm confused though because if those block bug packages aren't packaged for Debian yet (they're wnpp), then how can they be duplicated library code? Duplicated in other packages. (e.g. ‘jquery.hotkeys.js’ is in Debian's ‘wordpress’, ‘spotweb’,

Bug#635476: duplicated library code

2013-05-21 Thread Ben Finney
On 21-May-2013, Barry Warsaw wrote: On May 21, 2013, at 01:30 PM, Ben Finney wrote: Barry Warsaw wrote: Can't we get coverage 3.6 into Debian, with enabled Python 3 support now? If you can see a way to do it without adding those libraries in the package, sure. I think it would not be

Bug#635476: duplicated library code

2013-05-20 Thread Ben Finney
On 20-May-2013, Barry Warsaw wrote: Hi Ben […] Upstream version 3.5 introduces yet more duplicated library code that is currently not packaged properly for Debian, so upstream version 3.5 cannot be packaged yet. I'm confused though because if those block bug packages aren't packaged