On Tuesday, July 24, 2012 06:52:13 AM James McCoy wrote:
> On Wed, Jul 18, 2012 at 09:35:28AM +0200, Jakub Wilk wrote:
> > Plan B
> > ==
> > In any order:
> > - Fix vim build not to link config.c into the binary. (I attached a
> > proposed patch.)
>
> I've uploaded Vim 2:7.3.547-4.
>
> > - Fi
On Wed, Jul 18, 2012 at 09:35:28AM +0200, Jakub Wilk wrote:
> Plan B
> ==
> In any order:
> - Fix vim build not to link config.c into the binary. (I attached a
> proposed patch.)
I've uploaded Vim 2:7.3.547-4.
> - Fix python2.7 symbols. Add Breaks for each provider of vim-python.
Please add
On Wed, Jul 18, 2012 at 11:41:31AM +0200, Julien Cristau wrote:
> On Wed, Jul 18, 2012 at 09:35:28 +0200, Jakub Wilk wrote:
> > Plan B
> > ==
> > In any order:
> > - Fix vim build not to link config.c into the binary. (I attached a
> > proposed patch.)
> > - Fix python2.7 symbols. Add Breaks fo
On Wed, Jul 18, 2012 at 09:35:28 +0200, Jakub Wilk wrote:
> I can see two ways to fix this mess:
>
> Plan A
> ==
> 1) Fix python2.7 symbols. Add Breaks for each provider of vim-python.
> 2) binNMU vim.
>
> Plan B
> ==
> In any order:
> - Fix vim build not to link config.c into the binary
* Julien Cristau , 2012-07-16, 15:07:
it's a plain bug in libpython2.7 AFAICT.
ACK, though it woudn't trigger if vim build system didn't do dubious
things...
I can see two ways to fix this mess:
Plan A
==
1) Fix python2.7 symbols. Add Breaks for each provider of vim-python.
2) binNMU vi
On Mon, Jul 16, 2012 at 11:28:57 +0200, Cyril Brulebois wrote:
> Hi James,
>
> James McCoy (15/07/2012):
> > So a simple binNMU won't help because it wouldn't have a tight enough
> > dependency and therefore could transition before python2.7, leaving a
> > broken Vim in Wheezy.
>
> you could ke
Hi James,
James McCoy (15/07/2012):
> So a simple binNMU won't help because it wouldn't have a tight enough
> dependency and therefore could transition before python2.7, leaving a
> broken Vim in Wheezy.
you could keep a serious bug open until python2.7 migrates, to solve the
issue you're mentio
Adding debian-release to get their take.
On Sun, Jul 15, 2012 at 11:51:20PM +0200, Jakub Wilk wrote:
> * Jakub Wilk , 2012-07-15, 15:07:
> >>this is most likely caused by building _hashlib as an extension,
> >>not a builtin anymore, to address #680930. rebuilding vim should
> >>fix it.
> >Indeed,
* Jakub Wilk , 2012-07-15, 15:07:
this is most likely caused by building _hashlib as an extension,
not a builtin anymore, to address #680930. rebuilding vim should
fix it.
Indeed, rebuild fixed the problem for me.
However, in comparison to version in testing (2.7.3~rc2-2.1),
libpython2.7 not
* Matthias Klose , 2012-07-14, 20:38:
Trying to import hashlib crashes the Python interpreter that vim
embeds:
$ vim -c 'python import hashlib'
vim: symbol lookup error: vim: undefined symbol: init_hashlib
This didn't happen with python2.7/2.7.3-1… However, I cannot reproduce
it without vim
On 14.07.2012 18:37, Jakub Wilk wrote:
> Package: vim-nox,libpython2.7
> Version: vim-nox/2:7.3.547-3
> Version: libpython2.7/2.7.3-2
> Severity: important
> Usertags: serious
>
> Trying to import hashlib crashes the Python interpreter that vim embeds:
>
> $ vim -c 'python import hashlib'
> vim:
Package: vim-nox,libpython2.7
Version: vim-nox/2:7.3.547-3
Version: libpython2.7/2.7.3-2
Severity: important
Usertags: serious
Trying to import hashlib crashes the Python interpreter that vim embeds:
$ vim -c 'python import hashlib'
vim: symbol lookup error: vim: undefined symbol: init_hashlib
12 matches
Mail list logo
