On Fri, Mar 29, 2013 at 03:41:00PM +0100, John Paul Adrian Glaubitz wrote:
On 03/29/2013 03:38 PM, Christoph Egger wrote:
Because in unstable/wheezy python depends on python2.7 not python2.6. if
you depend on python you can assume /usr/bin/python but not either of
python2.6 and python2.7
control: notfound -1 2.28.6-10
I've done some testing. I've found wheezy not affected.
python-gebject-2-dev 2.28.6-10 has /usr/bin/python2.7 in
/usr/bin/pygobject-codegen-2.0, and thanks to Depends: python2.7 |
python2.6 in python-gobject-2, python2.7 will be installed
satisfiying that need.
On 03/29/2013 03:41 PM, John Paul Adrian Glaubitz wrote:
On 03/29/2013 03:38 PM, Christoph Egger wrote:
Because in unstable/wheezy python depends on python2.7 not python2.6. if
you depend on python you can assume /usr/bin/python but not either of
python2.6 and python2.7
Ah, you're right.
Source: python-gobject-dev
Version: 2.21.4+is.2.21.3-1
Severity: serious
usr/bin/pygobject-codegen-2.0
#!/bin/sh
prefix=/usr
datarootdir=${prefix}/share
datadir=${datarootdir}
codegendir=${datadir}/pygobject/2.0/codegen
PYTHONPATH=$codegendir
export PYTHONPATH
exec
explicitely executes python2.6 while the package only depends on
python (=2.5)
This causes the current gtk-vnc FTBFS
Interesting. When I search for the python meta-package, even on Squeeze
the package already pulls python2.6. How is it possible that it doesn't
get installed during gtk-vnc
John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de writes:
explicitely executes python2.6 while the package only depends on
python (=2.5)
This causes the current gtk-vnc FTBFS
Interesting. When I search for the python meta-package, even on
Squeeze the package already pulls python2.6.
On 03/29/2013 03:38 PM, Christoph Egger wrote:
Because in unstable/wheezy python depends on python2.7 not python2.6. if
you depend on python you can assume /usr/bin/python but not either of
python2.6 and python2.7
Ah, you're right. Thanks for the heads-up. I'll be there with a debdiff
showing
7 matches
Mail list logo